That's why this is running for two weeks after the official patch release, not two weeks from that post.im having a similar problem cause i can´t even enter westfall since i have only acces to german versions of wc3.
Will v1.24 be released in the whole world at the same time ? What is if for example people form USA have the new version of wc3 before the people in europe do ? It would be kind of the staff if they wait until everyone has acces the new version, elseway this will cause a lot of problems since THW is an international website.
Yes, and also you can use handles as a type in variables. I have tried it, looks nice, but maps may not work due to JASS fixes (one of them is the return bug). DotA doesn't work currently, but I'm sure IceFrog is on the move to resolve that.No. Hashtables are entering GUI in 1.24. Also, you can still use proper indexing systems, just not lame ones.
* 1.24-incompatible spells will not be acceptable.
Beyond the obvious route--testing them in 1.24, check out this page.How do I know if my spell is 1.24 incompatible? Will there be specific features rendering many spells incompatible in 1.24? There haven't even been released any 1.24 patch notes, how do you know things will be different with 1.24?
I would have to examine it in detail, but if it does indeed actually competently recycle indices then it would be acceptable.
So the question is .. GUI Indexing can it still be used ... like Paladon spells ?
Spells must be fully multiinstanceable, and done so competently (IE no "indexing systems" which just populate a massive array and count upwards until they hit a maximum, then restarting from the first possible value regardless of whether the position is taken).
It's gonna be a matter of nanoseconds if not picosecondsEleandor said:hashtables are 4 times slower, which means they're faster already if you use more than 4 indices...
...which reeks of BS.Blizzard Tech Support said:Blizzard did not develop the editor and does not support it. We paid royalties to include it in our games, but we didn't create it. It was created by a 3rd party which has since gone out of business. I apologize for any inconvenience.
In spells, the entire section will be purged.
Do not want cJass. If I recall correctly it's obscure, complicated and only used by the Russians.
It's an obscure, complicated Jass variation that the Russians use.
There are only 2.
Cjass is good for users who know C++ and sometimes allow to do better code than vJass.
But... vJass much more older and have more usability.
I'm guessing no GUI spells at all, then? That would be fun.
WILL, you tard. Read the thread.
I've been reading. I don't like what I've been reading. I thought we were finally refusing all GUI spells, seems like the rules have been changing in the last 4 pages.
Basically, any third party form of GUI will not be axcepted. Any GUI using stupid index systems with O(n) efficency or unnescescary index slot usage will not be axcepted as you can use hashtables which are only slightly slower than array handle index lookups to store stuff. Thus with GUI, you can still use arrays to hold data, but they must be used efficenly (no variable[variable[12]]) crap that I see so many spells do nowdays.
You can attach values to units and other objects using hashtables now, so instead of looping from 1 to 100 for your spell in all indexes it uses, you could simply enum through a group holding all units casting the spell and get their array index via hashtables ofthe unit itself. If you do not care about speed, you do not even need variable arrays and could run the whole thing off hashtables.
vJASS will still be allowed, so will structs as they are not stupid index systems. Unlike most of you believe, what people do in GUI is generally not how structs work. Structs have static indexes until they are destroyed and recycle indexes like below.
create struct returns 1
create struct returns 2
destroy struct 1
create struct returns 1
create struct returns 3
etc...
A lot of GUI systems do not have this feature and so clog up large numbers of indexes and even can leak handle indexes until recast 100s of times.
cJass might be more complicated i agree, but thats an advanced vjass so...
to me vjass codes (some spells) are fully unreadable, that is! its hard to find readable spells.
1) If you read what you quoted, you'd see that WILL corrected himself.
2) DSG, while confused, did not say GUI was not allowed.
As to Paladon's system, last time I checked did not use any more complicated algorithm, and was quite slow because of this.
EDIT:
As to the whole cJass thing:
So cJass is more complex, AND more readable?
//! textmacro MyMacro takes CODELINE
$CODELINE$
//! endtextmacro
//! runtextmacro MyMacro("call KillUnit(null)")
macro MyMacro takes CODELINE
$CODELINE$
endmacro
_MyMacro("call KillUnit(null)")