This is an OpenComputers script to automate the Blood Altar provided by Blood Magic in Minecraft. Specifically, this script is designed to be used in the modpack GT New Horizons.
This script fully automates a single blood altar with a connected Well of Suffering, Extreme Entity Crusher, and World Accelerators for the altar and ritual. It will periodically check an input chest for items, craft them a single time, output the new items, then refill the player's soul network with a blood orb. While idle, it will passively refill the player's soul network.
This repo includes an OPPM repo. To install this script just install oppm, then run the following commands:
oppm register RecursivePineapple/auto-altar
oppm install auto-altar
It will take around a minute to install everything. After installation, the computer should be rebooted.
This script contains a lot of functionality, although the underlying principles are simple. The core of the build is a blood altar of arbitrary tier, with a well of suffering and an EEC in ritual mode. World accelerators should be connected to the altar and ritual, but they aren't required. Everything for this build can be placed below the altar, although that makes it slightly more expensive due to the required transvector interface and MFU.
The OC network must have the following components: a translocator, an adapter, and a redstone I/O. The translocator must be connected to three chests/buffers as well as the altar (the altar can be connected through a transvector interface). The adapter must be connected to the altar (can be connected remotely through an MFU).
A line of redstone (ideally red alloy wire) should lead from the redstone I/O to the ritual, world accelerators, and EEC. This line acts as an on/off switch. I prefer to make it Disable with Redstone so that a power level cover can be used to shut the system down too, but this is configurable in the config script.
The translocator chests represent the following: an input (fed by an ME interface), a staging buffer (used to store orbs and altar products), and an output (used to push items back to the ME system). The chests can be any size, although the staging chest should be at least a vanilla chest. Blocking mode can be used on the ME interface, although the script will move items from the input chest in stacks. If a stack of 64 slates is inserted into the chest, the whole stack will be inserted into the altar. If blocking mode isn't enabled, consider setting stack merging to "Insert to empty slots only" in the interface if the stack size needs to be a specific amount.
Set the stack size in recipes so that your soul network is never close to being empty. Recipes should be as close to 64 as possible.
The computer and its CPU must be at least tier 2 due to the number of components required.
To run the script on boot, just add the following to your /home/.shrc file:
blood_altar
To exit cleanly, press Ctrl+C. When interrupted, the script should shut down the altar but not remove any items in the altar.
This script comes with a REPL configuration command called blood_altar_config which significantly simplifies setup. Running the script and saving will generate the config file /etc/blood-altar.cfg. The config can be hand edited, although this is not recommended since the contents are subject to change and there is no documentation for the format. Just read the code if you really want to edit it manually.
Once the config script is started, specify all components, sides, and the blood orb type. All options must be set for this script to work. The config script should be fairly self explanatory. If something isn't clear, send at message to recursive_pineapple on discord or open an issue.
The script has two states, active and idle. The script starts in the active state. In this state, the script will first finish whatever item is held in the altar. If this item is a blood orb, it will wait until the owner's soul network is full. Otherwise, it will wait until the item changes, which signifies that a craft has finished. Once the current item has finished, the script will move the item into the staging chest. Any non-orb items will then be moved to the output chest. A single orb matching the configuration will be kept in the staging chest.
Next, the script will check how much time has passed since the owner's soul network was refilled. If the time is past the configured threshold, it will insert an orb into the altar and wait until the owner's soul network is full. Otherwise, it will look for another stack in the input chest.
Once the input chest is empty, the script will enter the idle state. In this state, the script will keep a blood orb in the altar. If the owner's soul network isn't completely full, the script will start the altar until the network is full.
The script assumes the owner's soul network is full when the altar has been idle for a few seconds. The altar is considered idle when its contained blood amount is zero or above 90% of its total capacity.
The script will leave the idle state if an item is detected in the input chest.
The script will not work correctly if the altar is manually interacted with while the script is running. A 'manual' state may be implemented at some point, but for now the script assumes it is the only thing interacting with the altar.