flame-engine / flame-engine/flame
ShapeHitbox.allowSiblingCollision could be moved into broadphase
Open
enhancement
- Dominant language
- Dart
- Stars
- 10.8k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 21
Description
# What could be improved
Ideally, we cah check `allowSiblingCollision` at broadphase, before creating unnecesary `CollisionProspect` for siblings pairs. And skip several iterations over "potentials" list later.
# Why should this be improved
A little bit better performance.
# Any risks?
Every broadphase implementation should implement it's unique "siblings check". An interface could be added for that.
Contributor guide
Assessment
This issue has not been assessed yet.