Skip to content

Tiny Chaos handoff

Read the agent instructions, roadmap and relevant task. Inspect Git status and live source before changing anything; work may be uncommitted. This page gives current boundaries, not permission to restart earlier work.

Owner preferences

  • Use short, clear sentences and simple words when discussing this project. Use antislop during the session.
  • Work independently without routine confirmations. Preserve existing content, user changes, IDs, saves and recovery data. Do not commit or push without a current request.
  • Do not run real stages for agent tests. Use the short test setup with borrowed appearance; the owner assesses balance and gameplay feel.
  • The owner prefers to test further abilities manually for now. Record their results in the ability checklist; do not start another automated ability behavior test round.
  • The owner will check real gamepad use, keyboard/gamepad remapping and disconnect/re-detection. Simulated input is not physical-device evidence.

Current position

The common gameplay scene, isolated Linux player flow and short Editor test have reached the checks described in project status and testing. Several later fixes and documentation changes may be uncommitted. Do not repeat completed checks without a relevant change.

The owner recalled Archer, Miner, and Zenova as the Stage 1–3 character rewards and clarified that defeating the boss on Medium is the minimum. The references and rule were updated and checked with isolated data; a player-build check remains. See stage character unlocks and the task list for other open work and future proposals.

On 2026-11-03, the special-enemy outline and chest-effect overlap received fixes with passing Linux graphics checks; Unity crashed on shutdown afterward. The test-stage panel gained special-enemy selection and a boss-reward button, with selection/spawning checked. The previous private Linux build is older than these changes. See visual rendering bugs for the remaining player and Windows checks.

Unity and preservation

Before a Unity CLI run, check whether the Editor already has this project open. Capture package/settings bytes, isolate the profile and services, and restore only changes attributable to the run after the Editor exits. Follow the project Unity stabilization skill and other-PC setup. Do not assume temporary paths persist.

On this Linux machine, Unity Hub Editor 6000.2.8f1 received local compatibility libraries so the Editor could start without special environment variables. A graphical Editor launch added Linux toolchain entries to the package files; their pre-launch copies were captured in /tmp/tinychaos-editor-open.cYqxQl/baseline/Packages/ if still present. Do not restore files while the Editor is running; compare first and preserve later user edits. The Hub launch itself still needs the owner's confirmation.

Keep Assets/_Recovery and the archived ability assets. Preserve internal ability IDs, upgrade IDs, reporting codes, authored values and stage/difficulty IDs. Keep final player stat calculations easy to inspect. Revive is an upgrade action.

The earlier handoff preserves historical details, but its first-batch instructions and status are outdated.