Troubleshooting
The handful of things that actually go wrong, and what they mean.
The game crashes when I open a settings screen
Almost always a version mismatch between LumiLib and one of the mods that
builds on it. The crash report names a missing method in
com.lumitier.lumilib.api.
Update both to their newest versions, and make sure there is only one jar per mod in the folder.
A setting does nothing
Shadow Tweaks: Minecraft has its own Entity Shadows switch in the video settings, and Sodium Extra exposes the same one. Vanilla checks it before any shadow is calculated, so with it off, nothing this mod does has any effect.
Perpetual Snow in an arena: turn on snow everywhere. Vanilla only draws weather down to the highest solid block in a column, and under a roof that block is the roof.
Item Drop Tweaks and Experience Orb Tweaks, value-based options: without a merging mod, stacks and orbs never get large enough for the effect to show. The scale is logarithmic, and a max value far above your real numbers flattens it to nothing.
Settings are gone after a restart
Each mod keeps its settings in config/<modid>.json. A file that cannot be
read falls back to the defaults rather than refusing to start — so a settings
reset usually means that file was damaged, not that nothing was saved.
If it keeps happening, check whether the game has write access to the config folder.
Where to report something
Open an issue in the repository of the mod in question. The crash report from
crash-reports/ and the matching logs/latest.log are what make a report
useful; without them a bug report is a guess.