Game uploads
Authenticated developers can submit browser and mobile game builds through the current upload flow.
Developer platform
Ship games with a QA trail you can inspect.
8Bit Arcade combines game submission, sandbox credentials, DevOps QA reports, and engine integration work in one developer workflow. The platform tools are available now; engine packages remain in validation until their editor smoke tests pass.
Available now
Platform-owned developer workflow
These capabilities are part of the current authenticated developer experience. Sign-in is required for credentials, reports, and submissions.
Sandbox credentials
Create scoped credentials for development, run API smoke tests, and configure webhook endpoints.
DevOps QA reports
Store heuristic, platform-model, or local Ollama reports with findings, evidence, and report history.
Feedback capture
Record useful, not-useful, and corrected feedback so QA output can be reviewed and improved.
In validation
Engine integration readiness
Engine clients stay thin: they capture local evidence and can run local Ollama inference, while the platform owns authentication, storage, reports, feedback, and analytics.
UE5
Editor smoke pendingNative editor tab, snapshot and log capture, local Ollama import, and feedback actions are wired.
- Evidence
- UE 5.7 Win64 BuildPlugin package compile plus fixture checks
- Remaining blocker
- Editor tab smoke with a sandbox credential on the target machine
Unity
Editor smoke pendingUPM package, editor window, scene snapshot and console log capture, plus local Ollama import are wired; CI now stages the package shape.
- Evidence
- Fixture validation plus UPM staging helper checks
- Remaining blocker
- Unity package import, compile, and play-mode smoke
Godot
Editor smoke pendingGodot 4 dock, edited-scene snapshot capture, addon log buffer, local Ollama import, and feedback actions are wired; CI now stages the addon shape.
- Evidence
- Fixture validation plus Godot addon staging helper checks
- Remaining blocker
- Godot editor import and dock smoke
Phaser/Web
Starter-readyBrowser snapshot and console log capture, local Ollama import, and TypeScript smoke coverage are in place.
- Evidence
- CI runs Phaser/Web type-check and fixture validation
- Remaining blocker
- External packaging and production-safe token flow before distribution
GameMaker
Package pendingGML scripts capture debug logs and chain local Ollama inference into the platform report import route; CI now stages the .yymps package shape.
- Evidence
- CI .yymps staging helper plus fixture validation
- Remaining blocker
- GameMaker import/runtime smoke and final .yymps export
Construct
Package pendingBrowser runtime helper, generated Addon SDK wrapper files, and single-global runtime actions can capture logs, run local Ollama, normalize inference, and import the report.
- Evidence
- CI .c3addon staging helper, SDK wrapper checks, Construct smoke, and fixture validation
- Remaining blocker
- Construct Developer Mode smoke and final .c3addon export
Rolling out
Expansion follows validation
These areas are intentionally described as rollout work, not generally available product commitments.
- Broader self-service publishing beyond the current submission workflow
- Repeatable engine package distribution after editor validation is complete
- Commercial terms and expanded developer program access
Ownership
Your game remains yours.
Developers retain ownership of their games, source code, and original assets. A submission gives 8Bit Arcade only the access needed to evaluate and operate the submitted build under the applicable developer terms.
Start with the current workflow