MFFS Mining rigs

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Drkevlar

New Member
Jul 29, 2019
47
0
0
After seeing dw20 uberminer, I decided to give it a shot as well.
The pack I am using is Monster 1.1.1, so mileage may vary :)

I had several ideas and lots of client crashes so use caution!
Any comments or suggestions are welcome.

Idea #1: Tunnel bore with the RotaryCraft - Sonic Bore (SB).

It was A LOT of fun testing this machine.

Moving the SB seemed to cause issues when it was facing forward. The sonic wave often destroyed blocks behind it, bounced, or got stuck in weird places. Caught some sonic waves idle mid air, clicking them seemed to launch them :D

Item ducts seemed to cause lots of client crashes, but somehow resolved after some reboots.
More trouble with these guys in the next idea.

First time blocks got destroyed, I thought it might be the SB exploding because it had too much power, but it turned out to be the waves that were dispersed (?) right before the rig moved. So that got me thinking :)

Idea #2: Downward bore with the SB and TE3 Terrain Smasher (TS).

Basically what I did here is a SB facing down, and having an item vacuum suck items that the SB dropped.
Have TS eat the blocks in front of the rig. This worked okay, but it was very quirky.

Itemducts seem to be the culprit when I did the next setup. Every time I changed a facing of an itemduct and moved the rig,
the game crashed. To me it seems moving an itemduct that is not in the same state as when you placed it, can cause crashes?

I gave up this rig because it escaped. It still has items coming in, but it's nowhere to be found!

Idea #3: Upward bore with SB and TS

Why pull blocks up when you can make them fall down ?

This one still plagues me with crashes. I'm trying to do as much testing as I can.

I didn't want this one to get away, so I dropped in a wireless turtle for movement control.
Apparently turtles can't send any messages over rednet after you move a turtle listening for rednet events?

This bad boy is still work in progress and will try to keep you guys up to date with any progress or findings!
 
Last edited:

Celestialphoenix

Too Much Free Time
Nov 9, 2012
3,741
3,204
333
Tartarus.. I mean at work. Same thing really.
The upward bore may encounter issues with lava, but you should probably avoid itemducts if you're crashing this much.
Try dropping items directly into a tesseract/endechest.
Either way this is somewhat cooler than my technique of shunting block breakers through the earth. You totally need to drop some screenshots.

Regarding No.2 - please tell me you're playing on a server...
 
  • Like
Reactions: Drkevlar

namiasdf

New Member
Jul 29, 2019
2,183
0
0
The upward bore may encounter issues with lava, but you should probably avoid itemducts if you're crashing this much.
Try dropping items directly into a tesseract/endechest.
Either way this is somewhat cooler than my technique of shunting block breakers through the earth. You totally need to drop some screenshots.

Regarding No.2 - please tell me you're playing on a server...
There is no server, there is only an AE system filled with an entire server's worth of blocks... And entities..

Where did the players go?

Muahahhahahahahahahhaha.

No, I SSP.
 

Drkevlar

New Member
Jul 29, 2019
47
0
0
Just quarry everything.
No fun :).

The upward bore may encounter issues with lava, but you should probably avoid itemducts if you're crashing this much.
Try dropping items directly into a tesseract/endechest.

Next rig will have ender chests, haven't worked that out yet. Might try transfer nodes.
9 ender chest for 3x3 TS, and I could encase the rig so liquids should not be a problem.
But it seems bulky since I have a tesseract transferring all the energy and items.

And no, this is SSP, If I did this on a server, id have everyone yelling at me :)

Edit: I lost idea 3, had 1 screenshot, now the world won't load. Getting bit disappointed I can't show the rig in action!

Rig encased before crash.
 
Last edited:

Captain_Oats

New Member
Jul 29, 2019
116
0
0
I find the easiest method is using MFFS, Buildcraft mining wells, buildcraft gates, a TE tesseract and AE. No need for computer code, multiple enderchests, turtles etc etc. And functionally it is identical to what Dire did ( I believe).

Mining wells output to AE interfaces, AE transition planes carve out earth as the rig moves, all items sent through tesseract. Energy for MFFS and AE through tesseract as well. Buildcraft gates to detect when work is finished from 1 mining well (the others should be the same), which sends signal to move the rig automatically. Enderchest with another gate to detect if chest has item, which sends signal to Tesseract or energy cell to output energy.

Still has a problem with liquids, but I think I'll try adding one of those sponge modules to see if that helps.
 
  • Like
Reactions: Drkevlar

DZCreeper

New Member
Jul 29, 2019
1,469
0
1
Its not strictly MFFS but I am working on plans for a Remain in Motion frame machine. It uses the template carriages to move a stone cube that contains rows of mining wells, enderchests, and a control system I have not decided on yet. From what I hear wireless redstone has issues still so my solutions are:

1. Write a small mod that adds the redstone equivalent to Enderchests. Different blocks but they synchronize redstone signal strength. The idea hurts my brain right now but its doable.

2. Modify my turtle mining script so that it lacks any mining logic controls and instead just uses the refuel code module and a simple move forward, apply signal. This works because I can make the interior of the stone cube hollow so the turtle doesn't get pulled along.
 

Drkevlar

New Member
Jul 29, 2019
47
0
0
Hey guys,

I did some more testing and have some new findings.

Bad news:
- AE Controller can't be moved, it will cause controller conflicts, so no transition planes.
- Moving the rig twice in a row can lead to items blocks being eaten/disappearing.
- Flowing liquids are a PITA with an upward bore and terrain smashers.
- My up and forward bore got eaten by moving too fast :mad:

Good news:
- Transfer nodes do not mind being moved and remember their state!
- I got a partially working prototype with the upward bore.
- Controlling the rig can be handled with an enderchest and a turtle checking for items in it.
- Rednet cable colors are awesome for these kind of builds.
- Vacuum hopper sucks up xp orbs, and it fills up quite fast depending on the rigs speed.
- Multimeter readings had about 100 RF/t for 1 sonic bore and capacitor recharging.

Few pics before I got frustrated with disappearing blocks:

It moved!
https://dl.dropboxusercontent.com/u/74940625/bore1.png
https://dl.dropboxusercontent.com/u/74940625/bore2.png
https://dl.dropboxusercontent.com/u/74940625/bore3.png

Few enhancements
https://dl.dropboxusercontent.com/u/74940625/bore4.png

I did a few changes between pics, but you get the idea.

Code from my up and forward bore that I have to rebuild the front of :(

Edit: I need colors.combine for turning on the sonic bores, will implement that next test run.
Code:
local cableSide = "left"

local boreUp = colors.yellow
local boreFront = colors.lime
local moveRig = colors.orange
local moveManipulator = colors.white

local function move()
    redstone.setBundledOutput(cableSide, moveManipulator)
    sleep(1) -- Signal sleep
    redstone.setBundledOutput(cableSide, 0)
    redstone.setBundledOutput(cableSide, moveRig)
    sleep(1) -- Make it short enough to move
    return false -- if we get here, we probably did not move
end

local function collect()
    redstone.setBundledOutput(cableSide, boreUp)
    redstone.setBundledOutput(cableSide, boreFront)
    sleep(15)
    redstone.setBundledOutput(cableSide, 0)
end

local function main()
    -- Check enderchest for item
    if turtle.suck() and turtle.drop() then
        print("Collecting")
        collect()
        if not move() then
            sleep(2)
            move()
            print("Could not move")
            return false
        end
        return true
    end

    redstone.setBundledOutput(cableSide, 0)

    print("Waiting for enderchest signal")
    return true
end


while main() do
    sleep(1)
end

redstone.setBundledOutput(cableSide, 0)
 
Last edited:

Captain_Oats

New Member
Jul 29, 2019
116
0
0
Hey guys,

I did some more testing and have some new findings.

Bad news:
- AE Controller can't be moved, it will cause controller conflicts, so no transition planes.
- Moving the rig twice in a row can lead to items blocks being eaten/disappearing.
- Flowing liquids are a PITA with an upward bore and terrain smashers.
- My up and forward bore got eaten by moving too fast :mad:

[/spoiler]

What kind of problems are you having with AE? I've had no issues at all moving a controller, multiple interfaces, storage bus, cable and multiple transition planes.
 

Drkevlar

New Member
Jul 29, 2019
47
0
0
What kind of problems are you having with AE? I've had no issues at all moving a controller, multiple interfaces, storage bus, cable and multiple transition planes.

I might have moved twice in a row, but AE is not stable for me if I move the rig, controller has a lot of conflicts when moving faster.