Wind charges are culled on the server #315

New Issue

D4rkr34lm · 2026-04-22T17:43:04+02:00

D4rkr34lm commented

2026-04-22 17:43:04 +02:00

DoD:

When wind charges are within a defined range of each other & especialy on the exact position the client only sees one.
The system uses the same architectural pattern used by the hull hider. Especially the BlockIdWrapper to hide/show entities
Implementation should not conflct with hull-hider based hiding

**DoD:** - When wind charges are within a defined range of each other & especialy on the exact position the client only sees one. - The system uses the same architectural pattern used by the hull hider. Especially the `BlockIdWrapper` to hide/show entities - Implementation should not conflct with hull-hider based hiding

D4rkr34lm added the

System

FightSystem

label 2026-04-22 17:43:12 +02:00

D4rkr34lm self-assigned this 2026-04-22 17:43:17 +02:00

D4rkr34lm commented

2026-04-22 17:57:35 +02:00

Implementation Considerations:

Because of the current way hull-hider hides/shows entities, adding another hider could led to conflicts. We therefore require a middleman between the version dependent hiding and the respective visibility controller
Location implement a proper implementation of hashCode we can therefore use a hash set to dedup in O(n) if we set the margin for dedup to 0 otherwise we need to implement the margin directly into the hashCode or alternatively accept a O(n²) runtime - Questioning users & bench marking is required before deciding on final accepted solution

**Implementation Considerations:** - Because of the current way hull-hider hides/shows entities, adding another hider could led to conflicts. We therefore require a middleman between the version dependent hiding and the respective visibility controller - Location implement a proper implementation of `hashCode` we can therefore use a hash set to dedup in O(n) if we set the margin for dedup to 0 otherwise we need to implement the margin directly into the `hashCode` or alternatively accept a O(n²) runtime - Questioning users & bench marking is required before deciding on final accepted solution

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SteamWar/SteamWar#315