Modern Elevators and Escalators

Modern Elevators and Escalators

106k Downloads

[Forge 1.19.2] Crash on boat depot creation

dagobertdu94 opened this issue ยท 8 comments

commented

Expected Behaviour
The marked area in the boat dashboard shouldn't crash the game, and let me create a new boat depot.

Actual Behaviour
The game crashed right after I marked an area for my boat depot.

Reproduction Steps
Steps to reproduce the behaviour:

  1. Open boat dashboard and go to the Depots tab
  2. Create a new depot and mark the area for it (after marking the game will crash)

Crash Report
https://pastebin.com/r0dZMMZ1

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • Minecraft Version: 1.19.2 (Forge 43.3.0)
  • Installed Mods: listed at the end of the crash report

Additional Information
Anything else you want to add?

commented

Incompatibility with MrCrayFish Framework mod as FakeBoat passes world as null

Offending code no longer exists in upcoming MTR versions.

commented

EDIT: I found out that it isn't caused by the depot itself or its creation.
It seems that either the depot rail or the vehicle on that depot rail is causing the problem.
But I don't know why...

commented

Hi, I have the same issue. Have you already solved it?

commented

Hi, I have the same issue. Have you already solved it?

No, I couldn't solve it yet...

commented

But now I have a technical question, why is it only occuring for boats and not even for trains and planes?
Or are trains and planes just ignored by the Framework mod?

commented

Incompatibility with MrCrayFish Framework mod as FakeBoat passes world as null

Offending code no longer exists in upcoming MTR versions.

So it will be fixed for Forge 1.19.2 with the next update?
That would be great.

commented

Pretty sure boat uses the vanilla Minecraft boat for the rowing animation, which is why it tries to create a fake vanilla boat entity
While trains and planes don't have any vanilla animation

commented

This should be fixed in 4.0.0. Please reopen this bug if you still encounter this issue with 4.0.0, thanks!