Codex Reference Integrations

Other Mods

QNet works together with many mods. Pipster is required; everything else is optional and switches itself on when the other mod is installed. On a server, each integration that runs on the server can be switched off in the section features. of the configuration, see Configuration. Computers have a page of their own: ComputerCraft.

Pipster (required)

QNet has no cables or pipes of its own. Energy, items, fluids and gases all travel through Pipster (version 1.2.0 or newer), which you install separately.

• Energy: 1 E is 1 FE and 1 unit of Team Reborn Energy, so Pipster cables, and the cables, generators and batteries of other mods, connect to QNet machines directly.
• Gases are Pipster gases. Gas pipes, gas tanks and QNet machines share them; the gases of other mods that are registered with Pipster work too.
• Energy Input Hatches have six tiers, one for each Pipster cable tier: a hatch lets in as much as a cable of its tier carries. See Plant Parts.
• Output ports and output slots are passive. Set the Pipster pipe at an output to extract mode to pull the products out. Generators, the Energy Cell and the Energy Output Ports of plants push their energy by themselves.

Recipe viewers: JEI, REI and EMI

QNet shows its machine recipes in JEI, REI and EMI, with the same look in all three:

• One category per process type (crushing, alloying, pressing, the plant processes and more), plus the Fuel Fabricator, the Matter Compressor and the Centrifuge Cascade.
• Each recipe shows its item and fluid slots and the time of one run. Small chips show energy, power, tier, heat, chance and similar values; point at a chip for the full text.
• Gases are drawn as gauges with their name and amount, because the viewers have no gases of their own. You cannot click a gas to look it up.
• The machines that run a category are listed with it: look up the uses of a machine to see all of its recipes.
• On a server, the recipes come from the server after you join and again after every /reload, exactly as the server uses them, with its tags and its other mods. A recipe that a server setting switches off does not appear.

The recipe viewers run only on your own computer; there is nothing to switch on the server.

Jade

Point at a QNet machine, plant controller or port, and Jade shows its main values: the status line and up to six lines from its window. A port shows the values of its plant. A block that the server has switched off shows the red line "Disabled by the server". Rift structures add their own lines, for example "Port of: …", "Checking structure: … / …" or "Structure complete". In Jade's settings the QNet lines are listed as "QNet machines".

Applied Energistics 2

On NeoForge, an AE2 storage bus placed on a Storage Interface mounts the QNet storage network directly:

• AE2 sees the items and fluids of the network's own storage units. Storages that the network only reaches through an External Storage Interface are left out, and so are gases.
• With an empty filter on the Storage Interface AE2 sees everything; with a filter it sees what the filter lets through.
• What AE2 puts in goes into the network's own units, whatever the filter says.
• Fluids count in mB on both sides.

Switch: features.integration.ae2 (default true).

Refined Storage 2 and Tom's Simple Storage

Both reach the QNet storage network through a Storage Interface, on Fabric and NeoForge: point RS2's External Storage or put Tom's Inventory Connector at the interface.

• They see and take what the interface's filter lets through, like a pipe does. With an empty filter they see nothing: set a filter for what they should reach.
• What they store goes into the network.
• QNet needs no switch for them: they use the interface's normal item and fluid connection.

Create and Mekanism recipes

With Create or Mekanism installed, QNet machines also run some of their recipes:

Recipe of	Runs in
Create crushing and milling	Crusher
Mekanism crushing and enriching	Crusher
Create pressing	Metal Former with the Plate Die

• Each of these recipes runs like a typical recipe of its machine: in the Crusher 140 ticks at 40 E/t, in the Metal Former 160 ticks at 60 E/t.
• Only recipes with one item as input are taken; recipes with fluids, several inputs or unknown items are left out.
• Of Create's results the Crusher keeps the main result and the first further one; chances are kept.
• QNet's own recipes and those of data packs always win for the same input.
• The balance check switches such a recipe off if it would make material from nothing in a loop.

Switches: features.integration.create (default true) and features.integration.mekanism (default true).

Party and claim mods

• FTB Teams and Open Parties and Claims: the members of one party are Operators of each other's QNet blocks, as if each had added the others to their team. See Teams and Rights.
• Open Parties and Claims: a QNet machine may not change a block in a claim that OPAC protects against it, the same rule OPAC applies to pistons and dispensers.
• FTB Chunks: a QNet machine may change a claimed chunk only if its owner is a member or ally of the claiming team, may bypass the protection, or the machine stands in a chunk of the same team. This also works while the owner is offline.

The machines that change the world are the Farming Station and the Tree Harvester. Severe incidents of power plants never destroy blocks in claimed land either.

Switches: features.integration.ftbteams (default true), features.integration.openpartiesandclaims (default true) and features.integration.ftbchunks (default true).

Permissions

QNet knows two permission nodes:

Node	Allows
qnet.admin	Every right on every QNet block, other players' teams included.
qnet.command	The operator parts of /qnet, see Commands.

A permission mod decides when one is installed: on Fabric through the Fabric Permissions API (for example LuckPerms), on NeoForge through NeoForge's permission system. Without one, or when a node is not set, the vanilla rule applies: operators (level 2) have both nodes, other players neither.

Switch: features.integration.permissions (default true).

For mod authors

QNet has a public interface for other mods (QNet API): other mods can hand heat to heat ports, read machines and plants, use the storage network, add materials and recipes, offer their own machines to the Factory Controller and listen to the events of plants.