Ricochet rules and caster-owned marks
An Unreal Engine 5.8 and C++ arena game in development. Its Q projectile ricochets off geometry, applies caster-owned marks and rejects consecutive hits on the same target.
Bencci is my solo Unreal Engine 5.8 arena project in development. Deadeye is a working character name. Its Q ricochets, damages targets and applies caster-owned marks.
The repository is private. I can walk through the implementation and design decisions in an interview.
A ricochet can bring a projectile back into the same target. I wanted geometry and target placement to matter without letting repeated contact with one opponent become the default source of damage.
The projectile remembers its last valid target. Consecutive hits on that target are rejected. A valid hit on another target replaces that history, making the first target eligible again.
Second contact rejected
A becomes eligible again
A wall bounce alone does not make the same opponent eligible again. The player needs another valid target in the route before returning to the first. That makes firing angle, nearby geometry and the positions of other opponents part of planning the shot.
Caster-owned marks prevent one Deadeye using another’s setup without landing Q. One active mark means switching targets gives up the previous setup. I chose that limit to restrain early damage potential and leave room for Evolution scaling.
C++ handles collision and target history. GAS owns ability state, damage, cooldown and mark expiry, with target visuals. Blueprint defaults and ability data expose configuration checked by editor validation.
Cast commitment blocks input-spam cancellation and releases the action lock at launch. Shared GAS state avoids competing cooldown/UI timers. Stable slots keep controls consistent when future ability versions change.
Single-player and two-player listen-server/client PIE checks covered Q damage, cooldown, mark application, expiry and visual feedback.
I tested both consecutive-hit rejection and A → B → A routing in multiplayer PIE.
Planned, not implemented or tested
W bonus damage, E teleport to an owned mark, Evolution and modifiers are planned. Dodging Q denies setup. Marks are intended to signal a possible future follow-up.
Inspired by player-built walls and destructible environments, I plan to explore changing terrain. Player control over angles, routes and safe positions could reduce repeated spatial solutions and map fatigue.