RDT Setup
RaindropTowns combines towns, nations, claimed territory, banks, taxes, travel and Nexus encounters.Requirements
Install matching Suite artifacts on Paper or Folia. Release JARs are adapted to Java 17 bytecode; your Minecraft server may require a newer Java runtime. Use the compatibility guide to choose the server and Java combination.
Installation
Stop the server and back up the plugin data and database when upgrading. Put matching RCore and one runtime JAR for each selected plugin in plugins/. Remove replaced JARs from that directory, then start the server and check that the plugins enable. RDT uses the single RDT-1.0.0-ALPHA-Build-1.jar artifact.
Minimal configuration
Review plugins/RDT/config/config.yml, config/bank.yml, config/tax.yml and database/hibernate.properties. Review the generated facility and raid settings before opening those systems to players. Economy integrations are optional at startup but required for operations that charge money.
First task
Use /rt to open the town command area and follow the town menu with an authorized test player. Ordinary command permission, town membership, ownership and town-role authority are separate checks. Test territory interactions using an ordinary member before enabling public access.
Banks and travel
Choose the providers and currencies used by bank and tax settings. Verify a small deposit and withdrawal with test funds. Travel applies its configured safety, combat, warmup, cooldown and cancellation checks; town spawn access also needs membership and the relevant role.
Nexus raids and recovery
An authorized Mayor or Officer starts a raid at the physical Nexus. Review admitted difficulty and persistent-damage settings before starting an encounter. Reward claims and repair operations use durable records; recovery authority requires raindroptowns.admin.raids in addition to command gates. Inspect uncertain effects before reconciliation.
Verification and troubleshooting
Confirm town persistence after restart, member access, protection, travel and the bank flow your server uses. Network raid arrivals and cross-server travel need separate database and RCore bridge setup. Test these workflows on your actual server combination.