Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[darklord92]

The main announcement log is usually filled, often quite quickly, with new announcements. This leads to mandates being missed simply because the player decided to set a large manager order such as process plants(30), and the log has been spammed heavily. The combat and hunting logs do a good job of reducing message spam from the important announcements. However seeing a separate "M" for mandate notification appear under the combat and hunting log indicators would be a great help. Even if the symbol is merely there to show a mandate is active or has changed.

[nogoodnames]

Just look at the noble screen. It tells you at a glance if a mandate is active, and full detail with one further keypress, the same as your suggestion.

[Larix]

I think it'd be a good idea if mandates were added to the configurable events in announcements.txt in the init folder - this way you could e.g. force a pause when a mandate gets issued. You can currently modify just about any other reported event from there.

[Loci]

Just look at the noble screen. It tells you at a glance if a mandate is active, and full detail with one further keypress, the same as your suggestion.

No, it's not the same. You have described a "polling" process, which requires constant player activity to monitor. darklord92 described an "interrupt" process that directly informs a player when conditions change.

I like the idea of a notification icon, but I would take it a step further and have the icon change color to denote the status of the most pressing mandate. An export ban in white, a production mandate starting gold and transitioning to yellow and red just like they do on the nobles page. Messages in the log for when a production mandate transitions from gold to yellow and yellow to red would also be nice to have, to remind the player that a mandate is nearing failure.

I think it'd be a good idea if mandates were added to the configurable events in announcements.txt in the init folder - this way you could e.g. force a pause when a mandate gets issued. You can currently modify just about any other reported event from there.

That's also a good idea.