LogFAQs > #908673449

Triggers were a headache because it caused a lot of burden of knowledge on the player. A player would need to read all the mercs on the opponent's team to detect them, and sometimes the admins could not be prompt in declaring that yes, indeed, a trigger had gone off. A defensive pre-battle or peacetime that would need to be declared in advance and "autotriggers" if the condition is met removes a lot of that burden of knowledge as you'd only need to read the bold text to see "oh crap something may trigger here I'd better check their merc page." You could even be more liberal with things like PMing targets/effects of triggers after the bold declaration in the topic if you really wanted to leave some mystery intact.

I think you could make most current triggers function in the form of an ability meant to be declared pre-emptively than triggers as stated. It does potentially weaken some, but I think if you're clever with Peacetime timings and such you could get a lot of use out of it.

On fatigue, you seem to be treating fatigue like an injury. That's not my vision for fatigue first of all. In my vision for fatigue it's a less significant cost, so you're less likely to end up paying for it. However, I don't think increasing the cost necessarily fixes the core problem. As previously stated by Chris which led into this Ability Point tangent, the problem with mercs is that ability walls are all built on potential costs rather than actual ones. If you're forced to burn abilities, losing those abilities for X weeks only matters if you're faced with a threat that requires those abilities. Similarly, fatiguing your mercs would only matter if you need those mercs unfatigued in the next few weeks.

But the idea of giving every merc its own amount to generate probably helps a bit if your heart is set on making it a generic mechanic, particularly if you're liberal with 0s and being able to generate AP is seen as a perk more than an assumed thing.
---

No problem!
This is a cute and pop genocide of love!