Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network Protocol Error due to use of Evaporation Tower #8303

Open
Gal1leoGal1le1 opened this issue Jan 12, 2025 · 1 comment
Open

Network Protocol Error due to use of Evaporation Tower #8303

Gal1leoGal1le1 opened this issue Jan 12, 2025 · 1 comment

Comments

@Gal1leoGal1le1
Copy link

Issue description

General Description

The issue involves a RuntimeException with Invalid fluid for tank: minecraft:water error message, the error log is provided further down. It appeared on a server with "All the Mods 10" installed, after a Evaporation Tower was build. The error only appeared for players who werent connected to the server when the tower was build and resulted in disconnecting.

Fast fix

A fast fix was to just destroy a block in the tower, when replacing it the bug reacured.
The bug was not reproduced by us, but still here are the steps that seem to lead to this bug:

Steps to reproduce

  1. Start Server with All the Mods 10 installed (possibly mekanism mod is enough)
  2. Join with one account and build a Evaporation Tower
  3. After Finishing the Tower, join with another account that wasnt on the server allready, and get close to the Tower
  4. The Error should occur

Minecraft version

1.21.1 (Latest)

NeoForge version

21.1.93

Mekanism version

10.7.7 (Latest)

Other relevant versions

Mekanism Version was 10.7.8 (Not selectable befor)

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

https://gist.github.com/Gal1leoGal1le1/961d72a71ee5fda32775f4949bf71bed

@thiakil
Copy link
Member

thiakil commented Jan 13, 2025

That looks like client/server recipe lists are out of sync or you got water in the output tank.
The former is not really something we can help with in a large modpack.

Try restarting clients until it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants