Leaving this writeup for the googlers that run into this issue in a few years. Deleting this file will reset the player, use it as a last resort. The PlayerData file will likely NOT be corrupted, but it's worth checking anyways.Continue through all other mod folders looking for corrupted files (either all blank or all NUL).If the file contains only blank spaces, no symbols (alternatively open in notepad++ and look for NULNULNULNUL), delete the file.When you find player specific configs, open the file for the player that crashes the server.Go to the world folder and then go through each mod folder looking for any folders that have player specific configs.To be clear: The issue was with corruption server side, not client side. Tekkit is a custom host which enables mods, thus allowing you to enjoy mods with other players. Ban items and blocks from vanilla Minecraft AND from any mod installed. This wikiHow teaches you how to install and set up a Tekkit server for Minecraft on your Windows computer.
Turns out the issue was caused by mod data getting corrupted for only a single player.Įdit: The mods that were corrupted were LogisticPipes and NEI.Įvery time that player would connect, both their client and the server would crash, but other players could join the server and load in to the same chunks that player was in.įor anyone wondering, this happened when the power went out and the server was still up. Prevention of certain server crashing Tekkit Classic problems, like REPs in a.
0 kommentar(er)
