claude-haiku-4-5-20251001 · $0.019
D&D Pro gameplay stream reveals ball-trapping bug and WiFi issues during extended session.
Ball became wedged behind the dragon's ramp mechanism after multiball mode glitched
high confidence · Wild Dog Arcade hosts discovered the ball visually stuck behind the dragon during physical inspection of the playfield
The gelatinous cube multiball mode has rules display clarity issues, with confusing on-screen instructions about shot requirements
high confidence · Hosts expressed confusion about conflicting on-screen prompts for shot requirements during gelatinous cube multiball activation
Code version .89 is currently running on this D&D Pro unit
high confidence · Host explicitly stated '.89 is the code right now' during service menu inspection
The game's ball-search routine continues even when a ball location is uncertain, not recognizing missing balls properly
medium confidence · Hosts noted the machine kept searching for a ball that may have been lost, continuing the search even after reboot
WiFi connectivity issues stem from Stern's use of 2.4 GHz routers with poor range
medium confidence · Host commentary suggests Sam Stern (speaker's reference) uses 2.4 GHz wifi that fails to reconnect if initial connection attempt fails
“It's behind the dragon! It's way in there.”
Wild Dog Arcade host@ 12:32 — Discovery of the mysteriously stuck ball location that became the central focus of the gameplay session
“Maybe that's what it was. The dragon ate the ball.”
Wild Dog Arcade host@ 11:36 — Humorous acknowledgment of the unusual ball-trapping phenomenon behind the dragon mechanism
“I don't remember ever reading that in the forums, but now we have video evidence of it. Dragon pooping pinballs. Exactly.”
Wild Dog Arcade host@ 13:27 — Recognition that this mechanical failure mode may be undocumented in the community
“The trough doesn't look full.”
Wild Dog Arcade host (co-host)@ 5:56 — Physical evidence that at least one ball was unaccounted for in the machine's ball storage
“I'm just not seeing where the ball is even. That's why I'm believing if we restart it, it will just forget that it's looking for it because it never was lost to begin with.”
Wild Dog Arcade host@ 7:49 — Hypothesis about code behavior when ball-tracking becomes corrupted
community_signal: Novel ball-trapping mechanics discovered during extended play; hosts intend to document and share findings with community via video
high · Hosts stated intent to create video montage and document dragon ball-trapping phenomenon for YouTube; recognition that this is undocumented
design_philosophy: Gelatinous cube multiball mode has confusing on-screen rule text with contradictory shot instructions
high · Hosts expressed explicit confusion about conflicting screen prompts; one prompt says 'hit teal shots to start' while another says shots are already qualified
product_concern: Scoop ball-return trajectory inconsistency; balls sometimes don't reach sufficient height to trigger gelatinous cube magnet capture
medium · Host noted that inconsistent ball exit from scoop prevents proper cube magnet engagement
product_concern: Ball-trapping behind dragon mechanism represents undocumented mechanical failure mode; ball becomes physically inaccessible during normal gameplay
high · Ball discovered wedged behind dragon ramp after multiball mode; hosts note this may be undocumented in community forums
technology_signal: WiFi connectivity using 2.4 GHz routers exhibits poor reconnection behavior; fails to retry connection if initial attempt fails
medium · Host commentary suggests WiFi stops working after service menu reset and doesn't reconnect automatically
youtube_groq_whisper · $0.053
technology_signal: Ball-search routine fails to properly track/recover from lost balls; machine continues searching after ball is physically unrecoverable
medium · Machine displayed ball-search behavior even after ball was determined to be wedged; unclear if code recognizes the loss condition