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

Pipes and Other Transmitters Client Sync #8223

Open
Soaryn opened this issue Sep 6, 2024 · 0 comments
Open

Pipes and Other Transmitters Client Sync #8223

Soaryn opened this issue Sep 6, 2024 · 0 comments

Comments

@Soaryn
Copy link

Soaryn commented Sep 6, 2024

Issue description

Pipes networks seem to lose their stored fluid/chemical on the client (the resourceis still present) when leaving an area and coming back. As discussed on discord, it seems to be an update packet missing. It is purely visual, but requires a person to either update the pipe, or relog.
image

Steps to reproduce

  • Start void world
  • /tp 300 ~ ~ or so to not have the loaded default chunks.
  • /setblock ~ ~-1 ~ stone to have something to place on
  • Fill a pipe with water and remove the source.
  • Fly away just a little after the fog hits the pipe. You can keep going, but you shouldn't need to. 12 chunks likely would guarantee it.
  • Come back to it (fly, don't teleport, not sure if it will present a problem when teleporting) and it will appear empty

Minecraft version

1.21.1 (Latest)

NeoForge version

21.1.37

Mekanism version

10.7.7 (Latest)

Other relevant versions

It doesn't need any chunkloading, and while I am in my dev environment, it the replication above seemingly indicates more towards just Mek in isolation

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

No response

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

1 participant