Install RTP
Start with a single backend. Add Velocity and Redis only if you need cross-server routing.
Single server
- Stop the server and place the RTP customer JAR in the backend plugins folder.
- Start the server once so the RTP folder and config are created.
- Add your AP key to
plugins/RTP/config.ymland restart. See Licensing. - Set SETTINGS.SINGLE-SERVER to true for direct local teleports.
- Review WORLD-SETTINGS and make sure each configured world exists.
Velocity / cross-server
- Install the RTP backend JAR on every backend that participates in RTP.
- Install the RTP Velocity companion JAR on each Velocity proxy used by the network.
- Set NETWORK.ENABLED to true and NETWORK.MODE to redis.
- Give every backend a unique NETWORK.SERVER-NAME matching your proxy configuration.
- Configure the same Redis service on all participating backends. For multi-proxy setups, also configure the public proxy host and port.
- Restart backends and proxies, then verify that server destinations appear in the RTP menu.
Database is optional
The RTP database section stores dimension unlock state across servers. Supported storage types in the provided config are MariaDB, MySQL, PostgreSQL and SQLite. SQLite is local only.