Quick answer: Make the build crash-resilient and fast to recover, capture reports and crashes automatically since you cannot watch every station, and review the data each evening. Show-floor support is about resilience and unattended capture, you will not be standing over every player when something breaks.
Showing your game at a festival or expo puts it in front of press, influencers, and players, often at multiple stations running unattended while you talk to someone else. A crash at a booth is a public, high-stakes failure you may not even witness. Preparing support for a show means making the build resilient and self-recovering, capturing crashes and feedback automatically because you cannot watch every station, and turning each day's data into fixes for the next.
Build for Resilience and Fast Recovery
On a show floor, the worst outcome is a station stuck on a crash while a line of players, or a journalist, waits. Prepare a build that recovers gracefully: auto-restart into a playable state, skip straight back to the demo, and avoid anything that requires you to come fix it manually. The goal is that a crash costs ten seconds, not a ruined demo and an awkward conversation.
Lock the demo scope and harden the common paths. A festival build should be the most stable thing you have shipped, because every failure happens in front of someone whose impression matters, and you will not always be there to explain it away.
Capture Crashes and Feedback Automatically
You cannot stand over every station, so the build has to record what happens when you are not looking. Automatic crash capture means that every booth crash, even ones you never saw, is logged with a stack trace and context for you to review. Without it, you finish the show knowing the game crashed sometimes but not where or why, the signal evaporates with the crowd.
Bugnet's crash reporting captures and groups crashes automatically, so an unattended festival build sends you a ranked list of exactly which crashes happened on the floor and how often. Add a quick in-game feedback path too, so a player or the person staffing the booth can flag a rough moment with context. The festival becomes a dense, recorded playtest rather than a blur you half-remember.
Review Each Evening and Fix for Tomorrow
A multi-day show is an iteration loop if you use it as one. Each evening, review the day's captured crashes and feedback, identify the most common floor crash or confusion point, and fix it overnight so the next day's players, and press, hit a better build. A crash fixed after day one is a crash that does not embarrass you in front of day-two journalists.
Everything you capture also feeds beyond the show. The crashes and rough edges a festival surfaces, on varied hardware, with players who have never seen your game, become a prioritized punch list you carry home. Treat the event as both a marketing moment and your most concentrated unattended playtest, and prepare the capture that lets you keep the data after the booth comes down.
On a show floor you cannot watch every station. Make the build recover itself and record every crash for you.