Soul Master
Hollow KnightSoul Master crosses the arena with four evenly spaced orbs rotating around him, then the pattern returns. The fixed spacing turns boss translation and orbital motion into one learnable moving gate.
Orbiting projectiles remain bound to one center while their positions rotate. The rule works when the anchor, radius, direction, angular speed, and spacing are readable before contact, every projectile keeps the committed formation, and a reachable gap or inner pocket remains available.
Kern reveals five projectiles, one fixed radius, equal spacing, and the clockwise direction before collision activates.
Autoplay is disabled by the reduced-motion setting. Use the timeline slider to inspect the orbit and crossing.
Design the orbit, spacing, entry route, active rotation, and recall as one continuous spatial rule.
Show the anchor, complete radius, direction, projectile count, and spacing together. A player should be able to predict every occupied position rather than infer the rear half after it arrives.
Lock radius, angular speed, direction, and relative spacing when collision begins. Check each projectile body separately so the safe gap shown by the signal matches the gap used by collision.
Sweep the full player body through the intended route over time. Leave enough angular and radial clearance to follow a gap, enter a pocket, or remain outside without requiring an unstated dash or invulnerability window.
Showing only the nearest projectiles hides count and spacing. Reveal the entire formation or use a persistent orbit guide before the active rotation.
Unannounced contraction or expansion erases a planned pocket. Treat a radius change as a new signal and commitment instead of silently modifying the active rule.
Large hidden hitboxes turn a readable opening into a trap. Test projectile radius plus the player’s full body and keep effects from obscuring the true clearance.
Represent anchor, radius, base angle, angular speed, direction, count, projectile radius, and activation time once. Derive rendering and collision from that same state.
Compute edge-to-edge clearance between neighboring projectiles, not only their center angles. Compare it with the player diameter and movement available during the crossing window.
If the boss moves, decide whether the formation follows rigidly, lags, or remains world-anchored. Signal that relationship because it changes every future projectile position.
Later variants can reverse direction, add a second radius, or release selected projectiles. Give each change its own cue so the learned base orbit still supports prediction.
An orbit makes Kern feel like the stable center of a rune system rather than a source of disposable shots. The ordered formation gives Tavi a visible moving boundary that can be understood before it must be crossed.
Basic movement can follow a wide gap or stay beyond the perimeter. A dash can cross a narrower opening, while block, parry, or projectile destruction may remove one body; state whether the remaining formation closes the gap or preserves its spacing.
Orbiting projectiles stay bound to an anchor while their positions rotate. A ring volley launches outward, a spiral barrage expands along a path, and rotating beams create continuous radial segments. Preserve the persistent anchor and discrete spacing.
Soul Master crosses the arena with four evenly spaced orbs rotating around him, then the pattern returns. The fixed spacing turns boss translation and orbital motion into one learnable moving gate.
Dark Energies form rotating arms around Ceaseless Void. Repeated spacing and a stable center show how a larger orbital formation can establish a phase-wide movement rhythm instead of reading as unrelated bullets.
Gabriel materializes light swords that orbit him as a temporary shield. The first-person view shows why a 3D orbit needs a strong anchor and silhouette: depth and camera motion can otherwise hide the spacing on the far side.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub