Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add per-server forwarding configuration in Velocity #453

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions docs/velocity/admin/getting-started/forwarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,20 @@ UUIDs and skins. Velocity supports three forwarding formats:

:::info

You may choose between only one of these forwarding formats. It is not currently possible to "mix
and match" forwarding modes or use all the forwarding formats together. In general, if you are
supporting clients using Minecraft 1.13 and newer only, use Velocity modern forwarding, else you
must use BungeeCord forwarding.
It is now possible to configure forwarding individually for each server.
In general, if you are supporting clients using Minecraft 1.13 and newer only, use Velocity modern forwarding.
For older versions, consider using BungeeGuard for added security; else you must use BungeeCord forwarding.

Example:

```toml
lobby = "127.0.0.1:30066"
```
Becomes:

```toml
lobby = { address = "127.0.0.1:30066", forwarding-mode = "MODERN" }
```

:::

Expand Down