Tinkers Construct

Tinkers Construct

160M Downloads

Seared/Scorched Channels break flow in multiplayer

Yaevo opened this issue ยท 8 comments

commented

Minecraft Version

1.16.5

Forge Version

36.2.1

Mantle Version

1.6.115

Tinkers' Construct Version

3.1.0.231

Describe your issue

While in multiplayer session (Forge server version 36.2.1), when you make a flow with the Channels, all goes well, but after the user that set the flows disconnects and connects again, they get messed up randomly, and have to be set again in order to function correctly.

Crash Report

No response

Reproduced with only Tinkers' Construct?

Yes

Other mods required

No response

  • Confirm you have checked the roadmap, what's new, and the FAQ for your issue
  • Confirm you are not using performance enhancers, such as optifine
commented

Explain "messed up randomly" better, maybe try some screenshots?

commented

This is just logging in:
image
Now it's set up to flow correctly:
image
After disconnecting and logging in again, it "messes up":
image

commented

Is this just visual, or functional? In other words, is it a desync?

commented

It's both visual and functional, I have to set them correctly again to get the ore to flow

commented

It resetting functionally on login sounds unlikely, unless that area was unloaded. Do you get the same behavior if you unload the chunks without logging off then come back? Or if you log in while another player by your channels?

commented

I haven't tried unloading the chunks, I'll do it when I can login again. And some of the friends that are near my house, often come by and tell me that they fix the channels because they find it like in the screenshots. At the moment I've tried only with me near the channels to check if they reset, I'll have to try with someone near them too.

commented

Oh, one more thing. Can you use F3 + G` to show chunk borders? I'm trying to find the logic behind those channels being the ones that disconnect

commented

Its been about 2 months with no update, and I still cannot reproduce this, so going to close. Give more information if you want a reopen