Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal
  1. OpenComputers

    1. Announcements

      OpenComputers official announcements.

    2. Feedback

      Tell us what you think.

    3. IRC

      #OC channel discussion
      irc.esper.net #oc

  2. Code Central

    1. Support

      Ask for support from the OpenComputers community

    2. Showcase

      Showcase what you have created for OC. No 'malware' or other junk!

    3. Tutorials

      Help other users out. Please no 'false tutorials'

  3. Addons & More

    1. Addons Mods

      Show off your OC addons mods

    2. Architectures

      Discussions for Architectures

    3. OpenEngineering Task Force

      Discussion board for the OETF documents

  4. General

    1. Lounge

      Just lounge around or have an open discussion.

    2. Forum Games

      Fight boredom!

    3. Showcase

      Show off your creations! (not for your programs)

    4. Servers

      A place to advertise your servers

  5. Archives

    1. Public Archives

      OpenComputers public archive forum

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Who's Online   0 Members, 0 Anonymous, 29 Guests (See full list)

    There are no registered users currently online

  • Topics

  • Posts

    • This is program for robot quarry. It uses a special pattern thanks to which it is up to 40% faster than the default dig.lua. The digging pattern also stretches into infinity, so if you equip the robot with a chunk loader upgrade you never have to worry about it again. The robot also remembers its position, so it the quarry can be easily resumed. Source code and detailed explanation can be found on Gitlab: https://gitlab.com/vitSkalicky/oc-column-quarry Usage Assemble a robot (see Robot requirements below). Set up power, tool supply, etc. (see Setup below). Place the robot and turn it on. Copy the minified program (squashed onto a single line). In the robot type "edit column_quarry.lua" and paste the program (by clicking the mouse wheel or using a keybind). Press ctrl+s to save the program and ctrl+w to exit editor. Run the program by typing "column_quarry". See Program options below. Robot requirements Minimal Computer case tier 2 CPU tier 1 2x memory tier 1 EPPROM with Lua BIOS Hard disk tier 1 with OpenOS installed* Screen tier 1 Keyboard Graphics card tier 1 Inventory controller upgrade Inventory upgrade (more is better) Hover upgrade ** *use a computer to install OpenOS on the disk before assembling the robot, or add a disk drive to the robot (like in the screenshot). **If you use Hover upgrade tier 1, you must start mining at y < 64, otherwise the robot will get stuck in the air. If you use tier 2 you can mine at any height. Also note that the minimal requirements robot does not have a Chunk loader upgrade, therefore you have to load the chunks externally (by using ChickenChunks chunk loader for example) Recommended Computer case tier 3 CPU tier 1 2x memory tier 1 EPPROM with Lua BIOS Hard disk tier 1 with OpenOS installed* Screen tier 1 Keyboard Graphics card tier 1 Inventory controller upgrade Chunkloader upgrade Battery upgrade Hover upgrade * Inventory upgrade (more is better) upgrade container for more inventory upgrades *see Minimal requirements Setup Schema: C R I P A A...        * R - Robot facing the top of schema * C - Charger * I - Items chest: the robot will put all mined blocks and resources here * P - Pickaxes: robot will take fresh primary mining tools from here and will put used (almost broken) ones to a chest *on top of it* * A - Additional tools: robot will take one tool from each chest in row. Almost broken ones will be put to a chest above. It will use these to try breaking blocks it cannot break with pickaxe (or the primary tool you supply it with). More on that later. * The robot mines area to the top right of the schema You can use any tool instead of pickaxe (such as a mining drill from IC2) and any inventory for items, not only chest. For example: the robot takes a charged mining drill from a batbox and it puts the discharged one into a hopper above the batbox, which pushes the discharged drill into the batbox for recharging. The robot cannot mine cobwebs using a pickaxe (and other blocks from mods such as Magic bees hives). That's what additional tools are for. If a robot fails to mine a block using pickaxe, it will try to mine it using all the available additional tools. The robot takes one additional tool from each chest to the right of the "pickaxe" chest. You can put as many chest you want - the robot counts how many chests there are.   Screenshot: The robot is facing away from the ender chest The charger is powered by a creative capacitor bank and is turned on by a lever. You can use almost any type of power, but for some you will need a power converter. Ender chest - mined resources will be put here Iron chest - robot will take fresh primary mining tools (pickaxes) from here Golden chest - used (almost broken) pickaxes will be put here Copper chests - robot will take one additional tool from each. There are three, but you can have more, less or even none. Diamond chest - used (almost broken) additional tools will be put here (to the one above the chest the tool was taken from) Red area will be mined (continues infinitely) Mid-game setup on Direwolf 1.12.2 I use diamond drill (IC2) instead of pickaxe, because it can be recharged. I also use a chainsaw (IC2)(rechargable too) for cobwebs and scoop for bee hives (Magic bees) Power is supplied using a geothermal generator with an ender tank hooked up to my lava pump in the nether. Ender chest sends mined items back to my base The robot will take a charged drill and chainsaw from the batbox and put the used one into the hopper which pushes the tool back to the batbox to recharge. The robot takes a charged drill first and then returns the used one, so I need two of them. One is being used by the robot and the other one is charging. (same for chainsaw) Scoops cannot be easily repaired, so I just have a ton of them. Don't forget to load the chunk with a spot loader and use a chunk loader upgrade in the robot. I use the `--alwaysChangeTool` flag so that the robot recharges the drill whenever it drops off item. End-game setup on Direwolf20 1.12.2 It is located in the Twilight forest dimension, because the y is lower in it (there is less stone to be mined before we get to the diamonds) and the solar cell works non-stop. I use EnderIO solar cell with a capacitor for power. There is another ender chest in my base which suck up items into my storage system and ore processing factory. The robot mines with an Efficiency V, Fortune III, Unbreaking III, Mending diamond pickaxe. I also use 2 additional tools: sword for cobwebs and scoop for bee hives (from Magic bees mod). Both have Mending on them as well. Tools are repaired in the EnderIO fluid tanks using liquid XP (tools have mending on them). I get the liquid XP from my mob farm by converting essence (Industrial foregoing) from mob crusher in fluid dictionary converter and pumping it through ender tank. There are always 2 identical tools of the same kind: one is being used by the robot and the other one is waiting repaired to be exchanged for the almost broken one. The robot takes a fresh tool from the fluid tank and puts the used tool into the hopper, which pushes it into the fluid tank, where it is repaired. Program options Usage column_quarry [OPTIONS]... column_quarry help Arguments help - Displays help instead of starting the quarry. Options --continue  Resumes the quarry progress on the last mined column. Useful for example if the robot got stuck and you had to break it. Just place the robot at the starting point, use this option and it will continue where it was. --continue=n Where *n* is the side of the already mined area. The robot will continue mining **roughly** at the end of the entered area. Useful if replacing a lost robot. If you want to replace a robot you did not lose, it is better copy the state file (see *State saving*) --alwaysChangeTool The robot will change its primary tool (pickaxe) every time it visits the start point, not only when it is almost broken. **Recommended when using a repairable tool** like in the example setups. State saving The robot saves its progress every time it finished mining a column into file named `column_quarry_state`. If you want to replace the robot, just copy the contents of this file onto the new robot and start the quarry on the new robot with the `--continue` option. I will continue, where the old robot finished. Download and source code Source code of this program along with more detailed description on how it works can be found here: https://gitlab.com/vitSkalicky/oc-column-quarry PS: I'm reposting this, because the forum got reset reveral times after the first time I posted this here.
    • Newest update adds in support for Intercom doors (although I know you prolly won't use it. It's something on my server) Will add in Staff doors soon
    • Sorry for long wait. The older version of opensecurity used to call the doorcontrol block os_door. It is now called os_doorcontrol so you will have to edit the code for it to work
    • I updated the server to use a new system for saving the files, and a new way of checking the user! Before, it used the name. The problem with that is that if you change the name, you cant use the card anymore. Now, the card uses a UUID! It doesn't change unless you reset the uuid, which will give it a new uuid, rendering the old card useless. Way better over all. Also made it so if a user has the staff pass, it will let them in through ANY door. Also adding images rn
    • Is 'special' defined before or after this function? Lua functions / variables / etc must be defined before they are used, similar to C / C++. You can define local variables for functions and assign them later in the file as well.
  • Popular Contributors

    Nobody has received reputation this week.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.