An environmental weapon makes a fixed arena device—not the player's ordinary attacks—the authoritative source of boss damage. The mechanic works when the access route, preparation state, aim commitment, and resolved hit are all readable, so operating the arena replaces a normal damage cycle without becoming a hidden interaction.
The fixed ballista, crystal switch, solid cable, and two stone covers are visible from the start. Tavi reaches the switch from 0.55 to 1.30 s, powers it at 1.55 s, then walks around the covers to the ballista by 2.45 s.
Autoplay is disabled by reduced motion. Scrub across 0.55, 1.30, 1.55, 1.65, 2.45, 2.55, 2.85, 3.12, 3.50, 3.68, 4.72, and 5.15 seconds to inspect access, preparation, aim, fire, impact, spent, reward, and reset states.
Define device ownership, access and interruption rules, preparation steps, interaction range and duration, aim commitment, projectile path, damage attribution, spent and reusable states, reset and checkpoint behavior, multiplayer authority, accessibility equivalents, and assertions that ordinary attacks cannot silently satisfy the objective.
Give the arena device a stable ID and make its resolved hit the authoritative cause of progress. Ordinary attacks may control nearby threats or create breathing room, but they must not decrement the same objective unless the lesson explicitly combines rules. Log activation, fire, impact, damage, and objective credit as separate events so a designer can distinguish a missed shot, a blocked hit, and broken attribution.
Compose a readable sequence of access, preparation, operation, and commitment. Specify movement distance, cover, interaction range, hold duration, interruption policy, camera framing, aim limits, and whether another actor can operate the device. Signal every completed prerequisite on both the device and its connection; a newly usable control should never look like unchanged scenery.
On impact, apply one named damage package, show the boss reaction and progress change together, and transition the device to spent, cooling, destroyed, or reusable. Define misses, premature activation, player death, boss movement, repeated input, checkpoint restoration, multiplayer contention, and network authority. Test that reset restores every prerequisite exactly once and cannot duplicate damage.
A generic object with a late interaction prompt turns the mechanic into pixel hunting. Establish the device silhouette, its line of effect, the prerequisite connection, and the route before the player commits; reinforce readiness with geometry, state change, sound, caption, and a stable interaction point.
A long forced animation can convert an authored decision into an uninterruptible cutscene, while delayed or off-screen damage makes ordinary attacks and device fire indistinguishable. Keep entry and exit rules explicit, preserve relevant camera information, and synchronize projectile impact, boss reaction, health change, and device cooldown.
Measure discovery, route travel, preparation, aim, fire, projectile travel, impact, exit, and recovery. The boss pressure pattern must leave a reachable opportunity for this complete sequence or provide interruption-safe checkpoints; shortening only the prompt hold does not repair an impossible route.
Validate player-radius clearance, camera occlusion, approach angles, cover ownership, knockback traps, and the return route. Place the device so the boss and aim line can be understood together, and test the slowest supported movement package without silently requiring a dash or invulnerability upgrade.
Expose inactive, preparing, ready, aiming, locked, fired, hit, and spent states in tools and telemetry. Automated tests should prove that fire cannot precede preparation, the projectile originates at the device, boss progress changes only after impact, the sword remains non-authoritative, and one activation cannot resolve twice.
Separate operator, defender, and aimer roles only when every role has feedback and a recovery path. Alternatives may widen interaction range, reduce hold time, strengthen path contrast, caption readiness, or snap aim to an authored target; they should preserve reaching, preparing, committing, and resolving the device.
Kern's runes have sealed the old machine, but its power stone still answers to the quarry floor. Tavi crosses between two broken pillars, wakes the cable, and turns the ballista toward the elemental. The harpoon cracks one glowing plate, then the machine vents its last charge and becomes inert.
Tavi reaches both stations without a special traversal upgrade and keeps the sword available for surrounding pressure, but the sword never substitutes for the ballista hit. A broad interaction ring, clear cable, stable camera, cancelable operation, and optional aim assist keep the sequence usable without changing its damage ownership.
An encounter-specific tool changes the player's temporary action set and can travel with the player. An environmental weapon remains anchored to the arena and asks the player to reach and operate it. Baited self-hit turns the boss's own attack back onto it; here the authored damage source is a separate device even when the boss pressures access.
Destroying an arena wall turret exposes an electrical point. The Grapple Beam can then connect that point through Draygon, turning fixed room infrastructure into a high-impact damage circuit. The setup is optional, spatial, and visibly distinct from ordinary weapon damage, so the arena itself becomes a tactical resource.
The fixed rocket turret locks onto Chell, while portals redirect its rocket into GLaDOS and detach a personality core. The device, target lock, portal route, impact, and detached core create a legible chain of ownership; direct portal-gun use does not damage the boss by itself.
The phase centers on reaching and activating two fixed ballistae while the Dragon God controls exposed routes. Each machine delivers a large authored damage event and changes the encounter state. The example makes access timing, safe cover, device readiness, and unmistakable impact more important than a conventional attack rotation.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub