Dialogue functions are complete crap...maybe the WC3 Editor too!

I've been working on a dialogue set that will replace that "step on circle of power" hero selection method that everybody copies from Blizzard's Warchasers map.

So let's say we have multiple user-controlled players entering a map. At about 3 seconds' time I set it to display a dialogue box with several buttons listing the several types of heroes that are available - say for arguments' we want it to be Archer, Warrior, Mage, Priest. We want the game to create one hero unit of that type at that player's start location.

So of course then I have a trigger set "A dialogue button is clicked for <SelectHeroDialogue>"

No conditions on it...let's say "If <Dialogue button clicked> is equal to <ArcherButton> Create a <Archer> unit for <triggering player> at <triggering player's> start location."

--> this does not work! It will not do it.


So let's say I want to add a condition then...say I'll make a trigger for each of the participating players and say "Condition: Triggering Player = <Player 1 Red>"

and then say "If <Dialogue button clicked>...for <Player 1 Red> at <Player 1 Red>'s start location."

--> This doesn't work either!


Just about the ONLY way it will work is to have no conditions on it whatsoever and just have it create the hero for the same player each and every time. There doesn't seem to be any way for it to distinguish between players and say "do this for the player who clicked the dialogue button and then hide the dialogue button for that player."

I suppose an alternate method would be to create a separate dialogue variable FOR EACH PLAYER and to do each one separately, but does anyone have any idea why this won't work?

The more I work with it the more I begin to see how Blizzard's editor is extremely limited and how all the creative nuances like this are completely screwy - for instance, why don't Array variables work for the "Game: Real Variable becomes = to" event...or for that matter, why can't you have ANY variable become equal to something in order to set off a trigger?! It would make so much more sense in some instances to have a Boolean function with a simple "True / False" than to have it equal to "0" and "1" even though those two essentially perform the same function.

Yes we already dscussed dialogs sucking theres a sticky about them if you must know.