Fusion Garden Defense
Browser game
Current build
This development note documents Fusion Garden Defense runtime v1.0.2, deployment build Fusion-Garden-Defense-v1.0.2-Q00P, release ID 20260819171316-pu0z5l6zcprvvchs. The package archive SHA-256 is f931d19ab77889ff9670e251d1ea97017108dd318a239a14f9d7ca3e81dfa9b4 and the release was validated on August 19, 2026.
The design is an ammunition factory first
The current runtime explicitly describes the game as an active ammunition-factory defense game, not an idle game. Four feeder ports produce ammunition into six reservoirs. MIX consumes different base elements to create hybrid rounds, RELEASE sends a manual salvo, and Overdrive provides a charged emergency action.
That structure is why the player is given a preparation state between assaults. The design goal is not constant firing; it is deciding when to build supply, when to change feeder output, when to fuse, and when to spend stored ammunition.
What is in the 1.0.2 package
The packaged README records:
- Five stages with escalating waves and a boss encounter.
- Four feeder or plant classes with upgrades.
- Six hybrid recipes and ten ammunition types.
- Manual salvo release, Overdrive, quests, progression, and save data.
- Touch and pointer controls, fullscreen, pause, and sound.
- Local PNG plant, enemy, projectile, VFX, UI, and core assets.
The static package keeps index.html, foundry.js, and the local assets together. It requires no Node.js build step, CDN, or external runtime dependency to launch the game.
Progression and save boundaries
The game saves persistent progression with browser localStorage under q00p_fusion_garden_defense_v100. The saved object tracks the highest unlocked stage, selected stage, sound state, tutorial state, total wins, and total fusions.
Current-wave enemies, reservoir contents, and the exact live factory layout belong to the running session rather than the persistent progression record. That separation keeps the permanent save focused on unlocks and preferences.
Package and asset accountability
The Q00P build manifest inventories the package files and hashes. The software license identifies the HTML, CSS, JavaScript, runtime systems, rules, progression logic, and interface implementation as Q00P build materials.
Bundled image assets are documented separately in the package provenance and asset notes. This development note therefore describes the runtime and packaged asset structure without making broader authorship claims about visual reference material beyond what the rights records support.
Evidence scope
This note is based on the current packaged runtime, README, manifest, license, provenance files, and source behavior. It does not invent browser/device test results that are not present in those records. Separate compatibility verification can be added when that testing is actually performed.
Publishing the build record gives Fusion Garden Defense a traceable development history: players can see which factory loop, save behavior, package structure, and release identifier the current Q00P page refers to.