[18ESP] clarify endgame banner description during OR

[queroscia]

Hello,

18ESP rules say: after purchasing or exporting the second 8/6+8 train, the current OR ends (not the complete set of SR+ORs) and the game enters the last SR. It implies a problem of confusions. Example: End game is triggered during OR8.1 or OR8.2. Program says the game will be end after OR9.3. It is true, but a player will usually think they still have OR8.2 and OR8.3 for playing, but it is not real. I would suggest an event written on the log. Something similar to: "End game has been triggered. At the end of this OR will enter the last SR of the game. No more ORs on that set."

Thank you,

Enrique Trigueros (queroscia): designer of 18ESP.

[queroscia]

By the way, if the second 8/6+8 train is purchased, for instance, during OR7.1, the game shows this sentence: "Phase 8 – Operating Round 7.1 (of 3): Game ends at conclusion of OR8.3." The sentence is (almost) true, because the program is well coded and the game skips from OR7.1 to SR8 directly. But it is confused for the players (about all new players) to see Operating Round 7.1 (of 3), when there are not OR7.2 nor OR7.3. In addition to the suggested event sentence on the log, would be possible that, just on the moment the second 8/6+8 train is purchased or exported, the "(of 3)" was changed by something similar as "(end game triggered; following round: last SR)"?

Thank you very much,

Enrique Trigueros (queroscia): designer of 18ESP.

[benjaminxscott]

To confirm my understanding:

Two cases trigger the endgame: 1 - The second 8/6+8 train is purchased, in which case the current OR is played out and the game enters the final SR (skipping any remaining ORs in that set) 2 - The second 8/6+8 train is exported at the end of an OR set, in which case the game enters the final SR immediately

The status banner is ambiguous when (1) triggers during e.g. OR8.1 or OR8.2 when it states the game ends after OR9.3. It also incorrectly conveys that the current round is ORX.Y (of 3) when X = 1 or 2

The banner could be clarified to the effect of "Final SR will be triggered after the current OR finishes."

The current OR count is dynamic (afaik) so we should be able to change that on the fly to (of Y) and have it be accurate