Games
Anime Aggressors
DEVELOPMENT BUILD
STAGING_WORKER
Development web build of draft ref v4/dual-form-power-roster. The Godot payload is loaded same-origin from a dedicated runtime prefix. It is not accepted main.
What is this?
PvP arena game. This staging Worker loads a development Godot web export through an R2 binding. The wasm file is not a Worker static asset.
Why does it exist?
It gives this repository a public web surface inside the gunnchOS ecosystem and a development boot path that stays inside the Worker asset limit.
What can I actually do with it today?
- Open the development build
- Open the source repository
What technology is inside it?
Classification HEAVY_ASSET_EXTERNAL_RUNTIME_SURFACE. Development source 11eb8a420c1f9777fe2555d64bdaf718c3955299. Accepted main remains 72e5dada4e557b42b6abb8c85f218f0a5b3d2e35. Godot 4.5.2 Web preset, threaded, with cross-origin isolation headers.
What evidence exists?
Source repository. Runtime identity is at /runtime-manifest.
What is not finished?
- Draft creative branch v4/dual-form-power-roster is not accepted main
- This is a development build, not a release
- Story is the in-product skeleton, not a finished campaign
Where does it fit in gunnchOS?
Family: Games. Return with the gunnchOS link in the header.