Troubleshooting
Last updated Oct 28, 2026
Troubleshooting
Short fixes by symptom. Full install steps: Getting Started.
Won’t enable / red plugin
- Extract the
.jarfrom the ZIP (do not leave the ZIP inplugins/). - Install SoapsCommon.
- Full server restart (not
/reload). - Search
logs/latest.logforSoapsTeleporter/SoapsCommon.
No plugins/SoapsTeleporter/ folder means the plugin never enabled.
| Pattern | Likely cause |
|---|---|
| ST red, SoapsCommon green | Exception on enable — read the stack in the log |
| Both red | Jars still zipped or missing |
Core loop broken (no teleport)
/st info <portal>— enabled? connected or RTP configured?- Permissions:
st.portal.useandst.portal.<name>.usewhen per-portal permissions are on. - Conditions or costs blocking the player.
/st debug issuesand/st reloadself-test.- Overlapping regions are rejected on create; move or remove conflicts.
Warmup cancels on move. Bypass: st.portal.bypass.warmup.
Optional systems weird
| Symptom | Check |
|---|---|
| Money cost ignored | Vault + provider, economy.enabled, /st debug economy → Vault Economy Setup |
| Charged but no refund | payment-timing / refund-on-failure → Economy |
| Particles missing | particles.enabled, stand within nearby-player-radius (30), client particle setting |
| Lands in claims | WorldGuard/Lands hooks default off → WorldGuard Setup · Lands Setup |
| RTP does nothing | Type must be RTP (/st settype) → Want RTP portal |
/st manage is chat not GUI |
gui.enabled: false → Admin GUI |
After update
- Jar upgrade needs a full restart, not only
/st reload. - Live YAML is never overwritten by the jar. Compare: Config Reference.
- Owner checklist: Upgrading to 1.0.7.
Still stuck? Ask about this page