StarEdit Tutorial - Generic Hyper Triggers

Incase you were not aware, StarCraft uses a delay when checking triggers, likely to use less memory on older machines. The delay is a whopping two seconds. For a basic triggered map, this may not be an issues, however, if you ever find yourself requiring a more precise timing due to certain events you would like to trigger, it is likely you are in dire need of this tutorial. Hyper triggers, or hypertriggers, allow you to adjust the game's trigger check speed to your own liking. There are different methods of performing this, but for the sake of simplicity, this tutorial will follow the most basic approach.

A generic hyper trigger may be defined as simply using wait actions within a lone trigger to allow the rest of the triggers to initiate at a much faster rate. The rate is speculated to be around twelve times as fast, meaning instead of being triggered every two seconds, they will trigger every .1 seconds, allow a more precise result for your triggers, allowing you to be utilize more advanced triggers.

The generic hyper trigger does have a limitation though, as it must be placed within a Player who does not have any triggers containing the Wait function already within it, but is also in the game. Basically, this means the Player must have a start location, and is most likely an unused Computer if you want to make this the easiest way possible.

The following is the player, conditions, and actions within the trigger. X being the unused Player.

Players:
- Player X
Trigger Conditions:
- Always
Trigger Actions:
- Preserve trigger
- Comment "Hyper Trigger"
- Wait 0 milliseconds
- Wait 0 milliseconds
...

Now you must Copy the Wait command until the Actions box maxes out and Copy becomes greyed out. At this point complete the trigger, and you have now adjusted StarCraft's trigger reading speed to every 1/10th (.1) seconds instead of 2 seconds.

Lavarinth
June, 2009