Plugins | ⚡ GNDisguise | BECOME SOMEONE ELSE! - NETWORK SUPPORT ⚡ [1.8, 1.11 - 1.16]

Versions

1.8
1.9
1.10
1.11
1.12
1.13
1.14
1.15
1.16

Source: https://www.spigotmc.org/resources/%E2%9A%A1-gndisguise-become-someone-else-network-support-%E2%9A%A1-1-8-1-11-1-16.69869/

Inspired by some of the most popular Minecraft Networks, GNDisguise is your go-to when it comes to protecting your content creators from getting targeted and/or stream sniped!

Plus it's an AWESOME perk for your Donators and Server Supporters!

DISGUISING / REVEALING / UNDISGUISING
Allows you to completely change how you appear to other players. Without modified clients players won't be able to tell the difference.

NAME PROTECTION
Allows you to add any name you wish and the plugin handles the rest. So in case the original owner of the name joins you won't have any problems.

DISGUISE PRESERVATION
Modifiable in settings, allows players to keep their disguise forever. (as long as the server is running)

AUTO REVEALING / UNDISGUISING
Modifiable in settings, allows you to set a timer to reveal disconnected players, so that the name won't be taken forever. When configuring it, the "for-how-long:" field is in seconds.

AUTO SKIN FETCHER
Allows you to get skin textures directly from Mojang, simply by putting the player's name in the configuration.

DISGUISE LOGGING
Allows you to easily check which player was disguised at specified time, so in case they were breaking the law while disguised, you can still punish them.

ON DISGUISE / ON REVEAL COMMANDS
Allows you expand the plugin further, ex. you can add a certain PEX group upon a player disguising in order to make the disguise more believable.

NETWORK SUPPORT
Allows your players to keep their disguises throughout the whole play session. Supports as many servers as your machine can handle.

NAMETAGEDIT SUPPORT
Your nametags will transfer over to your disguises.

TAB PLUGIN SUPPORT
In order to use GNDisguise with TAB plugin you will need to have PlaceholderAPI installed (TAB plugin's requirements), and in TAB Plugin's config.yml set customtabname: "%gndisguise_name%"
customtagname: "%gndisguise_name%"

change-nametag-prefix-suffix: true

unlimited-nametag-prefix-suffix-mode:
enabled: true

classic-vanilla-belowname:
enabled: false

FULLY CONFIGURABLE
Everything can be configured, including messages via messages.yml.

1. Download and extract
Download GNDisguise.zip and extract it, you will now have two JARs. GNDisguise.jar is the Spigot version, put it inside PLUGINS folder for each server you want GNDisguise to work in.

1.1 Dependencies
This plugin depends on ProtocolLib, when adding GNDisguise to your Spigot make sure you have ProtocolLib as well.

2. Place files
GNDisguise.jar is the Spigot version, put it inside PLUGINS folder for each server you want GNDisguise to work in.

GNDisguiseBungee.jar is the BungeeCord version, put it inside your PLUGINS folder in your BungeeCord server.

3. Restart
First restart your BungeeCord server, and then restart each Spigot server.

4. Configure
Move onto the next section for CONFIGURATION.

NETWORK CONFIGURATION
Keep this in mind to avoid confusion. Each server (BungeeCord included) needs to have its own unique port. Do not put ports that are already in use / can be in use (ex. 80, 8080). You should be able to just keep increasing the default port I put in (7722).

Example
First Spigot server will be on the default port 7722.
Second Spigot server will be on the port 7723.
Third Spigot server will be on the port 7724.
...

Default port for BungeeCord is 7790, you can leave this unchanged but no Spigot server can use this port.
In the GNBungee configuration you will need to list all used Spigot ports. 7722, 7723, 7724 in this case.

After configuring this, restart all the servers and you should be good to go. If you are having trouble PM me on-site and I'll try to help.

ADDING SKINS AND NAMES
To add a new skin & name entry you simply add the name to the CONFIG.yml.
Spoiler: EXAMPLE
If you know how to get the texture and signature you can add the "texture:" and "signature:" fields yourself, if you want the plugin to do it, do not add those two fields at all. Leave it as presented in the example.

THE REST
You can get a good idea of what a field does judging by its name, pretty self explanatory, however if you are confused about something PM me and I'll try to explain it to the best of my ability.