Simplifier

Think of your game like a big digital playground where players can roam around and do whatever they want. If the playground still has wet cement, missing swings, and holes in the ground, it is usually better to keep the gates closed for now. If you let people in too early and they get stuck or frustrated, they might remember the "broken" version forever, even after you fix everything. Showing an unfinished game is like inviting people to a dinner party when the food is still raw. Even if you promise it will be delicious later, all they will remember is the bad experience. In the world of games, first impressions are very hard to change. If the game doesn't work smoothly during a big event, people might lose interest before you even get a chance to finish it. Instead of letting people play a version that isn't ready, you can show them a short video of the best parts. This lets you highlight the cool things you have already built without the risk of something going wrong live on stage. It is much safer to show a "highlight reel" of what’s coming than to let people wander into parts of the game that aren't finished yet.

Visionary

We must look beyond the binary of "finished" or "unfinished." A showcase is not a status report; it is a declaration of intent. If your sandbox TPS represents a paradigm shift in how players interact with digital worlds, you must only reveal it when the demo can act as a portal to that future. If the current build merely highlights technical limitations rather than the transformative potential of the experience, then silence is your most strategic ally. The goal is to capture the horizon, not to apologize for the present. We are building a legacy, and a premature glimpse of a fragmented system can anchor your project to the very constraints we are trying to transcend. Wait until you can present a "vertical slice of the future"—a moment of gameplay that proves the systemic change you are promising is not just possible, but inevitable. True innovation requires the courage to protect the vision until it is ready to ignite the industry’s imagination. Use this time to refine the core essence of your world. When you finally step into the light, do not just show a game; show us the new trajectory of the medium. Momentum is built on awe, not on "almost."

Sentinel

Skipping the demo is the only prudent course of action when the product lacks fundamental stability. In a sandbox environment, the number of unpredictable variables and edge cases is exponentially higher than in linear titles. Presenting an unfinished build risks a catastrophic failure that could permanently damage the project's reputation and investor confidence. It is far better to maintain silence than to broadcast vulnerability. A premature showcase offers negligible upside compared to the severe downside of a public crash or a glitch-ridden experience. Precedent shows that first impressions are nearly impossible to overwrite; once the public perceives a project as unstable, that stigma persists regardless of future patches. You must protect the work that has already been completed by refusing to expose it before it is fortified. If a presence at the showcase is mandatory, pivot to a pre-recorded, highly controlled video sequence rather than a live or interactive demo. This safeguard allows you to demonstrate the vision while eliminating the inherent risks of a live environment. Vigilance requires acknowledging that "almost ready" is, in reality, not ready at all.

Empath

When we consider this choice, we must first look at the hearts of the people behind the project. If the game isn't ready, forcing a demo often means pushing your team into a state of high stress, exhaustion, and potential burnout. Their well-being and the passion they pour into their work are far more precious than any single marketing milestone. It is difficult for creators to feel proud of their work when they are forced to show something that doesn't yet reflect their true vision. We also have to think about the players and the community waiting for this experience. They are looking for a connection and a reason to be excited, but presenting them with a broken or unfinished sandbox can lead to genuine disappointment and a loss of trust. It’s much kinder to be honest about where the project stands than to offer an experience that feels frustrating or hollow, which could hurt the relationship you’ve built with your audience. Instead of a demo that might cause distress for both the creators and the fans, consider a more personal approach. Sharing a heartfelt update or a "behind-the-scenes" look at the journey can foster a deeper sense of community and understanding. Prioritizing the mental health of your team and the emotional experience of your players will always lead to a more sustainable and meaningful success in the long run.

Pragmatist

If the core mechanics—shooting, movement, and stability—aren't rock-solid, skip the live demo. A broken demo is a net negative that signals technical incompetence to investors and kills player hype. You don't get a second chance at a first impression, and the cost of repairing a damaged reputation far outweighs the temporary visibility of a premature reveal. Instead of a full sandbox demo, pivot to a "vertical slice" or a pre-recorded "in-engine" gameplay trailer. This allows you to showcase the visual fidelity and intended gameplay loop without the risk of a crash or game-breaking bug. It’s a more cost-effective way to generate measurable impact, such as wishlist additions or press coverage, while keeping your development team focused on fixing the game rather than patching a one-off demo build. The decision should be based on your specific goal for the showcase. If you need to prove technical feasibility to a publisher, you must have a stable, playable segment. If the goal is general marketing, a polished video is the pragmatic choice. If you cannot guarantee a 100% stable 10-minute loop, pull the live demo and redirect those resources toward hitting your next internal milestone.

Points of agreement

• First impressions are critical and nearly impossible to overwrite; a negative initial experience creates a lasting stigma that persists even after the game is fixed.
• Presenting a broken or unstable demo is a net negative that actively damages the project’s reputation, investor confidence, and player trust.
• Skipping the demo is the most prudent choice when the product lacks fundamental stability or fails to represent the intended quality of the final experience.

Points of disagreement

• The primary motivation for skipping the demo varies: some prioritize protecting the development team from burnout and stress (Empath), while others focus on technical risk mitigation (Sentinel) or preserving a high-concept brand image (Visionary).
• There is a lack of consensus on the best alternative to a live demo