I've seemed to run into an issue with FTB Chunks where after unloading a force loaded chunk, said chunk remains active and ticking. To the point where there is a significant performance impact on our server. (e.g. sub 10 tps average)
We are running the ATM7 4.22 mod pack with ftb-chunks-forge-1802.3.6-build.147.jar
Even after purging the ftbchunks folder and rebooting the issue persists. However, after disabling FTB Chunks mod, this issue goes away. Reenabling the mod causes the issue to return.
I've looked into the NBT data for some of the impacted regions/chunks and can’t seem to find anything that would explain this behavior. Attached are two screen shots from crash utils showing the loaded and ticking areas before and after disabling the FTB Chunks mod. Similar data is seen from observable and spark that matches crash utils. Is there another area in the world files to look for FTB Chunks data to stop these chunks from staying loaded so we can reenable the mod?
We are running the ATM7 4.22 mod pack with ftb-chunks-forge-1802.3.6-build.147.jar
Even after purging the ftbchunks folder and rebooting the issue persists. However, after disabling FTB Chunks mod, this issue goes away. Reenabling the mod causes the issue to return.
I've looked into the NBT data for some of the impacted regions/chunks and can’t seem to find anything that would explain this behavior. Attached are two screen shots from crash utils showing the loaded and ticking areas before and after disabling the FTB Chunks mod. Similar data is seen from observable and spark that matches crash utils. Is there another area in the world files to look for FTB Chunks data to stop these chunks from staying loaded so we can reenable the mod?
