AE2 Cross-Realm Wireless
Minecraft Your Applied Energistics 2 wireless terminal works across realms. Bind it to your ME network the normal way on your home realm, then carry it through a realm portal. The first time you open it on the other side, it remembers where it came from, and you start browsing your home network as if you were standing next to the controller.
Your AE2 network on Realm A. You on Realm B. The terminal links the two automatically the first time you open it.
The terminal still binds to a Wireless Access Point the normal AE2 way. The cross-realm part is automatic: your terminal quietly remembers which realm's network it was first opened against, and Miralis routes anything you do back to that network whenever you open it elsewhere.
What you can do remotely
A cross-realm terminal behaves like a wireless terminal that just happens to be very far away. Most of the things you'd do at the controller are available; a few are not.
Note
The inventory list refreshes every couple of seconds, so very-fast crafting throughput on the source network may take a beat to show up on a remote terminal. For everyday browsing it feels live.
What doesn't work cross-realm
Some operations need live grid state that can't travel between servers. These work normally when you are physically on the same realm as the network, just not from across the bridge.
- Autocrafting requests. You can't queue a craft from a remote terminal. Walk back to the realm with the network, or pre-queue the craft before leaving.
- Pattern encoding. Encoding a new pattern needs the live grid open. Encode locally, then carry the pattern back.
- ME monitor changes. Reading values is fine; changing settings on a remote ME monitor is not.
Setting one up
The setup is the same as any AE2 wireless terminal. The cross-realm trick happens on its own once it is bound.
Supported terminals
The cross-realm layer wraps every wireless terminal that goes through the standard AE2 / ae2wtlib machinery, plus the most common addon terminals.
| Terminal | Mod |
|---|---|
| Wireless Terminal | Applied Energistics 2 |
| Wireless Crafting Terminal | ae2wtlib |
| Wireless Pattern Encoding Terminal | ae2wtlib |
| Wireless Autocrafting Terminal | ae2wtlib |
| Quantum Crafter Wireless Terminal | AdvancedAE |
| Expanded Wireless Terminal | ExpandedAE |
| Requester Wireless Terminal | ME Requester |
Any new wireless terminal that registers through ae2wtlib gets cross-realm support automatically.
Commands
Most of the time you will not need any of these; the link is automatic. They exist for when you want to switch which network a terminal is bound to without rebinding through an access point.
| Command | What it does |
|---|---|
/miralis ae2bridge info |
Show the current bind: realm name, dimension, and whether the terminal is in cross-realm or local mode |
/miralis ae2bridge reset |
Forget the bind. The next time you open the terminal it binds to your current realm |
/miralis ae2bridge set <realm> |
Force a bind to a specific realm by name |
Things worth knowing
- No range limit cross-realm. Distance does not apply once the link goes through Miralis. Same realm, opposite realm, doesn't matter.
- No extra cost. The source network pays the same AE energy it would for a local wireless terminal access. Nothing extra is taken from your wallet.
- Two-second refresh. The remote inventory list is cached briefly so you don't hammer the source server with queries every tick. Withdrawals and deposits themselves are immediate.
- Source network has to be loaded. The chunks containing your controller and the access point need to be loaded for remote access to work. Use spawn chunks or a chunk-loader if you want it always-on.
- One terminal, one home network. A bound terminal points at the network it first connected to. Use
resetif you want to point it somewhere new. - If a realm goes down, your terminal goes quiet until it comes back. No data is lost; the connection just pauses.