Step 1
Put ProAntiTab in your Spigot plugins folder.

Step 2
Start your server and you're good to go! ^^

Step 1
Put ProAntiTab both in your Spigot and Bungeecord plugins folder.

Step 2
Go to your Bungeecord plugins folder, open the ProAntiTab/token.yml file, search for the token and copy this token. This token is the access token so that the Spigot server can communicate with the Bungeecord server afterwards and exchange information.
Here's an example of how this token looks like:

Code (YAML):

token : ID32-FNI3-3FOc-34FD

Step 3
Next, go to your Spigot plugins folder, open the ProAntiTab/config.yml and search for "handle-through-proxy".
This will look like this:

Code (YAML):

handle-through-proxy:
  enabled : false
  token : insert-token-of-proxy-here

Here you have to set the option "enabled" to true and insert the token you have copied from your Bungeecord server before.

Step 4
Start both servers and you're good to go! ^^

Small tip:
It's recommended to use a permission plugin like LuckPerms that is bound through a database both on Bungeecord and Spigot, in order to give the bypass permission for any blocked command through ProAntiTab.

Step 1
Put ProAntiTab both in your Spigot and Velocity plugins folder.

Step 2
Go to your Velocity plugins folder, open the ProAntiTab/token.yml file, search for the token and copy this token. This token is the access token so that the Spigot server can communicate with the Velocity server afterwards and exchange information.
Here's an example of how this token looks like:

Code (YAML):

token : ID32-FNI3-3FOc-34FD

Step 3
Next, go to your Spigot plugins folder, open the ProAntiTab/config.yml and search for "handle-through-proxy".
This will look like this:

Code (YAML):

handle-through-proxy:
  enabled : false
  token : insert-token-of-proxy-here

Here you have to set the option "enabled" to true and insert the token you have copied from your Velocity server before.

Step 4
Start both servers and you're good to go! ^^

Warning: When the black/whitelist has been changed or the player receives a bypass permission for a certain command and didn't rejoin the proxy afterwards, the player's auto-tab-completion won't update until then. The player has to rejoin the proxy to update the auto-tab-completion for the player.

Small tip:
It's recommended to use a permission plugin like LuckPerms that is bound through a database both on Velocity and Spigot, in order to give the bypass permission for any blocked command through ProAntiTab.