Normalize syntax of several SitReps and group them in a single line

For what's not in 'Top Priority Game Design'. Post your ideas, visions, suggestions for the game, rules, modifications, etc.

Moderators: Oberlus, Oberlus

Post Reply
Message
Author
User avatar
Oberlus
Cosmic Dragon
Posts: 2694
Joined: Mon Apr 10, 2017 4:25 pm

Normalize syntax of several SitReps and group them in a single line

#1 Post by Oberlus » Thu Jun 18, 2020 9:19 am

Normalize syntax of several SitReps and group them in a single line for certain cases.


Currently:

Partial repairs:
- On <planet>: the Orbital Drydock performed partial repairs on the <ship name>.

Completed repairs:
- On <planet>: the Orbital Drydock completed repairs on the <ship name>.

Unable to repair:
- On <planet>: The Orbital Drydock could not start repairs on <ship name>, due to low Happiness.

Damaged ship SitRep:
- At <system>: a <empire name> <ship design>, the '<ship name>', was damaged.

Destroyed ship SitRep:
- At <system>: a <ship design> (the <empire name> ship '<ship name>') was destroyed.


Suggested:

Partial repairs (one per system):
- On <planet>: the Orbital Drydock performed partial repairs on <list of ship names>.

Completed repairs (one per system):
- On <planet>: the Orbital Drydock completed repairs on <list of ship names>.

Unable to repair (one per system):
- On <planet>: the Orbital Drydock could not start repairs due to low Happiness.

Damaged ship SitRep (one per system):
- At <system>: <empire name> ships <list of ship names> were damaged.
Or (if only one damaged ship of this empire in this system)
- At <system>: <empire name> ship <ship name> was damaged.

Destroyed ship SitRep (one per ship design per system):
- At <system>: the <empire name> <ship design> ships <list of ship names> were destroyed.
Or (if only one destroyed ship of this empire and ship design in this system)
- At <system>: the <empire name> <ship design> ship <ship name> was destroyed.



Gain
  1. Much SitRep window space saved thanks to grouped SitReps, without the need to hide that type of SitReps if not interested on them for the time being.
  2. Better information presentation:
    • For Repair SitReps, you are only interested on the system where it happened, there is no need for listing each ship separately.
    • When ships survive a combat but get damaged, there is no need to know ship designs from the SitRep, player can find out which ships were damaged and how badly by going to the linked system and checking out fleets in there.
    • When ships are destroyed, player wants to know the ship design because those ships are no longer visible in the system, and it can be helpful to know if you lost more chaff or troops or whatever.
    • For all cases above, one line per ship is completely unnecessary and swamps the player with useless information that makes harder to get the whole picture, specially when there are various empires involved in each battle.
I hope this is possible and not too hard to implement?
Issue with the feature request.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 12675
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: Normalize syntax of several SitReps and group them in a single line

#2 Post by Geoff the Medio » Thu Jun 18, 2020 1:48 pm

An effect that produces a sitrep that internally has a <list of ship names> probably isn't easily supported now, given how effects targetting and sitrep generation effects work.

Easier might be to do something client-side to merge a bunch of related sitreps into a single UI representation. An option to "merge similar sitreps" could be added to make the SitRepPanel do that.

Post Reply