Issue type:

• 🐛 Bug

Short description:

When moving from one location to another, sometimes the console gets spammed every tick with the warning message from the title. This is not a full error, nothing crashes, but the message says to report this issue.

Steps to reproduce the problem:

Instead of actual steps to do this at home, I can sadly only describe what is going on because we do not even have found a clear pattern when this happens.
We have currently 2 networks that exert this behavior.

1. One is contained within a single chunk, this is a small network that takes items from an input barrel and distributes them across 8 modded furnaces, then return the output to an Applied Energistics interface block. When we leave the area this machine is constructed in, the console gets spammed with this message:
   "[27Feb2025 15:30:19.242] [Server thread/WARN] [integrateddynamics/]: Attempted to tick a part that was not properly unloaded. Report this to the Integrated Dynamics issue tracker with details on what you did leading up to this stacktrace. The part was forcefully unloaded" and "No part state for part at position DimPos(XYZ, worldreference=null) side west was found. World loaded = true, Chunk loaded = true, Part container = null, Parts = null" (stacktrace is in the appended pictures). An additional thing popped up related to this, the network seemed to suddenly forget all the variables within this network. "Error: Variable ID XXXX not found within the network" for the variables used within the variables of the erroring parts. Breaking a cable with no parts attached and replacing it removes this second error, but the console spam persists. Only a full server restart removes the log spam
2. Across multiple chunks we have a network that navigates items back and forth to take some instruction from the chosen item (the tech of which is not made using InDy, so I doubt this would be relevant). This network has shown this behavior for the first time. The log message is the same as in example 1.

Expected behaviour:

I expect the console to not get spammed with these logs, because they usually indicate something went wrong at some point.

Versions:

• The installed Integrated mods:
  • IntegratedDynamics-1.20.1-1.25.2.jar
  • IntegratedTerminals-1.20.1-1.6.5.jar
  • IntegratedTunnels-1.20.1-1.8.34.jar
• Minecraft: 1.20.1
• Mod loader version: Forge 47.3.27

I am unsure if this is a compatibility between InDy and the blocks of the mods attached, so here is a list of the modded blocks that were next to the reported coordinates inside the stacktrace:

• Mana & Artifice 3.1.0.4 Runeforge
• Create 0.5.1j Fluid Tank
• Applied Energistics 15.3.3 Pattern Provider
• ExtendedAE 1.20-1.1.11-forge Extended Pattern Provider

Screenshots:

Console Spam:

Stacktrace:

Sure, this is the full log file from today:
2025-03-04-1.log.gz

And because the spamming started yesterday already (again), here is the beginning of said spam:
2025-03-05-1.log.gz

The log files are pretty much purely that error message repeated about a million times over. As soon as I send the "stop" command to the java gui it halts that spamming and proceeds to shut down the server. Unless you mean something else that I dont know about, this is pretty much all I can tell you sadly

It might be good to take this up with your modpack author.

I would also suspect that you could see strange behaviour from other mods in your pack resulting from unsaved chunks.

This is a selfmade kitchen sink pack, and I am one of the authors effectively. Also, I was able to collect some more data for analysis:

• The machine is hooked up to an ExtendedAE pattern provider. The console spam only starts once the autocrafting uses this machine - even when the machine is still fully loaded.
• Screenshots of the machine in case those can help:
  
  
  
  
  

Could you send your full log file?

Thanks for reporting!

This probably means there's a chunk saving issue in your world that is caused by some other mod.
Do you see anything in the logs that may indicate that?

I could not find anything in your logs showing what is causing the chunk save issues.
In any case, I will push a change that will reduce the log spam to a single occurrence.
This will both allow you to pinpoint the precise moment in time the problem is created (which may help finding the root cause of the problem), and it will reduce log size.