Alright, so a spell im working on is suppose to recall the 4 corners of the arena. The computer has arbitors with full energy and recall researched, so Idk what's wrong. Can someone please tell me how to use the AI recall trigger?

If you need anymore info just post here.

Have you followed the instructions here: http://www.staredit.net/?p=oldwiki&s=94 ?

Make sure you aren't using hero Arbiters.

Make sure your RunAIScriptAtLocation is run by the player that owns the arbiters.

Maybe the condition isn't going off. Check with something noticable like creating a building over water (unplaceable error).

If there are too many sprite animations the recalls won't show. Had this problem myself once.

Alright, I got the recalls in, but I have another question.

Once the recalls start, there is suppose to be a scout spawning at each corner, then moving clockwise around the map.
I can do all the timing and stuff, just wondering if anyone knows a way so it spawns 1 scout, waits a little while, then spawns another instead of spawn spamming one, and in the end getting like, 50 scouts at 1 corner.

Everytime I use a wait for this, It freezes the trigger, even if its for 50 milliseconds.

Post has been edited 1 time(s), last time on May 10 2013, 10:58 pm by Omegwavex.

That sounds like a wait block. Three possible solutions:

1. If you are using the Wait(0)x63 type of hypers, move them to the bottom of the trigger list to prevent (most) related wait blocks.

2. Use switch hyper triggers instead. Example:


3. Eliminate the waits entirely and switch to death counter (DC) timers.

You're running into Wait Blocks.

It is strongly recommended that you use Death Counters as your timers instead of waits which is also the answer to delaying the scout spawns.

Basically Death counters are the equivalent of variables in programming languages. You (mis-)use the death counters of unused units to store and retrieve values. And since with Hyper Triggers you know each trigger loop is 1/8 of a game second it's easy to create a counter with which you can measure time. The counter value becomes equivalent of a certain time span so you can calculate when to spawn a scout.

For example you want to create a scout every 5 (ingame) seconds. What you do is add 1 death for cantina every trigger loop.
When cantina reaches 8 triggers / s * 5s = 40 death counts you reset the death counter of cantina to 0 and create 1 scout.

Thanks guys. My friend gave me a solution to just have a unit timer; everytime a zergling reaches location B, send it back to location A, then do the recalls and scouts.

That's bad practice. You should wrap your head around the death counter system if you're at least half serious about your map.

Death counters are so much more professional, clean, reliable, precise and resource friendly than physical timers. And once you got the principle down they're even easier to implement.

I just couldn't find a way to make DC's equal up for the computer and a player. I needed them both to end at the same time, so we just thought that adding one each time he got to Location B was a good solution.

There's is no reason to even them up. Set/Add them for a specific player that'll always be in the game (for example a P8 computer player) and always read them for that player. Players can read/write other player's death counts.

For example:


The reason you can't "synch" the counts of different players that you have waits in your map.
Whenever a wait runs it breaks the current trigger loop and starts a new one, meaning players with a higher number than the player number that ran the wait will run 1 less trigger loop. Or rather the other players will run an extra loop.