Repository navigation
Conversation
The design document of the roadmap's area MN, written from the code: how a monster or NPC reaches the client (0x13, 0x1F, 0x45, 0x68, the cinematics), its numbers, names and kind, its setup at spawn, its models, animation speeds and sounds, which animation an attack or a skill plays (MonsterSkill.bmd and the hard-coded map handlers), death, idle and movement code, the NPC talk rules, and what OpenMU knows about monsters. It decides D44-D60 (monster and model entries in Data/Monsters/Monsters.json and Models.json, attack animations by skill number, names by language, editing a running game, the monster tools sharing one selection), lists the problems found on the way (P1-P19), the verification with a monster recorder, and the phases MN1-MN9 with MN-B on the OpenMU side, grouped into three pull requests now and three later ones. All 15 questions were answered. The roadmap links it: the MN row, the model list per area (decided), the "later" area gets NPC dialogues and quests, a read-only "what a skill uses" view for SK1, and the shared tool basics of the editors.
Owner
Author
|
Upstream merged the design as sven-n#848; closing the fork PR without merging (fork main mirrors upstream). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The design document for area MN (Monsters and NPCs) of the data-driven content roadmap, written from the code:
docs/superpowers/specs/2026-10-23-data-driven-monsters-design.md. Documentation only; no code changes.Monsters and NPCs become data like the items: a monster entry per number (names in every language, kind, model, setup at spawn, which animation each skill plays, NPC talk rules) in
Data/Monsters/Monsters.json, model entries (file, textures, animation speeds, sounds, bounding box, weapon bones) inData/Monsters/Models.json, and focused MuEditor tools that share one monster selection (browser, setup, attacks, model, preview with an animation preview, translations, checks).What the document covers
CreateMonsterwith its 269 cases and the map creators,OpenMonsterModel/OpenNpc(519 speed overrides, 387 sound loads), the attack animation handlers andMonsterSkill.bmd(only 20 of its 56 monsters are ever read), death, idle and movement code, NPC talk rules, and what OpenMU knows (489 numbers, names, kinds, event skills).none,otherwise,clearSkill) instead of the BMD's positions; names follow the UI language; edits reach the running game; the monster tools use the shared editor undo.Pull requests planned
Roadmap
The roadmap links the design (MN row), records the model list per area as decided, adds NPC dialogues and quests to the "later" area, a read-only "what a skill uses" view to SK1, and the shared tool basics of the editors.
How it was checked
Two review rounds over seven areas (spawn, data files, rendering, attacks, OpenMU, editor and tests, the document's own claims), every finding checked by a second reviewer, a completeness check, and a final check of consistency, facts and coverage. All 15 open questions were answered on 2026-10-23.