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

Implement spatial ownership for substrate #119

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

Description

World divided into chunks, each owned by one peer.

Acceptance Criteria

Scenario: Spatial ownership works
  Given world is divided into chunks
  When substrate state changes
  Then owning peer updates chunk authoritatively
  And non-owners receive chunk state updates
  And chunk ownership is determined by player proximity
  And chunk ownership transfers smoothly

Technical Notes

  • Chunk size: 50m × 50m for balanced ownership
  • Chunk ownership: peer with closest player owns chunk
  • Substrate sync: chunk owner syncs substrate state (temperature, substances, contagion)
  • Border handling: chunks share border state with neighbors
  • Sync frequency: moderate (every 100ms for substrate)
  • Load balancing: ensure even chunk distribution

Size: S (2 points)
Priority: P1
Phase: 12 - Networking & Sync

## Description World divided into chunks, each owned by one peer. ## Acceptance Criteria ```gherkin Scenario: Spatial ownership works Given world is divided into chunks When substrate state changes Then owning peer updates chunk authoritatively And non-owners receive chunk state updates And chunk ownership is determined by player proximity And chunk ownership transfers smoothly ``` ## Technical Notes - Chunk size: 50m × 50m for balanced ownership - Chunk ownership: peer with closest player owns chunk - Substrate sync: chunk owner syncs substrate state (temperature, substances, contagion) - Border handling: chunks share border state with neighbors - Sync frequency: moderate (every 100ms for substrate) - Load balancing: ensure even chunk distribution **Size:** S (2 points) **Priority:** P1 **Phase:** 12 - Networking & Sync
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 v1
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#119
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?