Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Oberlus opened this issue Jun 18, 2020 · 0 comments
Open

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

Oberlus opened this issue Jun 18, 2020 · 0 comments
Labels
category:feature The Issue/PR describes or implements a new game feature. component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. component:UI The Issue/PR deals with the game user interface, graphical or other.

Comments

@Oberlus
Copy link
Contributor

Oberlus commented Jun 18, 2020

Feature request

Idea

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.

Discussion

Forum thread

@Oberlus Oberlus added the category:feature The Issue/PR describes or implements a new game feature. label Jun 18, 2020
@Vezzra Vezzra added component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. component:UI The Issue/PR deals with the game user interface, graphical or other. labels Jun 21, 2020
@Vezzra Vezzra added this to the post release milestone Jun 21, 2020
@Vezzra Vezzra removed this from the v0.5 milestone Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:feature The Issue/PR describes or implements a new game feature. component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. component:UI The Issue/PR deals with the game user interface, graphical or other.
Projects
None yet
Development

No branches or pull requests

2 participants