Preparing a build for a publisher meeting: the technical checklist
The demo will be played on someone else's laptop, in a noisy hall, by a person with twelve minutes. What the build has to survive, and what to have ready when they ask the technical questions.
The conditions
A publisher meeting is not a playtest. The build runs on hardware you did not choose, in a hall with bad wifi and worse lighting, for a person who has seen ten builds that morning and will give yours twelve minutes. The technical goal is not to impress. It is to remove every reason the meeting goes badly that is not the game itself. Here is the list I use before any build leaves the studio for one, in the order it gets done.
Two weeks before
A build that runs from a clean install on a machine that is not a developer’s. If it needs a runtime, a driver, a login, or an environment variable, it will fail on the laptop in the hall. Test on the oldest machine in the studio, freshly reset.
A fixed scenario. A saved state that starts at the best fifteen minutes of the game, with a way to restart it in one keypress. Nobody in the hall will play the tutorial. The scenario has a beginning that shows the hook within sixty seconds and a beat at the ten-minute mark that shows the ambition.
Frame rate on the demo hardware, measured, in the scenario, with the settings locked so nobody can change them. If the demo machine is a laptop, the laptop’s thermal behaviour after twenty minutes is the number that matters, because it will be running all day.
One week before
Offline. The build does not need the network for anything in the demo. If the game is multiplayer, the demo has a local mode, a bot, or a recorded session, because the hall’s wifi will not carry a match and a demo waiting for a server is a demo that ended.
Crash handling. The build catches what it can, logs to a file the team can read afterwards, and, if it must fail, fails to the desktop with the game’s icon still visible so it can be restarted in seconds. A crash to a debugger window is a meeting that is over.
Input. Controller and keyboard both work, both are plugged in, and the controller is the one the publisher’s staff are used to. An input mapping that needs explanation is thirty seconds of the twelve minutes.
Nothing in the build that is not for the meeting: no debug menus reachable by accident, no unfinished text, no console that opens on a key someone will press.
The day before
Three copies. The demo machine, a backup machine with the same build, and a drive with the installer, because the demo machine will be the one that decides to update its operating system in the hall.
A video of the scenario, on a phone, in case every machine fails. It has happened to everyone.
The numbers ready. The publisher’s technical person, if there is one, will ask about the target platforms, the frame rate, the engine version, the team size, the build size, the multiplayer architecture and the schedule. Have the honest answers on one page, with the numbers, because “we are optimising” is not an answer and a specific number with a plan behind it is.
In the meeting
Someone from the team drives, unless the publisher asks to play, in which case hand over the controller and stop talking. The technical person’s job during the demo is to watch the machine, not the publisher: the frame rate counter, the temperature, the log. If something goes wrong, restart to the scenario without explaining; a restart is ten seconds, an explanation is a minute of the twelve.
After
Read the log. Every crash, every warning, every dropped frame in the hall is data about a build that will be sent to that publisher for evaluation next week, on their hardware, unattended. The evaluation build is the meeting build with the fixes from the log, and it is the one that decides the deal.
Why this is a technical director’s list
None of it is game design. All of it is the difference between a game being judged and a build being judged, and a studio that has a technical owner for the build is a studio whose demo shows the game. I have carried builds to meetings for my own studio and for clients, and every item above is on the list because it once was not.
If a publisher meeting is on your calendar and the build is not ready for the conditions above, a Performance Teardown pointed at the demo scenario is the fastest way to know what will break, and the technical due diligence is what the publisher will run on you afterwards.