SoapsUniverse

Portal Types

Last updated Oct 28, 2026

Portal Types

SoapsTeleporter supports three portal types. Change type in-game or through the management GUI connection menu. Version 1.0.7.

Staff how-to

  1. Create two portals (or one for RTP).
  2. /st settype <portal> standard|oneway|rtp …
  3. For standard/one-way: /st connect (and optionally /st setrouting / /st setdestinations).
  4. For RTP: set world/min/max; set cooldown with /st setcooldown if desired.
  5. Confirm with /st info <portal>.

Standard Portals

Default type. A standard portal teleports to its connected destination (or uses multi-destination routing).

/st settype <portal> standard

Requires a valid connection or routing setup:

/st connect <source> <target>

Or multi-destination routing:

/st setrouting <portal> fixed|random|weighted|permission
/st setdestinations <portal> dest1,dest2,...

Standard links are two-way unless you use a one-way type on the destination side.

One-Way Portals

Travel works from source to target, but players cannot enter from the one-way destination portal to return.

/st settype <portal> oneway

Typical setup:

  1. Create entrance and exit portals.
  2. Run /st connect entrance exit.
  3. Run /st settype exit oneway.

Players entering exit see the one-way blocked message. Players entering entrance still teleport to exit.

The management GUI type selector also offers One-Way (ONEWAY).

RTP Portals (Random Teleport)

Sends players to a random safe location. No second portal required.

/st settype <portal> rtp [world] [min] [max]
Parameter Default Description
world Current world Target world name
min 100 Minimum distance from world center
max 5000 Maximum distance from world center

Examples:

/st settype wilderness rtp
/st settype wilderness rtp world 500 10000
/st settype nether_rtp rtp world_nether 100 3000

How RTP works

  1. Player enters the portal region.
  2. Plugin picks a random coordinate in range.
  3. Chunks preload (see rtp.preload in config).
  4. Safety checks run; failed spots retry up to rtp.retry.max-attempts.
  5. Player teleports on success.

RTP rules

  • Disconnect the portal before switching an existing linked portal to RTP.
  • Range must be between 50 and 100,000 blocks.
  • min must be less than max.
  • Cooldown uses the per-portal value from /st setcooldown <portal> <seconds> (same as standard portals). There is no separate rtp.cooldown key in config.yml. Bypass: st.portal.bypass.cooldown.
  • Chunk preload / retry settings live under rtp.preload and rtp.retry in config.

Changing Types

Change Effect
To RTP Clears standard connection requirements; configure RTP range
To standard Clears RTP-specific settings
To one-way Keeps connection; blocks use from the one-way portal side

Use /st info <portal> to confirm the active type.

Next Steps

Defaults: Default config.yml · Config Reference

Still stuck? Ask about this page