claude-haiku-4-5-20251001 · $0.034
Zen's Peter Grafl explains design choices, leaderboard constraints, and UX challenges in pinball digital recreation.
Zen avoids rolling code updates primarily due to online leaderboard reset concerns—changing scoring rules requires leaderboard resets which they want to minimize
high confidence · Peter Grafl direct response: 'The main reason behind this is the online leaderboard. And if we change something in the table that affects the scoring possibilities, we would have to reset the leaderboard.'
Altering original Williams/Bally ROMs is 'extremely difficult' and Zen can only modify options available in the original ROM's operator menu
high confidence · Peter Grafl: 'Altering original ROMs is extremely difficult. It was an enormous task to implement these old systems into Pinball FX... we can easily change only the options that can be found in the ROM's original operator menu.'
DMD message timing during critical gameplay is intentional design—holding the ball for all text would be more frustrating than letting messages trigger during play
high confidence · Peter Grafl: 'I just imagine a table where the ball gets always held in a sinkhole or saucer and waits for the text to display. This would be much more frustrating in my opinion.'
Zen has implemented leaderboard resets multiple times during early access and console releases, contradicting the stated reasoning for not doing rolling code updates
high confidence · Chris Freebus and Jared Morgan discuss: 'their leaderboards reset all the time' and 'I've seen this going into the game, then having to redo all my scores on the leaderboard.'
Physical pinball code updates from manufacturers like Stern have included major gameplay additions (e.g., James Bond gaining five skill shots, Guardians of the Galaxy significantly improved)
high confidence · Jared Morgan: 'James Bond pinball machines... when they first released with the code, it was bare bones... latest code update... had like about five different skill shots.'
Zen designers are not maintaining/iterating on tables post-release; once a designer finishes, they move to the next project rather than spending additional time on feedback implementation
medium confidence · Chris Freebus: 'Or maybe it just doesn't fit Zen's design model, which is, "Look, once the designer is done with the table, they're moving on to the next table," rather than having them... There's not a maintenance program in place.'
“The main reason behind this is the online leaderboard. And if we change something in the table that affects the scoring possibilities, we would have to reset the leaderboard, and this is what we want to avoid as much as possible.”
Peter Grafl (Deep), Zen Studios head designer @ ~20:30 — Core explanation for why Zen doesn't implement rolling code updates despite pressure from the community and other manufacturers doing so
“Their leaderboards reset all the time. I've seen this going into the game, then having to redo all my scores on the leaderboard. So I don't see them being very averse to resetting leaderboards.”
Chris Freebus @ ~21:45 — Direct contradiction of Zen's stated reasoning—leaderboards have been reset frequently across platform transitions
“Like, for example, a good example is the James Bond pinball machines that came out. Like, when they first released with the code, it was bare bones... But now they've got, like, the latest code update that I played had like about five different skill shots you could have.”
Jared Morgan @ ~22:15 — Concrete example of how physical pinball manufacturers substantially improve games post-release through code updates
“There's not a maintenance program in place, essentially... Rather than having it be: the table is released, and that designer sticks with the table for another two months to register all the feedback and then potentially make further adjustments.”
Chris Freebus @ ~25:00 — Identifies structural difference between Zen's process and other manufacturers' ongoing support model
“I just imagine a table where the ball gets always held in a sinkhole or saucer and waits for the text to display. This would be much more frustrating in my opinion than letting the instructions come and go as they're triggered.”
Peter Grafl @ ~32:15 — Explains design philosophy behind DMD timing issue—Grafl believes releasing ball during text is better UX than holding it
“And I think it's just like there's been enough tables that we've mentioned that—I mean, even some of these new ones that we went over—where we were like, 'This could be better, this could be better, this could be better, change this.' We have to be able to play the thing first to be able to make suggestions.”
business_signal: Zen's leaderboard-preservation policy contradicts industry standard practice and constrains gameplay design; leaderboards are reset regularly anyway during platform transitions, undermining the stated rationale
high · Hosts confirm multiple leaderboard resets during early access and console releases; Grafl states leaderboards as primary reason for no rolling updates, but hosts directly contradicted this with personal experience
community_signal: Community frustrated with Zen's inflexible approach to leaderboard mechanics limiting gameplay feature implementation (progressive jackpots, ROM status) despite technical feasibility
high · Extended discussion of how leaderboard protection prevents desired ROM status carryover; hosts propose tournament mode/local leaderboard compromise as solution
community_signal: Zen soliciting community feedback and willing to provide follow-up textual responses on technical questions, suggesting some openness to dialogue despite structural constraints on implementation
medium · Hosts planning to send follow-up clarifying questions to Grafl on ROM status issue; Grafl acknowledged 'If you have suggestions for any of the tables that can make the rules better, please let us know'
design_philosophy: Zen's original table designs criticized for not following established pinball UX conventions around rule communication and progression, making learning curve steeper for new players
medium · Hosts note new players on Discord frustrated with difficulty/unclear mechanics; discuss how classic games use lighting/callouts to communicate intent non-verbally rather than DMD text walls
groq_whisper · $0.223
Williams Bally recreations haven't significantly influenced Zen's original design philosophy, though they did adopt GI (global lights) handling techniques from the recreation work
high confidence · Peter Grafl: 'I couldn't say so, at least not in terms of design... We took benefits from the handling of the GI, the global lights.'
Chris Freebus @ ~26:00 — Articulates catch-22: can't test/provide feedback on design issues until after release, but post-release updates aren't happening
“Make them skippable, but don't launch the ball while we're trying to read them. How about make the first time the info is important, you hold it? And thereafter, if you relight that same hole or whatever, or do the same thing, now you understand what is happening.”
Jared Morgan @ ~34:30 — Proposes practical compromise solution for DMD timing issue that Grafl partially acknowledged
“I just remember when I played Iron Man, and I finally gotten to the wizard mode, and I start the wizard mode, and there was a block of text up on the DMD telling me what to do. And at the same time, I'm trying to capture the ball, but it's multiball, and by the time I had any kind of control, the message was already gone.”
Chris Freebus @ ~35:30 — Concrete example of player frustration with current DMD implementation during high-stakes gameplay moments
“It seems that leaderboards, while they're great, are actually causing some degree of issue with how the games are presented to us as players. So I don't know what I'd want more. Would I want leaderboards or would I want these gameplay features?”
Jared Morgan @ ~31:00 — Identifies core tension: leaderboard preservation is constraining game design and post-release iteration
“Altering original ROMs is extremely difficult. It was an enormous task to implement these old systems into Pinball FX, making it possible to support the multiplication of the original scores with the upgrade powers.”
Peter Grafl @ ~27:30 — Explains technical constraints around ROM modification that limit ROM status carryover features
design_philosophy: Zen intentionally diverges from classic pinball design tropes and conventions, prioritizing their own digital-native approach over established pinball language
high · Grafl: 'We have more creative freedom when we design a table from scratch' and 'Williams Bally tables are different enough... because of the nature of digital pinball itself.' Hosts note this causes frustration when genre conventions aren't followed.
market_signal: Peter Grafl response acknowledges technical limitations (ROM modification difficulty) and design philosophy differences; defensive tone on leaderboard policy suggests awareness of community criticism
medium · Grafl offers explanations and partial compromises (making messages skippable) rather than dismissing feedback; suggests designers 'used to hold the ball for most important text' indicating some awareness of issue
community_signal: Peter Grafl (Deep) revealed as head designer at Zen; communicated via video response rather than live interview due to language barrier and comfort level, indicating communication limitations at organizational level
high · Chris Freebus: 'Deep's not quite comfortable doing a live interaction yet—language barrier and all... we fired off these questions. Deep went ahead and sent back video responses.'
personnel_signal: Zen lacks post-release maintenance workflow; designers move to next project after completion rather than iterating on feedback, contrasting sharply with Stern, Jersey Jack, and Spooky practices
high · Chris Freebus: 'Or maybe it just doesn't fit Zen's design model... once the designer is done with the table, they're moving on to the next table... There's not a maintenance program in place'
product_strategy: Hosts propose specific UX improvements for DMD messaging: make first instance mandatory/ball-held, subsequent instances skippable; implement tournament vs casual gameplay modes with different ROM state handling
medium · Jared Morgan detailed proposal: 'make the first time the info is important, you hold it. And thereafter... now you understand what is happening' and Chris Freebus' tournament mode suggestion with fresh ROM state
product_concern: DMD message timing during critical gameplay moments (especially wizard modes) is cited as recurring frustration across multiple Zen tables (Iron Man example); design rationale provided but community workarounds proposed
high · Chris Freebus describes Iron Man wizard mode where message disappeared before ball could be controlled; Grafl acknowledges but defends current approach as better than always holding ball
sentiment_shift: Community perception of Zen's approach shifting negatively as expectations increase with physical manufacturers (Stern) demonstrating ongoing support model; gap between digital and physical widening
high · Hosts repeatedly contrast Zen's static approach to James Bond/Guardians of the Galaxy receiving major post-release improvements at Stern; frustration evident throughout interview
technology_signal: ROM status carryover limited by technical constraints of integrating legacy Williams/Bally systems; some features implemented (Twilight Zone Power Ball) while others (vault letters, progressive meters) not carried over
high · Grafl: 'Altering original ROMs is extremely difficult... we can easily change only the options that can be found in the ROM's original operator menu.' Hosts note inconsistency across different tables.