조건 전체 목록 — 맵 제작 강좌

Conditions decide when a trigger fires. There are only 23, and about ten of them do the day-to-day work - but it is worth reading the rest once, so that the right one comes to mind when you need it.

The ones you will use constantly

Always	Always true. This is what a trigger that must run every cycle uses.
Bring	How many of a player's units are inside a location. The basis of pads and zone checks.
Command	How many of a unit a player owns, anywhere on the map.
Deaths	A death counter's value - in practice, your variable system.
Switch	Whether a named switch is set.
Kill	How many of a unit type a player has killed.
Elapsed Time	Seconds since the game began.
Never	Always false. Used to switch a trigger off without deleting it.

Resources and score

Accumulate	Whether a player has gathered a given amount of minerals or gas.
Score	Whether a player's score has reached a figure.
Most Resources	Whether this player holds the most resources.
Least Resources	Whether this player holds the fewest resources.
Highest Score	Whether this player has the highest score.
Lowest Score	Whether this player has the lowest score.

Comparisons between players

Command the Most	Whether this player commands the most of a unit type.
Command the Most At	The same, but counted inside a location.
Command the Least	Whether this player commands the fewest of a unit type.
Command the Least At	The same, but counted inside a location.
Most Kills	Whether this player has the most kills of a unit type.
Least Kills	Whether this player has the fewest kills of a unit type.

The rest

Countdown Timer	How much time is left on the countdown timer.
Opponents	How many opposing players remain.
Memory	Compares a memory value directly. This is the EUD condition ScmDraft 2 exposes, and it returns in the EUD module.

All conditions must be true together. There is no OR - if you need “A or B”, write two triggers.