Page 1 of 1

[15.19] Crash, related to Mods most likely.

Posted: Fri Jun 09, 2017 12:29 am
by Coltaine
The culprit is almost 100% likely to be the mod Picker Extended in collaboration with Nanobots: Early Bots, at least if one removes the chair->pc interface device from the equation. I couldn't find a mod-specific bug report sub-forum which is why I'm posting it here.

I was placing a Nanobot logistics network interface, realised I'd placed it in the wrong spot as it was unpowered and used Picker's nudge function to move it, which caused a crash. This is repeatable, I've done it several times. It will not crash immediately, and also seems to not happen until you've moved the Nanobot logistics interface into the range of a powerpole and further on another tile.

I did a quick recording: https://www.youtube.com/watch?v=b369gypZn-0 (Sorry for the slightly fussy quality I couldn't be bothered to fix up the settings for display capture and I feel it gets the point across just fine)

Mods enabled:
FARL
What is it Really Used For
Bob's Inserters
Bottleneck
Bottleneck Logistics
Even Distribution
Greedy Quickbar Filters
Helmod
Nanobots
Picker Extended
Upgrade Planner
Angels Infinite Ores

(Is this where I say "Nexela please fix"? :P )

Re: [15.19] Crash, related to Mods most likely.

Posted: Fri Jun 09, 2017 1:20 am
by Nexela
One one hand yes, this is where you say it :) On the other hand it is a hard crash so that requires the devs to fix, On the third hand I was thinking to myself the other day. I added a picker api for moving stuff but I don't think I ever added that to nanobots :)

Re: [15.19] Crash, related to Mods most likely.

Posted: Fri Jun 09, 2017 3:02 am
by Nexela
Some background

Reproduced with nanobots and picker (could probably just use .teleport() to cause it), The roboport has 0 inventory and 0 charging ports.

Move it from a place with no power into an electrical grid and crash occurs.

Re: [15.19] Crash, related to Mods most likely.

Posted: Sun Jun 11, 2017 8:10 pm
by Rseding91
Thanks for the report. This is now fixed for the next version of 0.15.