nao tein
eloy2030
Recent community posts
one more...
https://onedrive.live.com/?cid=6bce30ead55a3edc&id=6BCE30EAD55A3EDC%21416&authkey=!AG5n5lKFCgN7pM8
enjoy!
edit: im posting on onedrive because i dont want to add an extension to chrome... hope it doesnt mess the rules too much
no, that doesn´t take the bot out of the collection loop... I want to get him out of the collection loop if there are no more seeds to pick or if the storage is empty... afaik, theres now way to do that now, hence, the post
or am i missing something?
edit: the example u provide (from the post) actually does take the bot out of the collection loop. Problem, is this is VERY inefficient. I want to break the loop ONLY when the storage is empty, not every time it is not full. That way I would need more bots to make the same task, which is what I want to avoid. (in may case, having to open the bot to take the seeds out, in any case, more work)
the code is this
...and the problem happens when (if) somehow there are no more trees to cut and no more seeds lying around... can u think of an (automated) solution for that with the available tools?
tks!
edit: if the ¨until storage is empty/not empty¨ option would be available, I could have one bot deliver to storage, and only pick until ¨storage is empty¨
something like this (but change ¨until inventory empty¨ for ¨until storage empty¨
hope it makes sense.
I thought of a good example of how to use the ¨if¨ statement. (at leas I think so)
Sometime when having multiple robots collecting the same (plantable) thing (tree seeds, cereal, apples) Production would be interrupeted because the thing that needs to be picked up is the same thing u need to be able to pick it up.
ie. If bot doesn't plant because his hands are not full no more tree will grow and he will have nothing to collect.
so, ¨if (item) is not in range¨ or ¨if storage is empty¨ would come in handy here.
Edit: We might need an ¨end¨ statement as as well, to move out of the loo... or something similar.
when data storage was implemented was a huge change and improvement. Now that I have +200 bot it is starting to be difficult to keep track of all the disks, plus, all those disks lying around. Furthermore, If I want to save, change or restore a disk, I, sometime, have to walk a long distance.
I was thinking of a different way:
Use the bot assembler as a data storage. We would, still, have to use the disks (or maybe not) to save the data and then ¨upload¨ it into the assembler, then if we want to do something with that data, we just select a bot and (somehow, a scroll list, maybe) we can do it from there, from everywhere on the map.
maybe it is too much, I dont know, and ¨naming¨ would have to be implemented first, but I think it would be a nice improvement.