Automatic Logistic Chests

by Daschi

Automatically configures item requests and inserter conditions. Supports all logistic chests: passive provider, active provider, storage, requester, and buffer.

Utilities
7 months ago
1.0 - 2.0
10.3K
Logistic network Circuit network

b [fixed] non-recoverable error on rocket silos.

7 months ago

The mod Automatic Logistic Chests (2.0.1) 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 200)
automatic-logistic-chests/runtime/utils.lua:69: attempt to index field '?' (a nil value)
stack traceback:
automatic-logistic-chests/runtime/utils.lua:69: in function 'get_stack_size'
automatic-logistic-chests/runtime/recipe-handler.lua:105: in function 'get_educts_amounts'
automatic-logistic-chests/runtime/recipe-handler.lua:45: in function 'gather_educts_and_quality'
automatic-logistic-chests/runtime/logistics-handler.lua:15: in function 'handle_requester'
automatic-logistic-chests/runtime/logistics-handler.lua:161: in function 'handle_container'
...utomatic-logistic-chests-refresh-all-logistic-chests.lua:13: in function <...utomatic-logistic-chests-refresh-all-logistic-chests.lua:3>

7 months ago
(updated 7 months ago)

It looks like this issue is caused by an item defined within the Ingredient Integrations that does not actually exist. For example, something like rocket-silo=wasd in the setting, where wasd is an item that the game does not recognize.

I’d love to understand what you configured and why, as this could help me improve the documentation for this setting. Additionally, if there's anything I can do to assist you in achieving what you intended with this setting, let me know!

That said, I’ll also implement a safeguard to prevent crashes when non-existent items (or entities for that matter) are declared. Instead of causing a game-breaking error, the game will print a warning instead. Thanks for reporting this!

7 months ago

This issue has been addressed in version 2.1.0! A safeguard has been implemented to prevent crashes when non-existent items or entities are declared in integration settings. Instead of an error being thrown, a warning message will now be shown instead.

Feel free to still report any issues if you need help with integration settings or if something else isn't working as expected. Thanks again for your report!

New response