-
-
Notifications
You must be signed in to change notification settings - Fork 10
Spatial Entity Interest Management #321
Copy link
Copy link
Open
Labels
risk: mediumModerate impact, needs focused validation.Moderate impact, needs focused validation.status: help wantedExtra attention is neededExtra attention is neededtype: enhancementNew feature or requestNew feature or requesttype: perfImproves tick time, memory use, or throughput.Improves tick time, memory use, or throughput.
Description
Activity
Metadata
Metadata
Assignees
Labels
risk: mediumModerate impact, needs focused validation.Moderate impact, needs focused validation.status: help wantedExtra attention is neededExtra attention is neededtype: enhancementNew feature or requestNew feature or requesttype: perfImproves tick time, memory use, or throughput.Improves tick time, memory use, or throughput.
Problem
Complexity: Medium-Hard
At high player and entity counts, determining which entities need to be synchronized to which players can become a significant CPU and bandwidth cost.
Proposed change
Investigate spatial entity interest management so players receive updates only for relevant entities.
Potential approaches include spatial subscriptions, region-based tracking, existing entity-tracking improvements, or other mechanisms that reduce unnecessary recipient calculations.
[Implementation Note]
The proposed approach is a starting hypothesis, not a requirement. Profile the existing entity tracking and synchronization path before implementing a new spatial system. Reuse or extend existing Stratum mechanisms where appropriate.
[Acceptance Criteria]
•Entity visibility remains correct.
•Uninterested players do not receive unnecessary entity updates.
•CPU spent determining recipients is reduced.
•Network bandwidth reduction is measurable.
•Entity movement across spatial boundaries is handled correctly.
Alternatives considered
No response
Scope