Dung Defender
Hollow KnightDung Defender demonstrates ricochet projectile in a 2D encounter. Use a stable reflection rule and a visible impact cue so the next segment can be predicted from the incoming angle and surface.
A projectile changes direction after contacting arena boundaries, making walls part of its future trajectory and extending the threat beyond the initial shot.
Use a stable reflection rule and a visible impact cue so the next segment can be predicted from the incoming angle and surface.
Autoplay is disabled by the reduced-motion setting. Use the timeline slider to inspect the loop.
Tune the signal, commitment, geometry, response, and recovery of a ricochet projectile as one rule.
Use a stable reflection rule and a visible impact cue so the next segment can be predicted from the incoming angle and surface.
Players should anticipate the bounce, move to a region the reflected line will miss, or manipulate the impact point when the system permits it.
The projectile expires after its advertised bounce count or lifetime with a visible fade, so reflected paths cannot remain as unbounded background danger.
Random reflection angles remove the spatial reasoning that distinguishes a ricochet from an ordinary erratic projectile.
If the visible ricochet projectile cue promises a different area or timing, the player cannot carry the learned rule into the next cycle.
Limit lifetime or bounce count, then test speed, collision radius, wall angles, and camera framing across every supported arena shape.
Increase bounce count or add destructible reflectors while keeping the reflection law and projectile lifetime visible.
The projectile expires after its advertised bounce count or lifetime with a visible fade, so reflected paths cannot remain as unbounded background danger.
A projectile changes direction after contacting arena boundaries, making walls part of its future trajectory and extending the threat beyond the initial shot. The encounter uses that rule as a short promise: a visible signal, a committed action, and a result the player can verify.
Players should anticipate the bounce, move to a region the reflected line will miss, or manipulate the impact point when the system permits it. Limit lifetime or bounce count, then test speed, collision radius, wall angles, and camera framing across every supported arena shape.
Random reflection angles remove the spatial reasoning that distinguishes a ricochet from an ordinary erratic projectile. Do not hide that distinction behind extra effects or tracking that the announced rule does not contain.
Dung Defender demonstrates ricochet projectile in a 2D encounter. Use a stable reflection rule and a visible impact cue so the next segment can be predicted from the incoming angle and surface.
Wally Warbles demonstrates ricochet projectile in a 2D encounter. Players should anticipate the bounce, move to a region the reflected line will miss, or manipulate the impact point when the system permits it.
Ziva the Engineer demonstrates ricochet projectile in a 3D encounter. Limit lifetime or bounce count, then test speed, collision radius, wall angles, and camera framing across every supported arena shape.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub