Spidertron Automation

by ILLISIS

Automated Spidertrons; have the ability to move, set logistic requests, construct, deconstruct, repair, upgrade entities/blueprints and destroy enemies of any size, anywhere on the map with items from your logistic network for the ultimate fire and forget automation and megabase quality of life experience with unmatched scaling potential.

Tweaks
19 hours ago
1.1 - 2.0
34.9K
Logistics Combat Logistic network

b Non-recoverable error when mining a blue constructron

2 years ago

When mining a blue constructron

The mod Constructron-Continued (1.0.5) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event Constructron-Continued::on_nth_tick(60)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
    [C]: in function '__index'
    __Constructron-Continued__/control.lua:806: in function '?'
    __Constructron-Continued__/control.lua:573: in function 'do_until_leave'
    __Constructron-Continued__/control.lua:1118: in function 'do_job'
    __Constructron-Continued__/control.lua:1136: in function <__Constructron-Continued__/control.lua:1127>
2 years ago

Thanks, there is a lot of validation not taking place in many functions. At the end of the day it's much cleaner to wait until a job is complete.

What was the reason for mining it at that time?

2 years ago

It was requesting items that are not in the local logistics network. When this happens, the Constructron deadlocks. I can manually clear its logistic requests, but I still have to mine it to move it, and so I still get the crash.

Adding support for gathering resources from different networks may be a feature request unto itself. I can explain more about why I need that here, or make another thread. Let me know.

2 years ago

I'm getting lots of apparent deadlocks. They just stop working. Usually they are blue when this happens. Mining them and placing them again usually un-sticks it, but it's manual labor that kind of defeats the purpose of the mod.

2 years ago

Closing this thread as well, v1.0.7 resolved this issue.