This repository has been archived by the owner on Dec 30, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
115 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
Configuring player information forwarding | ||
========================================= | ||
|
||
Velocity supports forwarding information about your players to your servers, such | ||
as IP addresses, UUIDs, and skins. Velocity supports two different methods for | ||
forwarding player information to your servers: | ||
|
||
* ``modern`` forwarding is a Velocity-native format. It forwards all player information | ||
in an efficient binary format and ensures that nobody tries to trick the server into | ||
impersonating your Velocity proxy. However, it is only available for Minecraft 1.13 | ||
or higher. | ||
* ``legacy`` forwarding is the player information forwarding protocol used by BungeeCord. | ||
This is extremely compatible across all Minecraft versions that Velocity supports, but | ||
requires proper configuration to ensure that nobody pretends to be your proxy by using | ||
a firewall or a plugin like IPWhitelist. | ||
|
||
Configuring modern forwarding | ||
----------------------------- | ||
|
||
Currently, no server implementations support Velocity's modern forwarding. | ||
|
||
Configuring legacy BungeeCord-compatible forwarding | ||
--------------------------------------------------- | ||
|
||
If you need to use legacy BungeeCord-compatible forwarding, simply set your ``player-info-forwarding`` | ||
setting in ``velocity.toml`` to ``legacy``. You will also need to make sure your server | ||
is properly configured to understand the data. | ||
|
||
.. caution:: Legacy BungeeCord-compatible forwarding allows anyone to pretend they are your proxy | ||
and allow them to log in under any username or IP address! You must make sure that | ||
you have a firewall set up on your servers or use a plugin such as `IPWhitelist <https://www.spigotmc.org/resources/ipwhitelist.61/>`_ | ||
to make sure your servers are protected. | ||
|
||
Spigot / Paper | ||
^^^^^^^^^^^^^^ | ||
|
||
To make Spigot or Paper understand the data forwarded from Velocity, set ``settings.bungeecord`` to | ||
``true`` in your ``spigot.yml`` and then reboot your server. | ||
|
||
Sponge | ||
^^^^^^ | ||
|
||
To configure Sponge to understand the data forwarded from Velocity, set ``modules.bungeecord`` to ``true`` | ||
and ``bungeecord.ip-forwarding`` to ``true`` in your ``config/sponge/global.conf`` file, and then restart | ||
your Sponge server. |