OK...so I'm trying to get my bot to chop logs until hands empty OR storage full...if I nest the hands empty command inside the full storage one, it will chop trees all over and if do the reverse, its axe will break and not be replenished until wood storage fills...anyone have an elegant solution for this?
My goal is to use as few steps as possible...I hope for deeper logic, even variables :D - 'Human Resource Machine'esque
If you do it that way, bot will chop logs until axe breaks even if storage is full. Right now, it will chop one tree each time storage empties and two other bots are basically always immediately putting a log in storage to fill it back up again. Only, once the axe breaks - unless storage is full, it will not replace it with a new one.
I do a similar thing kernelstubbs, but have an additional repeat within the hands empty.
This inner most repeat is an "until Log storage is NOT empty" and causes a loop of nothing. So the robot sits idle waiting for some room in storage before proceeding. The combined repeats mean the robot handles the storage filling up before or after the robot having an axe.
Note I just make a bunch of tools and leave them on the ground near my workers, so let them find their own tool :)
It did take a bit of trial and error to get to this working setup.
I haven't had any problems with this kind of setup
it can run for hours unattended without any overflow and your logging camp looks clean
I used until storage not for both repeat loops.
by doing it this way the repeat loop pauses the bot until the storage isnt full and parks my bot in the base of my logging camp. the outer repeat loop creates a delay before the bot can start mining if the storage is no longer full. this is nice as there are usually 1 or 2 bots with logs ready to re top off the storage to full. without the delay the bot begin chopping trees even though the storage was refilled within a second of it being not full.
This is also a handy way to add delay for any other operation and all you have to do to increase the delay is make the to move points further away from each other.
and since these steps are only when storage is not full it doesn't slow them down at all.
the last section is just for once his tool is broken to go make another one on his own and pick it up.
that way i don't need to have mountains of pre-made tools in the sky.
Now only if i new what to do with all these tree seeds and stones!!!!!
Everything else has a place but them
This actually gave me an idea...by adding an "until log storage not full" to the start of my loop, it will pause there until a log is removed - then the bot will cut one tree and one tree only until another is removed.
I use this Code, to let my Bot do it's work and re fit it's tool. All of my Bots with a Tool that breaks do that on a per tool created Workbench.
nope he loops only sometimes after loading the game, if you setup this in a active save the bot stops fine. i play for houres with it and mostly need to search for him when he stops. i already extended this code so he can work on a apple tree farm as primary, sourced on apple storage and switches over to pine trees until Logs are full and stops when the log storage is near full.
