FAQ

Frequently Asked Questions (FAQ)

Q: Does this plugin handle the actual RTP math?

A: No. PixelRTPPool acts as a highly advanced, aesthetically pleasing bridge. It requires an actual teleportation plugin (like SimpleRTP, BetterRTP, or Essentials) to execute the /rtp command when the countdown finishes.

Q: Why do my MiniMessage gradients look weird?

A: Ensure your server is running on Paper and supports RGB colors. If you are using Geyser (Bedrock players), complex hex gradients may downgrade to standard colors depending on your Geyser configuration.

Q: Can players bypass the countdown by logging out and logging back in?

A: No. The CountdownManager immediately cancels and destroys the active task if a player disconnects. They will have to start over.

Troubleshooting

Issue: "WorldGuard Hook Failed" on startup.

Solution: You either do not have WorldGuard installed, or you are running an outdated version of WorldGuard that does not support the v7+ Session API.

Issue: The pool isn't doing anything when I walk in.

Solution:

1. Verify that your WorldGuard region is actually defined (/rg info).
2. Check that the region name in config.yml exactly matches the WorldGuard region name.
3. Ensure you have the pixelrtppool.use permission (operators have it by default).
4. Run /rtppool reload to ensure the config is actively loaded into memory.

Issue: The console spams errors when someone teleports.

Solution: This is almost always an issue with the underlying RTP plugin you are triggering, not PixelRTPPool. Test executing your configured teleport.command manually as a player. If it errors manually, PixelRTPPool cannot fix it.

Known Limitations

• Currently, cooldowns are global per player, meaning a player cannot jump into Pool A, and then immediately jump into Pool B if they share the same cooldown timeframe.
• World boundaries are not currently strictly enforced by PixelRTPPool; it assumes your underlying RTP plugin restricts dimensions appropriately.

---

🏡 Home | 📖 Read Next: Roadmap