diff --git a/planning/PLAYWRIGHT-TODO.md b/planning/PLAYWRIGHT-TODO.md new file mode 100644 index 0000000..24bd21e --- /dev/null +++ b/planning/PLAYWRIGHT-TODO.md @@ -0,0 +1,30 @@ +# Deferred Playwright coverage + +The user will manually test each milestone after commit/push. New automated +Playwright tests and routine local suite runs are deferred to conserve resources. +Keep existing tests; this decision does not modify CI, required type/build checks, +or Go lifecycle tests. Revisit this backlog when the user asks to resume browser +automation. These are future tasks, not completion gates for the current milestones. + +- [ ] Review existing browser tests against the agreed lifecycle and travel rules. +- [ ] Content editors: validation, version conflicts, permissions, and previews. +- [ ] Esc closes only the focused menu and restores focus without gameplay input. +- [ ] Terrain/jumping/camera, gathering requirements, yields, and profession panels. +- [ ] Melee/ranged targeting, cross-chunk mobs/projectiles/AoE, loot, and admin spawns. +- [ ] Equipment attachments, animation transitions, and sound settings/event playback. +- [ ] Hub-instance switching, admission limits, escape items, and victory portals. +- [ ] Craft discovery/valid failure, materials, quality rolls, and maker/world labels. +- [ ] Hub crafting records discoveries and consumes resources with every XP track unchanged. +- [ ] Spell books/ranks/unlocks, weapon abilities, rebinding, and controller flows. +- [ ] Corpse resurrection after looting; rejection after replacement/world destruction. +- [ ] Structures and house placement, keys/guest permissions, storage, and recovery UI. +- [ ] Last-key three-second deletion and recovery before the death-world deadline. +- [ ] Cosmetics: ordinary drops, house placement, push/pull, and entitled/unentitled pickup. +- [ ] Character creation, desktop/mobile layouts, and keyboard focus/accessibility. +- [ ] Event start/cancel/status, swarms, announcements, and Harbinger scheduling. +- [ ] Dungeon portal entry, population limits, completion/reset, and exit handling. +- [ ] Trade, chat, parties, and guilds after their individual scopes are agreed. + +Use [SYSTEMS-ROADMAP.md](SYSTEMS-ROADMAP.md) for the milestone order and detailed +acceptance scenarios. When automation resumes, prioritize fragile user flows and +previously reported regressions; do not duplicate server tests in the browser. diff --git a/planning/SYSTEMS-ROADMAP.md b/planning/SYSTEMS-ROADMAP.md index aefb633..96f44fe 100644 --- a/planning/SYSTEMS-ROADMAP.md +++ b/planning/SYSTEMS-ROADMAP.md @@ -506,36 +506,56 @@ player announcements. Never restore a lost world through a timing edit. Admin healing does not revive dead characters or reset their daily allowance. Announcements are an in-game feature proposal; no external messages are sent by this plan. -## 10. Proposed implementation sequence +## 10. Agreed milestone order and handoff -Each phase should produce one playable, reviewable slice before expanding its -content library. These are dependency-based phases, not time or capacity estimates. +This replaces the earlier proposed order. Each milestone produces a reviewable +slice, followed by commit/push and a user testing handoff. These are dependency-based +milestones, not time estimates or new tested-capacity claims. -| Phase | Deliverable | Exit criteria | +| Milestone | Deliverable | Review/playtest focus | | --- | --- | --- | -| 0. Agree rules | Resolve the decisions below; define progression and content schemas | Examples for success, failure, death, and transfer are agreed | -| 1. Authoring foundation | Versioned definitions, asset references, reusable requirements/effects, previews | Bad references/edits rejected; existing saves load unchanged | -| 2. World and gathering | Initial biome, resource editor, three gathering professions, terrain/camera/jump baseline | Higher-tier node gates correctly; rewards/respawn survive reload; movement matches terrain | -| 3. Combat and creatures | Melee/ranged contract, navigation, mob/spawn/loot editors, animated test combat | Mobs/projectiles/AoE work across chunks; no duplicate loot; measured crowded encounter | -| 4. Crafting and building | Hidden recipes, nine professions, difficulty/failure curves, random stats/provenance, persistent structures | Valid-recipe feedback; no rerolls on retries; items conserved; structures survive restart | -| 5. Spells and abilities | Spell books/ranks/unlocks, weapon proficiency, effects, rebinding/controller support | Use-to-progress and targeting work; unlock cycles and XP exploits covered | -| 6. Live operations | Spawn/swarm/event tools, announcements, Harbinger scheduling, expanded healing | Audited retry-safe commands; event resumes/cancels correctly after restart | -| 7. Presentation completion | Simple creator, account cosmetics, animation/sound library, visible gear and camera polish | Rig compatibility, cosmetic entitlement/transfer rules, and input UI checked | -| 8. Survivor expansion | Hub instances/travel, escape items/victory portals, key-owned housing, portal dungeons | No hub/housing XP; travel, timed deletion/recovery, and instance lifecycles preserve ownership | +| 1. Lifecycle and ownership | Define durable resurrection, travel/hub instances, account entitlements, house keys/recovery, and XP policy | Agreed state transitions and migration boundaries; preserve current saves | +| 2. Content foundation | Admin definitions, reusable requirements/effects, validation/versioning, and input actions | Publish valid definitions, reject invalid changes, focused-menu Esc behavior | +| 3. Terrain, movement, gathering | Hills/valleys/forests, biomes, jumping, closer camera, resources, three gathering professions | Movement/terrain agreement, resource requirements/yields/respawn, profession XP | +| 4. Combat and mobs | Melee/ranged combat, navigation across chunks, projectiles/AoE, mob/spawn/loot editors | Targeting, damage, chunk crossings, loot, basic Control spawning | +| 4.5. Models and action presentation | Model rigs, equipment attachments, animations, sound hooks | Compatible rigs/slots, locomotion/attack/gather animation, action/outcome sounds | +| 5. Playable hub travel | Hub instances/switching, survival-world entry, escape items, Harbinger victory portal | Admission, escape restrictions, single character/item ownership, hub XP restrictions | +| 6. Crafting and item quality | Recipe discovery, nine professions, failure/refund curves, random stats, crafter provenance, hub crafting | Valid-recipe feedback, resource use, quality/provenance, discoveries without hub XP | +| 7. Spells, abilities, resurrection | Spell books/ranks/unlocks, weapon proficiency, corpse revival, full bindings/controller targeting | Use-based progression, effects, resurrection constraints, input usability | +| 8. Building and housing | Destructible world structures, house instances, keys, permissions, storage, timed deletion/recovery | Persistence, ownership, navigation changes, guest access, three-second deletion and recovery | +| 9. Cosmetics and customization | Simple character creator, account cosmetic application, furniture exceptions, presentation polish | Entitlements, appearance compatibility, drop versus placement/push/pickup | +| 10. Dungeons and social expansion | Portal instances and lifecycle; separately scoped communication, trade, parties, guilds | Instance population/reset/exit rules, item exchange, membership and permissions | -Asset conventions and basic action bindings begin in phase 1, even though their -full player-facing scope lands later. Phase 2 terrain choices must inform phase 3 -navigation. Phase 3 provides structure-aware navigation hooks; phase 4 completes -them with real buildings. Phase 3 tests AoE using simple effects before the full -spell progression UI exists. Phase 6 depends on the mob/effect foundation and can -move ahead of phases 4/5 if live admin tools are the higher priority. -Cosmetic definitions and account entitlement boundaries belong in the phase 1 -design. Player/equipment cosmetics can land in phase 7; the placed-furniture -exception needs phase 8 housing and its distinct placement/movement/pickup actions. +Model rigs, equipment attachments, animations, and sound hooks are explicitly +deferred from milestone 2 to **4.5**, after combat/mobs and before hub travel. +Milestones 3 and 4 use existing assets/placeholders as needed. Milestone 2 may +retain basic asset references in content definitions without building the rig, +attachment, animation, or audio systems early. -Resurrection gets a separate implementation gate after its detailed lifecycle is -specified; the agreed corpse/item/spell rules do not turn ordinary healing into -revival. Housing also needs key-deletion/recovery semantics agreed before coding. +Admin editors arrive alongside their gameplay systems. Basic spawn/heal/message +tools can arrive early; swarms and staged events follow combat/navigation/effects. +Keep event persistence, cancellation, rewards, and Harbinger scheduling in that +live-operations scope rather than dropping them from the revised order. + +Milestone 1 defines ownership boundaries; it does not implement every later system. +Milestone 3 terrain informs milestone 4 navigation. Combat exposes the obstacle +hooks that milestone 8 structures use. Cosmetic account boundaries are designed in +milestone 1, while player/furniture application follows the rig and housing work. +Resurrection and housing require their remaining lifecycle details to be settled +before their respective implementation milestones. + +At the end of **every milestone**: + +1. Complete the relevant required checks and review the scoped diff. +2. Commit and push the milestone; report the commit and push outcome. +3. Provide a short manual checklist, where to find the feature, and known limits. + For a foundation milestone, state clearly which parts are not yet playable. +4. Hand back to the user to test the build. Resume the next milestone after their + feedback or instruction to continue; address reported milestone defects first. + +Do not combine multiple milestones into an unreviewed batch. Automated Playwright +test authoring/runs are deferred as described below to conserve resources. This +planning update itself does not start milestone implementation. ## 11. Decisions to resolve together @@ -564,14 +584,23 @@ creator scope and asset sourcing. Keep these open rather than inventing final tu ## 12. Validation and completion policy -For each implemented slice run the repository checks (`npm run check`, `npm run -build`, and `go test ./...` in `server`), plus focused browser and lifecycle tests -appropriate to the changes. Generate protocol bindings through `npm run generate`. -Test progression, consumption/rewards, restart, retries, death, daily cap, and -survivor transfer together. Use representative load scenarios for dense mobs, -projectiles, areas, structures, and animations before changing capacity claims. +The user will manually playtest each pushed milestone. Defer automated Playwright +test authoring and routine Playwright suite runs to +[PLAYWRIGHT-TODO.md](PLAYWRIGHT-TODO.md); retain existing tests. This does not change +CI configuration or remove server lifecycle coverage. -New design examples to turn into acceptance tests when implemented: +For each implemented slice still run the required repository checks: `npm run check`, +`npm run build`, and `go test ./...` in `server`. Add focused server tests for lifecycle +changes, especially consumption/rewards, restart, retries, death, daily cap, and +survivor transfer. Generate protocol bindings through `npm run generate` when needed. +Avoid repeated checks without a relevant change or failure. Documentation-only +milestones need document/diff validation, not a gameplay test run. + +Keep representative load testing as a requirement before increasing capacity claims; +manual playtesting does not establish crowded-world capacity. + +Acceptance scenarios for server coverage where applicable and the user's milestone +playtest checklists; browser automation versions are deferred to the TODO list: - A looted corpse revives with only its remaining items; an empty corpse revives with none. A destroyed world or replacement character makes revival ineligible. diff --git a/planning/VISION.md b/planning/VISION.md index 4ce1b98..e537013 100644 --- a/planning/VISION.md +++ b/planning/VISION.md @@ -166,6 +166,11 @@ Tracked across: - Networking: is node size (128x128x128) fixed/final, or a placeholder for tuning? ## Backlog +- Follow the agreed milestone order and handoff in the systems roadmap. Model rigs, + equipment attachments, animations, and sound hooks are milestone 4.5. Commit and + push after each milestone, then hand off for the user's manual playtest before + continuing. Playwright automation is deferred in [PLAYWRIGHT-TODO.md](PLAYWRIGHT-TODO.md); + required type/build checks and Go lifecycle tests remain in place. - See [Systems roadmap](SYSTEMS-ROADMAP.md) for the September 8 draft covering gathering professions, biomes, mobs, crafting, terrain, combat, spells, abilities, structures, survivor hubs, presentation, social systems, and live administration.