From: Washington D.C.
I'm working on a scenario with a lot of moving parts and I was curious what other folks are doing to keep your events organized?
I just type a quick phrase describing the intended functionality of the trigger, condition, event or action. Most of my actions are LUA actions. Very few of them are set to go off at specific times. I tend to prefer conditionals. Complicated LUA code gets commented because I don't have enough brain cells left to decipher my own code twice. They also are not necessarily specifically tied to missions, either.
For example, when I'm encoding a victory condition, I might use a regular interval trigger intended to go off every 5 minutes. I'll call that, "Every five minutes." If the victory condition is "20% of the POL storage is destroyed" I'll call a condition "Check POL storage condition." Then make a points action to attribute however much weight to victory I think that victory condition deserves. Finally, I'll create an event which puts all three pieces together, the trigger, the condition, and the action, and call it something like, "Achieved min POL storage destruction requirement." When I see what happens in the log, I understand exactly what just happened.
< Message edited by SeaQueen -- 1/22/2019 1:20:06 AM >