Files

Claude (Chronicler #83 - The Compiler) 29f0127a60 v1.0.3: Fix config read — wrong event bus + section header comments

1.20.1: ModConfigEvent fires on mod bus, not MinecraftForge.EVENT_BUS.
Moved Loading/Reloading to FMLJavaModLoadingContext.getModEventBus().
Added config file header warning about preserving [section] headers.
Debug logging in RulesCommand prints token length + channel at runtime.
All 6 builds bumped to 1.0.3.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-13 17:53:28 -05:00

1.2 KiB

Raw Blame History

Rules Mod — Install Procedure

Correct Install Steps

Place the jar in the server's mods/ folder
Start the server once — Forge generates the config with defaults
Stop the server
Edit config/firefrostrules-common.toml (or config/discordrules-common.toml):
- Set bot_token to your Discord bot token
- Set channel_id to the channel containing your rules message
- Set message_id to the specific message ID
- IMPORTANT: Keep the [discord] and [performance] section headers!
- Only change the values, not the file structure
Start the server again

Verify It Worked

Check server logs on startup for:

Rules mod config loaded successfully. Channel: <your_channel_id>

If you see this instead, the config is still on defaults:

Rules mod is using default config values! Edit config/firefrostrules-common.toml

Config Location

The config lives at config/firefrostrules-common.toml (COMMON type). This loads once at startup and persists reliably across restarts.

Upgrading from v1.0.0 or v1.0.1

Old versions used world/serverconfig/firefrostrules-server.toml. That file is now ignored. Copy your values to the new location above.

1.2 KiB Raw Blame History