Repository navigation
Tesseracts
A tesseract sends resources through a channel to other tesseracts on the same channel, over any distance and without pipes in between.
| Block | Range | Throughput per resource type |
|---|---|---|
| Resonant Tesseract | any distance in the same dimension | T4 (Resonant) |
| Quantum Tesseract | across all dimensions of the server | T5 (Quantum) |
A channel between a Resonant and a Quantum Tesseract works only within one dimension. Only if both are Quantum Tesseracts can it cross dimensions.
Right-click a tesseract to open the channel screen.
- Every tesseract can bind one channel per resource type (items, fluids, gas, energy).
- Create a channel with a name. It belongs to you.
-
Visibility:
- Private: only you
- Invited players: you and the players you invite by name
- Public: everyone on the server
- Delete removes a channel you own. Tesseracts bound to it go offline.
- A player can own up to 128 channels.
- Teams: with FTB Teams or Open Parties and Claims installed, players of one team or party share their channels as if each of them owned them, also channels created before someone joined. See Resources and Compatibility.
If someone loses access to a channel (visibility changed, invitation removed), their tesseract stays bound but goes offline ("Access revoked: offline"). Nothing is deleted.
Each of the six sides of a tesseract works like a pipe port: click a side to change its mode (Insert, Extract, Both, Off); Cfg opens its filter and rule settings. A side can connect to a machine directly or to a Pipster pipe network.
- All involved chunks must be loaded. Tesseracts never load chunks. A tesseract in an unloaded chunk simply counts as offline.
- At most one channel hop. A resource that arrived through a channel cannot enter another channel on the same trip. This rules out endless loops.
- Resources never go back into the network they came from.
- A channel is only as fast as its members: the channel budget is the best tier among loaded member tesseracts, and each tesseract is still limited by its own tier.
- Two tesseracts placed side by side do not connect to each other, so channels cannot be chained that way.
- Buffered resources stay in the dropped item and come back when placed.
- The channel binding is not kept in the item, so access control cannot be bypassed by handing a tesseract to someone else.
Operators (permission level 2) can see and edit all channels and use the command below. With a
permission mod, these rights can also be given with the nodes pipster.admin (channels) and
pipster.command (the command).
/pipster channels list
/pipster channels delete <channel-uuid>