Package Factory Game runtime sprites for browser and container builds #60
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/factory-game-v3#60
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #59. The accepted factory sprites now load from the factory_shell crate asset root in the local Bevy viewer, and the Wasm target compiles against those handles. Browser delivery remains intentionally out of scope for that integration.\n\nAcceptance criteria:\n\n- Trunk output includes the seven runtime sprites under the URL layout expected by AssetServer.\n- The container image copies and serves those files with suitable cache behavior.\n- Browser rendering preserves the native colored fallbacks when an asset request fails.\n- The packaged browser viewer is verified for ground, truck, iron deposit, foundry, iron ore, and iron bars presentation.\n- Existing deployment ownership and exposure boundaries remain unchanged.