[🐞]: Internal Server disconnection, Received attachment change for unknown target
AkkiTheGamerFox opened this issue · 47 comments
Before Continuing:
- Check you are using the latest version of the mods and its dependencies
- Always include a latest.log if you are crashing
- Remove known hacky mods such as: Optifine, Fabric API/Connector on forge, and every kind of hybrid server like Mohist and Velocity. None of these are supported. Also try without other lesser usual suspects like Sodium and Lithium.
- If you are unsure which mod is the culprit.
Disable all of your mods and enable them 1-2 mods each time to isolate the culprit - Confirm that there is no existing issue with a similar description submitted in the list of issues.
Version
1.21.1-FABRIC
Supplementaries Version
Supplementaries 1.21 - 3.4.20
Moonlight Lib Version
Moonlight Lib 1.21 - 2.25.3
Describe Issue
While I'm not 100% sure Supplementaries is solely responsible for this crash, it did occur after updating the mod, and no others. Unfortuly this bug might be difficult to find the cause to due to it causing an internal server error, plus it makes the world unplayable unless you wipe all entity data. The latest game logs are provided in the attachment below. Even if it's not a problem on this mod's end, I do hope I can at least be pointed in the right direction. I can also provide a mod list if requested.
I'm crying right now. I had the same issue for 3 days, i removed does it tick and now everything works for me
I'll now report to fabric api dev and hopefully this will be resolved soon but chances are it could also be an issue entirely from that mod instead of being fabric api fault
I'm really sorry to writing that message too soon... I'll delete it if needed. After 1 minute of playing the issue repeated itslef
But removing does it tick let the game work for at leas one minute. In the past days I wasn't even alllowed to join the server.
It's a fabric api issue
Ah, alright then, and I see you've already opened a bug report on the Fabric API github. I'll keep an eye on that.
also i cant even replicate. Ive tried throwin slimeballs around at stuff and it doesnt crash for me
No mobs around
Mind you, this bug happened to me after DAYS worth of playtime on a single world, which has a file size of over a Gig. Farbic API is updated to it's latest version. As I said, I'm testing further to see if I missed anything from the first time around. I can't test the world with only Supplementaries installed as removing too many mods causes the save to become invalid.
also i cant even replicate. Ive tried throwin slimeballs around at stuff and it doesnt crash for me
That's the weird part, I've never thrown slimeballs at anything, nor have I had any slime chunks in the vicinity. Further more, it continues to happen even after wiping all entities from the world. I'm going to make a copy of the world I'm on for testing perposes, and try to see if I can track down any other possible causes...
That's why I asked if it happened in superflat
I've yet to replicate it outside of the affected world. The issue also seems to have stopped once I removed Mob AI tweaks or Nostalgic Tweaks, the latter of which has caused issues with other mods before. Though this isn't certian as the timing of it seems very inconsistant.
Ok fine don't blame that mod but downgrading Supplementaries, Suppsquared, Amendments & Moonlight allow one to go back & play in there world so to me it's a problem with Supplementaries update not playing nice atm..
So downgrading these 4 mods solves the error.
I have 150 mods on a fully updated fabric loader all of which work fine.
minus the 4 mods above & my world loads fine right now no issues.
If I update those 4 mods above.
My world will cease to work.
So that tells me there's an issue with Supplementaries or Moonlight Lib giving Supplementaries is the one calling the error.
Say what you want, downgrading those mods fixes the error atm ..
Same issue & i just gave up,
Supplementaries has the habit of breaking my worlds on there updates,
seems to be only mod that breaks stuff this is the 5th time this has happened.
its why i back up my mods prior to running my auto updater.
Then when this mess occurs AGAIN.
I let every other mod stay updated but theres.
I put back the old working Moonlight Lib, SuppSquared, Supplementaries & Amendments.
My fabric is updated to latest as of me typing this,
all my mods I just updated work fine,
my old world loads in perfectly fine with
Supplementaries 1.21-3.4.18-fabric,
Suppsquared 1.21-1.2.15-fabric
Amendments 1.21-2.08-fabric &
Moonlight 1.21-2.25.0-fabric
when I updated these when world errored boots me out with an Internal Server disconnection, Received attachment change states some kinda mob & a number.
Sorry all my mods work perfectly fine updated but these so downgraded I did not gonna update if it's gonna mean I have to spend hours figuring out what mod supp is no longer compatible with no not happening.
Just know this happens alot & it's always these that cause the crashes x.x
guess it's a good thing cause there the first mods I check now on issues.
Updated grammar edit
That's surely a wall of text that doesn't add anything to this issue. I can't replicate on my end. All I see is some brittleness from fabric API which was triggered by god knows what
This is very likely an incompatibility between a mod and an implementation of fabric API I'm using. I will send here a version which will print all the entities IDs such that I can trac down what entity it is
Please use this version which has extra logging and send a log here once it crashes
That isn't what they asked for...
sorry, im so new to this github whats exactly required, so i can send whatever log over.
They need you to send your log file after using the attached version of moonlight (In the unzip me file), and to send the log file once the internal server crashes.
sorry, im so new to this github whats exactly required, so i can send whatever log over.
I was able to replicate with just my stuff + cobblemon for some reason (which you dont even have). im now even more sure its fabric api issue
Hi, first time commenter I will try to give as much information as I can.
I just got this error and saw this thread.
I had cobblemon as well and Fabric version 0.17.2 and recently updated supplementaries to the latest version along with a bunch of other mods.
I got the same error.
I tried to see if upgrading the Fabric loader to 0.17.3 version and no difference.
I was also trying to run repairs (via the modirinth app)
eventually I degraded the supplementaries 1 update (from ver 3.4.20 to 3.4.18) and then I managed to load my world
no issues or crashes.
so at least there seems to be an easy solution that doesn't ruing anything
let me know if any more info is needed I will try to get it
Fabric API issue page since it wasn't linked before FabricMC/fabric#4943 (comment)
Finally got it to crash again.
latest.log](https://github.com/user-attachments/files/23155292/latest.log)
At this point this is outside of my control. Reason this happens btw is I switched from a ad-hoc solution I had using hacky mixins to using stuff specifically designed for it which is provided by fabric API. Too bad this seems to be bugged as heck, that's what I get for trying to do things properly.
I don't really plan to revert this tbh, sorry, the API is the correct way to do this and if it's bugged the issue is not on my end.
This other issue is likely related too.
At this point this is outside of my control. Reason this happens btw is I switched from a ad-hoc solution I had using hacky mixins to using stuff specifically designed for it which is provided by fabric API. Too bad this seems to be bugged as heck, that's what I get for trying to do things properly.
I don't really plan to revert this tbh, sorry, the API is the correct way to do this and if it's bugged the issue is not on my end. This other issue is likely related too.
So, what I'm taking from this is that this is a problem with Fabric API itself, and not your mod.
yeah thats what i said at the beginning. Replicating this in dev tho is hard. with just cobblemon it happens. without it doesnt. you dont have cobblemon i see so it must have some other trigger too. Until we find a mod that when added allows for this to happen aswell tracking this will be hard
yeah thats what i said at the beginning. Replicating this in dev tho is hard. with just cobblemon it happens. without it doesnt. you dont have cobblemon i see so it must have some other trigger too. Until we find a mod that when added allows for this to happen aswell tracking this will be hard
I also have some datapacks as well, if you think those could be a problem, as one Datapack does effect mobs, and the crash seemed to occur from what seems to be a cow if I'm reading the logs right? I've tested without the other two mods I mentioned and it didn't seem to happen, but like I said it's difficult to test as the timing appears to be very inconsistant.
I have quite a few mods that fit that discription, so I'll test around and see if I have any results
It may have something to do with mods that affect mob spawning, as if I recall correctly Cobblemon, by default, prevents vanilla mob spawns. I have respawning animals, which alters the mechanics for how passive mobs spawn and the error appears to be occuring for me while attempting to spawn said passive mobs, so that may be a possible cause.
yes its definitely something that alters mob spawning or add new mobs that spawn on their own or even something that alters how mobs are synced
I've tested, and have narrowed it down to the following mods:
https://www.curseforge.com/minecraft/mc-mods/does-it-tick
https://www.curseforge.com/minecraft/mc-mods/friends-and-foes
https://www.curseforge.com/minecraft/mc-mods/nostalgic-tweaks
https://www.curseforge.com/minecraft/mc-mods/mutant-monsters
https://www.curseforge.com/minecraft/mc-mods/servercore
I only had these mods (And supplementaries, and their dependents) enabled and had the crash occur...though I did forget to install the version of moonlight with logging, sorry.
It's also crashing very consistently with this mod set, so we may have our culprit somewhere in this list.
Server core or does it tick are my bet
Well, I'm going to start eliminating mods from the list here, I'll keep you updated
I've tested, and have narrowed it down to the following mods: https://www.curseforge.com/minecraft/mc-mods/does-it-tick https://www.curseforge.com/minecraft/mc-mods/friends-and-foes https://www.curseforge.com/minecraft/mc-mods/nostalgic-tweaks https://www.curseforge.com/minecraft/mc-mods/mutant-monsters https://www.curseforge.com/minecraft/mc-mods/servercore
I only had these mods (And supplementaries, and their dependents) enabled and had the crash occur...though I did forget to install the version of moonlight with logging, sorry.
Ive tried all those together and cant replicate
Id really like to call this a cobblemon issue but since it was replicated without that it disproves it, at least partially
I didn’t mentioned it before but I’m using also cobblemon and a bunch of related side-mods. Meanwhile I’v solved downgrading moonlight and supplementaries to the right previous working versions (which while I’m writing are respectively 2.25.3 and 3.4.18. ).
I've tested, and have narrowed it down to the following mods: https://www.curseforge.com/minecraft/mc-mods/does-it-tick https://www.curseforge.com/minecraft/mc-mods/friends-and-foes https://www.curseforge.com/minecraft/mc-mods/nostalgic-tweaks https://www.curseforge.com/minecraft/mc-mods/mutant-monsters https://www.curseforge.com/minecraft/mc-mods/servercore
I only had these mods (And supplementaries, and their dependents) enabled and had the crash occur...though I did forget to install the version of moonlight with logging, sorry.Ive tried all those together and cant replicate
It always seem to take a while to crash, as I said the timing is very inconsistant.