Hephaestus Forge causes a disconnect when putting in a recipe

[Tomska95]

Modpack

FTB Evolution

Modpack version

1.4.1

Launcher

Prism

Has the pack been modified

No

Log Files

disconnect-2024-12-08_14.20.27-client.txt

Describe the bug

While crafting with the Hephaestus forge, if the recipe and requirements are otherwise met and the last item inserted is the middle item in the forge itself you get disconnected with network protocol error.

This happens in both single- and multiplayer but I was not able to test what happens to people other than the one putting in the item in multiplayer. At least for that person you are not able to log back in until the server has been restarted.

Rejoining in singleplayer or restarting the multiplayer server seems to reset the forge back to its default state without any of the previous contents. Presumably neoforge resetting the erroring entity?

The log hints at it being a block state issue but I'll leave analyzing that to someone who can actually read the log.

Steps to reproduce

1. Insert all the required items on the pedestals
2. make sure all the soul/blood etc. requirements are met
3. insert the last item in the middle
4. get disconnected with Network Protocol Error

Expected behaviour

After putting in the last item you should be able to exit the gui and start the ritual as normal

Screenshots

No response

Additional information

Workaround:
This doesn't happen if you insert the middle item first and complete the recipe by putting in the last item on one of the surrounding pedestals.

[r-mc2]

We're having this same issue on my server. Also v1.4.1 of the pack.

However the workaround Tomska mentions above doesn't seem to work in a server setting, only in SSP.

We've tried changing the order we place items on the pedestal, unclaming the chunks the forge sits in, and even moving the forge to sit within a single chunk (instead of spanning multiple). Nothing will start any of the rituals, so we cannot even upgrade the forge much less do any of the tier 1 recipes.

[Gaz492]

Is this still an issue on the latest version of the modpack (1.7.0) for any of you?