Rapier collision queries
Gives collisions, sensors and ray queries distinct gameplay meanings. It connects collider results to stable objects and filters, so a pickup zone does not behave like a wall or create repeated rewards.
rapier-collision-queries
See how it helpsWhen is it useful?
Use it when hits are missing, sensor events duplicate or filters produce unexpected interactions between object categories.
What does it help you do?
- Separates physical collision response from sensor notifications.
- Defines groups, filters and required event activation.
- Converts collider hits into stable gameplay events after removal.
Try asking this
In our stealth game, use a sensor for a doorway alarm and a ray query for line of sight. The player should pass through the alarm, scenery should block vision and removing a guard should not leave query results pointing to a nonexistent character.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Rapier — collision queries
Use when implementing Rapier collision groups, sensors, contact events, raycasts or shape casts.
Version and project gate
Inspect Rust crate features or JS/WASM package and version, 2D/3D choice, framework wrapper version, units, solver settings, timestep ownership, body/collider handles and render synchronization. Determinism depends on binding, version, initialization and operation order. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Define group/filter semantics and which interaction produces solver response versus notification. Read event activation requirements for the binding. Translate hit data into stable game events after considering removal and multiple colliders. Set query filters from gameplay intent.
Deliver
A collision/filter table and query/event integration with explicit event ownership. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A sensor overlap is not a physical contact impulse; missing event flags can look like broken collision detection.
Acceptance scenario
Exercise self-filtering, sensor entry/exit, a removed collider and a fast-moving hit using the appropriate query or CCD approach. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Vector. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md