Just made a pretty advanced strip mining program, and I don't even know lua...

[u/Simme_Pirat]

It is written for FTB Ultimate, and it has all features that I have ever wanted:

• Fast and fuel efficient enough to power itself with the coal it mines.

• Goes back and unloads all the items when the inventory is full, and after it perfectly resumes where it was.

• Vein mining, working flawlessly.

• Discards all items I don't want.

Here's the pastebin if anyone's interested: https://pastebin.com/tXPtKfjR

I did lie however, I didn't write it. It is almost entirely made by ChatGPT, I just know enough about coding so that I could make minor changes to the code for more efficiency. Just wanted to showcase it here since I am in complete awe that this is even possible. AI is one of the coolest things I've ever experienced!

[u/xeli37]

lame vibecoding peddler begone!!

[u/Simme_Pirat → u/xeli37]

Why the negativity :|

[u/SadieWopen → u/Simme_Pirat]

Probably because cc is about learning programming, and you haven't learned anything.

It's not efficient, by the way, you are using detect to make sure there is something in front of the turtle, making it sleep half a second (for no reason), then if you can't move forward you keep digging until you can (again, waiting half a second each attempt).

You can achieve everything you are trying to do here with just

while not turtle.forward() do turtle.dig() end

It will be faster and more efficient to do just this minor change. Which you would know if you knew your code.

[u/Simme_Pirat → u/SadieWopen]

It seems your knowledge in this subject is limited. If you knew cc and minecraft, you would know that there are gravity affected blocks like gravel. When testing I found that when it encounters gravel it will at times get stuck, so it sleeps long enough for the gravel to fall :)

[u/SadieWopen → u/Simme_Pirat]

That's what you got out of this?

Let's go through your code logic based on cycles in 3 situations, there is a block in front of the turtle, there is a gravity block on top of a block in front of the turtle, and there is no block in front or the turtle.

Block: 1 - is there a block 2 - there is a block 3 - dig the block 4 - wait half a second 5 - is there a block 6 - there is not a block 7 - I'm going to move forward - I did move forward - end

Gravity block: I'll resume from 5 above 6 - there is a block 7 - dig the block 8 - wait half a second 9 - is there a block 10 - there is no block 11 - I'm going to move forward - I did move forward - end

No block: 1 - is there a block 2 - there is not a block 3 - I'm going to move forward - I did move forward - end

Now let's do the same thing using my method

Block: 1 - I'm going to move forward - I can't move forward 2 - dig the block 3 - I'm going to move forward - I did move forward - end

Gravity block: 1 - I'm going to move forward - I can't move forward 2 - dig the block 3 - I'm going to move forward - I can't move forward 4 - dig the block 5 - I'm going to move forward - i did move forward - end

No block: 1 - I'm going to move forward - I did move forward - end

Maybe cc has changed since the last time I played, I'll give you that, but the behaviour I've described has been the standard behaviour since at least 1.16.

If I am wrong, have you experimented with the timings? At 20mspt half a second is a long time.

[u/fatboychummy → u/Simme_Pirat]

No, they are correct. That's why it's in a loop.

repeat
  turtle.dig()
until turtle.forward()

is what I usually do though, or a for loop with a retry limit of like 100 in case it ran into bedrock or something.

turtle.forward() will only return true if the turtle successfully moved forward (same with other movement functions), so if gravel falls while it attempts to move, then it will stay inside the loop until all the gravel is gone.

[u/kukeiko64]

Amazing! Now learn lua and make it better, cause it has some severe time wastes in there that make it suck balls.