Interface interaction makes the game boundary part of the encounter: a controller route, microphone, second screen, file picker, camera, or platform panel becomes a deliberate response. The boss proves why the normal verb fails, pauses danger while attention leaves the arena, confirms the result, and provides an equivalent fallback.
At 0.62 seconds, Tavi attacks through channel A and Kern's ward blocks the sword. At 1.28 seconds, combat pauses before focus leaves the arena.
Autoplay is disabled by reduced motion. Scrub across 0.40, 0.62, 0.88, 1.28, 1.65, 2.05, 2.38, 2.72, 3.05, 3.45, 3.78, 4.18, 4.65, 5.05, and 5.35 seconds.
Define the blocked in-world verb, external channel, capability check, consent boundary, safe interaction window, confirmation event, timeout, cancellation, fallback route, retry state, platform parity, privacy limits, accessibility, and telemetry.
Show the boss reading, mirroring, jamming, or escaping the normal channel before asking for anything external. Keep the failed attempt safe and repeatable, and name the rule through animation, sound, text, and controller-independent status cues.
Enter an explicit interaction state: pause hostile simulation, release held inputs, keep audio intelligible, detect available capabilities, explain data access, and allow cancel or timeout. Never ask the player to unplug hardware, blow into a microphone, open files, or move to another screen while damage continues.
Convert the external action into one deterministic confirmation event, restore focus and controls, show the changed boss state, and run a full combat telegraph. Save a known route for retry and provide a menu, remap, button, or simulated-input fallback with the same timing and reward.
A microphone may be broken, a controller port may not exist, file access may be sandboxed, and motion or camera input may be inaccessible. Detect support before the fight and treat the alternate interface as presentation, not as permission to strand players.
Do not delete files, alter system settings, capture media, or contact a service without informed consent. Use generated safe data, narrow permissions, reversible previews, clear cancellation, and a fully local fallback.
Use ordinary, exception-proved, interaction-paused, route-selected, confirmed, resumed, cancelled, timed-out, and fallback states. Make confirmation idempotent so focus changes, reconnects, and duplicate platform callbacks cannot open the boss twice.
The same fiction can map controller port to virtual slot, microphone to hold input, file picker to a generated archive, or second screen to an in-game panel. Preserve information, timing, consequence, and dramatic reveal even when the hardware changes.
Record capability class, prompt shown, fallback offered, selection, confirmation latency, cancellation, timeout, reconnect, retry, and completion. Never log filenames, audio, images, contacts, or device identifiers unless they are essential, consented, minimized, and protected.
Kern catches Tavi's first sword command in a cyan ward linked to port A. The arena freezes, Tavi routes the command through a second rune socket, and a confirmation seal breaks the prediction. Only then does the duel resume.
Announce required capabilities before commitment, support keyboard, controller, touch, assistive remaps, silent microphone simulation, no-camera mode, sandboxed sample files, and a conventional menu fallback. Pause timers and attacks while focus is outside combat, and never require force, breath duration, precise motion, private data, or system changes.
A control-mode shift changes how ordinary movement or attacks map during live play. An encounter-specific tool still exists inside the game world. Interface interaction deliberately crosses into another input or system surface, then returns one confirmed result to encounter logic.
On the original PlayStation, Psycho Mantis reads player-one inputs and evades attacks; moving the controller to port two removes that advantage. Later releases must virtualize or replace the physical port while preserving the revelation that the boss was reading an interface route.
The original Nintendo DS giant battle routes Bowser's fire breath through the microphone, and the moving Fawful Express makes that channel central to the damage race. The 3DS remake replaces the microphone action, illustrating why platform-equivalent fallback belongs in the design from the start.
The Archivist opens a file-selection surface: file size becomes damage weight, and an old file becomes a powerful hostage card. The encounter uses real metadata for fiction, but its implementation avoids actually deleting the selected file, a crucial boundary for safe external-interface play.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub