- Joined
- May 16, 2016
- Messages
- 730
Ohhhh. That's really something significant.Most buffs/debuffs can simultaneously apply to the same unit if their ID’s are different
Ohhhh. That's really something significant.Most buffs/debuffs can simultaneously apply to the same unit if their ID’s are different
All the ones which I've tested (ie. SetEventDamage). Even the new ones added the other day like PlaySpecialEffect. The GUI actions also convert to the Blz-less natives. The compile error message is something like "invalid item name" with the Blz- but compiles and plays perfectly without it.
//Generated allocator of Foo
function s__Foo__allocate takes nothing returns integer
local integer this=si__Foo_F0
if (this!=0) then
set si__Foo_F=si__Foo_V[this]
else
set si__Foo_I=si__Foo_I+1
set this=si__Foo_I
endif
if (this>8190) then
return 0
endif
set si__Foo_V[this]=-1
return this
endfunction
Nice update!
I know this can easily solved by using extends array, maybe increase the struct instances to 32676?
vJASS://Generated allocator of Foo function s__Foo__allocate takes nothing returns integer local integer this=si__Foo_F0 if (this!=0) then set si__Foo_F=si__Foo_V[this] else set si__Foo_I=si__Foo_I+1 set this=si__Foo_I endif if (this>8190) then return 0 endif set si__Foo_V[this]=-1 return this endfunction
Making a thread in Patch Discussion should be enough.Is there a proper bug report thread/post where I can post this?
This is something I've looked into. In the JassHelper source there's a constant for the array limit and I could recompile a version with the value changed. However, I'm unsure if changing this value has other side effects, so I wanted to look into it more before changing it.Nice update!
I know this can easily solved by using extends array, maybe increase the struct instances to 32676?
vJASS://Generated allocator of Foo function s__Foo__allocate takes nothing returns integer local integer this=si__Foo_F0 if (this!=0) then set si__Foo_F=si__Foo_V[this] else set si__Foo_I=si__Foo_I+1 set this=si__Foo_I endif if (this>8190) then return 0 endif set si__Foo_V[this]=-1 return this endfunction
Wait, what? There was another way of doing that? I thought that was where custom MPQs came in...You could use .mix files as file containers for your resources you used in a map without directly importing them into the map itself.
Way to show respect.A Void said:Why do they do this? Why destroy something good and useful? Who was in charge of this moronic idea?
Wait, what? There was another way of doing that? I thought that was where custom MPQs came in...
This is something I've looked into. In the JassHelper source there's a constant for the array limit and I could recompile a version with the value changed. However, I'm unsure if changing this value has other side effects, so I wanted to look into it more before changing it.
private thistype allocator
private boolean isAlloc
method deallocate()
if (not this.isAlloc) or (this.allocator != 0)
...
return
this.allocator = thistype(0).allocator
thistype(0).allocator = this
static method allocate() -> thistype
var this = thistype(0).allocator
if (this.allocator == 0)
thistype(0).allocator = integer(this) + 1
this.isAlloc = true
else
thistype(0).allocator = this.allocator
this.allocator = 0
return this
Dll injection software exists...Is it true that they removed .mix file support with Miles removal? That is so messed up if true. .MIX files were loaded as custom .dll's into Warcraft 3 automatically, thus they allowed various nifty hacks and mods to work.
You could use .mix files as file containers for your resources you used in a map without directly importing them into the map itself.
Why do they do this? Why destroy something good and useful? [...]
@WeirdEditor: PTR versions are *Public Test* versions. Therefore, expect issues with them.[...] How does every recent patch break campaign again and again?
Dll injection software exists...
Out of curiosity and interest, does anybody know which version of FMOD the PTR uses?
FMODEx, 4th version of FMOD
[...] Plus fmod is modern and well-maintained [...]
One is not 16 years old? [...]
As this API is modern this may have other advantages. I suggest people test out what sound formats Warcraft III supports play back of. It might have fixed the mp3 playback difficulties. It may also have added support for new audio formats. [...]
".\Warcraft III.exe" -loadfile Maps\Scenario\(4)WarChasers.w3m
".\Warcraft III.exe" -loadmod Mods\ReterasMod.mpq
It seems it is still pretty current with FMOD 5 being quite new with low adoption rate. One must remember that FMOD is licenced software within the scope Blizzard is using it and hence moving from 4 to 5 might not be free.Isn't FMOD 4 (a.k.a. FMOD Ex) a legacy product by now?
FMOD Studio seems to be their flagship product.It seems it is still pretty current with FMOD 5 being quite new with low adoption rate. One must remember that FMOD is licenced software within the scope Blizzard is using it and hence moving from 4 to 5 might not be free.
... like this does not already exist.[...] they have made it require special licencing, possibly to protect their intellectual property as it may expose low level mechanics of FMOD which could be used to create ones own audio library component with similar performance.
Good point.I am guessing the reason Blizzard moved to FMOD is because all modern Blizzard products use FMOD. [...]
Yea, verily shall the Ancient Ones stir from their long slumber amidst the Stars...Member Since: 2004
This is a known issue with orders exclusive to 1.30 PTR. It has been fixed and should not be an issue in the future.
Cool cool!This is a known issue with orders exclusive to 1.30 PTR. It has been fixed and should not be an issue in the future.
Tried placing them in the file system with local files registry setting enabled? Apparently local files still works.Our isn't able to load anymore, I think it is bad for all the moders and people that liked our stuff , atleast will there be a way to do what war3mod.mpq does with casc files?
Atleast this is nice , though old 'inside' mpqs are replaced too so I can't make cliffs work right , do we have any clues about how they are working in new casc system ?AFAIR, nope. Local files has been a thing since the old days.
Game isnt dead but i agree about the modding, keeping the MPQs as secondary/legacy archive would work, if not there should be 1.29 installer left for offline mods if its impossible or too much work to do to keep in working state.Ok i will shorten the story : Removing .mix support was bad idea for modders , but its fine if blizz had to do it if they plan upgrade wc3 file to modern
Second and most important thing : We know that some of hives had build a career in blizz directly from this site ,and some who are not employeses still having direct contact with them
Is there any Blizzard employee who would listen our voice i talk about wcunderground community ? We are the second wc3 important community after hive and we deal with other stuff like modding . Can you please consider us a bit , cause i am afraid wc3 patches are iintentionally going towards killing mods .
I will remind you that we too (Specually Rebirth which is part of WAA) are idolising blizzard , using blizzard resources , we are aware that they dont care about us much, but still we are aware its their property too , and we follow rules and respect our God.
Please login to bnet and see how dead the game is with tons of empty games hosted by bots - you know it . Hive discussed already about it .
I think hive is doing their job to serving blizzard god , and we try to do some on our own way .
Now my appeal is : We try to revive a game (i know its on amateur level,but we do our best)that is dead ,by dragging people using fancy graphics,blizzard models parts,art,style etc so DONT KILL US hive-blizz gentleman . Thank you very much
Can you elaborate? Perhaps provide some examples/screenshots?If the people are interested in this, I've solved it myself 'inside' mpqs (for example b.mpq for barrens) are now inside folders, they are named in the old way for example for barrens b.mpq but as A FOLDER, So if you want to replace it dont save it as a mpq but name your folder 'b.mpq'
Ofc okay I'll show it it is simple actually: they are named like this but they are not a mpq file , they are just a folderCan you elaborate? Perhaps provide some examples/screenshots?
Ooh, thanks!
I'll ask more later (@ work), but are you saying it *doesn't* work as of 1.29, 1.30, or what?