Look this stuff up, goldarn it.
The fact that ti_once is there in place of an integer should tell you that it's a constant with a value. It's defined in header_triggers.py as an arbitrary big number. So putting ti_once in the re-arm field means the trigger comes back into effect after three-four years in real time letting the game run. (i.e. never).
The delays stuff is easy to work out. If you're lost just add all three numbers and you'll get the total time for the trigger to reset.
simple_triggers is probably a ram-saving thing as you said. There's no reason to out them in module_triggers. All you're missing out on is the delay values and the conditions field, neither of which are necessary when you can stick the consequences and conditions together like in simple_triggers.
The fact that ti_once is there in place of an integer should tell you that it's a constant with a value. It's defined in header_triggers.py as an arbitrary big number. So putting ti_once in the re-arm field means the trigger comes back into effect after three-four years in real time letting the game run. (i.e. never).
The delays stuff is easy to work out. If you're lost just add all three numbers and you'll get the total time for the trigger to reset.
simple_triggers is probably a ram-saving thing as you said. There's no reason to out them in module_triggers. All you're missing out on is the delay values and the conditions field, neither of which are necessary when you can stick the consequences and conditions together like in simple_triggers.