You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The code for saving pipenets in the WorldSavedData assumes it is "multiplexed" by world/dimension.
e.g. The pipenets only store chunk and block positions with the actual world coming from the WorldPipeNet.
This assumption is not correct, Minecraft saves all dimensions in one WorldSavedData file for a data id.
Additionally, there are a few places that are trying to access pipenet data on the client world, such as the damage
from hot pipes or uninsulated cables. In fact, this is being done twice, once against the server world and once on the client.
I don't think it actually causes a real problem in the current code, but this could potentially have the client trying to modify the pipenet data in competition with the server.
Versions
Forge: 14.23.5.2854
GTCE: 1.10.9.612 (current from GitHub)
Steps To Reproduce
In the overworld try to fill a wooden fluid pipe with steam
It will burn
Repeat the process in the nether
It won't burn
Expected behavior
The reason why it won't burn in the nether is because it is trying to burn a block in the overworld with the same blockpos
I have a fix for these issues, which I will try to submit as a PR once I figure out how GitHub works.
The text was updated successfully, but these errors were encountered:
Describe the bug
The code for saving pipenets in the WorldSavedData assumes it is "multiplexed" by world/dimension.
e.g. The pipenets only store chunk and block positions with the actual world coming from the WorldPipeNet.
This assumption is not correct, Minecraft saves all dimensions in one WorldSavedData file for a data id.
Additionally, there are a few places that are trying to access pipenet data on the client world, such as the damage
from hot pipes or uninsulated cables. In fact, this is being done twice, once against the server world and once on the client.
I don't think it actually causes a real problem in the current code, but this could potentially have the client trying to modify the pipenet data in competition with the server.
Versions
Forge: 14.23.5.2854
GTCE: 1.10.9.612 (current from GitHub)
Steps To Reproduce
Expected behavior
The reason why it won't burn in the nether is because it is trying to burn a block in the overworld with the same blockpos
I have a fix for these issues, which I will try to submit as a PR once I figure out how GitHub works.
The text was updated successfully, but these errors were encountered: