[Crash]: Placed Maple Sign, then Crashed
GrimWolf47 opened this issue ยท 30 comments
Minecraft Version
1.18.2
BYG Version
1.4.1
Terrablender Version
1.1.0.102
Mod Loader
Forge
Mod Loader Version
40,1,31
What happened?
Seems to be a mod incompatibility, but I was just building a greenhouse in my smp, then when I placed a Maple Sign on some leaves it crashed me, but not the server, so I tried to have my friend break it, and then it crashed him as well, neither of us can join back now as we instantly crash when within 100 blocks of the sign
crash-log
crash-2022-06-11_01.04.51-client.txt
latest.log
Minecraft Version
1.18.2
BYG Version
1.14.1
Terrablender Version
1.1.0.102
Mod Loader
1.18.2-forge-40.1.51
Same Issue, placed a Cherry sign and had to load a backup since i crashed instantly, again client side, server was fine, everyone who loaded the chunk with the sign crashed as well
The list of mods i use, maybe the other two crashes can post theirs as well so we can search for similarities.
I renamed the file from html to txt since github does not allow html files here.
The list of mods i use, maybe the other two crashes can post theirs as well so we can search for similarities. I renamed the file from html to txt since github does not allow html files here.
I'll post my modlist here in a sec
I also am experiencing this same bug. Modlist is also in crash report.
crash-2022-06-14_22.26.49-client.txt
Also interestingly another player was using the maple signs just fine beforehand. This issue started with the rainbow eucalyptus for me.
The list of mods i use, maybe the other two crashes can post theirs as well so we can search for similarities. I renamed the file from html to txt since github does not allow html files here.
modlist.txt
Here's the Mods I use,
Same here. With a cherry wood sign.
modlist.txt
To fix, I did as an above user mentioned and changed my player's position via NBTExplorer (thanks for that) but using a command to remove the block didn't seem to work, so I used an rf tools builder to remove a 10x10 area where the sign was placed. You can get about 100 blocks away and said builder has a max offset of 512 blocks so it should be reproducible for anyone with the mod.
I cannot replicate this issue, you'd need to figure out this mod incompatibility yourself i think
Minecraft Version
1.18.2
BYG Version
1.14.1
Terrablender Version
1.1.0.102
Mod Loader
1.18.2-forge-40.1.51
I have a same inssue, when I placed byg:cherry_sign then it crashed my game but not server.
To join my own server, I use NBTExplorer to change my position far away from the sign. But got crash again when I go straight to the sign.
I use command to delete that sign, and everything go normal again.
Server-log (appear when re-join then get crash again):
[Netty Server IO #19/ERROR] [minecraft/ArgumentTypes]: Could not serialize io.github.apace100.apoli.command.PowerSourceArgumentType@769dadd1 (class io.github.apace100.apoli.command.PowerSourceArgumentType) - will not be sent to client!
Crash-log, client-side
crash-2022-06-13_21.45.51-client.txt
Same here. With a cherry wood sign. modlist.txt
To fix, I did as an above user mentioned and changed my player's position via NBTExplorer (thanks for that) but using a command to remove the block didn't seem to work, so I used an rf tools builder to remove a 10x10 area where the sign was placed. You can get about 100 blocks away and said builder has a max offset of 512 blocks so it should be reproducible for anyone with the mod.
We have several of the same mods, not sure how or why some would cause the crash but the common mods are, Supplementaries, Sophisticated Backpacks, Tinkers Construct, Appleskin, Artifacts, Carryon, Cosmetic Armor, Polymorph, Dark Paintings, Mekanism and its addons, Mystical Agriculture and Agraditions, Repurposed Structures, Waystones, Quark, and Yungs better dungeons
From Fabric. Got an issue where two of my friends placed a cherry sign and rendering it caused the client to crash. Used worldedit to remove the block. The crash log specifically mentioned it was "byg:cherry_wall_sign" that made it crash.
I also encountered this crash
To rescue the player, I teleported them out by editing their playerdata file with NbtStudio. Then I removed the block in the region file using Amulet. If your world save is too big to download from a server, identify which region file the sign is in using the crash report and download only that and paste it into a new world on your computer. Open that world with Amulet, delete the sign, then reupload that region file to the server. It'll have a missing texture for modded blocks but you know the exact coords from the crash report
I then banned all BYG signs just to be safe using Item Banning and removed recipes using Craft Tweaker. Script: craftingTable.removeByRegex(".*byg:.*sign");
Supplementaries, Sophisticated Backpacks, Tinkers Construct, Appleskin, Artifacts, Carryon, Cosmetic Armor, Polymorph, Dark Paintings, Mekanism and its addons, Mystical Agriculture and Agraditions, Repurposed Structures, Waystones, Quark, and Yungs better dungeons
Just tried making a pack with said mods and with rubidium and oculus and it worked fine placing signs. However my modpack still crashes.
Mod list here:
modlist.txt
I have a very similar modlist with the same issue. I do not have:
- Carryon
- Mekanism
- Mystical Agriculture
- Waystones
I've also experienced this same bug in a multi-modded server. Placing any of this mod's signs into the world triggers a error on render for anybody that can see it. Followed @getBoolean 's solution of just editing the world with Amulet and that allowed me to delete the sign.
Ah, not just me then. We're having the same issue with the Signs from this modpack. If anyone walks up close to them, they crash (server does not).
I loaded these mods only, and it crashed.
TerraBlender-fabric-1.18.2-1.1.0.102
Oh_The_Biomes_You'll_Go-fabric-1.18.2-1.4.1
fabric-api-0.56.0+1.18.2
New world, baobab sign crashed it. However, reloading with only those mods on the client side as well makes it work just fine... I think there's a client side issue with the baobab sign.
Will do more mod elimination.
I loaded these mods only, and it crashed.
TerraBlender-fabric-1.18.2-1.1.0.102 Oh_The_Biomes_You'll_Go-fabric-1.18.2-1.4.1 fabric-api-0.56.0+1.18.2
New world, baobab sign crashed it. However, reloading with only those mods on the client side as well makes it work just fine... I think there's a client side issue with the baobab sign.
Will do more mod elimination.
alright, I'm pretty sure its just Biomes you'll go's signs are having issues, seems in your video you had terralith installed as well, could possibly be the issue but I somehow doubt its that so I wish you luck with your mod eliminating I might do some testing myself here soon
Found the mod combo that screws it up. (for me, at least)
biomemakeover-FABRIC-1.18.2-1.4.24 on the client (Not even loaded on the server at this moment)
+
Oh_The_Biomes_You'll_Go-fabric-1.18.2-1.4.1 on the server
Running this combo causes a crash.
I see other users without biomemakeover having this same crash, and not even on fabric, so there has to be something with the byg mod that's conflicting with something that these other mods use.
I ran that last test without sodium, to see if it was an issue there somewhere, but it looks like it's not. It's gotta be between biomemakeover on the client and byg on the server.
On Forge, this happens without Biomemaker. Perhaps its an Architectury issue?
Very, very good chance! I can try running the same tests without biomemakeover, and keep architectury installed, but I'm not even sure it'll init due to no dependents.
Yeah, architectury on both client and server, sign places fine. Unsure if it's being loaded, to be honest, in my case. What's another fabric mod that depends on architectury? I'll install it on both and retest.
Nah, REI uses architectury, and I've got REI on client and server. It's not that, at least, not the way that REI is using the API.
I am having the same issue in Fabric.
Crash report
Mod list
The game appears to crash every time a player loads a chunk with any sign from BYG. The weird thing to me is that both Forge and Fabric clients experience these crashes.
For now seems like the best fix is to just ban the signs using the Item Banning mod.
The mod is not ported to Fabric
With repeating command blocks you can use the /clear command to achieve the same effect, but of course that will only help on a server.
crash-2022-06-26_19.47.32-client.txt
Mods list:
Terrablender
Terralith
FabricAPI
FabricProxyLite
BYG
2022-06-26.19-50-40_Trim.mp4
@AOCAWOL
In my world, I place a baobab sign down, and instantly get kicked.