Copperwake

Premise and audience

Run a small copper tug in a storm-damaged port. Hook salvage, read the tide, and deliver awkward cargo through moving harbor traffic.

Build a human-playable browser game. The user delegated the surprise concepts and assigned two builds to Claude Code and two to Codex. This project’s builder is codex.

The first satisfying move

The player cuts thrust before a quay, watches the cargo swing wide, and uses a short opposite push to settle it into the dock. A rope snaps straight, the dock crane lifts the salvage, and the tug gives a low horn. The next contract offers a heavier load and a safer long route.

Core loop

Choose a contract and fitting, study the harbor, attach salvage, tow and manage its swing, dock within the visible speed limit, then spend the earned upgrade before choosing the next job.

Playtime and progression

Target: 20 to 30 minutes for a first clear. This is a design target until playtesting supplies evidence.

Harbor Contracts Challenge and target
Old Quay 3 Attach, settle a light crate, choose a longer safe approach
Salt Works 3 Strong currents, fragile cargo, and moving barges
Breakwater 3 Heavy loads, narrow docks, and alternate tide routes
Outer Sound 3 Combine traffic and cargo handling, then restore the beacon

Twelve contracts target roughly 90 to 150 seconds each, with short optional fitting stops. The first campaign aims for 20 to 30 minutes. A skilled repeat run can finish faster. Include clean-delivery and speed medals as optional mastery goals, not progress locks.

References and lessons

Controls

Keyboard: WASD or arrows apply screen-relative thrust, Space attaches or releases the nearest eligible cargo, Shift brakes. Escape pauses. Pointer and touch: a drag joystick plus tow and brake buttons provide equivalent control. Show the attach radius and selected cargo before input.

Art direction

An illustrated working harbor seen from above. Use painted hull panels, blocky cranes with cast shadows, tide contours, readable striped quays, and a rope whose curve exposes tension. Use a slab-like Georgia title and compact sans instrument labels. Create four distinct harbor silhouettes.

Palette: Deep petrol water #173D48, oxidized copper #BB7448, pale foam #E8DDBD, sea green safe docks #65B7A0, and rust red hazard stripes #D16B52. Give docks and danger areas different patterns.

Use a responsive Canvas 2D playfield with DOM menus and controls. Define the logical board or world dimensions once, transform pointer coordinates through the view, and preserve geometry on resize. Draw a representative active screen before expanding the asset family. Store the approved capture and provenance in this project.

Sound and motion

Layer a soft engine hum with thrust, rope creaks under tension, water on turns, and a brief delivery horn. Add restrained musical layers as contracts become demanding. Route music and effects separately with mute and volume controls.

Scale effects to the action. Make routine feedback brief. Keep decorative motion from masking threats or interrupting player control.

Experience finish list

Browser build

Use native JavaScript with Canvas 2D and Web Audio. Keep editable source in src/game.html and produce dist/game.html with python3 tools/build.py. Embed HTML, CSS, JavaScript, and the game’s own visual and sound assets. Do not require local companion files or a running development server to play the release. Avoid runtime dependencies for this project.

The build should be reproducible and remain under 5,000,000 bytes. The exact dist/game.html must pass local browser checks and then the AOG hosted smoke test.

Relevant skills

Read skills from /root/aog/.agents/skills. Begin with router, then use physics-tuning, input-systems, level-design, game-feel, game-ui-ux, audio-design, save-systems, create-game-assets. Use last-20-percent to inspect the full player experience. Follow stop-slop and deslopify for prose. Load the pinned agents-of-games skill before publication.

Scope boundaries and risk

Out of scope: A port management economy, realistic fluid simulation, open-world sailing, multiplayer, and mandatory repeated contracts for money.

Primary risk: Tow physics could oscillate or make narrow approaches frustrating. Prove one light and one heavy cargo delivery with normal controls before expanding the harbor set.

Verification and release

  1. Build dist/game.html and record its SHA-256. Test that exact file, not an alternate debug build. Keep the final HTML under 5,000,000 bytes as a conservative interpretation of the platform’s 5 MB limit.
  2. Implement the listed build and test commands. Capture actual output and exit codes in verification. A missing script is unfinished work, not a reason to weaken the command.
  3. Run browser tests using the shared Python Playwright installation. Exercise keyboard, pointer, and real touch events. Watch page exceptions, console errors, and failed requests. Verify pause, settings, saved progress, failure, restart, and final success.
  4. Complete the authored campaign using player controls. Read-only state and reproducible action fixtures are acceptable. Direct progress writes, teleports, invulnerability, or hidden solved-state setters cannot stand in for a playable route. Keep action evidence and distinguish complete-run tests from targeted diagnostic tests.
  5. Capture title, opening play, middle play, a difficult late challenge, failure, final success, and narrow and wide layouts. Open and inspect every representative image with an image tool. Record image names and specific findings in verification/REPORT.md. Fix defects and repeat affected checks.
  6. Check the opening, middle, and late game for fair cues and meaningful decisions. Record the intended playtime separately from observed test time. Do not claim a human playtime measurement from a fast automated replay.
  7. Update DESIGN.md with implementation facts. Keep the user’s genre and playtime decisions intact. Explain any meaningful balance or content changes with evidence.

After local verification passes, load /root/aog/.agents/skills/agents-of-games/SKILL.md and follow /root/aog/AGENTS.md for automatic publishing. The user already authorized AOG publishing.

Implementation facts

The source uses an 1100 by 700 logical harbor and Canvas contain scaling. Physics runs at 60 Hz with at most eight catch-up steps. The renderer interpolates the previous and current body positions. A speed cap limits travel to less than two world units per tick. Five projection and collision passes constrain a 66-unit rope and keep cargo outside solid quays. Cargo arrives only inside the handover zone, below 14 displayed knots, with the line released for 0.8 seconds.

The implemented campaign has 24 authored cargo deliveries in twelve contracts, with three contracts per harbor. The contract manifest records the cargo allocation, expected time, actual obstacle, and alternate routes. Each load ends with a crane handover and the next salvage assignment. The final contract supplies power, a counterweight, and the beacon lens.

Storm relief pays for fitting swaps and repairs. The four optional fittings are the bollard engine, harbor fins, fender belt, and long keel. The standard screw can complete the campaign. Each optional fitting trades one handling benefit against a cost. This replaces a money requirement with a free workshop choice, within the brief’s ban on required grinding.

Completion, medals, fitting, audio levels, and motion settings use a validated version-one localStorage record. Storage failure keeps the current session playable and shows a save notice. Retry restores the current contract’s cargo and hull without spending resources. Audio uses original synthesized effects and restrained layered notes with separate music and effects buses.

The 20 to 30 minute first-clear target remains an estimate until human playtesting supplies evidence. Automated control runs prove routes and measure their own elapsed time. They do not establish human first-clear pacing.