Problem
Procedural asset workflows become difficult to trust when preview, export, packaging, and smoke verification live in separate manual steps.
Tool Case Study
AssetForge
A recipe-driven toolkit for generating lowpoly assets, biome layouts, previews, exports, and release-ready packages.
Procedural game asset pipelineProcedural content pipelinePublic repository
Solution
Connected recipe packs, quality profiles, workflow wrappers, and clean-install verification into a reproducible Godot-first content pipeline.
Result
Closed release-hygiene work around patch and stable-candidate packaging with smoke evidence and archive integrity checks.
How it works
01
Asset recipes describe modular low-poly assets, material rules, and export expectations.
02
Sockets, anchor points, attachment points, pivots, origins, and transforms define how modular pieces connect.
03
LOD, collider, and physics proxy outputs are validated through smoke gates and reproducible build checks.
Build proof
Source smoke and clean-install smoke were preserved around release packaging.
Archive integrity and dependency hygiene checks were documented for release readiness.
Heavy 3D/runtime content remains external; the website uses screenshots and case-study diagrams.
Current status
Public repository. This page presents a lightweight case study and links outward for repositories, releases, demos, or heavy artifacts instead of bundling them into the website runtime.
Terminology
socketanchor pointattachment pointpivotorigintransformLODcolliderphysics proxymodular assetprocedural asset pipelinesmoke gatevalidation report
Stack
TypeScriptNode.jsGodot 4.4.1JSON packsSmoke scripts