The mod Automatic Logistic Chests (1.5.3) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event automatic-logistic-chests::automatic-logistic-chests-refresh-all-logistic-chests (ID 219)
trying to change logistic section that is not manual
stack traceback:
[C]: in function 'clear_slot'
automatic-logistic-chests/runtime/logistics-handler.lua:38: in function 'handle_requester'
automatic-logistic-chests/runtime/logistics-handler.lua:158: in function 'handle_container'
...utomatic-logistic-chests-refresh-all-logistic-chests.lua:13: in function <...utomatic-logistic-chests-refresh-all-logistic-chests.lua:3>

Hi, thank you for reporting this issue! Based on the error message, it seems like the problem occurs when the mod attempts to change a logistic section that isn’t manually configurable. This could indicate a specific requester or buffer chest in your world behaving differently from others.

To help me reproduce and investigate the issue further, could you please provide a bit more information?

1. Do you know if there’s any chest in your setup that might be configured differently or have unique settings compared to others?
2. Does this error occur every time you try to refresh all chests, or was it a one-time issue?
3. Alternatively, if possible, could you share your save file with me? This would allow me to reproduce the bug and work on a fix more effectively.

Thanks again for your help!

I just got an idea regarding this. Do you by any chance have any circuit logic that sets logistic requests in the default logistic section in request and/or buffer chests?

Can you please confirm if that is the case for your map/setup?

I disabled your mod, I'm sorry, but most likely yes, there are requests initiated by the logical network.

I'm not sure about the "default" section, I didn't set up anything on purpose, just connected the wires and turned on the "set request" mode

No need to be sorry, but this does indeed sound like it’s most likely caused by the circuit network setting requests. Thanks for confirming! I’ll aim to have a fix ready by next weekend.

Thanks :)

This issue has been fixed in version 2.0.1. Thanks again for your report! I’d really appreciate it if you could test it in your world to confirm that it is working for you as well.