Troubleshooting
List of Known Errors and Potential Fixes:
"TIMED OUT" While Connecting to Server
This issue can often be resolved by simply reconnecting. If that doesn’t work, follow these steps:
Check Your Network Connection:
Ensure you are connected to Wi-Fi or Ethernet with a reasonable speed.
To check your speed, use: speedtest.net or fast.com.
A stable connection of at least 6 Mbit/s is recommended, though it may vary based on your location.
If your Wi-Fi connection is stable, restart your game and check the server status.
Server status can be found at the top of unknown.
If the server is online and you still can’t connect, seek support from the staff.
Crash on Start with AMD Graphics Card
If you encounter the error EXCEPTION_ACCESS_VIOLATION (0xc0000005), this is likely caused by your AMD graphics card. The solution is to revert a recent graphics card update. Follow this tutorial for assistance: https://youtu.be/amKzOhu4jPc?si=sPGVhZkLr_3Dfeaf
"Failed to Connect to Server"
Internal Exception:
java.lang.nullpointerexception: cannot invoke "net.minecraft.nbt.compoundtag.m_128471_(string)" because "nbt" is null.
This error should already be resolved. If you still encounter it, contact staff for assistance by opening a ticket. (Ensure you haven't modified the modpack in any way)
Mismatch in Mod Versions or Missing Mods When Connecting
This typically occurs when:
- You're using an outdated version of the modpack. Check
📆┃updatesfor the latest modpack version. - The server is undergoing maintenance.
- It could also be due to manual modifications of the modpack. Never modify the modpack manually. If you have, reinstall the modpack.
Crash or high lag in Singleplayer for no reason
This is likely caused by alexsmobs:centipide_body conflict with VS2. Use /kill if high lag and NBT Editor if crash. No permanent fix.
If your issue is not listed here, contact staff or ask for help in a support channel.