How RitsuLib Is Organized

Choose An Entry Point

Most mods only need five entry points.

Need	Use
Register models, keywords, epochs, card piles, and top-bar buttons	`RitsuLibFramework.CreateContentPack(modId)`
Patch game methods	`RitsuLibFramework.CreatePatcher(modId, patcherName)`
React to game timing	`RitsuLibFramework.SubscribeLifecycle<TEvent>(...)`
Store JSON data	`RitsuLibFramework.BeginModDataRegistration(modId)` and `GetDataStore(modId)`
Add settings UI	`RitsuLibFramework.RegisterModSettings(modId, configure)`

Use lower-level registries only when you need conditional registration, manifest-style arrays, or integration code shared across several mods.

大多数 Mod 只需要五个入口。

需求	使用
注册模型、关键词、Epoch、卡堆和顶栏按钮	`RitsuLibFramework.CreateContentPack(modId)`
Patch 游戏方法	`RitsuLibFramework.CreatePatcher(modId, patcherName)`
响应游戏时机	`RitsuLibFramework.SubscribeLifecycle<TEvent>(...)`
存储 JSON 数据	`RitsuLibFramework.BeginModDataRegistration(modId)` 与 `GetDataStore(modId)`
添加设置界面	`RitsuLibFramework.RegisterModSettings(modId, configure)`

只有在需要条件注册、数组清单式注册，或要把集成代码复用到多个 Mod 时，才直接使用底层注册器。

RitsuLib’s public API is split by the work a mod author is doing:

Scaffolding.Content supplies templates and builder methods for game content.
Content, Keywords, CardTags, CardPiles, Timeline, Unlocks, and TopBar hold registries.
Data and Utils.Persistence handle mod data.
Settings.ModSettings and Settings.ModSettingsUi build player-facing settings pages.
Patching wraps Harmony registration and diagnostics.
Audio, RuntimeInput, and Ui provide runtime helpers.

RitsuLib 的公开 API 按 Mod 作者正在做的事情划分：

Scaffolding.Content 提供游戏内容模板和 builder 方法。
Content、Keywords、CardTags、CardPiles、Timeline、Unlocks、TopBar 保存注册器。
Data 和 Utils.Persistence 处理 Mod 数据。
Settings.ModSettings 与 Settings.ModSettingsUi 构建玩家可见的设置页面。
Patching 封装 Harmony 注册和诊断。
Audio、RuntimeInput、Ui 提供运行时辅助能力。