#[SERVER] Invalid Player Data on Portal Re-entry/Relog

8 messages · Page 1 of 1 (latest)

tacit spruce
#

Pretty much shooting in the dark with this server error, but would genuinely appreciate ideas

Context is a 1.20.1 Forge 47.3.1 server where I made a custom modpack feat multiple Create addons (all fully updated except Create Wizardry and Copycats)

We have a monorail built in the nether, but whenever any player enters a nether portal or logs in when there's a monorail train nearby (like within several chunks), they immediately get disconnected and get "Invalid Player Data" as an error and can't log in anymore, until the train is moved by some other player out of the range.

At first I thought it was because the monorail train was made from copycats (1.2.6) but the same issues persists with trains made from just a few blocks a seat, and a controller, and it still invalidates player data. Couldn't find any thread with this issue on 0.5.1.f Create or on this server.

I also noted the huge hitboxes of trains and tried to make sure they didn't collide with any copycat/portal/weird blocks. Nothing. Tried setting disableDataFixer from false to true, to no avail.

Server console screenshot sent: sorry I can't provide copy and pasted lines rn.

Also attaching a crash log

image.png 📎 crash-2024-07-03_15.35.05-server.txt
vocal cedarBOT
#

Hello @tacit spruce! Someone will help you shortly, please do not ping moderators or other people and just wait for someone to come help.

tacit spruce
#

I would love to blame sinytra connector but can't test it without it because the pack doesn't start if it's not included (embarassingly, I'm not sure which mods are even using sinytra now. There shouldn't be any after I removed mods that did use them i.e. Eldritch End)

#

Annnnnd will note that sometimes the entire train becomes invisible to certain players but not everyone. anyway sorry for the spam

subtle ember
#

!!binary-search

vocal cedarBOT
#
Binary Search - A method of finding problems with mods

The binary search is a way of finding a faulty thing amongst a lot of other things, without having to remove the things one-by-one. This is useful for finding a broken mod among hundreds of mods, without having to spend time testing the mods one-by-one.

The procedure is simple:

  1. Remove half of the existing things, and put them aside.
  2. Run the program / game.
  3. Does the issue still exist?
    If YES: Repeat from step 1 with the current things.
    IF NO: Swap out the current things with the ones set aside, and repeat from step 1.
  4. Repeat this process until the problematic thing/s have been found.

Credit to the Quilt Community discord and the NeoForge Discord for these instructions.

tacit spruce
#

yep I feared i had to try that