Swarm Miner - Quarry Up Where You Want. Version 2.0

pastebin get LXLBZK25 disk/startup

• Mining of Preset Area
• Uses Standard by now 3 layers at once mining system.
• No limit to amount of turtles working - you can use 1 or 30 - it will still work like it should with turtles talking to each other and working together.
• Included Scanner that shows where turtles are in area and what they are doing/mining.
• Ability to continue from where it stopped after server stop/crash or chunk unload
• Delivers mined blocks in selected chest or into provided Enderchest
• Refuels from selected chest or from provided enderchest
• Can drop unneeded cobble (or any other material) increasing time it can mine between dropping mined material/decrease amount of trash in mined material
• Automatically recognizes chests and removes content before mining it
• Never mines anything that is a peripheral (chests from feature before excluded)
• Auto stops at y=5 - never gets stuck on bedrock! Mines layer 4 if needed. (can be changed to dig deeper in case of flat bedrock)
• Full installer floppy disk that downloads other files and can update them if asked (update attribute)

• Minimal mining level can be adjusted by changing levelmin value inside swarminer file on the floppy disk.
• Installed Vacuum cleaner that collects most of dropped items that turtle finds while mining
• Breaks minecarts and collects them too. In case of storage minecarts most of contents gets picked up by Vacuum cleaner.
• Startup files in miner and scanner contains Top Level Coroutine Overwrite that removes rednet coroutine and Api. That lovers amount of event that turtles receive by half.
• Main Installer Floppy Disk automagicly detects witch drive its run from and allows auto installation or miner or scanner depending on if its run on turtle/computer
• Scanner can be used to pause/unpause turtles in its area of effect
• Main Installer Floppy Disk can be preformatted with order that allows faster deployment of mining turtles
• All Mining Turtles and Scanner contain gps host code spreading gps signal in area
• Automatically add labels to all data storage mediums its used on.
• Scanners share data about turtles in their zones of influence.
• Emergency Beacon - any Turtle that crashes to shell will emit ERROR Signal
• If You place a Monitor next to Scanner it will print basic stats data on it.

• In Mining Turtles:

1. Press "p" to pause and "o" to unpause selected turtle

• In Scanner

1. Press "p" to pause and "o" to unpause all turtles in signal range
2. Press "t" to change type of informations that are provided by it
3. Left Right Up and Down keys move map marker allowing you to inspect map
4. Pg_Up (or "w") and PG_Down (or "s") allow you to scroll trough list of turtles. Map maker will move to this turtle if its possible.

• Instaler file is made to be run from floppy disk - it will not work from "/" but it may work if placed inside any directory (not 100% tested)
• System requires gps signal in area of its effect ( You can set up effective gps signal in area by setting up 4-5 scanner computers in area [all programs contain gps host code inside of them])
• gps-less mode is coded hoever its not stable on server crashes and stops
• To mine area system needs

1. Start Point and Direction
2. Forward Size of one Sector (values under 10 work best - for large area mines simply set large amount of repeats. Also values under 3 while supported may lead to weird side effects.)
3. Sideways (to right) Size of one Sector (same as above)
4. How many blocks down to mine [min 3] (if gets to y=5 then it wont go deeper - can be changed in program code.)
5. How many Sectors to mine Forward
6. How many Sectors to mine Sideways (to right)
7. Manual refuel/dropoff point and direction. (by default its same as start but backwards)

• Each turtle needs those settings and items to work

1. If it uses Enderchests then it will ask for them
2. If it drops cobble will ask for one piece for furure reference.
3. If neater it will not ask for anything.

• If starting from preformated order turtle will attempt to get some fuel at start. If has enderchests it will look there or if not it will look in chest above it.
• Refuel point is a 2 chest setup one in front of this point and one above it. Front one recives Mined items and top one is where turtles look for fuel (if enderchests are used turtles never go here) There is a screenshot of correct refuel point in spoiler below.
• System includes many undocumented command line options that allow advanced users to use system more efficient.

1. You can define areas (cuboids) inside area that will not be mined by turtles ( can be used to preserve mob spawner ect. Right now only trough adding in predefined order (addzone atribute in floppy disk) or manual editing of order.log file.
2. Full Gps - less mode - Not 100% Stable with current system - can be turned on by manually changing flag in swarminer file.

• Try to have the turtle's check which direction they're facing at the beginning. I've noticed if I don't place my turtles facing north every time they go the completely wrong place.
• Also, my turtles will not empty their inventories into the drop off chest, they just sit there and select every slot over and over.
• My turtle got an ambiguous gps position, so it moved and tried again - and then crashed with an error - something to do with __sub
• Not sure of why these bugs are happening. This is ftb unleashed 1.5.2. I'll reply with more info if you need it.

• Hmm… There is code that detects direction where its facting. No idea why its not working. works perfect for me but i made this so by definition it should work for me. It cant detect where its facing with no fuel.
• Either turtle don't have any fuel - give him some for startup or you didn't place drop-off and refuel chest correctly. IN default mode turtle faces backwards from start point for drop off and looks up for refuel.
• That means there is not strong gps signal in area "ambiguous gps" is i think 3 sources 4 are needed for accurate gps - try setting up some scanners around - they act like gps host too. __Sub part i can't solve cause i don't know witch line it happened at. - can Guesstimate based on your questions but well.
• I tested it on Unleashed, just computercraft and computerccraft+openPeripherals. So your bugs should not be connected to Unleashed.

• From fuel standpoint i was using 1000 during testing. I meant to change it to 100 + distance from refuel point but i never go to it…. It will be in next update (tomorrow probably).
• The way to clear current order and a recall function are coded into turtles - it simply never got added to scanners. I will look into adding it to scanners. Hoewer due to probable damage it could cause to your mine it will probably be a argument called when manually running scanner and not an option inside scanner.
• For the last part i don't think there even is the way to detect amount of viable fuel in chest - i could detect all items in chest and divide it by space left… but that would not give you info how effective each item is and if someone simply didn't put a ton of cobble into it.

• Refueling System tweaked - Now it refuels based on how far it has to go from where its mining to refueling station (in case of Enderchests how far its from start of mine so it can always go back) + small buffor just in case. Also now don't overfuels - fuel it don't needs is placed back in chest.
• Added WipeOrder, Goto, and Emergency arguments to scanner. First one WipesOrder - Second issues Goto command to provided cords (asks for them) and 3th one Crashes all turtles in area (Emergency Break :)/> )
• I think detecting amount of fuel in fuel chest could be done with OpenPeripherals but i am not that good with that. :)/> Sorry.
• Also i will make Documentation of all Arguments that can be called in Scanner/ Swarminer and Installer and what they do. Most of them are Redundant but could be useful for people.

• Added queue system for refueling purposes
• Added time of last message to scanner system (in second page - press t to toggle to second page)
• Refueling code optimized - now 3 times faster
• Added compression code - Turtle will always check if he can't squeeze a little bit more space in its inventory.
• Bug-fix in path-finding - tx to lewanator1 for finding and reporting bug.

 disk/startup update 

• Scanners now attempt to share info about turtles in range.if data about turtle was received form another scanner (and said turtle is out of range of this one) it will show distance of "EX" (in second page - press t to toggle to second page)

 disk/startup update 

disk/startup update

wojbie, on 20 October 2013 - 05:25 PM said:

Face-palm. I placed a dot in wrong place there - gimme a sec to fix it and it should work.


EDIT: Fixed!!

run

disk/startup update

and try again

HeffeD, on 21 October 2013 - 01:17 PM said:

That seems to have fixed it! Thanks for the quick fix. :D/>

I think there are still some pathfinding issues because the turtles have a tendency to get stuck. Sometimes they will just go up and down, or back and forth a single block until they run out of fuel. (This was without enderchests, they may not run out of fuel with enderchests) Or, I will find them just sitting there not doing anything. (Yes, I'm aware of the compression function, but they aren't doing this)

HeffeD, on 21 October 2013 - 01:17 PM said:

I have also seen some that report that they are out of fuel, and when I go check on them, their inventory is empty. So I can only assume they've just dropped off all of the items they've mined and somehow got lost on their way back, (probably doing the bouncing back and forth thing I mentioned) or is there some instance where they will drop all of their inventory?

HeffeD, on 21 October 2013 - 01:17 PM said:

The scanner is very nice for keeping tabs on what the various turtles are doing, and makes it pretty easy to go find them if they're stuck. :)/>

HeffeD, on 21 October 2013 - 01:17 PM said:

And they apparently get stuck on storage minecarts? If the minecart is below them, they will suck all of the items out of the chest, which is nice, but then they will just sit there tapping the cart forever. I'm assuming that this is because they attack the cart instead of mine it? And if the cart is in front of them, they won't suck the items out, they just sit and tap it.

I haven't actually seen them stuck on a minecart in the wild, but I've placed a few minecarts in their path to see what they do when they find one, and they behave as I've stated.

HeffeD, on 21 October 2013 - 01:17 PM said:

There are still some issues, but this is is a pretty neat script! B)/>

HeffeD, on 21 October 2013 - 01:17 PM said:

Something that would make it even nicer is if it had a block compare function so it doesn't need to mine absolutely everything, which tends to get you a lot of blocks that you don't want/need. Yes, I know that you can have the turtles drop the cobble, but in the interests of lag, dropping a bunch of entities on the ground isn't as prefereable as just not mining the the things you don't want to start with.

This script I think operates very efficiently.
http://www.computerc...tle-ore-quarry/

It will still mine three layers at a time, but it only mines the middle layer completely because that is the layer that it travels in. For the layers above and below the turtle, it compares your "noise" blocks, so it only actually mines the valuable things, leaving the unwanted stone and dirt behind. So for example, you give it a stone block and a dirt block, and it will mine everything that isn't these blocks. It also starts at the bottom of the world, and works up, so you mine the most valuable ores first. :ph34r:/>

Please note that I'm not trying to tell you that you should make your script more like somebody else's. I'm just pointing out some functionality that could be useful.

wojbie, on 21 October 2013 - 02:44 PM said:

Pathfinding is a bit random based and i am firm belier that turtle should not touch a block outside of quarry - Still having trouble getting exact situations this happens but i think that by now i already fixed most of them. Turtles stuck doing nothing could be waiting in queue for unloading station - they stop about 15 blocks from it and wait until its empty. Other than that i didn't have that problems thanks for report i will look into it.

wojbie, on 21 October 2013 - 02:44 PM said:

They should never drop inventory unless 1) in the enderchests or 2) are 100% sure that they are in maintence point and drop there. So most likly chances are they got lost back - manual refueling point works best at default settings - using other point there are chance that turtle will get lost sometimes.

wojbie, on 21 October 2013 - 02:44 PM said:

Minecarts are kinda tricky with detection and emptying - depending of small changes of position you could be able to suck content or not ect,
Otherwise they get detected by mob removal system and dealt with by attacking..repeatedly.. That they don't break is kinda dependand on server lag.
I am working on that but well there is no 100% sure way that works

wojbie, on 21 October 2013 - 02:44 PM said:

While i agree that this functionality is usefully i Want to point out one problem i have with that - if you use program that leaves stone it to mine large area it leaves a lot of 1x1x2 1x1x3 shafts that work as monster-spawn points. I seen that end up badly. also a lot of spider spawn plates on those middle levels. Also i like making big holes. - I tend to pump them full of lava from neather and make a base inside.

wojbie, on 21 October 2013 - 02:44 PM said:

As for dropping cobble turtles attempt to drop full stacks of cobble at the time and they disappear after 5 min so there is not much buildup of entities. From large scale test i run on this code there where no issues from those ( and i tested a 102 turtles quarry :P/> - Scanner Still perfectly detected all of them. )

wojbie, on 21 October 2013 - 02:44 PM said:

Never saw point of starting from a bottom. Real quarry should start from top - no-one sane is mining from earth core after all are they?
Point of quarry is to get 100% of stuff in area - you will get that stuff anyways.

HeffeD, on 21 October 2013 - 03:58 PM said:

No server lag, as I'm not playing on a server. (Just the internal server in single player) I guess the turtles may break the cart eventually. I've only sat and watched for a minute and assumed the cart would never break… :unsure:/>

HeffeD, on 21 October 2013 - 03:58 PM said:

I haven't tried the drop cobble option, I was just going by what I witnessed in one of my quarries with a full turtle moving from the bottom of the quarry to a new sector. (I've seen this happen twice) The turtle mines a shaft up the edge of its new sector, spitting each piece of cobble out individually. (Leaving potentially 60+ entities on the ground from a single turtle) So in this instance, it may behave differently than the standard cobble drop routine?

GeneralHARM, on 21 October 2013 - 07:12 PM said:

Love the program thank you,
i had it setup and working nicely last night, but i wanted to change the grid and reset it, go i went out and gathered up all of my miners, now i have setup and deployed a single miner to the grid that i want, but when i try to add a new miner to the swarm i get
Love the program getting a weird error

Running parallel:22: Swarminer:858: index expected, got nil

just tried to deploy another, it mined 9 blocks then returned

miningparallel :22: swarminer:130: attempt to compare nil with number

HeffeD, on 21 October 2013 - 07:18 PM said:

On my current quarry, (48x48) using the enderchests I'm not having any turtles get lost and run out of fuel, but I have had two of them just stop working for no reason. Plenty of room in inventory, plenty of fuel. One had mined the block in front of it, but didn't move forward to the empty space before stopping, the other had just reached the edge of its sector and had turned, but it hadn't mined the block in front of it.

HeffeD, on 21 October 2013 - 07:18 PM said:

I also saw a very odd bit of pathfinding. A turtle had just started mining a sector at the surface, and another had just come up from bedrock and was traveling to its new sector. The turtle on the surface stopped to run the compression routine, and the other turtle ran into it. The original turtle placed an enderchest and dumped its inventory, then continued mining. Oddly, the second turtle turned exactly where it had and was following it a block behind.

I thought that as soon as the first turtle reached the edge of the sector and turned, the second turtle would continue on to its new sector. However, it made the same turn that the first turtle did, and continued following it! I watched them until it reached the other end of the sector and turned, with the second turtle again following. :unsure:/>

I ran over to the scanner to see if it listed two turtles mining the same sector. I didn't see any duplicates, so I decided to go over and get both of the turtle ID's, so I could see which sector the the scanner thought the turtles were mining. But when I got back over to the turtles, the second turtle was no longer following the other turtle and had started mining its own sector. But it had very definitely seen the turtle follow the other for three rows in a sector. :huh:/>

I had seen a turtle following another one previously, but it was on my initial testing quarry where I was intentionally trying to confuse the system by purposefully breaking and re-placing turtles, and even doing some config shuffling and giving two turtles the same ID. (In case you're interested, the scanner display will switch back and forth when each turtle with the same ID communcicates, but other than that, it routed them to separate sectors throughout the quarry! :o/> Nice!) So I thought it was probably due to me deliberately trying to confuse it, so I just broke the second turtle. This time however, it was a standard, start the quarry and let it run. So I have no idea why it did that, or how it managed to correct itself, but I figured you'd probably want to know any odd things that happen while running your scripts.

sirrasmusdk, on 22 October 2013 - 06:46 AM said:

Okay my computer keeps saying,

Finding Position…
Could not determine
no gps online
enter scanner data

i enter and it goes to this screen:



I really want this to work and im litterally losing my mind currently :/

disk/startup update

wojbie, on 22 October 2013 - 04:42 AM said:

I am using internal debug code and I am as lost as you - according to code they are doing something - but i have no idea what, or why. Still a good pause/unpause seems to fix that/reset also works/unloading and reloading chunk - so they are able to recover from this adleast.

wojbie, on 22 October 2013 - 04:42 AM said:

Ahahaha you are seeing anti-sector-collision code in action - when somehow 2 turtles decide to mine same sector they enter into a "competition" mode - first one to next layer wins and gets to keep sector while 2nd one has to find new one for himself. It happens from time to time and looks weird when happening :lol:/> Weirdest code i done in loooong time.

HeffeD, on 22 October 2013 - 12:30 PM said:

If pause/unpause works, I guess you could add a temporary quick and dirty workaround until you figure out what's happening. You could have the scanner pause and unpause the turtles every 5 minutes or so. That wouldn't slow things down very much, and would hopefully free up any turtles that have stopped working.

HeffeD, on 22 October 2013 - 12:30 PM said:

Oh good, it's intentional! :lol:/> Like I said, I couldn't figure out why that had happened, and how it could have fixed itself after it started happening. So it may be weird code, but it does what it's supposed to do. B)/>

ZudoHackz, on 22 October 2013 - 01:37 PM said:

Awesome. I can't believe I am the first 200+ poster on this thread :)/>

wojbie, on 22 October 2013 - 04:42 AM said:

GeneralHARM, on 21 October 2013 - 07:12 PM said:

Love the program thank you,
i had it setup and working nicely last night, but i wanted to change the grid and reset it, go i went out and gathered up all of my miners, now i have setup and deployed a single miner to the grid that i want, but when i try to add a new miner to the swarm i get
Love the program getting a weird error

Running parallel:22: Swarminer:858: index expected, got nil

just tried to deploy another, it mined 9 blocks then returned

miningparallel :22: swarminer:130: attempt to compare nil with number

Did a Ninja Fix on that one. Weird bug - can you provide me with contents of current.log files from both of those turtles? That would help me making it less likely to happen - sadly it never seems to happen to me. After that update program and that should not happen again.

GeneralHARM, on 22 October 2013 - 03:23 PM said:

I'll see if i have the log in one of my turtles when i check it out tonight, i wiped a few of them and re-tasked them so maybe we'll be lucky.

GeneralHARM, on 22 October 2013 - 03:23 PM said:

On a side note how effective is this system at getting Diamond if it does not go all the way to bedrock? havent been able to run it that way down yet.

wojbie, on 22 October 2013 - 03:40 PM said:

When i want to dig to bedrock i usually say i want 255 deep - nice round number.

wojbie, on 22 October 2013 - 03:40 PM said:

Turtles Stopping in middle of whatever they where doing - Negated to lover levels than before - or could be lucky. Still could not get out of them why…. Irritating.

HeffeD, on 22 October 2013 - 10:49 PM said:

I just use whatever height I'm starting from. If I'm starting the quarry at level 74, I'll set the depth to 74. With flat bedrock, that mines all the way down.

local levelmin=5

wojbie, on 23 October 2013 - 03:47 AM said:

Ahh thats your problem - Turtles gave hard-coded bedrock level at level 5!!

1. Those errors are biggest headscrachers i had on this program yet
2. I have no idea what happened

Mad_Professor, on 24 October 2013 - 09:15 AM said:

I gave your script a shot in my single player, it doesn't work.

I got 4 scanners up, the turtle can't find gps, I turned off one scanner and now the turtle has gps. I set up a 128L x 3W x 3D repeat 10 times, I sent it on it's way. 10 minutes went by, it did not come back to refuel/dropoff, it only had 1000 fuel. So I went after it, dug 1000 blocks following the single hole, gave up.

I treid again with a new setup with 5 scanners, same problem turtle could not find gps and scanner number 5 is off by 5 blocks and scanner 2 is off by 1 block. Removed those two scanner and now the turtle has GPS, I set up the sector again this time I did 3x3x3 repeat once and limited the fuel to 100. It move one block forward then said "work done!"

It's broken, or I'm doing something really wrong.

• http://www.computerc...-to-make-a-gps/
• http://www.computerc...osition-system/

honsbeekiejj, on 24 October 2013 - 12:10 PM said:

hey I'm running your programm now and i had 3 turtles running and they stopped at different levels saying: too long without yielding i believe they said line 85 but not sure will edit when it happens again

honsbeekiejj, on 24 October 2013 - 12:21 PM said:

Miningparallel:22:swarminer:251: Too long without yielding

wojbie, on 24 October 2013 - 12:18 PM said:

Mad_Professor, on 24 October 2013 - 09:15 AM said:

I gave your script a shot in my single player, it doesn't work.

I got 4 scanners up, the turtle can't find gps, I turned off one scanner and now the turtle has gps. I set up a 128L x 3W x 3D repeat 10 times, I sent it on it's way. 10 minutes went by, it did not come back to refuel/dropoff, it only had 1000 fuel. So I went after it, dug 1000 blocks following the single hole, gave up.

I treid again with a new setup with 5 scanners, same problem turtle could not find gps and scanner number 5 is off by 5 blocks and scanner 2 is off by 1 block. Removed those two scanner and now the turtle has GPS, I set up the sector again this time I did 3x3x3 repeat once and limited the fuel to 100. It move one block forward then said "work done!"

It's broken, or I'm doing something really wrong.

Ok i see your problem

First:
Read How GPS Systems work in Minecraft -

• http://www.computerc...-to-make-a-gps/
• http://www.computerc...osition-system/

Basically you need to set up scanners in correct way for them to provide good gps signal.

Second:
Triple check coordinates you are giving to the program. Both scanners and in Orders you are programming.
In Scanners its asking for computer coordinates not wireless modem coordinates(common mistake - sounds like that from you rapport.)
If you type one coordinate wrong program will assume you meant it and go there.

3th
You need to find that first turtle. If it is in area It will keep sending data to other turtles causing Work Done to be issued. Scanners should be able to detect it if its in range and tell you its position ( after you set up good gps)

Also how did you limit fuel to 100?? Program should have not started with 100 fuel - there is lock on that. Unless you edited code than i am sorry but thats not under warranty.

Hope That helps.

local i = turtle.getFuelLevel()

mistagnerd, on 25 October 2013 - 06:21 AM said:

Hello, I'm quite new to computercraft and am having trouble following your imgur album. Do you by chance have a video explaining the setup process? I wil be away for a few days. So I will check back then! Thank you for any help you can provide.

• version of computerraft
• contents of current.log file
• type of turtle (advanced or normal)

wojbie, on 25 October 2013 - 09:03 AM said:

I am working on "Too long without yielding" issue but i am having trouble tracking down witch part of code is responsible for making that loop.
Sadly function that you are pointing to is called by many functions inside program and every time i add some kind of debug code i get nothing. Still i am working on it so no worries. I will have it tracked down. Still it would be useful if you people provided me with

• version of computerraft
• contents of current.log file
• type of turtle (advanced or normal)

wojbie, on 25 October 2013 - 09:36 AM said:

Can you tell me exactly in witch lines? That would help a lot.Cause you probably placed in in function that was causing problems.

wojbie, on 25 October 2013 - 09:36 AM said:

Can you tell me exactly in witch lines? That would help a lot.Cause you probably placed in in function that was causing problems.

• Bugfixes

 disk/startup update 

wojbie, on 25 October 2013 - 09:53 AM said:

perfect!!! ones in 86 88 90 92 are useless but one in 256 would get called every so often breaking yeld timer. Thats not a fix but a brute force hack - meh i needed it to anyways i will gladly take it. Ok Editing main file to have it inside - will make it smaller one thought 0.01 probably.
Will also include some bugfixes so.


UPDATE!! No version change

• Bugfixes

Run

 disk/startup update 

on your swarminer disk to download latest version

• version of computercraft (or modpack)
• contents of current.log file (when applicable)
• type of turtle (advanced or normal)

wojbie, on 25 October 2013 - 10:32 AM said:

When i post with update thing that means its on pastebin.
When you specify drop off point you are specifying empty space that faces (f:) drop-off chest and is under fuel chest - not a chest itself.
Also moved minimal fuel level up a bit in pastebin - should work better for you now. Had a lot of messages on priv and here saying that turtles took to much fuel so i lowered minimal amounts. now i upped them back up a bit - its hard to please everyone. So update again and it should work better. If not its a bug i need to look for.. again.

Also for All Future bugreports can i please get:

• version of computercraft (or modpack)
• contents of current.log file (when applicable)
• type of turtle (advanced or normal)

This is important info for me!

wojbie, on 25 October 2013 - 11:15 AM said:

ok i see you set dropoff chest somewhere away from main quarry and did a tunnel to it?
Then traffic jams are unavoidable in server-less system (like this one). Curent pathfinding system is designed for going over small roadblocks - they are not smart to wait at end of tunnel for other turtles to clear.
As i stated before its best if dropoff point is a startup point or somewhere withing a quarried area. Other points might work - but are not 100% sure.

As for current.log i need one from any of the turtles. Not in this case but for future reference.

wojbie, on 25 October 2013 - 11:48 AM said:

Ahh all of them formed one big queue? cause one of them was at refuel point and locked it down? that sounds probable.

wojbie, on 25 October 2013 - 12:40 PM said:

Well they are on exactly same pathinding code - of course they will go same way.
As for mining in same place? That should solve itself in about a minute - 2 minutes - see few posts before for explanation.

wojbie, on 25 October 2013 - 01:43 PM said:

How big is your sector size again… Also look inside of them what sector they assigned to themselves - if same one then there should resolve itself sooner or later. Hopefully.

wojbie, on 25 October 2013 - 02:18 PM said:

Why Exacly you made one sector 128 blocks long? Idea is sectors are small little squares that are mined by one turtle.

With sector like that i would suggest 16 repeats of sectors of 8Lx6Wx10D

No wonder you are having problems with code - Its not designed for such big sectors - idea is you make small sector and repeat it a lot of time on both axises.

wojbie, on 25 October 2013 - 02:30 PM said:

One of the features - each turtle acts like a mobile gps tower - providing gps signal to his brothers and sisters. And no there is no coded way to turn it off.

Also sorry to inform you but with this size of sector its unlikely that you will be able to get it t work - all auto-correction code will crap out on you. and conga lines will form.

scanner Goto

Mad_Professor, on 25 October 2013 - 02:27 PM said:

Because I can do it?

Mad_Professor, on 25 October 2013 - 02:27 PM said:

well it does work, but uh, some of these turtles are broadcasting gps, screwing things up for me. any ideas why?

HeffeD, on 25 October 2013 - 03:13 PM said:

Mad_Professor, on 25 October 2013 - 02:27 PM said:

Because I can do it?

Yes, you can do it, but it makes absolutely no sense. Were you perhaps thinking that "sector" meant, "entire area of quarry"?

Having a sector size this large will not save you any time using a swarm of turtles. The idea behind a swarm is that you break up a large area into lots of little pieces, then have a lot of turtles working on these little pieces! This is what makes the system efficient in terms of time.

So if you have, say, 10 turtles mining your quarry that is 128x6x10, your quarry will be completed in a tenth of the time as as single turtle mining the same area!

I find it easiest if you limit your quarries to chunk boundaries because that makes it easiest to set up chunkloaders, and 8x8 sectors work pretty well with this script. So if you want to mine a single chunk, use 8x8 sectors and repeat that twice in both directions. Put 4 turtles on that and you can mine the entire chunk in 1/4 the time it would take a single turtle to mine the same area.

Just upscale from there. Want a 64x64 quarry? Repeat 8x8 sectors 8 times in both directions. Then deploy as many turtles as you want.

Mad_Professor, on 25 October 2013 - 02:27 PM said:

well it does work, but uh, some of these turtles are broadcasting gps, screwing things up for me. any ideas why?

Well, it doesn't really work…

You're sending a swarm of turtles out to mine a single giant sector. Since there is just one sector, they'll all be trying to do the same thing, causing the "conga line" effect you're seeing.

Wojbie has code that if multiple turtles are trying to mine the same sector, it will be able to correct this by having a bit of a competition between the turtles. The first turtle to go down to the next mining layer will "win" and the other turtle will go on to mine a new sector. In your case, it would probably take well over an hour for the lead turtle to clear the first mining pass and move down to mine the next three layers. Therefore, all of the other turtles would be tagging along for quite a long time before they could be routed elsewhere!

Edit: Sorry Mad_Professor, I was in the middle of typing this up when you posted your latest reply. Glad to see you've got it sorted out!

wojbie, on 14 October 2013 - 02:59 PM said:

Well thanks to you i got idea to include vacuum cleaner into code :P/> It looks funny when turtle breaks minecraft and then begins to vaccum contents :)/>

EDIT: Just something for fun - how manu turtles do you see on image?

Spoiler

ATMunn, on 25 October 2013 - 03:59 PM said:

wojbie, on 14 October 2013 - 02:59 PM said:

Well thanks to you i got idea to include vacuum cleaner into code :P/> It looks funny when turtle breaks minecraft and then begins to vaccum contents :)/>

EDIT: Just something for fun - how manu turtles do you see on image?

Spoiler

I see 8.

wojbie, on 25 October 2013 - 04:08 PM said:

They will refuel until they get 400+"distance to start point" units of fuel - are you sure there is fuel in ender-chest?

wojbie, on 25 October 2013 - 03:44 PM said:

128x10 times 128x10 thats 16384x100 mine!!! Wow that turtle could be anywhere… Wierd thing is it should never started up - fuel lock should have prevented it friom starting unless you provided 17000 of fuel. - Ok another thing to look into.

wojbie, on 25 October 2013 - 03:33 PM said:

nope - Still preformatted on disk - Deplorer will be "advanced" option of placing turtle on disk/drive and giving it items. - Not connected to swarminer network in any shape or form. Only interaction will be when user activates recall mode - and that will be single impulse goto message to all turtles. There will be never a server in my swarm!

Think of it as speedloader for a quarry. As stupid as it sounds :D/>

I Got a 64 turtle quarry with a speedloader!!! :P/>

HeffeD, on 25 October 2013 - 07:32 PM said:

Or is your method to send the first turtle out manually just like you do now, (create the order, reboot the turtle and load the latest swarminer) then tell the deployer turtle to send out the rest?

honsbeekiejj, on 25 October 2013 - 06:50 PM said:

Miningparallel :22: turtle:22: Too long without yielding

edit current.log

wojbie, on 27 October 2013 - 11:11 AM said:

Did you play with them in creative mode?

Swarminer id: is id of computer assigned by ComputerCraft - I simply use that cause i have 100% knowledge it will be unique. Unless you pick one of labeled computers in creative and place it few times. In other words they are always unique in survival and in creative you need to watch out for duplicating. Same case for installer disks id - also assigned unique by ComputerCraft

Side Note - I am finishing working on that yield error - tx to help from ask a pro subforums i should be able minimize its happening.
Should be ready for release in next 24h.

Warlordjones, on 27 October 2013 - 12:34 PM said:

The program is working out very well for me, but not for the server I am running it on. When the server boots, all of my turtles booting at once is apparently causing CPU use to shoot through the roof. Would it be possible to insert a os.sleep(100) just before any turtle begins mining, to allow the server time to start up and stabilize. I tried doing this myself, but I cannot find the correct place to insert it!

Mad_Professor, on 27 October 2013 - 11:22 AM said:

It's single player survival, but I had to switch to peaceful a few times when I was trying to figure this stuff out and kept getting bugged by the mobs. Doesn't seem to affect it though, but just makes it harder to track on the scanner when two id flash two different sets of information.

also, stil having turtles run out of fuel, it's almost as if they are not aware of running low, but as you said you can't reproduce it, so I'm S.o.L. It's not a big deal, unless they stall in a laval pool.

Mad_Professor, on 27 October 2013 - 11:22 AM said:

It's single player survival, but I had to switch to peaceful a few times when I was trying to figure this stuff out and kept getting bugged by the mobs. Doesn't seem to affect it though, but just makes it harder to track on the scanner when two id flash two different sets of information.

wojbie, on 27 October 2013 - 01:21 PM said:

Having more than one turtle with same number id is a weird situation - code is not designed to handle it - can cause all matter of bugs and hangs.
Best for you would be to get rid of one of duplicates.

HeffeD, on 27 October 2013 - 01:31 PM said:

Mad_Professor, on 27 October 2013 - 11:22 AM said:

It's single player survival, but I had to switch to peaceful a few times when I was trying to figure this stuff out and kept getting bugged by the mobs. Doesn't seem to affect it though, but just makes it harder to track on the scanner when two id flash two different sets of information.

Switching to peaceful wouldn't do it. Turtles and computers are given a unique ID by ComputerCraft when they are placed in the world.

Without manually editing some config files, the only way to get a duplicate ID is to place the turtle in creative mode. Since creative mode doesn't remove the item you've placed from your inventory, in the case of a turtle or computer, placing the item will duplicate it. The end result is that you have more than one turtle or computer with the same ID. That's the only way it will happen.

karlsen, on 27 October 2013 - 10:20 PM said:

This is the kind of program I've always dreamed about creating. I have a few ideas about features you could implement:

1: Make it possible to set up multiple mining areas using different channels.

karlsen, on 27 October 2013 - 10:20 PM said:

2: As seen on this screenshot http://i.imgur.com/4SdRNjr.png it seems like the turtles "line" up after each other because the first "layer" of a section isn't mined. Would it be possible for the turtles in the "line" to make a path between the sector it is trying to get through and the one it wants to get to like in this picture: http://i.imgur.com/sjTBIQa.png (where the glass would be the possible pathing between the sectors).
2 ½: An alternative "fix" the above "problem" would be to allow the turtles in the section to communicate and divide the area they have to mine (adaptive sub-sections).
2.75: Another way to "fix" the problem from #2 would be to mine the first layer of the sections in an alternative way by mining out the edge first then going back to the regular mining of this section.

karlsen, on 27 October 2013 - 10:20 PM said:

From here on it's more "wishes" than actual requests :)/>

3: If #1 Would become possible another feature could be to have "master" turtles which automatically sets an entire mining operation. (requires GPS coverage in the area?) Given they get the coordinates, the facing and unlabled empty turtles, drop off materials (ender chest for example), disk drive, disk, and coble stone.

karlsen, on 27 October 2013 - 10:20 PM said:

4: If #3 then you could use a different channel on the modem to send information about that specific digsite through an adhoc like network of "gps towers". Where this information would be sent with progress updates of each section every 10 seconds which would consist of the y-level/the depth/ number of layers completed in every section.

karlsen, on 27 October 2013 - 10:20 PM said:

5: If #4 then you could possible make these master turtles automatically move mining operations once they have been completed to another area. This could be achieved through temporary enderchest storage for the labeled & already programmed turtles. If this feature was created the user would probably have to give it some "upper" bounds of areas it's allowed to move to. If this "fully" automatic system would be set up it would probably need "blacklisted/whitelisted" areas.

karlsen, on 27 October 2013 - 10:20 PM said:

6: Have a suggested dropsite being a bit above the center of the entire "map" with all the sections. Or possible add the option of having multiple drop locations where the turtle would figure out which one it is closest to and choose that one.

If all these things would be set up it would be possible to have a fully automated mining system which adaptivly moves to new digsites once it has completed it's current one.

karlsen, on 27 October 2013 - 10:20 PM said:

I have a question about the movement of the turtles: I've noticed they stop up a lot and wait a tiny bit before they move on. Is this due to the information they send/receive ?

karlsen, on 27 October 2013 - 10:20 PM said:

Another question would be about the connection between the turtles. Do they work like ad-hoc networks in real life where if Turtle1 and Turtle3 are too far from each other to communicate but Turtle2 is in between Turtle1 & Turtle3 and has a connection to both of them. So Turtle2 would passthrough information Turtle1 need to send to Turtle3?

karlsen, on 27 October 2013 - 10:20 PM said:

Hope I did not overwhelm you but I really enjoy seeing this project of yours since it's almost what I have dreamed of achieving with computercraft. Please reply if some of my suggestions/questions are unclear and I'll make sure to edit them to be more detailed.

dronf, on 27 October 2013 - 09:00 PM said:

I finally got this working, but have had some odd results. I noticed that turtles will frequently get stuck following each other, so there will end up being like 8 in a row, slowly following the first. If that first one tries to turn around, the whole thing stops. Anyone seen something like this?

• "To long without yeld" error fixes added.
• New even faster refuelling code
• Limited sector size to 2-10 range on both axis.
• Small amount of code for future deplorer added.
• Goto Code fine-tuning (again)

 disk/startup update 

swarminer:863: index expected, got nil

{["fuel"]=575,["layer"]=1,["id"]=39,["run"]=true,["loc"]={["x"]=12,["z"]=16,},["pos"]={["y"]=14,["x"]=-333,["z"]=-137,["zd"]=0,["xd"]=-1,},}

• Emergency Beacon Added - Any turtle that crashes down to shell will emit send ping signal to scanners informing them of it
• Refined anti-sector-colision code - Sadly that makes "race" situation 99.9% rarer. Turtles now decide it based on who has lover id number.
• Scanner Code updated to properly show Emergency Beacon status.
• Additional code added for Deployer/collector needs.

 disk/startup update 

 disk/startup update 

wojbie, on 29 October 2013 - 12:51 PM said:

Face-palm - fixed tx for report - no idea how i missed that. :(/>

wojbie, on 29 October 2013 - 12:51 PM said:

But it should clear data correctly now. :)/>

HeffeD, on 29 October 2013 - 01:00 PM said:

Thanks for the quick fix! :ph34r:/>

{["layer"]=16,["loc"]={["x"]=1,["z"]=6,},["pos"]={["y"]=47,["x"]=1511,["z"]=-608,["zd"]=1,["xd"]=0,},["run"]=true,["fuel"]=345,["id"]=0,}

wojbie, on 29 October 2013 - 04:07 PM said:

OK i already found where that bug is from - working on fixing it.

Also side note
["id"]=0?
That turtle id is 0? interesting coincidence.

HeffeD, on 29 October 2013 - 05:03 PM said:

Yes, the turtle is ID 0. I didn't think of that. Maybe he's a ghost? :lol:/>

• Added additional Situational Awareness code - turtle recognizes if it makes a mistake and carries on
• Refined anti-sector-colision code - again
• Added layer info to scanner screen
• Added cycle and recovery files to disk - those are deployer/collector code that i am working on - operational right now but untestet/lacks UI.
• Tweaked Top Level Overwrite and Beacon - now broken scanners will emit Beacon Signal too.
• Bugfixes

 disk/startup update 

 disk/startup update 

 disk/startup update 

{["layer"]=0,["loc"]={["x"]=4,["z"]=3,},["pos"]={["y"]=2,["x"]=1536,["z"]=-592,["zd"]=1,["xd"]=0,},["run"]=true,["fuel"]=253,["id"]=17,}

{["layer"]=6,["loc"]={["x"]=4,["z"]=3,},["pos"]={["y"]=77,["x"]=1535,["z"]=-584,["zd"]=1,["xd"]=0,},["run"]=true,["fuel"]=231,["id"]=17,}

{["layer"]=6,["loc"]={["x"]=4,["z"]=3,},["pos"]={["y"]=77,["x"]=1535,["z"]=-584,["zd"]=1,["xd"]=0,},["run"]=true,["fuel"]=225,["id"]=18,}

wojbie, on 30 October 2013 - 12:51 PM said:

Well scanner part worked correctly so thats a plus. :D/>

• Removed OpenPeripheral requirement for emptying chests - i realized i can code it smarter.
• If OpenPeripheral installed will recognize monster_spawner and not mine it. Along with all other peripheral blocks ( chests excluded.)
• Whole Program Got reread and cleanup
• Removed lots of small bugs/applied tweaks.
• Added Screen Saver on turtles that lovers amount of operations each turtle does.
• Added Monitor Support to Scanners - if you place monitor next to scanner it will automatically display statistical data about: amount mined/amount currently in mining/amount to mine. It also auto detects Monitor Size and writes in largest font possible.
• Rewrote fuel handling code… again. (I can't seem to be able to stop messing with it)
• Added Logo. Just to stroke my ego.
• Something i am forgetting right now should be here.

 disk/startup update 

• Bugfix
• Added fastgps utility program to floppy - allows for fast gps computer setup. It scans for coords from gps in area if not get them asks them. Then it creates basic gps host program that spreads gps signal. If there is startup file on computer it moves it into startup.backup[nr] file. Can be also used directly from pastebin on v1.6.2 and after that by simply calling pastebin run 4xanbDSX for even faster speeder setup.

 disk/startup update 

wojbie, on 02 November 2013 - 03:47 PM said:

If OpenPeripheral installed will recognize monster_spawner and not mine it. Along with all other peripheral blocks ( chests excluded.)

HeffeD, on 09 November 2013 - 01:48 PM said:

wojbie, on 02 November 2013 - 03:47 PM said:

If OpenPeripheral installed will recognize monster_spawner and not mine it. Along with all other peripheral blocks ( chests excluded.)

I haven't had a chance to try version 2.0 yet, but this functionality was in the previous version as well. After my last quarry was complete, I was surprised to see a zombie spawner floating inside the cleared area.

This makes it very easy to build mob farms around the spawners. :)/>

scanner:86: No such method isWireless

if peripheral.call(i,"isWireless") then

wojbie, on 09 November 2013 - 06:04 PM said:

What version of ComputerCraft are you using?
Do you have any ComputerCraft peripherals installed? If yes what kind?
Cause in vanilla ComputerCraft this should not bug this way.

 disk/startup update 

Simon, on 10 November 2013 - 12:25 PM said:

bios:333: [string "swarminer"]:26: no loop to break

bios:333: [string "swarminer"]:31: no loop to break

swarminer:1509: attempt to index ? (a boolean value) press any key to continue

 disk/startup update 

wojbie, on 10 November 2013 - 12:41 PM said:

Fixed Fixed and Fixed

HeffeD, on 10 November 2013 - 05:01 PM said:

wojbie, on 10 November 2013 - 12:41 PM said:

Fixed Fixed and Fixed

Third one is not fixed. I just got almost the exact same error.
swarminer:1509: attempt to index ? (a boolean value)

This happened right after the turtle determined its position, and started moving. It moved two blocks forward from its starting position on top of the disk drive and encountered this error. If I restart the turtle, it will find its position and move one block forward and then give the same error.

 disk/startup update 

{["layer"]=2,["loc"]={["x"]=1,["z"]=1,},["pos"]={["y"]=63,["x"]=1488,["z"]=-609,["zd"]=-1,["xd"]=0,},["run"]=true,["fuel"]=1084,["id"]=0,}
{["layer"]=2,["loc"]={["x"]=1,["z"]=1,},["pos"]={["y"]=63,["x"]=1488,["z"]=-609,["zd"]=-1,["xd"]=0,},["run"]=true,["fuel"]=143,["id"]=19,}

{["layer"]=2,["loc"]={["x"]=2,["z"]=2,},["pos"]={["y"]=63,["x"]=1496,["z"]=-617,["zd"]=-1,["xd"]=0,},["run"]=true,["fuel"]=43625,["id"]=4,}
{["layer"]=2,["loc"]={["x"]=2,["z"]=2,},["pos"]={["y"]=63,["x"]=1496,["z"]=-617,["zd"]=-1,["xd"]=0,},["run"]=true,["fuel"]=177,["id"]=18,}

wojbie, on 10 November 2013 - 07:55 PM said:

Well how far away are other turtles from this one?

• With amount of data that turtles synchronize even with 4 turtles you would run out of turtle drive space in like 30-40 sec.
• No matter how hard i try said problem always fixes itself in my tests - on different versions of computer-craft ect. Sometimes it takes 2 sec sometimes it takes a min.
• I Find that a low priority error - its not a problem with whole Swarm and it should auto-correct itself in long run. This program was never supposed to be fuel efficient or max speed.
• I am currently working on other programs of mine. Swarm Miner got put on back-burner for now. Its working and its working good.

Zierk11001, on 11 November 2013 - 03:18 PM said:

Getting the same no such method isWireless from parallel:22 once you setup the turtle's inventory with the 2 ender chests. It takes 1 step forward then errors.

http://i.imgur.com/yFDs0Qa.png

 disk/startup update 

0:Eparallel:22: scanner:295: attempt to concatenate string and nil

 disk/startup update 

Simon, on 21 November 2013 - 09:50 PM said:

Mua Ha Ha Ha!

(this is very exciting)

8 turtles going on a 120x120 pit im diging for nix. How long do you think it will take?

Simon, on 21 November 2013 - 09:50 PM said:

-snip-

wojbie, on 24 November 2013 - 09:57 AM said:

Please provide contents of current.log file inside of bugged turtle. It contains data i can use to track down problem.

saqr, on 25 November 2013 - 10:52 AM said:

Hi i have a problem with that program. My gps is working fine (i think), and my turtle move 2 blocks from disk drive and start spinning, when i right click him he show that he is mining. Can you make screen shot tutorial how to make, a proper gps system ?

honsbeekiejj, on 27 November 2013 - 09:20 AM said:

hmm anyone else has this problem where turtle's don't see if there is another turtle mining an area already?

Apemanzilla, on 29 November 2013 - 08:16 PM said:

-When I drop in fuel (in the form of coal) it doesnt eat it like it does inpicture guide. Havent seen a turtle run out of fuel yet so I can't tell you what happens when it's empty.

Apemanzilla, on 29 November 2013 - 08:16 PM said:

-If a mob is in the way, will the turtle kill it and move on without getting stuck?

wojbie, on 30 November 2013 - 09:48 AM said:

Apemanzilla, on 29 November 2013 - 08:16 PM said:

-When I drop in fuel (in the form of coal) it doesnt eat it like it does inpicture guide. Havent seen a turtle run out of fuel yet so I can't tell you what happens when it's empty.

Refueling system got inproved from time guide was made. Right now turtle will not overeat - it will only eat fuel it needs and leave rest.

Apemanzilla, on 29 November 2013 - 08:16 PM said:

-If a mob is in the way, will the turtle kill it and move on without getting stuck?

They are killing everything that is in the way of movement during mining. So it will not only kill mobs in the way - it will collect all drops from said mobs. I tend to get some slimes from my quarries from time to time. Some gunpowder sometimes ;p But watch out. They will attack and kill you too if you get in the way.

Apemanzilla, on 30 November 2013 - 05:36 PM said:

Hmm… When it started spamming "0," as it tried to start mining, I dropped in some fuel but it didn't touch any of it.

Apemanzilla, on 30 November 2013 - 05:36 PM said:

Edit: Also, can I revamp this a bit? (Fixing the spelling, making it a bit faster, etc…) I'd give you most of the credit of course.

Nice to see mobs are handled - some other quarry programs get stuck on mobs and then fall out of place when trying to mine.

wojbie, on 01 December 2013 - 07:57 AM said:

Apemanzilla, on 30 November 2013 - 05:36 PM said:

Hmm… When it started spamming "0," as it tried to start mining, I dropped in some fuel but it didn't touch any of it.

Than thats a bug - adding to todo list - thanks for report.

Apemanzilla, on 30 November 2013 - 05:36 PM said:

Edit: Also, can I revamp this a bit? (Fixing the spelling, making it a bit faster, etc…) I'd give you most of the credit of course.

Nice to see mobs are handled - some other quarry programs get stuck on mobs and then fall out of place when trying to mine.

How big revamp are we talking here? What changes are you considering adding? (Spelling mistakes? Damn i thought i got them all)
I must say i feel iffy about idea. Could you go in bit more detail?

As for mobs - thats part of my position keeping movement code that i made. :D/> its in my all turtle programs ;p

wojbie, on 01 December 2013 - 04:24 PM said:

OK i see you given some thought in the plan. Feel free to revamp it. Truthfully i kinda lost my drive to work on this program anymore.
there are some comments in code so you should not be going in blank.

Here are links to all subprograms that come in swarminer pack:
Floppy Disk(startup)="LXLBZK25",
Swarminer="2h1RmbAR",
Swarmstart(Top Level Coroutine Overwrite)="aFgPSyGe",
scanner="4wgEDymE",

and extras that where never finished:
cycle="7tWnxwLU",
recovery="pPqghm6F",
fastgps="4xanbDSX"

Hope you have fun working with it.
Also i ask you to give credit to me in all files you end up releasing that contain my code.
I will be watching to see what you do with this thing. ;p good luck

Apemanzilla, on 01 December 2013 - 06:00 PM said:

Once I start on it, I'll be putting new versions onto my dropbox, and theyll be public. If you have one, I can share it with you and youll be able to edit them as well.

I may look into using ApeNet instead of rednet to make long-distance communication easier

wojbie, on 01 December 2013 - 06:22 PM said:

Apemanzilla, on 01 December 2013 - 06:00 PM said:

Once I start on it, I'll be putting new versions onto my dropbox, and theyll be public. If you have one, I can share it with you and youll be able to edit them as well.

I may look into using ApeNet instead of rednet to make long-distance communication easier

I am kinda using my own communication scheme directly on modem peripheral. and top level overwrite remowes rednet coroutine to lessen amount of treads that get events. So that would require a lot of rewiring.

HunterG22, on 04 December 2013 - 09:33 PM said:

Is there anyway you can make it compatible with an endertank for fuel in the second slot?

HunterG22, on 05 December 2013 - 11:37 AM said:

Hmmm… for some reason when i start the program my turtle moves 2 blocks then goes straight up for a bit then starts doing 180's… tried reinstalling everything still does it.

 disk/startup update 

Meit, on 03 March 2017 - 05:01 PM said:

Does this still work? can someone find out?

jakejakey, on 12 March 2018 - 03:49 AM said:

This looks great! Can't wait to try it!