For example, in any trigger capable of interfering with a cinematic, I always include the condition "QV Check: Movie = 0". In every cinematic, I start off with "QV Set: Movie = 1". That way, triggers do not fire during a cinematic. Be sure to remember to set the QV "Movie" back to 0 after the cinematic ends.

What are some tips and guidelines you guys use whenever making scenarios?

I will add them to the list below:

pftq
SINGLE-PLAYER SCENARIOS
1) Cinematics: Every trigger capable of interfering with cinematics has the condition "QV Check: Movie = 0". Every cinematic starts off with "QV Set: Movie = 1". Every cinematic ends with "QV Set: Movie = 0".

2) Looping triggers always contain a QV condition. This way, it can be deactivated via QV Set. Disable Trigger is known to not completely disable looping triggers.

3) Skippable Into Cinematics:When using "Abort Cinematic" to make intro cinematics skippable, contain in that trigger (Abort1) "QV Set: QV = 0". Then in every trigger within the intro cinematic, contain the condition "QV Check: QV = 1". After the trigger (Abort1), fire trigger (Abort2) which then disables every trigger in the intro cinematic. This method guarentees the cinematic to skip correctly.

4) Modify Protounit: Population Count: If population is important in your scenario, never use this. When saved and reloaded, the scenario will set the total pop count to 0, making it possible for the player to have a negative pop count and therefore ruining your scenario.

5) Active Triggers: Avoid having too many triggers active at once. Make use of the effect "Fire Trigger", which activates an unactive trigger.

6) Distance to...: When possible, use Distance to Unit/Point instead of Units in Area. Distance to Point/Unit works faster than Units in Area.

7) Soundfile Name: Fire Trigger: Be careful when using the Trigger part of Soundfile Name effect. It fires the next trigger when the sound is finished playing. If your scenario lags, the sound may finish playing and fire the next trigger sooner than you intended.

AOMPlayer000
1) Player Change LOS: Don't use this. When the map is reloaded, the LOS is messed up. Use "Set Tech Status: Shared LOS, Unobtainable" instead.

Gummyworm
Use Groups - Although it's not nessesary, making groups for your triggers (and naming triggers) can really make the scenario more tidy. It's also useful if one of your triggers is "bugged" and needs to be debugged, so you can find the trigger.

Jot Down QVs - Keep a list of all your scenario's QVs in a notepad file or on a piece of paper, along with a description. That way, you don't forget what the var is.

Have More than one Run Immediately Trigger - If at the start you want to modify protounit, change diplomacy, start movie, and Set Techs, use separate triggers. Doing so will make the effects easier to find for future reference.

Save Before entering Sound/Music filename triggers into Editor - This is obvious, but it bears mentioning. Always save before using the two "Trouble Triggers"

Check for Cinematic Inconsistancies before starting - Always make sure that cinematics have On and Off triggers in them before you test.

Archaeopterix
- While making the scenario, make sure you have a temporary trigger with the condition "abort cinematic" and effect "cinematic mode OFF", so you can always escape.
- Use QVs for everything. I have tons of them which are either 1 ("on") or 0 ("off"). A good example is what pftq said: the movie checks (I always have a "busy" QV, which - during dialogues and cinematics - is given the value 1). But I also use them to keep track of items in an inventory, to keep track of the optional objectives that are currently running, to "create" time (a QV "hours" and a QV "days"), to set a day-night cycle and city-life making use of "hours" and many many more.
QV pwnage.

[This message has been edited by pftq (edited 04-20-2005 @ 09:45 PM).]