That makes sense. Triggering player relates to the event. For instance if you use the event "unit enters region", if player 3's unit enters the region, triggering player will return player 3. No player triggers the map initialization.
Sounds like you found a solution. It sounded like the behavior was being applied to the dying unit a second time, so my thoughts were stop it from being applied that second time. So using a validator on the effect that applies the behavior to check if it already has it.
Here's my thought experiment guess as a potential work around. Place gateways, then order the the AI to transform gateways into warp gates... it might work :)
I suppose I would give every unit a behavior buff (add it to them in data). I would then use triggers with a unit dies event. I would use the catalog actions to modify the behavior.
I would use Map>Game Attribute. With this you can use player options in the lobby. They'll look similar to the player picking their color and race.
It's been awhile since I've used them, so you may need to experiment to get it just right. You'll click the little plus sign to add a new one. Under general, you'll want to click Player, instead of game. Under Usage, I think you want first come first serve (so only one player can select each). Under values is where you'll add your different factions. If it's just one faction you could have 4 values of faction 1, and 2 values of faction 2.
In the trigger editor you can then use the "Attribute Player Value" to find out what each player selected in the lobby. You can then use that to give control of units and set up alliances.
Just an FYI, by default, conditions are considered under "and". Also to properly use an "and", "or", "not", etc, both conditions would need to be underneath the "and". Since "and" is the default, your version still works. Just good to know if you ever decide to use one of the other types.
Not entirely sure what your goal is or what you're making... You can try out the campaign ai and using attack waves . If you go to my project page for Mapsters, check out the triggers for mission 6. The player has an ally Commander, and I change the allies primary target based on conditions.
I'm not really sure what the best solution would be... One option would be to give the unit multiple weapons with minimum and maximum ranges which do not overlap.
Edit: my solution would be for the attacker. Did you want this for the one receiving damage instead?
I haven't looked at the other solution... Is this for a unit or all units. Because you can use behavior damage responses as dummies for event triggers.
0
That makes sense. Triggering player relates to the event. For instance if you use the event "unit enters region", if player 3's unit enters the region, triggering player will return player 3. No player triggers the map initialization.
0
Have a good time good buddy! Feel free to visit anytime! :D
0
Sounds like you found a solution. It sounded like the behavior was being applied to the dying unit a second time, so my thoughts were stop it from being applied that second time. So using a validator on the effect that applies the behavior to check if it already has it.
0
Here's my thought experiment guess as a potential work around. Place gateways, then order the the AI to transform gateways into warp gates... it might work :)
0
I suppose I would give every unit a behavior buff (add it to them in data). I would then use triggers with a unit dies event. I would use the catalog actions to modify the behavior.
0
Hey guys. I'm releasing my game in Early Access on Tuesday. You can try the demo on Steam now. Check it out!
https://store.steampowered.com/app/1083460/Rencia/
0
I would use Map>Game Attribute. With this you can use player options in the lobby. They'll look similar to the player picking their color and race.
It's been awhile since I've used them, so you may need to experiment to get it just right. You'll click the little plus sign to add a new one. Under general, you'll want to click Player, instead of game. Under Usage, I think you want first come first serve (so only one player can select each). Under values is where you'll add your different factions. If it's just one faction you could have 4 values of faction 1, and 2 values of faction 2.
In the trigger editor you can then use the "Attribute Player Value" to find out what each player selected in the lobby. You can then use that to give control of units and set up alliances.
0.940731399747793
Just an FYI, by default, conditions are considered under "and". Also to properly use an "and", "or", "not", etc, both conditions would need to be underneath the "and". Since "and" is the default, your version still works. Just good to know if you ever decide to use one of the other types.
0
If a link is dead, try searching the forums for the name of the tutorial. They are often the same.
0
What's creating the spawns? AI editor? Triggers? Data?
0
Not entirely sure what your goal is or what you're making... You can try out the campaign ai and using attack waves . If you go to my project page for Mapsters, check out the triggers for mission 6. The player has an ally Commander, and I change the allies primary target based on conditions.
1.82576638468667
0
Above works. Personally I'd make an array variable and loop through it.
0
I'm not really sure what the best solution would be... One option would be to give the unit multiple weapons with minimum and maximum ranges which do not overlap.
Edit: my solution would be for the attacker. Did you want this for the one receiving damage instead?
0.937450929076158
I haven't looked at the other solution... Is this for a unit or all units. Because you can use behavior damage responses as dummies for event triggers.