The novel template becomes the intended layering: collection novel_template
lists my_novel_game (its own scenes, scenarios, text), town_pack (reusable
backgrounds and the bar ambience) and the engine. The town entrance and the
home vestibule move from cthangover_game into town_pack instead of being
copied; cthangover_game depends on it. Docs explain how to start a game from
these three layers.
The mod holding the main game's own scenes and story follows the <game>_game
naming rule; further parts stay <game>_<part>, reusable content is <theme>_pack.
Mods are renamed by role (shell2d_base, menu_base, ui_base, live2d_base,
editor_tools, cthangover_story, cthangover_murakami, cthangover_party) and
every reference follows. Engine UI prefabs (dialog, answers, message, game
menu, inventory, map, skills) and their panel entries moved out of the story
mod into the subsystem mods; the card_novel and vn_starter_novel collections
are removed.
Findings of the resource atlas: engine and shell mods took these
resources from the content mod without depending on it.
- Main menu music (Serpent's Lament + the mainmenu playlist) -> base_menu.
- Battle win/defeat sounds -> turn_battle_base; UI sounds close_click and
skip -> interface; card selection effect -> card_battle.
- Journal notification texts (ui/journal/new, updated) -> quests_base;
settings screen texts (settings/*) -> base_menu.
- depends now declares characters_base, items_base and quests_base, whose
resources the content uses.
cthangover
