Frequently asked questions

Minecraft 1.20.1 on Forge 47.4.13. Other Minecraft versions are not supported, and neither are Fabric, NeoForge or Quilt.

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. Two indexed files are the exception: your server list in servers.dat and the log filter in config/logbegone.toml are only written on a fresh install, so your edits to those stay put.

For client installs, the easiest route is to download the new .mrpack and use Update from file in Prism Launcher. For servers, run PACKWIZ_SIDE=server bash tools/update.sh on Linux or .\tools\update.ps1 -PackwizSide server on Windows, or set PACKWIZ_AUTO_UPDATE=true to sync on every start.

It syncs the published pack metadata and the exact indexed files that belong to the pack. It is off by default, so restarting a server never changes your mod set on its own. Turn it on with PACKWIZ_AUTO_UPDATE=true when you want the server to follow the published pack, and leave it off if you would rather update deliberately.

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

Java 17 or 21 both work. Most launchers handle this for you, and the server scripts fetch a local Temurin 21 if neither is present.

Yes, provided the server is running the pack properly and UDP traffic is allowed on the configured voice port. Server owners can switch it off with ENABLE_VOICE_CHAT=false, which binds the voice server to 127.0.0.1 and leaves the rest of its config file alone.

No. OptiFine and modern Forge mod stacks rarely get on well. Thunder has no shader route yet either, so there is nothing to point you at instead. Adding one is on the list.

It is fetching 130 mods and building the model and recipe caches for all of them. Later launches are much quicker. Give the first one a few minutes before deciding something has gone wrong.

Check RAM allocation first and keep it around 8 GB, then drop render distance and simulation distance. Simulation distance is the expensive one, because it decides how many chunks are actively ticked and this pack is full of block entities. Keep both nearer 12 than 32. Do not mistake first-launch stutter for normal performance. If you have bolted extra mods on top, remove them before blaming the base pack.

No. Nothing is sold, nothing is monetised, and there are no adverts anywhere. Thunder exists because it is a good modpack worth sharing.