Modded Multiplayer shield crash issue (Exception caught in client main loop, (EofException)

[halcyon rain]

I have been having issues with a multiplayer modded playthrough, using frackin universe, whenever someone pulls out a shield or selects it in hot bar/inventory near me in the same planet It boots me from the server with the error. "Exception caught in client main loop, (EofException) Failed to read full buffer in readFull, eof reached" this also happens if I’m hosting, and boots the current near player from the game, when I select shields or equipping one.

Additionally, during this playthrough I’ve also had complementary errors of being booted off the game when trying to load on the planet with the previously mentioned error forcing me to migrate my character, however I’ve not had that error since the migration.

two of the logs are from me joining and crashing and a friend joining me and crashing and the one where I was hosting when the friend crashed

Modlist: : https://steamcommunity.com/sharedfiles/filedetails/?id=3238749053

• Frackin Universe: More Planet Info Official Patch

• [OFFICIAL] FU BYOS Modded Race Patch

• Freedom of Movement

• Shellguard: Starbound Expansion Remastered

• More planet Ingo (work with 1.4.X not guaranteed)

• Bk3k’s inventory

• XS Mechs : Modular Edition (BETA)

• Frackin’ Action Bars

• Enhanced Storage

• Stardust Core Lite

• Stardust Core

• Startech - Stardust Technologies

• Frackin’ Interface

• Frackin’ Music

• Frackin’ Universe

[verbal lark]

Hmmm. Can you test and confirm with your friends if it's ANY shield, or only certain ones?
Like you could try spawning an vanilla common shield, an FU shield, and a Shellguard shield to see if it kicks your friends from the world or not.
It might help narrow down the source of the problem if there are outliers that don't cause the crash.

[halcyon rain]

My friend said he tested with Vanilla and FU shields which both crashed/booted me from the game

so i assume it effects all shields regardless of mod origin

[verbal lark]

based on my old unpak of FU (might not be the case anymore), they added a shield.lua which would supercede the Vanilla one, adding a lot of FU-specific code. There could be some kind of conflict there with an update or something they aren't aware of:

Since a lot of people don't really use shields, and since it only happens in multiplayer, and only to a client, it could've flown under their radar.
Again, this is just an empty theory, as I don't have an up-to-date FU unpack.
But it appears that there's an excessive amount of code running when the shield gets equipped that the game engine is refusing to process. Likely a feedback loop that isn't resolving.

You said the bug is compromising worlds that you perform it on, making it so you can't visit them again?

[halcyon rain]

Oh yeah that error basically gave me the same eof error like the shield, when I joined back with my first character, which I was on a desert planet it kept booting me every time I joined back, which Is why I migrated to a new character

But I’m unsure why the shield bug is only effecting me, when other people in the play-through are fine when using shields when joining my friend, if it is indeed a client-side issue which I’ve already re-downloaded and tried other options

[halcyon rain]

what would you recommend I try to a attempt resolve

[verbal lark]

I'm genuinely not sure. It's even weirder if it's only happening for you, but not the other players, if I read that right.
I'll go out on a limb and guess that you had some other mods installed at some point, but have since removed them?
I know there are certain things that stick around even after uninstalling mods, generally stuck in the universe or player files. I used to get a bunch of errors from some unknown mod with a lot of missing assets, even when I was running vanilla.
If you're willing to do a full wipe of your universe/player files and try again, that'd be my only real idea at this point. You can always make backups of your universe file before doing so if there's stuff you want to hang on to in-case it doesn't work.

[halcyon rain]

Yeah, I’ve tried using different characters but that didn’t work and redownloading the game while backing up my universe and player files. That didn’t it fix, and we haven’t changed the mods we are using. plus verifying files and turning off V-sync and asset mismatch on. But I guess I could try deleting all my player universe files not using the backup first and see how that goes

[verbal lark]

yeah, it's worth a shot, you should just be able to move the files out of those folders, launch the game, and do a test. if it fails, just move em' back

[halcyon rain]

Ok I tried it still caused the crash, but just closed my game without booting me with the EOF error, here is the log:

[finite fox]

No error at the bottom of the log. Huh. Did you ever get an error dialogue?

[halcyon rain]

nope it closed my game after my friend used a shield

we tried again it closed my game still.

[finite fox]

That «failed to read full buffer» is normally diagnostic of a difference between players' modpacks. Starbound adjusts its packet structures according to what mods you have installed in some places.

[halcyon rain]

alright

I was using my friends Modpack for the playthrough in workshop

so i'm certian i have all the correct mods installed

[finite fox]

Which is weird since it appears you both are subscribed to the exact same mods on the Workshop, which means Steam should have kept your mods up to date and synchronised.

[halcyon rain]

yeah

[finite fox]

I suggest removing StardustLib and StarTech though. I just discovered an unrelated compatibility issue between the Stardust mods and xSB-2 that causes UI clipping glitches with Stardust's interfaces. Yeah, sure, that issue wouldn't affect you since you don't use xSB-2, but I'd remove Zia Satazaki's mods just in case there are other compatibility issues caused by them.