-
-
Notifications
You must be signed in to change notification settings - Fork 3
Auto Pearl Stasis Guide
AutoPearlStasis automatically pulls your loaded ender pearl out of a stasis chamber when a chosen condition is met, such as low health or a keybind press.
This module needs 2 Minecraft accounts running at the same time on the same computer. Main is the account you normally play on. Puller is a second account that stays at the stasis chamber and physically pulls the pearl when told to.
- Build a standard ender pearl stasis chamber, a bubble column that catches a thrown pearl and holds it in place.
- Place any trapdoor on top of the bubble column, directly above where the pearl will sit. This is the trapdoor the Puller account will interact with.
- Have your Main account stand near the chamber and throw an ender pearl in, so it lands and floats at the trapdoor position.
| Setting | Description |
|---|---|
mode |
Main or Puller. Set this differently on each account. |
port |
Network port used for the Main to Puller connection. Must be the same number on both accounts. Default is 67. |
On the main account, set mode to Main, then activate the module. It will start listening on the chosen port and display "Waiting for Puller..." in chat.
On your second account, at the chamber, set mode to Puller, then set the trapdoor position setting to the coordinates of the trapdoor sitting on the bubble column.
Activate the module. It attempts to connect to Main on localhost at the configured port. "Connected to main." means the connection succeeded. "Connection failed: ..." followed by automatic retries every few seconds means Main isn't listening yet (check it's activated) or the ports don't match.
Once connected, make sure the puller account stays within reach of the trapdoor.
Open the module's settings screen on either account. It shows a live status section with the other account's username, the other account's connection address, and whether a pearl is currently detected as loaded.
There's also a Test Connection button that pings the other side without triggering a real pull.
- Puller keeps retrying and never connects: both must use the identical
portvalue. Also confirm both accounts are on the same machine. - "Puller not found" error on pull: The connection failed. Check if Puller is still active and the section shows a connection.
- "Pearl not loaded" error on pull: The pearl hasn't been detected sitting on the trapdoor position yet, or it landed in the wrong spot. Re-throw it so it settles directly above the trapdoor.
- "selected position is not a trapdoor", "is out of reach", or "trapdoor is closed". Double check the trapdoor position points at an actual trapdoor block, also if it's within reach distance, and that it's open.
- "Puller is connected but they're not on the same server." Main detected Puller is on a different world or server. The pearl mechanics only work within the server. However, if either accounts are using a different IP but still on the same server, then it should still work normally.
if you have any other issues/unexpected behavior, please report them to the issue tracker. Include game logs (use mclo.gs) from both the Main and Puller accounts in the report.