RoR can have QMAW as a treat

changelog

@@ -21,9 +21,13 @@
     * The fat man only gets a single nuke
     * Certain legendaries do not give ammo at all, they are omitted when three randomly held guns are selected
 * Ammo containers are now found in more itempools
+* The arc furnace input queue can now be moved into the recipe grid if the lid is at least slightly open instead of requiring a fully opened lid
+  * This means that in system with slow input, the time window when items can be added to the arc furance is now more forgiving
 
 ## Fixed
 * Fixed arc furnace only allowing electrodes to be inserted when the lid is down instead of up
 * Fixed issue where the `amounts` tracker wasn't being used correctly when using a custom acidizer config, preventing the acidizer partitioner from working
 * Fixed multi fluid ID search potentially not working on systems with a non-latin locale
 * Fixed particle accelerator source working even if not cooled
+* Fixed foundry channels being overly laggy in certain setups
+* Fixed potential mod incompatibilities with world generation mods that use outdated forge hooks

src/main/resources/assets/hbm/manual/ror/redstoneoverradio.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone over Radio",
+	"icon": ["hbm:tile.radio_telex", 1, 0],
+	"trigger": [],
+	"title": {
+		"en_US": "Redstone over Radio"
+	},
+	"content": {
+		"en_US": "Redstone over radio is a system that allows signals to be sent and received within a dimension, with no delay or distance restrictions. In its most basic form, redstone over radio can be used to send redstone signals with standard impulse strengths of 0 - 15 to control simple mechanisms from afar, however there are no actual restrictions on what exactly a signal can be. Depending on the application, larger numbers or even text can be sent, and interpreted as needed.<br><br>To get a simple RoR setup to work, only a single RoR compatible transmitter and receiver are needed. RoR transmitters for example will, if not configured to do otherwise, simply translate the redstone signal of the block they are connected to into a radio signal with that numeric value, and RoR receivers will turn that numeric radio signal back into a redstone signal.<br><br>Most RoR compatible machines have two operating modes, \"State Change\" and \"Polling\". When set to state change, transmitters will only send one single impulse when their signal changes, and receivers will update their output once they receive such an impulse. This means that, should a transmitter unload or be destroyed, receivers will retain their most recent signal. Polling means that checks are expected every tick, so transmitters will send constantly and receivers will listen constantly, should a transmitter unload or be destroyed, the receiver will immediately lose the signal.<br><br>To send a signal, a frequency must be specified, one frequency can only hold one signal at a time. If multiple signlals are sent on one frequency, the most recent signal is the one that's preferred. There is however an exception to this rule: If there's two numeric signals on the same frequency and within the same tick, the resulting frequency is the sum of all numeric signals being sent.<br><br>Redstone over radio transmitting devices include:<br>* [[Redstone-over-Radio Transmitter]]: The simplest of transmitters, either just sends the strength of a redstone signal, or can use custom redstone strength to text mapping<br>* [[Redstone-over-Radio Item Counter]]: Counts the configured items in a connected container and sends them on the specified frequencies, up to three items can be configured<br>* [[Redstone-over-Radio Reader]]: Can be connected to machines that support it to read values and then send those values over the specified frequencies<br><br>Redstone over radio receiving devices include:<br>* [[Redstone-over-Radio Receiver]]: The simplest receiving device which either receives numerical values and emits them as redstone signals, or maps custom values to redstone signals<br>* [[Redstone-over-Radio Logic Receiver]]: A more advanced receiver that uses a list of logic operations, like comparing numeric values or text, to figure out what redstone signal to emit<br>* [[Redstone-over-Radio Controller]]: An advanced component that can be connected to supporting machines, where it can receive commands with parameters to perform certain actions with that machine<br><br>Additionally, some devices can transmit and receive signals simultaneously:<br>* [[TELEX Machine]]: Wireless communications that can send and receive text, letter by letter"
+	}
+}

src/main/resources/assets/hbm/manual/ror/rorcontroller.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Controller",
+	"icon": ["hbm:tile.radio_torch_controller", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_controller"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Controller"
+	},
+	"content": {
+		"en_US": "Advanced [[redstone over radio|Redstone over Radio]] receiving device, listens on one frequency for commands to execute for the connected block. Commands follow the format of <command_name>!<parameter1>:<parameter2> where the actual command name is followed by a \"!\" which separates the command name from the parameters, which are separated from one another with \":\". Hovering over the [V] icon will list available commands for the connected block, as well as what parameters are accepted.<br><br>The controller can be used for example for barrels, where the \"setmode\" command can use a number from 0 to 3 to change the barrel's IO mode. The second variant of the same command has another parameter, which is a fallback to use if the first specified mode is already selected, ultimately allowing the command to \"switch\" between two modes instead of just setting it."
+	}
+}

src/main/resources/assets/hbm/manual/ror/rorcounter.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Item Counter",
+	"icon": ["hbm:tile.radio_torch_counter", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_counter"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Transmitter"
+	},
+	"content": {
+		"en_US": "Advanced [[redstone over radio|Redstone over Radio]] transmitting device, can broadcast to up to three frequencies at once. When connected to an inventory (e.g. a chest), it will count items that match the specified filters, and output the resulting values as a radio signals."
+	}
+}

src/main/resources/assets/hbm/manual/ror/rorlogic.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Logic Receiver",
+	"icon": ["hbm:tile.radio_torch_logic", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_logic"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Logic Receiver"
+	},
+	"content": {
+		"en_US": "Advanced [[redstone over radio|Redstone over Radio]] receiving device, reads a radio signal and tries to interpret it as a redstone signal using the supplied rules. Can compare numbers as well as text (\"Strings\"), and will evaluate the signal in ascending or descending order, depending on how it is configured. The first condition that matches will determine the resulting redstone signal strength. If no condition matches, the resulting redstone output is 0.<br><br>Most commonly used along with the [[item counter|Redstone-over-Radio Item Counter]], since it's capable of comparing quantities of items that surpass the limitations of regular redstone signals with exact precision."
+	}
+}

src/main/resources/assets/hbm/manual/ror/rorreader.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Reader",
+	"icon": ["hbm:tile.radio_torch_reader", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_reader"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Reader"
+	},
+	"content": {
+		"en_US": "Advanced [[redstone over radio|Redstone over Radio]] transmitting device, can be connected to certain machines and configured to read up to eight different values and transmit them over separate fequencies. Supported values are listed when hovering over the [V] icon. Comparators, and therefore [[RoR transmitters|Redstone-over-Radio Transmitter]] are limited to interpreting single values as numbers 0 - 15, while the reader can send multiple values with exact precision. For example, connecting the reader to a barrel and reading the \"fill\" value will cause it to send the exact amount of millibuckets in that barrel."
+	}
+}

src/main/resources/assets/hbm/manual/ror/rorreceiver.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Receiver",
+	"icon": ["hbm:tile.radio_torch_receiver", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_receiver"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Receiver"
+	},
+	"content": {
+		"en_US": "Basic [[redstone over radio|Redstone over Radio]] receiving device, reads the configured radio signal and outputs a redstone signal based on that. By default, it is set to \"Redstone Passthrough\" which means it will simply try to interpret the signal as a number and produce a matching redstone signal. If set to \"Custom Mapping\", it will instead translate the received value to a redstone signal level. Received signals must match the configured mapping exactly in order to be interpreted, for less precise comparisons, a [[logic receiver|Redstone-over-Radio Logic Receiver]] is required."
+	}
+}

src/main/resources/assets/hbm/manual/ror/rortransmitter.json

@@ -0,0 +1,11 @@
+{
+	"name": "Redstone-over-Radio Transmitter",
+	"icon": ["hbm:tile.radio_torch_sender", 1, 0],
+	"trigger": [["hbm:tile.radio_torch_sender"]],
+	"title": {
+		"en_US": "Redstone-over-Radio Transmitter"
+	},
+	"content": {
+		"en_US": "Basic [[redstone over radio|Redstone over Radio]] transmitting device, reads the redstone signal strength of the block it is connected to (connecting redstone to the torch itself does nothing) and sends a radio signal based on that. If no redstone signal is found, it will act like a comparator, meaning it can read the fill state of chests or barrels and interpret them in increments from 0 to 15. By default, it is set to \"Redstone Passthrough\" which means it will simply send the numeric value of the redstone signal it receives. If set to \"Custom Mapping\", it will instead translate the received value to a specified line of text, and send that text instead. Text that only contains numbers can be interpreted like numbers by receivers that support it."
+	}
+}