Search the Community

Immediate feedback is relatively easy to communicate. A player makes a choice, a statistic changes, and the relationship is obvious. The harder design problem appears when a decision is supposed to matter several turns, years, or events later. If the delayed consequence appears without enough context, players may interpret it as randomness. If the game repeatedly reminds them that an earlier choice caused the outcome, the system can become overly explanatory and reduce discovery. I’m helping share 1 in 8 Billion, a browser-based life simulator centered on life progression, starting circumstances, character statistics, and player choices. Game link: https://1-in-8-billion.com/ For developers, what techniques have worked well for connecting delayed outcomes to earlier actions? A decision history? Small trend indicators? Event text referencing previous choices? Changes in visible statistics? Or is it better to let players infer the relationship themselves? I’m particularly interested in approaches that preserve uncertainty while still giving players enough feedback to believe the simulation is responding to what they do.

In decision-heavy games, clarity is important. Players need enough information to understand what they are choosing and why an outcome occurred. But if every option clearly maps to a visible numerical benefit, the decision can stop feeling like a choice and start feeling like a calculation. Life simulation games make this especially interesting because several values may compete at once. A decision could affect health, happiness, knowledge, savings, or future opportunities. Showing every consequence in advance improves transparency, but it can also remove uncertainty and reduce the value of experimentation. I’m helping promote 1 in 8 Billion, a browser-based life simulator featuring character statistics, different starting circumstances, player decisions, and life progression. Game: https://1-in-8-billion.com/ For developers working on simulations or management games: how much information do you expose before a player commits to a choice? Do you show exact stat changes, use qualitative hints, reveal only immediate effects, or let players learn the relationships through repeated play? I’d also be interested in examples where a game communicates trade-offs clearly without making one option feel objectively correct.

How Much Information Should a Simulation Game Display? Browser-based simulation games often need to communicate several types of information within a limited screen area. Displaying too many statistics can overwhelm players, but hiding important information can make decisions difficult to understand. A useful interface needs to balance clarity, visual hierarchy, and gameplay depth. I'm helping promote 1 in 8 Billion, a browser-based life simulator featuring health, happiness, knowledge, savings, and life progression statistics. View https://1-in-8-billion.com/ For developers working on game interfaces, which information would you keep permanently visible? Would you use expandable panels, contextual information, or a minimal dashboard? I'd appreciate examples of simulation interfaces that handle information density particularly well.

If you like pixel art, weird stories and electro music - you might like the following music videos by Gamer. Warning - Videos contains violent scenes and weirdness GAMER - Turbo GAMER - Shaping Staff Official bandcamp page can be found here: http://gamer.bandcamp.com/