Commit Graph
7 Commits
Author SHA1 Message Date
cthangover ba1b1f8c0e Battle registries are fed by the kernel's assembly consumers
Battle cores, winground listeners and status effect behaviours reach their
registries through ModTypeConsumer subclasses instead of per-mod assembly
lookups and AppDomain rescans, and leave again when their mod unloads, so a
game switch or hot reload never keeps a released mod's types alive.
2026-10-17 21:02:29 +02:00
cthangover bc615c2ddf Resource ownership: battle sounds in, character actions out
- The win/defeat sounds (sounds/battle/winground, deadground) used by the
  battle report move here from visual_novel_core.
- The basic physics actions (attack, defence, stun) are character data
  every mod with characters uses; they move to characters_base.
- depends no longer lists visual_novel_core: the battle platform does not
  use the novel content.
2026-10-17 14:30:33 +00:00
cthangover bbc75eeadd Battle core from the game's settings
BattleCoreRegistry.GetActive: without an explicit battle.set_core the
active game collection's settings["battle.core"] chooses the core (e.g.
card_battle for cthangover and card_novel), then the first registered one.
2026-10-17 14:30:33 +00:00
cthangover 46afb4b533 map ui, skill ui, update skills data 2026-09-29 13:05:41 +03:00
cthangover 8fbac46378 new battle gui 2026-09-28 10:48:04 +03:00
cthangover b5ad139d69 ui stule update 2026-09-26 08:05:11 +03:00
cthangover c286271083 upd 2026-09-24 11:17:02 +03:00