Fireplace Lib Mod FAQ

No setup is required—Fireplace Lib runs automatically in the background. Just make sure it's installed alongside any mods that depend on it, and you're ready to play.

If you're only using one mod from the Fireplace ecosystem, you technically don't need it. However, if that mod lists Fireplace Lib as a requirement, you must install it or the mod won't load.

They're designed to work together—that's the whole point of Fireplace Lib. Using multiple dependent mods at once actually reduces overhead since they share the same backend systems instead of each running their own.

Fireplace Lib handles heavy operations like saving data and processing commands without freezing your game world. This keeps your frame rate stable even when multiple mods are working at once.

Configuration files are typically saved in your world or server's data folder, organized by the mods using Fireplace Lib. Check your mod's specific documentation for the exact file paths.

First, verify Fireplace Lib itself is installed and up to date. Then check your game logs for errors—common causes include mod version mismatches, conflicting mods, or corrupted config files that need to be deleted and regenerated.

No—it's designed to improve performance by centralizing shared tasks and running them on separate threads. If you notice lag, the issue is likely with a specific mod using Fireplace Lib, not the library itself.

Yes, Fireplace Lib handles translations for dependent mods. Language settings are usually controlled through each individual mod's config or through your Minecraft language selection, and changes apply to all custom menus.

Check that Fireplace Lib is installed and matches the mod's version requirements. If errors persist, try deleting the mod's config folder to reset settings, or consult the specific mod's troubleshooting guide.

Only if you're using a mod that depends on it. Fireplace Lib works the same way in single-player and multiplayer, so if a mod needs it, you need it regardless of game mode.