TASK: Stable Impact-Reactor Activation — GUI Control

OBJECTIVE AND SCORING SCOPE

Configure the 32 designated switches in the supplied Mindustry map to produce a recording containing 60 consecutive seconds accepted by the supplied two-stage sampling checker: the designated Impact Reactor, Power Output: 6300.0, and a visibly full Health bar must be visible in both checked samples of each second.

This is a final-state video task. Its sole scored deliverable is run_recording.mp4, and success is determined only by the supplied video checker. Exact switch strings, operation traces, intermediate-state simulations, reports, screenshots, and preservation of every other building are not additional scoring requirements. The checker does not certify earlier action history or GUI compliance.

HOST SETUP — COMPLETE BEFORE THE AGENT STARTS

The host must provide a Windows machine with Mindustry v159, the native Windows Computer Use plugin, and OBS Studio installed and working. The host also provisions a separate evaluator environment with Python, the packages in requirements.txt, and native ffmpeg/ffprobe executables on PATH. Checker code, assets, reference answers and recordings remain inaccessible to the solver through a separate machine/workspace or enforced OS account permissions. The host verifies this separation from the solver identity before the attempt.

The host loads test.msav once, leaves the game paused with all 32 switches off, and provides these solver-visible inputs:

- switch_index_legend.png: identifies switches 01-32.
- Mindustry_Basic_Reference.md: generic offline game information.
- RECORDING_INSTRUCTIONS.txt: capture and visibility requirements.

The host configures OBS Studio to capture the Mindustry window and produce an unedited, normal-speed MP4. OBS Studio recording is explicitly authorized and is managed by the host. The host starts recording before handing control to the agent, keeps recording through the final verification interval, and stops it after the agent declares completion. The host places the completed capture at:

D:\Benchmark\deliverables\run_recording.mp4

The agent does not install, configure, control, or edit the recorder. If the game, native GUI control, or host recording is unavailable, report an environment blockage and stop; setup must be corrected before a valid attempt is started.

COMPUTER USE

Use the installed native Windows Computer Use plugin. Read its skill and follow its initialization and recovery instructions. Its documented JavaScript runtime is permitted only for plugin setup, window discovery, screenshot handling, and GUI observation/input. Tool discovery may be used to locate the required deferred runtime; absent standalone GUI function names do not establish that the plugin is unavailable.

Use the already-running Mindustry window. If it cannot be controlled, perform the documented recovery once and report NATIVE_GUI_UNAVAILABLE or MINDUSTRY_WINDOW_UNAVAILABLE if access remains unavailable.

OPERATING PROTOCOL

Use rendered game information and the supplied offline documents to choose switch settings. You may pan, zoom, pause/unpause, inspect buildings and resource indicators, read in-game processor code and links without editing them, and toggle designated switches one at a time.

Do not use external solutions, internet searches, save-file parsing, hidden application state, shells, arbitrary code, OCR utilities, or unauthorized automation. Do not manually alter non-switch blocks, processor code or links, simulation settings, or game speed. Do not reload, restart, reset, or open a map copy. These define the intended GUI workflow; this submission does not claim that the video checker independently audits them or assigns separate compliance scores.

COMPLETION AND RECORDING

After configuring the switches, open the designated Impact Reactor information panel and let the game run unpaused at normal speed. Keep the reactor and neighboring battery structures visible together with the readable English panel showing Impact Reactor, Power Output: 6300.0, and a visibly full Health bar.

Maintain that visible state for at least 60 seconds. The authoritative checker first samples every 3 seconds to locate candidate intervals, then samples at each candidate second's start and midpoint. Both fine samples must pass its visual and sampled-motion checks for that second to count; 60 consecutive accepted seconds are required. Frames between the samples are not checked. Recording 65 seconds of the final state is recommended to allow for frame boundaries. Do not change switches during this interval. The qualifying interval may occur anywhere in the recording; earlier inspection, switching, and startup may remain in the video. There is no separately scored startup deadline.

Different runs may use any recording resolution, aspect ratio, or window position, provided the required text and map features remain readable. Keep canvas dimensions constant within each recording. The checker locates them automatically. Prefer a stable view to avoid obscuring the panel. Do not substitute a screenshot loop, alter playback speed, or edit the recording.

Declare completion after the interval so that the host can finalize run_recording.mp4. No text trace, final bit-string file, screenshot, or run report is required for scoring. Reference answers, checker code/assets, and reference recordings are evaluator-only and must not be accessible to the agent.
