Sonar Documentation
  • Become a Patreon
  • Join the Discord
  • Sonar
    • Welcome
    • Getting started
    • Supported versions
    • Translations
  • Administration
    • Commands and Permissions
    • Usage of MiniMessage
    • Configuring Sonar
      • General settings
      • Adjusting the attack tracker
      • Setting up a database
      • Configuring the verification
        • Using 1.20.5+ transfers
  • Development
    • Working with the API
    • Building
  • Contributing
    • Guidelines
    • Pull Requests
    • Bug Reports
    • Feature Requests
Powered by GitBook
On this page
  1. Administration
  2. Configuring Sonar
  3. Configuring the verification

Using 1.20.5+ transfers

Sonar includes a feature that allows players to be automatically transferred back to the origin server after successfully passing bot verification, introduced in Minecraft version 1.20.5.

PreviousConfiguring the verificationNextWorking with the API

Last updated 1 month ago

Set to true to enable the transfer feature. Ensure the feature is enabled in your server's configuration and consider adjusting login rate-limiting settings in Velocity or other proxies/plugins to avoid transfer issues. Default is false.

  • Set the login ratelimit in Velocity to 1000 (or disable it)—the BungeeCord and Bukkit equivalent is connection throttling.

  • Enable transfers in velocity.toml (Velocity); config.yml (BungeeCord); server.properties (Bukkit)

enabled: false

Specify the server IP or domain where players should be transferred after verification. This is the IP or domain used by players to connect to your server (e.g., play.my-server.com).

destination-host: play.my-server.com

Define the port for the origin server connection. The default is 25565, which is standard unless your server requires a different port.

destination-port: 25565

If your server allows Bedrock players to join via Geyser, make sure to set up for Geyser, so Bedrock players are redirected to the correct server.

TransferTool