I've got a selection system where if you select a hero it checks to see if the player force (force 1) has at most 0 'hero name'.

Then i've got another trigger where if you attempt to select it but someones already taken it I made it to check force 1 commands at most 1 'hero name' and even though no one has picked the hero, it keeps giving me the error. I used the same trigger for the other heroes and it works. I tried at least 1 'hero name' too but it still gives me the error. Anyone know what's up?

Post has been edited 1 time(s), last time on Sep 8 2008, 10:05 pm by ColdFusion.

Uh... What?

I'm sorry, but I don't understand what you're saying. I'll take a shot at it anyways.

You're using "Commands at most 1 (hero)" which, in translation, means "Commands 0 or 1 (hero)." Maybe this is the source of your problem?

You didn't elaborate on this "error." Could you describe what this error is? And maybe describe this selection system a bit more?

The error is a display text I put for someone who tries to pick an already picked hero. "Error: Hero is already taken"

Also, for the Hero Taken trigger I tried changing it to force 1 commands at least 1 'hero' and exactly 1 'hero' but when I do that nothing happens at all. It doesn't pick nor gives an error. Graghhh.

Could it be because i'm using a force? Perhaps i'm going to have to do the player 1-8 commands at least 1 'hero'

Thanks for updating your first post

Well, "At most" is definitely the wrong condition to be using. "At least" SHOULD work, but as you stated, you still get a problem. I would review your trigger and make sure everything is right (You can compare with the triggers that you claim work). If nothing is amiss, I would check for silly things you might accidentally overlook, such as placing the hero on the map owned by someone in force 1. If you still have problems and feel comfortable doing so, I would suggest posting the map.

(Does your first trigger create the hero for the player when he/she selects it?)

Of course, you could do other methods of selecting a hero, such as adding the selection condition "(computer player) commands at least 1 (hero)" and then give the hero to the player. Therefore the trigger could only run once, because the condition would be checking for if the computer player still had the hero.

Hum, I just now tried deleting the 'Hero already picked' trigger and it still doesn't even want to pick. This narrows it down..

Uhm when the hero has been chosen by a player, and then another player steps on the same beacon (if thats your choosing system) you can detect for at least 1 <hero name> of force 1 and give the error message.
If he steps on the beacon and force 1 brings 0 <hero name> to anywhere then just give him his hero.
Its really simple. As Roy said, you should check your triggers for mistakes.

Lol, you guys were right. It was something retarded, I got one of my locations wrong.