Deployer crashes the game/server when placed/loaded 1.20.1
Zanodar opened this issue ยท 24 comments
Describe the Bug
The game crashes when placing a deployer block
Reproduction Steps
- place/load deployer
- crash
...
Expected Result
The expected result would be the game not crashing.
Screenshots and Videos
No response
Crash Report or Log
Operating System
windows 10
Mod Version
0.5.1d
Minecraft Version
1.20.1
Forge Version
47.1.15
Other Mods
Adaptive Performance Tweaks: Core
Adaptive Performance Tweaks: Spawn
Additional Enchanted Miner
AI Improvements
AmbientSounds 5
AppleSkin
Architectury API (Fabric/Forge)
Canary
Carry On
Chunky (Forge)
Cloth Config API (Fabric/Forge)
Connectivity[Forge/Fabric]
CreativeCore
Drip Sounds (Forge)
EdivadLib
ExtraStorage
Farsight [Forge]
Fast Leaf Decay
FerriteCore (Forge)
Inventory Profiles Next
Jade ๐
Jade Addons (Forge)
Just Enough Items (JEI)
Just Enough Resources (JER)
Kotlin for Forge
libIPN
Light Overlay (Rift/Forge/Fabric)
Magnesium/Rubidium Extras
Mouse Tweaks
Nature's Compass
Oculus
Open Parties and Claims
Pipez
Polymorph (Fabric/Forge/Quilt)
Powah! (Rearchitected)
Refined Storage
Refined Storage Addons
Rubidium
Scalable Cat's Force
Server Tab Info
Simple Tomb
Sound Physics Remastered
spark
Xaero's Minimap
Xaero's World Map
XaeroPlus
Additional Context
No response
crash-2023-07-15_14.03.38-server.txt
Just incase heres a crash-report from a completely newly created save, where all i did was place down a deployer
I have now tried all forge versions above 47.1.5 and it stops working when using a higher version.
in the forge change log it states this "- 47.1.6 Fix entity size event not being fired, changed it to split eye height and size calculations. (#9535)" as the change that was done in 47.1.6 which idk if has anything to do with it but its not working from 47.1.6 and up
Appears to be any direction. When the game crashes, it shows an error as followed:
The game crashed whilst ticking block entity
Error: java.lang.NoSuchMethodError: 'void net.minecraftforge.event.entity.EntityEvent$Size.setNewEyeHeight(float)'
This bug happens on both single player, and multiplayer.
I will attach a video file demonstrating a crash...
2023-07-16.11-57-21.1.mp4
could you please try with forge 47.1.4
Sure thing...
It now doesnt crash!!! Yay!
So in short, as a temp fix, just install Forge 47.1.4
The following post has nothing to do with deployers
I dont know if this is related, but I now got an error code when I clicked on the [small grinding thingy] which was attached to an andersite funnel, which was attached to a conveyor belt. My error was as followed:
The game crashed whilst ticking block entity
Error: java.lang.IllegalAccessError: class com.simibubi.create.content.kinetics.belt.transport.BeltMovementHandler tried to access private field net.minecraft.world.entity.Entity.f_19793_ (com.simibubi.create.content.kinetics.belt.transport.BeltMovementHandler is in module [email protected] of loader 'TRANSFORMER' @708eb310; net.minecraft.world.entity.Entity is in module [email protected] of loader 'TRANSFORMER' @708eb310)
yh it seems to be a bug in forge that developped after 47.1.4. if this solution fixes it for all you guys, maybe you could close the issue.
It is not related to parties & claims it is a purely Create bug as upon testing with only Create 0.5.1.d on Forge 47.1.15 & even Create 0.5.1.c on the same forge version causes the crash
Create version 0.5.1.d
https://mclo.gs/rkO8MU9
Create version 0.5.1.c
https://mclo.gs/udQVBQH
I think a Size event is fired during construction of the DeployerFakePlayer class at which point the object is not properly initialized. I dont know why you are affected and most others are not. Are you placing the deployer in a specific orientation (or is this happening in a different circumstance?)
setNewEyeHeight
was moved from the Size
event to the EyeHeight
event, so the following code needs to be modified:
public static void deployerHasEyesOnHisFeet(EntityEvent.Size event) {
if (event.getEntity() instanceof DeployerFakePlayer)
event.setNewEyeHeight(0);
}
so is this issue something forge needs to fix or ?
so we gotto wait for a forge version that doesent crash