Local Nicknames

While there is a standard way for spigot plugins to make their set prefixes etc. available for MultiChat to use (Vault), there is no set way for them to do this with nicknames. As such, it is impossible for MultiChat to use the nicknames set by other plugins.

MultiChat hence features its own nickname command which can act as a replacement for the nickname command in plugins like essentials. This command is part of MultiChatBridge, the local part of MultiChat that runs on your spigot server rather than on bungeecord. This is because it is designed to emulate your normal nicknaming system.

---

The /nick command allows you to give a player a nickname. For example:

/nick Revilo410 Revilo

This will make my name in chat display as Revilo instead of Revilo410. To disable it we can use:

/nick Revilo410 off

Permission (to set your own nickname): multichatbridge.nick.self
(multichatsponge.nick.self for SPONGE)
Permission (to set others nicknames): multichatbridge.nick.others
(multichatsponge.nick.others for SPONGE)

Other permissions (SPIGOT ONLY):

multichatbridge.nick.special Ability to use special characters in nicknames (anything other than "^[a-zA-Z0-9&_]+$")

multichatbridge.nick.color/colour (Ability to use colour codes in nicknames) (&a &b &1 &2 etc.)

multichatbridge.nick.format (Ability to use format codes in nicknames) (&l &o etc.)

multichatbridge.nick.anylength (Allows nickname longer than 20 characters)

---

The /realname command allows a player to find the real name of someone with a nickname. It is currently only avaliable on SPIGOT (not Sponge).

/realname <nickname>

Permission: multichatbridge.realname

The realname command also supports partial matches (if you have the appropriate permission). These are by default limited to 10 results, but you can list ALL the results that match if you have the right permission. The reason this limit is in place by default is that the task could be computationally expensive, and you dont want players spamming /realname .* and listing everyone on your entire network's nickname...

multichatbridge.realname.partial (Permission to allow partial nicknames to be found for a /realname query)

multichatbridge.realname.nolimit (Allows ALL matches for a realname query to be shown instead of limit 10)

How do partial matches work in /realname?

Assume I have 3 players on my servers with nicknames, "CrafterBoy, MinerGirl and MinecraftPlayer123".

If I run /realname CrafterBoy it will return the exact match for this nickname.

If I run /realname Crafter then MultiChat will say no exact match could be found, but will list people with possible matches, in this case it will be 'CrafterBoy'.

If I run /realname m then the plugin will again say no exact matches could be found, but will list MinerGirl and MinecraftPlayer123 as partial matches because they both start with 'm'.

The way this search for partial matches works is as follows:

• MultiChat searches for any nicknames starting with the search term
• If no matches were found then MultiChat searches for nicknames containing the search term
• If still no match was found, then MultiChat will treat the search term as a regular expression (regex) and see if it finds anyone that way.

This means that the most relevant results will always be displayed. If you have players with nickname MinecraftPlayer123, and IPlayMinecraft, then doing /realname Minecraft will return the former. This makes the most sense! If you were searcing for the latter player, you would likely not search for "Minecraft" in /realname!