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

Consider showing a detailed view of all variables that should be accessible to the player #209

Open
Greenheart opened this issue Sep 9, 2023 · 0 comments
Labels
feature New feature idea Discussions and inspiration

Comments

@Greenheart
Copy link
Owner

For example, some scenarios might benefit from being able to show more detailed game state variables compared to just having the stats at the top of the screen.

In the default scenario, it might for example be interesting to know how many solar power plants that have been built. Or how many days that are left until a special event will occur (if they play as the president and it's important that the player prioritise their actions, say, before an election).

It could also show time of day, rounds played, and many more details that might add depth to the simulation.

Having a view of detailed variables would allow the player to better understand some scenarios where a lot might be going on in the background that is important to keep an eye on and manage.

Implementation thoughts

  • Allow each game state variable to define if it should be visible to the player. If it is, it could be shown in some special UI with the detailed game state.
  • One possible implementation approach could be to let the scenario define which game state variables that should be grouped together, possibly with descriptions and titles for each variable and/or section.
@Greenheart Greenheart added feature New feature idea Discussions and inspiration labels Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature idea Discussions and inspiration
Projects
None yet
Development

No branches or pull requests

1 participant