Strange things ocurring during gameplay

[TheChosenIndividual]

I dont even know how to describe the bug, mostly just its effects, ill start the list

1. Suddenly, a paintable fluid duct disappeared and became the block it was painted as (This happened after a version update, so it might be an ID change or others)

2. Energy storage blocks being voided for no reason, my output energy storage for an RBMK simply got voided suddenly, with no version or config changes (This happened while testing issue RBMK Heat values become stuck #1864)

3. Fluid tanks becoming glitched, when opening the same world as issue RBMK Heat values become stuck #1864, a fluid tank for water had lost its water identification, visually it looked like if it simply hadnt been identified, however the GUI showed it being identified as a water tank, despite this, it could not be filled any way i tried, breaking the tank fixed the glitch, other tanks placed work normally, if it helps, the tank was identified by shift clicking it with the identifier in hand

The weirdest thing about these bugs is that they seem to happen with no apparent trigger aside from the game being closed and re-opened, and they seem to have no relation in between each other, the only reason i grouped them together is due to their strange effects, good luck HBM

-Chosen

[TheChosenIndividual]

Update: bug 3 also affects barrels, it happened just now, its consistent with the trigger of identifying the barrel with shift-clicking rather than using the GUI, though it seems to happen overtime, and i cant get it to happen on-command, continuing to monitor

[BallOfEnergy1]

I suggest trying disabling NTM packet threading to see if that fixes your issue, as that's the most recent change that I can think of that would cause an issue like this. It can be done using /ntmpackets togglePacketThreading or by using the config option. It will disable the threading of packets and move the process over to the main thread. If it fixes the issue, then it would be my bad and I'll have to go back and fix some things. If it doesn't fix it, then that's not good at all.

Edit: This comment applies for both this issue and the mentioned issue.

[TheChosenIndividual]

I suggest trying disabling NTM packet threading to see if that fixes your issue, as that's the most recent change that I can think of that would cause an issue like this. It can be done using /ntmpackets togglePacketThreading or by using the config option. It will disable the threading of packets and move the process over to the main thread. If it fixes the issue, then it would be my bad and I'll have to go back and fix some things. If it doesn't fix it, then that's not good at all.

Edit: This comment applies for both this issue and the mentioned issue.

Might work...but wont that tank the performance of the game?