Post by Shieldwolf on May 21, 2010 16:06:12 GMT
- Making a flare on a dead object, or an object that will be removed in the map will mostly make the editor crash.
- If you have the same Condition in 2 similar triggers, with 1 of them under a cinematic and the other not, be sure to let the non-cinematic trigger fire first, because if the cinematic one goes first, the other (usually) won't fire.
- Simply selecting a gate and then graphically altering it to zero won't make it invisible. Instead, select first the sections of the wall you want to make the gate from, and then, graphically set it to zero%.
- If you're using the Effect-Triggers Attribute ON and OFF, minimize deleting a trigger. Usually, the effects description stays, so that the first Trigger still fires.
- Avoid using Always True as trigger. Sometimes, it will continually fire and you may end up starting triggers you don't want to start. Instead, use an Object Existing condition (i.e., if this object exists, your trigger fires).
- Avoid using previously saved scenarios as template for another scenario. The variables and previously fired triggers are already hard-coded in the scenario, and most probably, these triggers will mess up your subsequent ones. It will also most likely result to random scenario crashes.
Feel free to post here of your discovery. I'll be updating this from time to time.
- If you have the same Condition in 2 similar triggers, with 1 of them under a cinematic and the other not, be sure to let the non-cinematic trigger fire first, because if the cinematic one goes first, the other (usually) won't fire.
- Simply selecting a gate and then graphically altering it to zero won't make it invisible. Instead, select first the sections of the wall you want to make the gate from, and then, graphically set it to zero%.
- If you're using the Effect-Triggers Attribute ON and OFF, minimize deleting a trigger. Usually, the effects description stays, so that the first Trigger still fires.
- Avoid using Always True as trigger. Sometimes, it will continually fire and you may end up starting triggers you don't want to start. Instead, use an Object Existing condition (i.e., if this object exists, your trigger fires).
- Avoid using previously saved scenarios as template for another scenario. The variables and previously fired triggers are already hard-coded in the scenario, and most probably, these triggers will mess up your subsequent ones. It will also most likely result to random scenario crashes.
Feel free to post here of your discovery. I'll be updating this from time to time.
