A splitting projectile changes from one moving threat into several at a defined trigger. It works when the split point or condition is announced before it happens, the parent and fragments have distinct silhouettes, every fragment route commits at the split, and the player has enough space to clear the complete spread.
Kern charges one large projectile and marks both its split point and the three fragment routes.
Autoplay is disabled by the reduced-motion setting. Use the timeline slider to inspect the split.
Design the parent path, split trigger, fragment pattern, response window, and recovery as one continuous promise.
Signal the trigger through a marker, timer, boundary, impact surface, or vulnerable state. Preview the fragment count and broad directions early enough that the split reads as the promised second part of one attack.
Create every fragment from the same split event and lock its angle, speed, radius, and lifetime there. Test the complete player body against the expanding pattern, not only against the parent projectile.
Keep the fragment pattern visible until it passes the intended response route. Begin recovery only after every child projectile has cleared, so the player can connect the cue, split, and safe result.
A large projectile that suddenly fills the arena with fragments creates memorization rather than anticipation. Reveal the split rule before the first dangerous transformation.
Late steering invalidates the announced gaps. If fragments home, treat tracking as a separate communicated rule with its own cutoff instead of silently adding it to the split.
Destroy or clearly deactivate the parent at the split frame. Overlapping collision volumes turn a readable transformation into an accidental damage spike.
Store the parent route, trigger, split position, fragment definitions, and collision handoff in one immutable plan. Visuals, audio, damage, and previews should all consume that same event.
Make the parent larger, slower, or differently colored than its fragments. A short flash or collapse at the marker helps the eye understand that one object ended and several new ones began.
Angular spacing grows with distance. Tune fragment count and collision radii at the expected crossing depth, including camera projection and the slowest supported movement verb.
Later versions can move the marker, delay one branch, or add a second generation. Preserve the base transformation and change one readable variable at a time.
The split lets one deliberate action unfold into a wider consequence. Kern appears to seed the arena with stored energy, while the visible transformation gives Tavi a moment of recognition instead of presenting unexplained density.
Ordinary movement needs a gap wide enough for the complete body. A block may stop the parent before it splits, a reflect may return the whole payload, and a destroy verb can intentionally trigger or cancel the fragments; choose one consequence and communicate it.
A splitting projectile begins as one projectile and transforms at a specific event. A projectile fan launches many shots directly from one source, a volley repeats releases over time, and an explosion may create area damage without persistent child projectiles. Preserve the parent-to-fragment handoff.
Wally fires a large egg across the screen; at the far boundary it breaks into smaller shell pieces with stable directions. The edge trigger makes the second geometry predictable before the fragments return through the play space.
Grim’s final phase sends fire bubbles that split into four shots when struck. The player-controlled trigger shows why collision feedback and fragment directions must be especially clear when counterplay can create the danger.
Elden Stars uses one prominent parent orb that emits many smaller tracking stars over time. It is a useful 3D variant: parent and children need separate silhouettes, depth cues, and lifetimes when the transformation is continuous rather than instantaneous.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub