studio/marathon
2
0
Fork 0
Code Issues 121 Pull Requests Actions Packages Projects Releases Wiki Activity

Implement substrate layer types (substances, temperature, light, sound, air quality, contagion) #93

New Issue
Open
opened 2025-12-17 03:22:53 +00:00 by siennathesane · 0 comments
siennathesane commented 2025-12-17 03:22:53 +00:00 (Migrated from github.com)
Copy Link

Description

Implement spatial grids or continuous fields for environmental state tracking.

Acceptance Criteria

Scenario: Substrate layers work
  Given world has environmental state
  When substrate layers are implemented
  Then substances can exist at locations (water, smoke, blood)
  And temperature varies spatially
  And light/sound propagate through space
  And air quality affects entities
  And contagion spreads through substrate

Technical Notes

  • Substrate types: Substance, Temperature, Light, Sound, AirQuality, Contagion
  • Spatial representation: grid or continuous field
  • Update strategies: diffusion, decay, propagation
  • Efficient spatial queries for affected entities
  • Substrate affects entity needs and conditions

Size: L (8 points)
Priority: P1
Phase: 5 - World Substrate

## Description Implement spatial grids or continuous fields for environmental state tracking. ## Acceptance Criteria ```gherkin Scenario: Substrate layers work Given world has environmental state When substrate layers are implemented Then substances can exist at locations (water, smoke, blood) And temperature varies spatially And light/sound propagate through space And air quality affects entities And contagion spreads through substrate ``` ## Technical Notes - Substrate types: Substance, Temperature, Light, Sound, AirQuality, Contagion - Spatial representation: grid or continuous field - Update strategies: diffusion, decay, propagation - Efficient spatial queries for affected entities - Substrate affects entity needs and conditions **Size:** L (8 points) **Priority:** P1 **Phase:** 5 - World Substrate
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/audio
Spatial audio engine, sound playback, audio mixing, music systems, 3D audio positioning
 area/content
Art assets, models, textures, audio files, dialogue trees, narrative content, game data
 area/core
Foundation systems, memory management, math libraries, data structures, core utilities
 area/docs
Documentation, technical specs, RFCs, architecture decisions, API docs, tutorials, guides
 area/infrastructure
Deployment pipelines, hosting, cloud services, monitoring, logging, DevOps, releases
 area/networking
iroh P2P, CRDT sync, gossip protocol, network replication, connection management
 area/platform
iOS/macOS platform code, cross-platform abstractions, input handling, OS integration
 area/rendering
Graphics pipeline, Bevy rendering, shaders, materials, lighting, cameras, meshes, textures
 area/rfc
RFC proposals, design discussions, architecture planning, feature specifications
 area/simulation
Agent systems, NPC behaviors, AI, game mechanics, interactions, simulation logic
 area/tooling
Build systems, CI/CD pipelines, development tools, code generation, testing infrastructure
 area/ui-ux
User interface, menus, HUD elements, input feedback, screen layouts, navigation
 dependencies
Pull requests that update a dependency file
 epic
Large body of work spanning multiple features
 rust
Pull requests that update rust code
No Label area/simulation
Milestone
No items
No Milestone v2
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_admin siennathesane
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: studio/marathon#93
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?