As long as it’s optional, I don’t see why it would be a bad thing. Although personally, I doubt I’d ever be interested in using it in an MP game.

Indeed. Some optional flexibility could be implemented in addition to an absolute score being reached by player A: -Add a timer condition: a timer would start. Player A wins if no one surpasses its score in that time. Otherwise, if player B surpasses A score, the timer resets and same winning condition applies now to player B.  -Add a relative score condition: a score difference has to also be achieved between the two highest absolute scores. One can try many combinations from this. Setting these two new conditions to 0 would just be the original case proposed. On the other hand, the absolute score condition could be set to 0, and with the other conditions one can achieve different game modes.

A absolute score sounds like a nightmare. You have a competitive game going on with armies clashing and suddenly it ends because one team has score X and the other maybe 100 points less. I got a relative score as a announcement in the oddity detector that tells you when it's time to resign. As clear victory condition would be also good. First I had the scores too announced. Some felt it were disclosing information. Although I see no real game play affecting change, I removed the score announcement. Besides it only tells you when it is time to resign. There is rarely a draw but still too many games dragging on unnecessary long because the players refuse or don't understand when it is time to resign.  

Are they include errors? If so, you probably just need to add some specific directories to the "includePaths" of your config.

The problem I see is that that's only taking Ceasefire into account. What about other events, like the ones you mentioned at the beginning? To solve that (and other issues mentioned), here my take on combining what I liked most of your ideas ("Ceasefire" should be also in green): And objectives without a time limit could follow below.