S14 · Finished Discord UX, maps and art
Implemented components; full stream acceptance is not yet demonstrated.
Current implementation: All 97 actions have Discord form contracts; the browser has thirteen sections and several visual build editors.
Outstanding acceptance: Desktop/mobile observation, remaining JSON editors, full art/text review and broad accessibility remain open.
The four requirements below preserve the original release target. Their historic baseline is not used as a current completion score. This page does not mark the entire stream complete merely because related components are installed.
Reference
| Requirement | Required deliverable | Acceptance standard |
|---|---|---|
| S14.01 · Complete native journeys for all systems | Design equipment, trees, trade, crafting, exploration, quests, pets, guilds and raids with readable detail and stable back navigation. | Every essential journey works on actual supported Discord clients; advanced costs are inspectable and no reference card impersonates an action. |
| S14.02 · Bind reviewed sprite and map assets | Inventory the actual asset library, verify rights, define pivots/scale, compose scenes and prepare icons, encounters and emblems. | Every reachable map state has a correct shipped visual or intentional text presentation; no missing sprite, unrelated stock image or fake interaction marker. |
| S14.03 · Finish player-facing writing and terminology | Produce journal, tooltips, NPC scenes, outcomes, tutorial, error messages and public terms from approved definitions. | Mechanical facts survive editing; voice review includes ordinary life and repetition across the corpus, not just keyword filtering. |
| S14.04 · Validate accessibility and notification behavior | Test mobile layouts, text alternatives, readable states, quiet hours, batching, expired controls and reconnection. | No essential cue depends only on color or image position; unavailable message surfaces do not lose a character activity. |