World Editor Crash

[jonbon29]

I'm using the action type Hastable - Save Ability Handle and upon clicking the Ability my editor crashes. Does anyone encounter this error?

 

[Nichilus]

Yes, that GUI action is bugged. I think it's still possible to save ability handle via jass tho.

 

[jonhysone]

Hmm, it's not the only function that crashes (considering the Hashtable's tab), well 'Save Region, Widget , EventID , ...' all crash.

Now since the problem here is the ability. You can save the ability's ID as a "string" using 'Save String in Hashtable'... then when you load it, use the jass function to load it (since it uses Abilities' IDs) ... and in ID's place, use String2ID and load that saved string in Hashtable.

 

[andreasaspenberg]

variables is also a posibility. the description of what you want to accomplish however is too short for me to help you. i can help you if you give me more information.

 

[PublishedShadow]

I think some of those GUI actions are JNPG added functions, which may be why they are somewhat buggy.

I've actually had the editor itself crash when just browsing through the list and scrolling over an action.

 

[Dr Super Good]

They crash because WC3 is a buggy, poorly documented mess.

Some poor Blizzard employees were forced to maintain Warcraft III after a critical security exploit was discovered involving typecasting code to allow arbitrary code execution. This is when they added the GetHandleId, the string hash, and hashtable natives we are so fond of today.

When adding these new features to GUI they saw GUI had "Region", "Ability", and other such types so decided to link it to them, after all people might find it useful. What they failed to spot was these types are a lie. GUI "Region" is actually a JASS rect, with JASS region being something completely different and entirely unsupported in GUI. Like wise GUI "Ability" is actually JASS integer, with JASS ability being an entirely unsupported WC3 type, probably representing internal functionality that cannot be accessed (no natives to manipulate) or a relic from early days of development. Non the less GUI actions were added to reference these unsupported in GUI types. As one knows the editor crashes as soon as they are processed.

One cannot really say the guys who made the mistake were to blame. Ultimately the blame falls with the developers of WC3 GUI who made it so poorly written, confusing and error prone in the first place. Fortunately SC2 GUI is considerably better engineered with much better linking between GUI and Galaxy script.

 

[TheLordOfChaos201]

can you use the star craft gui for warcraft maps?

 

[Bribe]

No, that would give people a reason to learn StarCraft 2 Editor

 

[TheLordOfChaos201]

that sucks... why even mention that starcrat is better If I can't use their editor...

it's not luckily.... it's unfortunately

 

[Bribe]

DSG is evangelical about SC2.

 

[Dr Super Good]

Which is why if you trigger for WC3 you really should be using JASS. It increases productivity, readability and performance.

 

[jonbon29]

Thanks for the comments guys and sorry for my late reply, I've been inactive these days. Any other way to save the ability in a hashtable, without writing it in Jass? My trigger is GUI.

 

[Nichilus]

Use jass equivalent to the GUI action and simply write that call into Custom script.

 

[jonbon29]

Hmmmm.... is that the Custom script where you call a function? Where can I see some example functions that I would write there? Like the Hastable - Save Ability Handle, how can I write it in the Custom script?