Game Development · Godot. Browse Why Does My Godot Web Build Run in the Editor but Stop in the Browser?, Why Does My Godot Game Work in the Editor and Break in the Web Build?, Why Does My Godot Game Chug When the Screen Fills Up? A Brotato Experiment Has Answers, with requirements, routes and walkthrough steps.
A threaded Godot 4 web export needs SharedArrayBuffer, available only on a cross-origin isolated page in a secure context. Without Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp, or the Progressive Web App service worker workaround, the documentation says the project will not run. Single-threaded export, the default since Godot 4.3, avoids the headers but cannot use threads.
BLAZOWACHO built err Friday for GMTK 2025 in about 12 to 15 hours, entirely in the Godot editor, and tested the HTML export only at the end. In the web build the death loop failed and enemy AI froze. The postmortem gives no root cause, so this article reports the symptoms, keeps the cause open, and adds Godot 4.4 web-export checks.
An independent experimenter ran Brotato on a weak ARM handheld, saw 5 to 10 FPS from around wave 20, failed first with a custom physics server, then rebuilt the test harness and found three small causes: unseparated collision layers, repeated per-frame work, and unbatched blood particles. The FPS gains are the author's own harness results, not official Brotato benchmarks.
