u/Steven_Volkov

Been chewing on why some simulated systems feel alive and others feel like hidden math. My theory: legibility is the part everyone skips. Teams nail the rules, sort of handle the emergent behavior, and completely forget the player's mental model. But if I can't tell WHY something happened in your sim, I'm not making decisions, I'm gambling.

Best example I know is the Plumbob in The Sims. Delete that green diamond and nothing about the simulation changes, but half th e game's appeal dies. It's not UI, it's the sim made readable.
The flip side is the fidelity trap. SimCity 4 tried simulating individual citizens, players couldn't tell the difference, so they cut it. Valve's water in HL2 is physically wrong and nobody cares because it makes the gravity gun feel good. Fidelity nobody can feel is just CPU cost.

But then there's Dwarf Fortress, which is deep AND illegible and people love it anyway. So maybe the community/wiki is doing the Plumbob's job externally?

Where's the line for you between "readable system" and "solved system"? At some point legibility kills the mystery.

Been chewing on why some simulated systems feel alive and others feel like hidden math. My theory: legibility is the part everyone skips. Teams nail the rules, sort of handle the emergent behavior, and completely forget the player's mental model. But if I can't tell WHY something happened in your sim, I'm not making decisions, I'm gambling.

Best example I know is the Plumbob in The Sims. Delete that green diamond and nothing about the simulation changes, but half th e game's appeal dies. It's not UI, it's the sim made readable.
The flip side is the fidelity trap. SimCity 4 tried simulating individual citizens, players couldn't tell the difference, so they cut it. Valve's water in HL2 is physically wrong and nobody cares because it makes the gravity gun feel good. Fidelity nobody can feel is just CPU cost.

But then there's Dwarf Fortress, which is deep AND illegible and people love it anyway. So maybe the community/wiki is doing the Plumbob's job externally?

Where's the line for you between "readable system" and "solved system"? At some point legibility kills the mystery.

Hey guys, In a recent project discussion, a PM reacted very strongly to a conversation based on only one side of what was said. It led to shutting down an idea about collecting player feedback / using it for AI training.
Later it turned out it was just a misunderstanding and not an actual task or proposal.
My question is how do you handle situations where a PM makes a strong decision or reaction before getting full context from both sides?
How do you prevent miscommunication from escalating like this in fast-paced teams?

Hi everyone, I’m researching tone of voice for game community managers and player support, especially in situations where players are frustrated after bugs, balance changes, compensation issues, delays, or unpopular updates.

I’m trying to understand what kind of wording feels respectful and useful to players, and what kind of wording makes things worse.

For example, I’m looking at questions like:

• How should a community manager acknowledge angry feedback without sounding fake or too corporate?
• What phrases should be avoided because they feel dismissive, defensive, or blame the player?
• How transparent should a studio be when there is no confirmed ETA or fix yet?
• Are there good examples of game studios handling backlash well?
• Are there bad examples where the wording made the situation worse?

I’m especially interested in practical wording, not only theory. For example, what would you say instead of phrases like “please be patient,” “we value your feedback,” or “this is working as intended”?

Would love to hear from people who have worked in community management, support, moderation, game development, or from players who have seen good/bad studio communication.

Thanks!

Hey guys , how developers handle building a community around a game, especially early in development or during prototype testing. A lot of games have a Discord server, but getting players to actually join and stay there feels difficult. Many players may try the game once, give no feedback, and never join the community.

For those of you who have managed to bring players into your Discord, Steam community, Reddit, or other community channels:

How do you do it in a way that feels natural and not annoying?

I’m especially interested in things like:

• Where do you place the Discord/community invite?
• Do you ask players after gameplay, on the main menu, after a win/loss, or somewhere else?
• What reason do you give players to join?
• Do rewards or exclusive content help, or does that attract the wrong people?
• How do you make the Discord useful for gameplay feedback, playtests, bug reports, and community discussion?
• What mistakes should be avoided when trying to move players from the game into a community?

I’m not asking about spammy marketing. I’m more interested in practical systems and player psychology.

What has worked for you, and what did not work?