Mission goal: Be the best big reactors controller there is. Nothing more, nothing less.

First things first - here's the website: https://tenyx.de/brgc/

NOTE: Due to a bug with OpenOS 1.7.4, BRGC will not work with that version. Please update to 1.7.5.

• Active and passive reactor support
• Support for multiple reactors and turbines at the same time (n:m)
• Control active and passive reactors with the same controller
• Automatic configuration of everything (EVERYTHING!)

Setup instructions

1. wget the installer from here: http://xypm.tenyx.de/standalone/brgc_installer.lua
2. Run it
3. Done

Big Reactors Grid Control comes with three rc.d files:

1. /etc/rc.d/brgc_reactor.lua
2. /etc/rc.d/brgc_turbine.lua
3. /etc/rc.d/brgc_grid.lua

If you want the controller to run at boot time, you can just use OpenOS' rc.d schema.

There's a GUI as well as a command line utility for advanced users.
To start the gui, simply run "brgc_gui" and watch the magic happen.
The gui scales the screen resolution to match the screens ratio and should scale with basically all screen setups.
I recommend 3x2 or 4x3 screens.

As of now the command line utility allows you to do (almost) everything you can do with the GUI and also allows you to change the controllers configuration at runtime (if you so desire).
Check out "brgcctrl help" for further information.

How to set up the grid

In a basic setup you just interconnect everything:
All active reactors can output steam to all turbines. All passive reactors and turbines output energy to the same grid.
You CAN have passive reactors and turbines output energy to different energy grids.
While this poses absolutely NO problem for passive reactors, you will have to set some turbines to "independent"-mode (more on that below).

If you want your reactors and turbines to properly cooperate, you'll also need to connect at least one energy storage block to your energy grid.
Currently supported storage "blocks" are:

• EnderIO Capacitors (requires the mod "Computronics")
• Draconic Evolution Energy Storage multiblocks.
• RFTools Energy Cells
• Thermal Expansion Energy Cells
• Mekanism Induction Matrices

You can connect them using OpenComputers Adapters.

As mentioned before the controller tries to autoconfigure everything:

When a new passive reactor is connected to the controller, the controller will first try to measure its maximum energy output. The reactor will have its output increased step by step and the average (interpolated) maximum will be used for that value (CALIBRATING).
After calibration has been completed, the controller calculates the most efficient energy output of the reactor.

Active Reactors

When a new active reactor is connected to the controller, the controller will first try to measure its maximum steam output (CALIBRATING). For this to work correctly the reactor must be able to output at least SOME steam (read: you need a consumer) and you will need to provide sufficient ammounts of water. The controller will detect reactors with a potential steam output greater than 50 B/t and limit its energy accordingly.

Turbines

When a new turbine is connected to the controller, the controller will first try to measure its maximum energy output (CALIBRATING). For this to work, make sure your turbine is built correctly. This means your turbine can be run at maximum supported steam (25mb/t per blade) without exceeding 1950 RPM. Should your turbine exceed 1950 RPM at any stage, the controller will shut down the turbine and flag it as failed.

Note: Your turbine is NOT required to be able to process 2000 mB/t. Smaller turbines work perfectly fine.

Screenshots

After this wall of text, here're some screenshots (pre 4.2).

Main view:

Passive reactor details:

Active reactor details:

Let's go in order:

When you start up the GUI you will be presented with the main view.
Here a combined overview of passive reactors, active reactors and turbines will be presented.
You can click (or touch) on any of these items to open up a detailed view of the component.
Here you can enable/disable the component or change its behaviour.

This is where it gets interesting.

You will notice that passive reactors have two modes and an "auto" mode.

This is the behaviour everyone knows: The reactor gets turned on when its internal energy storage drops below 10% and gets turned off when the energy storage exceeds 90% of it's maximum capacity.
In PWM mode the reactor will generate energy at its most efficient rod level.
Overall this mode allows the reactor to generate energy as efficiently as possible as long as your actual energy consumption is below or equal to its optimal energy output.
But sometimes you need just a bit more energy and you don't want to upgrade your reactor or build a new one. "Classic" controllers will fail to produce sufficient ammounts of energy here.

Load

"Auto"-mode aims to eliminate the disadvantages of both modes by combining them:
If the energy consumption can be satisfied with PWM-mode, PWM will be used. If the energy consumption is above optimal levels, "Load"-mode will be used instead.
As a result, "auto"-mode generates energy as efficient as possible while always saturating your energy demands.

As of now, active reactors only operate in "load" mode. Steam is consumed and produced way too fast and the reactors internal steam storage does not allow for anything else.

Turbines

Turbines controlled similar to reactors in "load" mode: The controller will always try to balance the turbines internal energy storage out to 50% by using a PD-like regulator.
Turbines can be operated in "ganged"-mode or in "independent"-mode, with "ganged"-mode being the default.
The only difference between these two modes is that turbines in "ganged"-mode can be shut down by the controller, while "independent" turbines will always be active, even if they overproduce energy at the lowest RPM allowed.
This is handy if one (or more) of your turbines produces energy for a seperate (dedicated) energy grid but has to be controlled by the same controller. If such a turbine is not in "independent"-mode it may be shut down which will lead to energy failure in that grid.

That's it for now. If you have any questions, want to report bugs, etc., feel free to drop a message here.

pastebin get nGp7V1vw /home/boot.lua

You can also customize what programs can be used to open files through the programs.cfg file.

Tutorials:

• Browsing files/directories
  • Select files/directories by clicking on them in the panel on the right side of the screen
  • If a directory contains a large amount of files or sub-directories, use the arrow buttons to scroll through pages
  • To go up a sub-directory, click the up arrow
  • To change directory to a sub-directory, select the sub-directory, and click on "Open..." in the options panel (bottom left)
• Using programs
  • Select file/directory
  • Select an option from the options panel (Run, Edit, Delete, etc.)
• Creating files/sub-directories
  • Navigate to the directory where the file/sub-directory will be created
  • Select "New File..."/"New Directory..." from the functions panel (top left)
  • A prompt for the name will appear at the bottom of the screen. Enter the name for the file/directory
• Adding programs
  • Open the programs.cfg file in the editor
  • Add a new line for your program
    • Warning: The syntax for the programs.cfg is very strict, and will not accept extra spaces/empty lines
  • Enter this info separated by semicolons:
    1. Program name
    2. Text for the options menu
    3. File types (separated by commas, for all files put "all", for directories put "dir", for specific file types, put the extension including the ".")
    4. Command that runs the program ("?file?" is a wildcard for the selected file/directory)
    5. Additional options (separated by commas, does not require semicolon or comma at the end)
       1. "s" prevents Cell from erasing the screen before running the program
  • For example, the line that add the editor is: 

    OpenOS Editor;Edit...;all;edit ?file?;

     

Minimum Requirements:

• Tier 2 Graphics Card
• Tier 2 Screen
• Tier 1 CPU
• 2x Tier 1 Memory
  • Internet card only required for installation

To install, run 

wget https://raw.githubusercontent.com/Elektron72/Cell/master/installer.lua installer.lua
installer.lua

At the prompt, enter the path where Cell should be installed.

Since this is currently in beta, report bugs at https://github.com/Elektron72/Cell

Source Code:

OC-8 : A Chip-8 Emulator For OpenComputers (version 1.1) - Pastebin.com

Screenshots!:

Lookup table generator

#DEFINE RAM UP

MOV 65 ACC        
LOOP: MOV ACC RAM
    SWP
    MOV ACC RAM
    ADD 1
    SWP
    SUB 90
    JEZ LOW
    SUB 32
    JEZ DIGITS
    ADD 65
    JEZ HALT
    ADD 58
    JMP LOOP
#BWTM

LOW: MOV 97 ACC
    JMP LOOP

DIGITS: MOV 48 ACC
    JMP LOOP

HALT: MOV 43 RAM
    MOV 62 RAM
    MOV 47 RAM
    MOV 63 RAM
    JRO 0

Decoder

#DEFINE TERM UP
#DEFINE ROM LEFT
#DEFINE BUFF RIGHT
#DEFINE OUT DOWN

LOOP: MOV TERM ACC #1
    JEZ CLEAR
    MOV ACC ROM
    MOV ROM ACC
    SUB 61
    JEZ CLEAR
    ADD 61
    SHL 2
    MOV ACC BUFF
    MOV TERM ROM
    MOV ROM ACC
    SAV
    SHR 4
    OR BUFF
    MOV ACC OUT
#BWTM

    SWP #2
    AND 15
    SHL 4
    MOV ACC BUFF
    MOV TERM ROM
    MOV ROM ACC
    SAV
    SHR 2
    OR BUFF
    MOV ACC OUT
    SWP #3
    AND 3
    SHL 6
    MOV TERM ROM
    OR ROM
    MOV ACC OUT
    JMP LOOP
CLEAR: SAV

Draconic Control will be the first program I'll be releasing (more to come).

The important stuff first: By now there are quite a few programs out there to control draconic reactors. However most of these don't even get close to about 1 MR/t. With this program 1.9 MRF/t (on average) is very well possible.

Of course if you're not interested in RF/t but only total RF generated, this program is for you as well.

Also, this one has a nice gui.

Go check it out here: https://tenyx.de/draconic_control/

Yes, it comes with yet another (unreleased) GUI library *cough*.

And yes it uses some kind of self built installer *doublecough*.

This program has a CC and OC version. If you want to skip to the OC setup instructions, click here: https://tenyx.de/draconic_control/#setup_oc

I'm open for suggestions and so forth.

This is the first of quite a few things I'm about to release so stay tuned if you like this one

You can follow me on twitter @XyFreak1 to stay up-to-date - I promise I won't spam your tweetdeck or something - mostly release related stuff

Have Fun

- XyFreak

WARNING

DO NOT USE THIS WITH OC 1.7.4! Timers are broken in that versions OpenOS and upgrading to this version will cause big holes in your world sooner or later!

MAKE SURE YOUR CPU IS SET TO LUA 5.2 TO NOT RUN INTO THE "UNKNOWN" REACTOR STATUS ISSUE! SEE HERE

Github: https://github.com/Tavyza/TherOS_community_repo

# Installation:

wget -f -q https://raw.githubusercontent.com/Tavyza/TherOS_community_repo/main/pkg-man/src/tocr.lua /tmp/tocr.lua
/tmp/tocr -i pkg-man
rm /tmp/tocr.lua

To add a package to the repository:

1. Fork it
2. create a folder (this will be the package name)
3. make a package.tc file (should contain the full raw github link to your program)
4. dependencies.tc (same as package.tc but for libraries your package would need)
5. add your package to the end of repo_list.tc in the root of the repository
6. make a pull request.

Questions? Issues? Suggestions? Comment them or open an issue in the repo.

Introducing TherOS, a minimal (operating system/environment?) that provides basic tools to do what you want. These tools include:

• A graphical file manager with basic file management and creation abilities
• A program installer (can install from pastebin or github/literally any website ig)
• A simple and easy-to-use installer
• A terminal that can be used to run whatever

The OS has 2 versions, main and  bleeding-edge (SUPPOSED TO BE the lastest developments for the OS)

1.1 -- GitHub repo

1.1 -- Github repo

Install:

wget https://raw.githubusercontent.com/Tavyza/TherOS/main/sys/apps/installer.lua && installer

Or if you have the TOCR Package Manager, do:

tocr -ib theros-core theros-apps

Please report all bugs or suggestions in the issues section of GitHub. (Yes, you can laugh at my code.)

Here are some designs:

If you would like to see this become a real OS in OC, please reply.

Computer Requirements:
Basic Components
OpenOS (Lua 5x)

Recommended:
Tier 2 Components
Tier 2 Screen and Graphics Card
OpenOS (Lua 5x)

Feel free to add comments, I would love recommendations

it's completely written on lua and it's not irssi compatible!
it's text only but It's quite easy to use! By doing :helpoc!
to chat, you just press ctrl and to do commands just do alt!

to use this IRC client, you need to do
pastebin run e1bQJEFa
or
pastebin get e1bQJEFa OCDALNET.lua

Source Code Is at https://pastebin.com/e1bQJEFa

Fuchas in a Nutshell

Fuchas is revolutionnary in that it uses drivers instead of component access and support UAC (with separate permissions!) ! It's the end of the era where the program needs to maintain integration with different components, the OS now does it! The driver library will try automatically choosing the best driver, but it can be configured by user. Meaning programs adapt to components with no effort (e.g. Computronics cards)

A feature of Fuchas is security. If you do not trust a program, you can control permissions. Each account can have its own set of permissions. Allow one to have free access on a specific drive? You can do that!. Security is useful for computers on big servers with competivity. Although remember that without disk encryption, data can be accessed simply by using another operating system. Fuchas doesn’t hide files starting with ".", it uses attributes, filesystem’s one if supported on unmanaged drives, or with a .dir file at file’s parent directory.

Fuchas is also fast at startup, around 2x faster than OpenOS down like memory usage. And graphical features are optional, so you can use command-line on your T1 computer, and a graphical interface on T3, all on the same OS! And since the UI is compatible with 40x16 and doesn't uses a lot of memory, you can use both on a T1 computer!

Extra Features

For example, the GUI interface of Fuchas (named "Concert") uses the newly added GPU buffers when available in a way that is transparent to programs and user.

Interfaces

Here are the interfaces included: Fushell (a command-line shell) and Concert.

For example here is Fushell (warn: old version [4 major releases ago], but still a little representative):

and Concert as of Fuchas 0.7:

Install It

OpenOS:

Just type the following:

pastebin run EbHYvEE8

MineOS:

Search for the application 'Fuchas Installer'. Install it, launch it, and press Install.

Fuchas:

You’re on Fuchas 

(Note that all comments about broken installation below are outdated, and installers has been fixed!)

Links: GitHub, Wiki, Progress to next version, And here is how to break the whole Fuchas security system

how to use:

1. copy fluids.lua or use the command in the readme (have an internet card, ofc) and put it wherever you want on your system. make sure to be connected to an ME system controller.

2. run fluids.lua and type `initialize`.

3. you can either edit the quantities you want as your minimum through the program using `edit` or through changing the appropriate value in fluids.cfg

4. add the code you want to be ran whenever a given fluid is lower than the check value in the FUNCTIONS function. i couldn't figure out how to make it less convoluted, as of now.

let me know if yall have any issues

github code: https://github.com/GlitterVappy/ME-system-fluid-manager/

or run: wget -fq "https://raw.githubusercontent.com/GlitterVappy/ME-system-fluid-manager/main/fluids.lua" "fluids.lua"

I might make a gui for it

For this, you will need a linked card, tier 3, tier 2 tablet case

Step 1 Place a tier 3 computer case

step 2 set up the computer 

step 3 put a linked card and internet card in it

step 4 connect the computer to fission controller

step 5 type pastebin get FByuRNGd server.lua

step 6 type server.lua or do edit /autorun.lua then type os.execute("/home/server.lua")

Now for setting up the tablet

get an assembler place a tier 2 tablet case in assembler

put a linked card and internet card in it

setup tablet

type pastebin get GbQjG7nY reactor.lua

then type reactor.lua or type edit /autorun.lua then type os.execute("/home/reactor.lua")

--------------------------------------------------------------------------------------------------------------------------------------------

-- To do

Add a safety measure to stop meltdowns

Notes

The full code can be found on https://github.com/Juanan7676/netcoin. This is a work in progress project, bugs and security issues are very common, use with caution!

Steps to use:

1. Arrange the modules in a comfortable configuration (lock the sides if necessary)

2. Set the constants

3. Upload the program to the execution module

4. Set the password

•   Right-click to open the ROM interface
•   In cell 0 set the password length
•   Sequentially set each digit of the password
•   Install the ROM into a casing block

5. To activate redstone, type the correct password and press "0" to confirm.

Constants:

•  DELAY - redstone activation time

  Sides:

• RED - redstone module
• ROM - ROM module
• KEY - keypad

          [KEY]
[ROM][EXE][RED]

----- PAGE 1 -----
#DEFINE DELAY 20
#DEFINE RED RIGHT
#DEFINE ROM LEFT
#DEFINE KEY UP
START: MOV NIL ACC
SAV
LOOP: MOV KEY ACC
  JEZ CHECK
  SWP
  ADD 1
  MOV ACC ROM
  SWP
  SUB ROM
  JNZ START
JMP LOOP
#BWTM
----- PAGE 2 -----
CHECK: SWP
  MOV NIL ROM
  SUB ROM
  JNZ START
  MOV 15 RED
  MOV DELAY ACC
  SLEEP:
    SUB 1
  JGZ SLEEP
  MOV NIL RED

pastebin run -f YVqKFnsP

 
Computer requirements:
- CPU T2
- GPU T2
- 12x Screen T2
- HDD T1 (with OpenOS)
- 2x Memory T1.5
- Internet Card - only required for installation and updates
- keyboard - only required for installation
- Redstone Card T2 - optional
- EEPROM (Lua BIOS)
 
features of my program:
- autoclose iris on incoming wormhole (when iriscontrol is turned on)
- autoopen iris if correct IDC is received (iris deactivation code)
- autoclose stargate after X seconds
- show all kinds of stats (local / remote address, state, direction, idc, iris state, energy, ...)
- multiple languages: right now german, english and russian
- displays energy in EU or RF
- displays up to 10 addresses on 1 page (unlimited pages)
- allows dialing from the address list
- check for updates on start
- emit redstone signals (right now for: state not idle, incoming, iris closed, idc accepted, wormhole connected)
- automatically adds new, unkown addresses when there is an open wormhole
- shows the required energy to dial an address (or error if invalid address)
- allows closing of incoming wormholes if its disabled in config AND there is a computer at either end
- automatically sends and receives entire address list on an open wormhole (without the IDC of course) and automatically adds the new addresses
- with touchscreen functionalities
- works with Computronics ColorfulLamps -> red = iris closed, green = idc accepted, yellow = outgoing wormhole, orange = incoming wormhole (priority from left to right)
- logbook with the last connections

Stargate controller based on GML library.

Showcase:

Installation steps:

1. First download the package manager that will be used to download the application and all required dependencies:

   wget https://gitlab.com/d_rzepka/oc-equipment/raw/master/installer/arpm.lua

2. Use the package manager do download SGCX:

   arpm install sgcx

    

3. Run SGCX with an additional argument - init. This will allow you to pick a stargate interface address from list. It is required only during the first startup - address will be saved in a configuration file.

   sgcx init

    

4. Optionally you can install the irisAuth package (remote iris management) using the previously mentioned package manager.

Features:

• Displaying Stargate status
• Storing gate addresses
• Grouping and searching addresses
• Disconnecting wormhole after specified time
• Automatic iris control (see installation steps, step 4)
• Displaying distance to the selected destination
• Address calculator: convert addresses within one dimension into chunk (and estimated block) coordinates and vice versa
• Animated dialing sequence with chevron drawings

Future plans:

• Dialing history
• Iris authorization usage history

Requirements:

• Tier 3 screen and GPU
• At least 1 MB RAM
• Network card
• Keyboard

(GitLab repository)

Client Minimum requirements

relay

network card

internet card

apu

Server Minimum Requirements;

Wireless network card 

Configured serverside program

Put your paste code in the server program or else it will say Hello.

I did this cause nobody else had and I thought it would be useful

Server paste code: B7b27pc2

Browser paste code: vkL422Sz

I am new to OC and this is my first program

And now I decided to release the code for everyone to enjoy my work. Feel free to improve upon it, or use as is.

Example setup:

Inventory of active drone:

Drone minimum components:

• Drone Case (Tier 1)
• Geolyzer
• Inventory Upgrade
• Central Processing Unit (CPU) (Tier 1)
• Memory (Tier 1)
• EEPROM with code provided

How to setup:

Drone never changes altitude and operates on single square area that may not be permanently obstructed. You must till farm plot manually. Drones always use global axes for movement, there's no rotation to keep track of. Adjust localX and localZ variables at start of code to designate dock area, drone must always boot up at dock, on top of charger with my example setup. If drone starts beeping upon bootup, you messed up the setup, drone is unable to locate inventory (or it's full). Drone also will start beeping at dock if output is full, just collect your obscene amount of produce when that occurs. minX/minZ/maxX/maxZ similarly define corners of farm plot. On my example setup screenshot player is facing north-west (towards negative X and negative Z), dock is at (15, 15), while most remote corner of farm plot is (0, 0). no_farm table contains exceptions where no farming operation should ever occur, using same local coordinate system. keep_seeds should allow for few missing plants to be replanted (but drone won't be able to deal with trampled fields automatically due to inability to use tools), you might want higher value if plant you are working with has chance to not drop seeds. ensure_space should be set to maximum amount of item types mature plant yields on breaking (2 being value for wheat or potatoes), otherwise you will suffer minor item loss if drone overflows. If two outputs are common (wheat), either use value of 1 or add another inventory upgrade. As I understand Minecraft farming mechanics, monoculture farming would not be faster than farming two plant types at once with plants being in lines. plant() contains logic for seed slot selection, adjust if you want to farm more than two types at single plot, but beware inventory constraints of drone and multiple outputs.

Code, goes into EEPROM of drone:

local d = component.proxy(component.list("drone", true)())
local g = component.proxy(component.list("geolyzer", true)())
local c = computer

d.setLightColor(0xff00ff)

local no_farm = {
[15] = { [15] = true, },
[12] = { [3] = true, [12] = true, },
[3] = { [3] = true, [12] = true, },
}
local to_collect = {
["minecraft:potatoes"] = true,
["minecraft:carrots"] = true,
}
local seed_slot = {
[1] = true,
[2] = true,
}
local keep_seeds = 4
local ensure_space = 2
local localX = 15
local localZ = 15
local minX = 0
local minZ = 0
local maxX = 15
local maxZ = 15
local inv_side = 1
local inv_name = "minecraft:chest"

local startX = localX
local startZ = localZ

local function sleep(sec)
  local dl = c.uptime() + sec
  repeat
    c.pullSignal(dl - computer.uptime())
  until c.uptime() >= dl
end

local function attn()
  c.beep(1500, 0.2)
  c.beep(1700, 0.2)
  c.beep(1300, 0.2)
  sleep(3)
end

local function plant()
  local slot = localX % 2 + 1
  if d.count(slot) > 1 then
    d.select(slot)
    if not d.place(0) then attn() end
  else
    attn()
  end
end

local first_free

local function got_free_slots(wanted, no_heur)
  local found = 0
  for slot = first_free or 1, d.inventorySize() do
    if d.count(slot) == 0 then
      found = found + 1
      first_free = first_free or slot
    end
    if found >= wanted then
      return true
    end
  end
  if first_free and not no_heur then
    first_free = nil
    return got_free_slots(wanted, true)
  end
  return false
end

local function farm()
  local found, desc = d.detect(0)
  if not found and desc == "air" then
    plant()
  elseif found and desc == "passable" then
    local block = g.analyze(0)
    if block ~= nil and block.growth ~= nil then
      if block.growth == 1 and to_collect[block.name] then
        d.select(1)
        d.swing(0)
        plant()
      end
    else
      attn()
    end
  else
    attn()
  end
end

local function put_away_excess()
  while true do
    local found, desc = d.detect(inv_side)
    if found and desc == "solid" then
      local block = g.analyze(inv_side)
      if block ~= nil and block.name == inv_name then break end
    end
    attn()
  end
  repeat
    local done = true
    for slot = 1, d.inventorySize() do
      local amt = d.count(slot)
      if amt > 0 then
        d.select(slot)
        local to_drop = math.huge
        if seed_slot[slot] then to_drop = amt - keep_seeds end
        if to_drop > 0 and not d.drop(inv_side, to_drop) then done = false attn() break end
      end
    end
  until done
  first_free = nil
end

local function vec_len(oX, oZ)
  return math.sqrt(oX*oX + oZ*oZ)
end

local function move_to(tgtX, tgtZ, precise)
  local offX = tgtX - localX
  local offZ = tgtZ - localZ
  if offX == 0 and offZ == 0 then return end
  d.move(offX, 0, offZ)
  local moved
  local goaldist = 0.45
  local goalvel = 2
  local timemult = 1
  if precise then
    goaldist = 0.1
    goalvel = 0.1
    timemult = timemult * 2
  end
  local dl = c.uptime() + vec_len(offX, offZ) * timemult
  repeat
    moved = d.getOffset() <= goaldist and d.getVelocity() <= goalvel
    if c.uptime() >= dl then break end
  until moved
  if moved then
    localX = localX + offX
    localZ = localZ + offZ
  else
    d.move(-offX, 0, -offZ)
    attn()
  end
end

local workX = startX
local workZ = startZ

local function next_spot()
  if workX < maxX then
    workX = workX + 1
  else
    workX = minX
    if workZ < maxZ then
      workZ = workZ + 1
    else
      workZ = minZ
    end
  end
  if no_farm[workX] ~= nil and no_farm[workX][workZ] then
    next_spot()
  end
  return workX, workZ
end

local function dock(optional)
  if optional and c.energy() >= 500 and got_free_slots(ensure_space) then return end
  move_to(startX, startZ, true)
  put_away_excess()
  while c.energy() < c.maxEnergy() - 500 do sleep(3) end
end

dock(false)

while true do
  dock(true)
  move_to(next_spot())
  farm()
end

License terms for my code:

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.

In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to <https://unlicense.org/>

Ideas for improvement:

• More robust detection of drone actually being at new position without slowing down operation. I've been adjusting goaldist and goalvel until drone stopped failing farm(), with no strong theory for what should be ideal values;
• Change scanlines pattern into zig-zag pattern for minor increase in farming speed;
• Have companion robot craft away wheat and similar things into cubes and/or fix trampled field;
• Handling of plants not exposing "growth" to geolyzer, like Immersive Engineering's hemp;
• Handling of multi-tile plants, like said hemp;
• Rotating between many plant types with just few being planted at given time;
• Melon and pumpkin farming (will likely release drone for that soon, as I already got stutter-inducing robot doing this).

I'm working on a Warehouse system for Open Computers. This is what I'm planning on having:

• Robots which do the work of grabbing items, sorting them, and packaging them in shulker boxes (if requested)
• A* Pathfinding with preferences (a robot is more likely to go above a block than go around it due to less steps)
• Collision detection (Robot in the way, request a repath)
• Possible integration with OpenSecurity Rolldoors (Place checkpoints inside the warehouse that the robots can request to be opened. Good for exits from the main warehouse area.)
• Auto-assortment into necessary bins (Certain chests will be associated with a type of item only, or if you need it, make them go into the miscellaneous area.
• Shulker box packages (put all requested items in a shulker to be outputted)
• Stock takes (Count items in the entire warehouse)
• I might add a store system so you can have people pay you for items.
• And more!

I'll post updates here when I start getting progress in, but at the moment, there is not really anything that is done. I did make an A* pathfinding script that works with the robot, which I might make a video about. Well, fun times ahead, wish you all adieu

OpenOS is a required dependency.

I created this for personal use in a Project Ozone 3 playthrough with a friend, and it's been working out so far. Willing to take feature suggestions and feedback.

I'm currently in the process of publishing it as a package for OPPM.

This is currently published as "todo" on this GitHub repository.

todo.lua