Mod Compatibility

What Nerospace shares with the other mods in your pack, and what it keeps to itself. Nothing here needs setting up — it is how the blocks behave once both mods are installed. (For the developer-facing integration surface, see Public Integration API.)

What crosses the mod boundary#

In practice a Universal Pipe connects to, pulls from and pushes into another mod's tanks, machines and pipes — and another mod's pipes can drain or fill a Nerospace Fluid Tank, Fuel Tank, Fuel Refinery, Quarry Controller, Launch Controller or Universal Pipe directly, with no Nerospace pipe in the line at all. A quarry can eject its mined items and the water it swallows into whatever storage you already run.

The one exception: the Rocket Launch Pad#

The Rocket Launch Pad's fluid connection is one-way — it feeds a docked rocket and can never be drained back out. The standard fluid handlers are transactional: another mod may insert and then undo it, as its ordinary way of asking "how much would you take?", and a one-way sink cannot answer that honestly. So the pad accepts fuel from Nerospace's own pipes only. To fuel a rocket from another mod's system, pipe into a Fuel Tank beside the pad and let it fuel the rocket as usual.

Your face settings still hold#

Per-face I/O modes and pipe filters treat a foreign neighbour exactly like a Nerospace one. A face set to Off with the Configurator looks shut to another mod's pipe too, and a filtered face passes only what you told it to pass — cross-mod reach never costs you control over what moves where.

Gas stays inside the Neroland mods#

The pipe's gas layer moves gas between Nerospace, Neroland Core and the other Neroland mods, such as NeroTech, through Core's shared gas capability. It carries any of their gases: oxygen from an Oxygen Generator or an Electrolyzer, hydrogen from an Electrolyzer, into a Gas Tank or a Chemical Processor. Oxygen is one gas, nerospace:oxygen, in every Neroland mod. There is no gas standard beyond the Neroland mods, so do not expect another mod's gas system to read it, or Nerospace to read theirs.

Recipes#

Nerospace's recipes are tag-based throughout, so another mod's equivalent ingredients — its glass, redstone, ore drops and the common c: material tags — work in them wherever the tag matches.

Quests (optional — NeroQuests)#

Nerospace bundles a quest chapter, Starfarer's Log (19 quests), that appears in the quest book when the sibling NeroQuests mod is installed. It follows the mod's own progression — first Nerosium, power, launch, orbit, the planets, suits, colonies, freight and terraforming — plus one shared world-log quest for a hundred cargo deliveries. NeroQuests is not required: without it the pack is inert data in the jar.

The milestones behind those quests are plain Neroland Core progression gates and threshold events, so any mod on Core can read them: the player-scope record gates nerospace:first_freight, nerospace:terraformed_ground and nerospace:living_world, and the world channel nerospace:cargo_delivered (scope = destination dimension id; rungs 1 / 10 / 100 / 1000). Two hook gates, nerospace:hook/reveal_star_guide_page and nerospace:hook/oxygen_top_up, work the other way round: open one for a player and Nerospace sends them a Star Guide hint or refills their oxygen once, then closes the gate again. None of these gates lock anything.

The caveat worth reading#

All of the above is Nerospace's half of the deal: it speaks the standard, platform-native APIs. Whether any particular other mod connects depends on that mod using them as well. If a block from another mod refuses to link up, that is what to check first.

---

See also: Universal Pipe, Neroland Core, Public Integration API, Fluid Tank.