TheRockettek, on 31 May 2016 - 11:13 AM, said:

Watch your systems available RAM while the program is running. If it is getting dangerously low, that means that your work size is probably still too high. You could try closing all other applications while you mine, as they all consume some amount of RAM and every bit helps.

My work size can go to 2^20 before my rates stop improving significantly, but I run my miner at 2^14 worksize so that my computer doesn't overheat or use excessive RAM. This enables me to go about my day on the PC while mining, without putting too much work on the PC.

What does the -v argument do?

Now that I can finally mine Krist with ease (many thanks to apemanzilla for developing and releasing turbokrist), what should I spend it on?

Just solved my first block while I was just configuring the settings and playing with my bat file. Pleasant surprise! Thanks for publishing this.

This is a fantastic program! I use it gather fuel for my farming turtle

How is the progress on the mining pool coming?

Does that mean that mining krist will always be possible, just extremely difficult when work is 0?

BeanD, this program does not work for certain versions of ComputerCraft.

"Attempt to call nil" indicates that the program attempted to execute a function that does not exist.

Here is line 63:

if (turtle.getItemDetail(i) ~= nil) then

The only function that is called here is turtle.getItemDetail(). That function was added in ComputerCraft 1.6.4.

If you are using the Tekkit modpack, it is important to note that this program will not work in your turtle because that modpack uses an older version of ComputerCraft.

If you are using Tekkit, I'd recommend upgrading to Tekkit Legends, which is using ComputerCraftEdu 1.7.4, a more current and stable version that will work with my program.

I do not care at all who made the first prototype Krist pool miner :B All I care about is who makes the first krist pool miner that I can use Nothing about the history books, only about me getting my hands on some krist.

Luca_S, on 23 January 2016 - 11:14 PM, said:

I can't wait to use it! This will give the miners that aren't as good a better shot at consistent KST.

3d6, on 23 January 2016 - 10:52 PM, said:

Wouldn't the pool operator be doing a huge brunt of the work, checking whether every random nonce submitted by a pool address is valid in this case?

Argh I'd really love to get a copy of it. I get terrible numbers from CPU mining, and I have a nice GPU

Well I can tell someone just started mining again

Hmm, interesting. The reason I ask is because I am using YTCIKristMiner with 2.2ghz clock speed on 8 cores, and getting 1.4 MH/S, which is what I was getting on my other computer with 1.9ghz clock speed on 2 cores...

Just a thought, what if you were to instead of running one process on, say, 4 threads, ran 4 different mining processes on 1 thread each using different nonces? Would you expect similar output, better, or worse?

You guys should bundle it as a technic mod pack! I've tried multiple versions of Forge 1.7.10, no luck.

What are the rules for a nonce? Alphanumeric? What are the minimum/maximum character counts?

Also, do some work better than others, or is it essentially random, like a minecraft world seed?

Well, I'm sure we are using different nonces, so it's not like we are overlapping work -- it's still theoretically possible for me to solve a block, right?

Awesome, thanks for the info. I'm really just doing this to play around because I'm interested in how it works -- I wouldn't be surprised if I get no krist at all from mining.

So I'm using my spare laptop right now as I am out and about. I'm getting ~1.35 MH/S with 2 cores, which from what I understand is not pitiful, but is also not good at all.

I noticed that it keeps changing what block it is working on at random intervals. Is that because someone else already solved the block my miner was working on? If so, holy cow... a block is being solved every 5-30 seconds which I didn't expect.

How much is a block worth?

realgogogoluke, on 21 January 2016 - 12:24 AM, said:

The latest version as in Forge 1.8? I saw most of the mods were 1.7.10, so I was trying that version of forge -- probably why I wasn't able to get in XD

I have an 8-core alienware laptop (2.0 ghz processor speed). I would like to mine krist but I don't want to overload the computer. Anyone have a miner jar they recommend using?

Which release of FML is best used with the modpack?

IGN: foogimicester
Age (Do not lie, we are open minded): 20
CC Experience: Limited experience (I have only worked with turtles so far)... Click Here For My Pride and Joy
Maturity: I am polite and have a calm, relaxed demeanor
Have you been banned from another server? If so, which one, and why? (Do not lie, everyone makes mistakes): Not that I am aware of! XD
How much are you going to play? I run a spigot non-modded server, so I won't be playing here exclusively. However, I would like to be on at least a few days a week.
Will you follow the rules? Of course! I will not intentionally damage another's property or the server, nor will I take what is not mine.
What time zone do you live in? EST

As promised, here is Foogle Proof Mining version 1.3!

Foogle Proof Mining Version 1.3: link

• Turtle now empties out unneeded items at end of return trip
  
• Turtle is now truly 100% gravel proof to my knowledge
  
• Turtle now places torches every 14 blocks. Due to its tunnel building skills, water will not destroy them to my knowledge.
  
• Fixed mistake in which the turtle placed random blocks if it ran out of cobblestone

At this point, all known bugs have been fixed!

Let me know what you would like to see in future updates, and let me know your thoughts and opinions on the code/performance!

Hey everyone! 3500 views, 1300 pastebin downloads on the latest version, and until now I had yet to fix the gravel issue, and yet to implement torch placing.

I stayed up late last night and pumped out Foogle Proof Mining Version 1.3.

In the latest version, the turtle now handles gravel flawlessly. I had already implemented a solution for gravel in front of the turtle.

However, the turtle failed to handle gravel properly if the gravel fell on it's head before it attempted to move up. Once I realized this is where the error was occurring, it was a simple matter of replacing turtle.up() with a recursive TurtleUp() function that utilizes the boolean returned by turtle.up() to determine if the turtle needs to continue mining blocks above it before it can move.

I also made it so that the turtle will not only dump excess items in a chest when its inventory overflows, but also when it finishes the trip.

In addition, as promised months ago, I implemented torch placing. If the turtle has a torch, it will locate it, and place it every 16 blocks along the mineshaft. This part was trickier than expected because it seems to always place the torch in a specific orientation, meaning that when the turtle is going one direction versus another, it would sometimes put the torch on the wrong wall and then mine that block, destroying the torch.

Also, as an experiment, I sent 16 mining turtles on 100 block long missions (Using the command: Mine 100) giving them only 1 bucket of lava. All turtles returned at the correct height level and did everything as expected, without running out of fuel.

Tonight I will implement a version of Lion4ever's compass program in order to place the torch securely without wasting any fuel by moving back to place the torch.

Be on the lookout for the new pastebin link for Foogle Proof Mining 1.3 within the next 12 hours!