A mine is a persistent object with at least three readable states: placed but safe, armed and triggerable, then spent or disarmed. Its location, trigger radius, arming moment, trigger condition, and lifetime must agree across visuals and collision.
Kern places a rune at one fixed point. Its full trigger circle and arming progress appear before collision becomes active.
Autoplay is disabled by reduced-motion settings. Use the timeline to inspect placement, arming, and disarming.
Design placement, arming, trigger geometry, route denial, and cleanup as one stateful rule.
Show the placed object and its complete trigger circle while it is still harmless. A charging rune, color shift, or staged audio can show progress, but every channel must agree on the first dangerous frame.
Drive the light, sound, trigger test, detonation, and cleanup from one mine state machine. Test the player's full body against the displayed radius so the marker never understates the dangerous footprint.
Measure routes around the mine with normal acceleration, camera framing, and any concurrent attack. The mine should deny a meaningful lane without silently removing every supported movement or defensive verb.
A harmless object that suddenly damages turns planning into guesswork. Give arming a readable duration and an unmistakable state change before collision activates.
Players judge the route from the visible perimeter. Include the player's full collision body in tuning, but do not hide extra trigger distance outside the signaled circle.
If the visual goes dark while collision remains, cleanup lies about the arena. End damage and blocking on the same state transition, or clearly show a separate lingering hazard.
Store placed, arming, armed, triggered, and disarmed states with timestamps. Derive visuals, audio, collision, targeting, and removal from that single source of truth.
A center point can clear a circle while shoulders or feet overlap it. Expand the trigger by the player's collision radius during path tests, then keep the visible perimeter honest.
The trigger condition may be contact, proximity, time, or a boss command; the detonation may be instant or delayed. Signal both moments when the player can make a different decision between them.
Lifetime and spawn cadence determine how much arena remains. Set an explicit maximum and a predictable removal rule before combining mines with other lane-denial mechanics.
Kern stakes a patch of the arena with a charged rune and makes that claim visible before it becomes dangerous. Tavi survives by respecting the boundary until the charge fades.
Walking needs generous margins and limited mine count. A dash may cross only when its invulnerability rule says so, while attacks, parries, or interactions can disarm a mine if that counterplay is explicitly signaled.
A mine waits as a persistent triggerable object. A marked-area strike resolves one zone on a schedule, a lingering hazard deals continuous damage inside an active area, and chain explosions hand danger through ordered nodes. Preserve the readable armed state and trigger condition.
Mine Flayer throws claymore mines that can chase the player or circle the room, explode on contact, and disappear after a while. Their persistent objects and readable perimeters make state, trigger, and lifetime central to route planning.
Armored Dock Platform releases AA mines whose red circles show their activation radius; entering that proximity pulls a mine toward the plane. The example tightly couples a visible radius to a specific trigger response.
Rearguard Mines move across the arena from its edges and detonate on contact. This moving variation still preserves a visible object and contact rule, forcing route planning while other attacks compete for attention.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub