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

Implement behavior tree outcome synchronization #117

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

Description

Fast-changing behavior trees sync outcomes, not state.

Acceptance Criteria

Scenario: Behavior outcome sync works
  Given entities are owned by different peers
  When behavior tree executes
  Then outcome is synced (action completed, position updated)
  And intermediate state is not synced
  And sync latency is <100ms
  And all peers see consistent behavior results

Technical Notes

  • Outcome types: movement, interaction, state change
  • Sync strategy: deterministic schedule + outcome sync
  • Determinism: schedule generation is deterministic, behavior tree evaluation is deterministic
  • Desync detection: periodic state hash comparison
  • Reconciliation: if desync detected, re-sync from owner
  • Ownership determines authority: owner's outcome is truth

Size: M (4 points)
Priority: P0
Phase: 12 - Networking & Sync

## Description Fast-changing behavior trees sync outcomes, not state. ## Acceptance Criteria ```gherkin Scenario: Behavior outcome sync works Given entities are owned by different peers When behavior tree executes Then outcome is synced (action completed, position updated) And intermediate state is not synced And sync latency is <100ms And all peers see consistent behavior results ``` ## Technical Notes - Outcome types: movement, interaction, state change - Sync strategy: deterministic schedule + outcome sync - Determinism: schedule generation is deterministic, behavior tree evaluation is deterministic - Desync detection: periodic state hash comparison - Reconciliation: if desync detected, re-sync from owner - Ownership determines authority: owner's outcome is truth **Size:** M (4 points) **Priority:** P0 **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#117
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?