Unity-Kampfphysik

Combat Physics and Hit Detection

Inspect Unity version, 2D versus 3D physics, fixed step, time scaling, layers, movement authority and actual projectile speed/size. State what counts as one hit and who may apply damage.

• Reproduce tunneling at the real speed and thinnest intended collider. Start with the existing collision mode; choose supported continuous detection or a swept query when measurement warrants it. CCD is not a guarantee for every body shape, trigger or moving target.
• Physics movement and forces belong to their simulation contract. Avoid render-frame-dependent impulses and direct transform writes that compete with a simulated Rigidbody. Evaluate interpolation separately from authoritative collision.
• Use explicit query masks and trigger policy. Filter the shooter, allies and already-hit targets according to the mechanic. Resolve a collider to the owning damageable entity so a multi-collider actor is not damaged repeatedly by one intended hit.
• For pooled projectiles, reset hit registries, velocity, lifetime, ignored collision pairs, ownership and delayed callbacks. A callback from a previous lifetime must not affect a reused projectile.
• Bound non-allocating query buffers and handle saturation; a full buffer is not proof that all hits were returned. Do not assume unsorted query results are distance ordered.
• Diagnose fixed steps per frame and catch-up spikes before shrinking the fixed timestep. Check collision callbacks, queries and allocations at representative projectile counts.

Verify thin-wall hits, moving targets, repeated contacts, pause/slow motion, pooled reuse, friendly-fire rules and a dense encounter. Record observed misses and CPU cost; do not claim universal CCD reliability.

Reference: the project-version Unity physics manual. The upstream skill's helper scripts and performance numbers are not installed or independently verified here.