Common questions

Frequently asked questions

If your question is not here, open an issue on the pack repository and include the relevant log. Guesswork helps nobody.

Give Minecraft at least 6 GB, ideally 8 GB. That is enough for Thunder's current 128-mod shape without getting silly. Do not go beyond 10 GB unless you have a real reason.

Yes, but know what the pack manages. Extra files with unique non-indexed paths are usually fine. Editing indexed pack files is a different matter, because packwiz can restore those exact paths on sync.

Only exact file paths listed in index.toml. Packwiz does not treat an entire directory as managed just because one file in that directory is indexed.

If you edit a path the pack already indexes, packwiz can restore the pack version of that exact file on sync. If you add a separate non-indexed file next to it, that separate file is usually left alone.

For client installs, the easiest route is to download the new .mrpack and use Update from file in Prism Launcher. For servers, use the official startup scripts and let packwiz sync before launch.

It syncs the published pack metadata and the exact indexed files that belong to the pack. If you want complete manual control, you can disable sync for a run, but that means you are choosing to diverge from the official pack state.

Yes. Thunder publishes pterodactyl.json as a release asset for panel imports.

Java 21.

Yes, provided the server is running the pack properly and UDP traffic is allowed on the configured voice port.

No. OptiFine and modern Forge mod stacks rarely get on well. If you want shaders, use the supported shader route rather than trying to wedge OptiFine into the pack.

Check RAM allocation first, keep it around 8 GB, drop render distance if needed, and do not mistake first-launch stutter for normal performance. If you have bolted extra mods on top, remove them before blaming the base pack.