Dear all,

THIS IS AN ESSENTIAL UPDATE TO FIX A CRITICAL EXPLOIT

Apologies that it has been such a long time since you have heard from me. The global situation has obviously put us all into new situations and my usually very busy schedule has only become more busy over this past year. However, thanks to the fantastic team helping me with the plugin everything has still been running smoothly.

It has been brought to our attention that a critical exploit exists in the plugin which could put your servers at harm. As such you should update immediately to MultiChat v1.9.6 which I release here.

If you have any problems just pop in to our Discord server and someone from the MultiChat team will be happy to help you.

Thanks as always for using the plugin, I am always glad to see so many people making use of it.

Kind regards,
Revilo

Hi all,

Apologies. I don't like to release loads of updates in quick succession, but on the release of the previous 1.9.4 update we discovered a few more places where RGB colour codes were displayed incorrectly.

After a lot of testing I am quite confident that 1.9.5 should work with nearly every setup. Hopefully this means there will not be a need for a 1.9.6!

This update ensures that RGB colour codes used in displaynames and in chat formats work correctly, regardless of if the letters are lowercase or uppercase, and regardless of if they are in the &x&a&b&c&d&e&f format or the &#abcdef / &xabcdef formats.

If you do have any issues feel free to join us on the Discord server and someone will help you out ASAP!

~ Revilo

Hi all,

This is a very quick and small update that provides better RGB colour support for plugins that have not yet provided internal support for the new codes.

Essentially, this update will allow better compatibility with codes set in LuckPerms and many other plugins which might have not been displayed correctly before.

I am currently working on the next set of features for MultiChat and I hope to bring a bigger update in the not too distant future, keep your eyes peeled!

~ Revilo

Hi everyone,

With the release of Minecraft 1.16 I am sure everyone is very excited to use the new RGB colour codes which are perhaps one of the biggest changes to Minecraft chat ever!

As such, it was only right to release a prompt update to MultiChat to bring full support for RGB colour codes. Many plugins have developed their own version of using the codes, so we are proud to support the main 3 ways in use today:

• &#abcdef
• &xabcdef
• &x&a&b&c&d&e&f

By doing this we hope to maintain compatibility with as many plugins as possible!

Additionally, MultiChat has full support for your legacy (pre-1.16) servers, we have developed our own methods for approximating the new RGB codes to their nearest old style code so that even your older servers can still function in the same way. If you have a RGB code in your nickname, then the older servers will just turn it into the nearest code they can support while you are on that server!

This update to MultiChat also includes better support for PremiumVanish (silent join when vanished) and more config options for the databases in localconfig.yml including using SSL etc.

For full instructions to update successfully please see this page.

For a full list of changes see the changelog.

Thanks as always for using MultiChat, I hope to bring more updates soon now that I am less busy and the Summer holidays are approaching. If you like the plugin please leave a review to help others find it

~ Revilo

Hello everyone,

***
Firstly, a quick notice from me. I would be extremely grateful if you could take part in this short survey about what features YOU would like to see in MultiChat v2.0: https://forms.gle/TcbbaNXtbR5XscXUA
***

Apologies for yet another small MultiChat update, but there were a few issues I needed to resolve to help make MultiChat 1.9 as stable as possible for you while I develop v2.0.

---

Changelog:

• Added support for PremiumVanish on the /msg and /staff commands
• Added permissions for individual types of format codes in nicknames (multichatlocal.nick.format.bold/italic/underline/strikethrough/obfuscated/reset) (multichatlocal.nick.format still grants permissions to ALL types of format codes)
• Display command now respects no_global list
• Fixed more null pointer exceptions
• Fixed missing SLF4J dependency on some systems
• Fixed bug where casts would sometimes have an extra space on the end of the format

---

This update adds support for PremiumVanish! It was a popular requested feature, so I thought that I might as well add it in to tide you over while I work on the bigger features for the next version. Why PremiumVanish? It is probably the most popular vanish plugin that is BUNGEECORD compatible. I cannot support plugins like SuperVanish because it is not compatible with bungee.

This update also adds some more refined permissions for format codes in nicknames so you can let your players use the bold permission, but not underlined for example.

If you want to make use of the newer features please see: https://github.com/MultiChat/Development/wiki/Updates#updating-to-v192-from-v191

Otherwise your current config file will continue to work (It will just be missing the premiumvanish settings).

Thanks as always for using MultiChat, and let me know if you have any issues and I will be more than happy to help you resolve them!

~ Revilo

Hi all,

This is a very small update that fixes an error that was occuring when the server shuts down in v1.9.

The database name in the onDisable function was incorrect so was throwing an error when disconnecting.

This has now been fixed.

Thanks for using the plugin, and if you ever have any issues then use our GitHub or Discord to report them and I will be more than happy to fix it for you!

~ Revilo

Hello everyone,

It is with great pleasure that I can announce the release of MultiChat v1.9. However, I need to start off with a warning...

*** WARNING: IMPORTANT NOTICE ***

FOLLOW THE INSTRUCTIONS FOUND HERE BEFORE UPDATING: https://github.com/MultiChat/Development/wiki/Updates#updating-to-v19-from-v181

If you do not follow these instructions carefully when updating, you will prevent MultiChat from working on your server! MultiChat 1.9 is essentially the first half of the 2.0 update for the plugin! In this update I have completely re-coded the Spigot and Sponge parts of the plugin. In the final release of v2.0 I will complete the re-code of the Proxy Bungeecord part of the plugin.

This means that there are a few steps you need to take to update safely from v1.8 to v1.9. These steps are documented in detail on our wiki here: https://github.com/MultiChat/Development/wiki/Updates#updating-to-v19-from-v181

If you do not follow these steps then the plugin will not keep working as you expect! Some permissions have been renamed, some commands have slightly changed, and the config files have moved around a tiny bit.

*** END OF NOTICE ***

MultiChat 1.9 combines MultiChatSpigot and MultiChatSponge into a unified codebase / API known as MultiChatLocal. This not only allows for better maintenance of Spigot and Sponge, but it ensures consistency between the two platforms and allows for easier expansion to new platforms in the future.

All permissions starting with multichatspigot or multichatsponge are now called multichatlocal, and the old multichatspigot and multichatsponge commands are also called multichatlocal.

Additionally, the spigotconfig.yml and multichatsponge.yml config files are now called localconfig.yml. Essentially, this update unifies the two platforms with identical features.

The full changelog can be found here: https://github.com/MultiChat/Development/wiki/Changelog but the main new features are as follows:

• Databases are now optimised using connection pools
• Spigot and Sponge have both been upgraded and now share the exact same features.
• We now support plugins such as Towny and many other features such as the local chat ranges in EssentialsX! There is a new section in the localconfig.yml which lets you match different types of chat formats using regular expressions and send them to specified channels.
• Sponge now has basic support for Magibridge in the same way Spigot supports DiscordSRV.
• Sponge now has a reload command and supports /sponge plugins reload
• You can now use MultiChat placeholders in other Sponge plugins' chat formats like {multichat_nickname} in Nucleus chat formats!
• You can now specify permission based chat control rules in the chatcontrol.yml file!
• You can now customise the regular expression used for finding links in the link control section
• Added a nicer error message when a regular expression was parsed incorrectly in /pxe and /mce
• Fixed an issue in one of the Post Chat Events triggered by MultiChat for logging in other plugins
• Fixed the errors received in client side consoles as a result of plugin messages not being marked as completed
• Fixed several null pointer exceptions
• LOADS of backend optimisations

This update has lots of new features, but the main focus of the update was to unify the codebase of Spigot and Sponge to promote better maintainability in the future, and facilitate a smooth update to MultiChat 2.0 coming soon!

MultiChat 1.9 is a "stepping stone" to the 2.0 update. v2.0 will feature full SQL support across all of MultiChat and add customisable chat channels and much much more!

As with any new update, there are like to be issues! If you find any then please take a look at our new Troubleshooting page on the wiki (it is only in Beta and is not yet 100% complete): https://github.com/MultiChat/Development/wiki/Troubleshooting

I advise everyone to join our discord for fast support: https://discord.gg/PVreERC

If you find any bugs in the plugin, you can report them on discord or using the GitHub issues tracker: https://github.com/MultiChat/Development/issues

This is a reminder please to NOT use reviews for feature requests, bug reports or anything along those lines! If you contact the Discord or use the GitHub issues tracker then we will be able to come up with a solution to your problem

However, if you do find the plugin useful, then I would really appreciate if you could leave us a review to help other people also find the plugin!

Thank you as always for using MultiChat, it is very positive to see so many new people using the plugin each day. I will be working hard on v2.0 ready to take the plugin to the next level! If you have any questions or suggestions then just visit our Discord!

~ Revilo

Dear all,

As with any major update there are small bugs to iron out. I am pleased to say that v1.8 has seemed to be working well for everyone, however I was made aware of two things. This means that you need to update to v1.8.1 as soon as possible.

1. There is a security flaw in v1.8 which could result in some of your MultiChat data being lost if you had a particularly malicious player. Considering I myself have studied cyber security in depth, the fact I made this error is something I am horrified about. It was a complete moment of stupidity. It will not necessarily affect your day to day use of the plugin, but PLEASE update as soon as possible to remove this vulnerability.

2. There is another small bug where if you regularly use nickname prefixes (for example the ~ character), it is being displayed in front of everyone's name even if they don't have a nickname. This has been fixed now.

IF YOU ARE UPDATING FROM v1.7.5 OR OLDER, THEN PLEASE READ THIS POST: https://www.spigotmc.org/resources/multichat.26204/update?update=327096

Apologies for these issues, it was inevitable that there would be a v1.8.1 soon anyway, I am confident that 1.8.1 is now secure.

Thanks as always for using the plugin, and I hope to get working on 1.9 soon!

~ Revilo

Hello everyone,

It is with great pleasure that I bring you MultiChat 1.8 - which I like to call the "Unity" update.

I call it this because it is an update that does more to bring all your servers together and makes MultiChat better than it ever has been before.

Firstly, this update is the first step towards full MultiChat support for MySQL and SQLite. It would be too dramatic to go from no SQL support to suddenly using it for everything, so this update implements support for MySQL and SQLite on the MultiChatSpigot and MultiChatSponge parts of the plugin. This means that your nicknames can now be synced across all your servers if you wish using MySQL, this includes between Spigot and Sponge servers!

The remainder of the MySQL and SQLite support for the rest of the plugin should follow in v1.9. This is the "trial" so to say, to iron out any creases before we roll it out everywhere.

For a very long time, Sponge support has lagged behind Spigot support in the plugin, and with this update I end this inequality! All of the previously implemented nickname features present on Spigot are now present on Sponge too. This update essentially brings Sponge up to speed with the Spigot version of the plugin to make sure all your servers work together seamlessly, especially now nicknames can be synced between them!

There are a host of new features available in this update and I present the changelog below:

• Added support for MySQL and SQLite for MultiChatSpigot AND MultiChatSponge
• Added MultiChat Database Manager to be used across all parts of the plugin
  
• Nicknames can be synced across multiple Spigot and Sponge servers using a MySQL database
• Added migration command to convert from file based storage to SQL
• Added "Proxy Execute" function that allows Proxy commands to be executed from Spigot & Sponge
• Added privacy options to config.yml to disable logging for private messages, staff & group chat
• Added config option to allow new player welcome messages to be displayed privately or broadcast or both
• Added minimum length for nicknames in both Spigot and Sponge
• Added permission to bypass nickname blacklist (multichatspigot.nick.blacklist/multichatsponge.nick.blacklist)
• Improved the local and global commands to allow direct messaging with /global [message] etc.
• Can now add aliases for local and global in the config.yml like /g and /l
• Re-built file based nickname storage in Sponge
• Added more advanced name management system to Sponge (the same once that is used in Spigot)
• Added colour and format permissions to Sponge nickname command
• Added special characters permission to Sponge nickname command
• Added max length to Sponge nicknames and override permission
• Added realname command to Sponge
• Added username command to Sponge
• Added French Translation for all config files (Thanks to Nogapra! If any of the translations are wrong then it is my fault as I had to make some last minute tweaks!)
  
• Fixed an issue where chat control settings, mute, freeze etc. would not apply to local chat
• Fixed a potential deadlock that could occur if lots of players were online at once
• Fixed an issue that stopped the MultiChat local format working when no_global was enabled
• Fixed a bug that prevented the MultiChatExecute command working with Sponge
• Many other minor bug fixes

If this update has not brought the feature you were looking for, then feel free to contact me on our Discord, or open up an issue on GitHub for it! Chances are it is already on my to-do list, and I hope that 1.9 brings full MySQL support across the board, as well as a possible overhaul of chat channels etc. to give you the ability to define your own channels and more.

Now for the important bit. The update instructions!

IF YOU DO NOT FOLLOW THESE INSTRUCTIONS CAREFULLY THEN YOU RISK CORRUPTING YOUR FILES

Firstly, as with any update, BACKUP all your files! I cannot stress this enough. Particularly your nickname data files if you intend to migrate to SQL... Just in case anything happens to go wrong! I have tested everything a lot, and so has the MultiChat community, but there will always be bugs introduced with new features.

The Wiki will now be the place to go for update instructions, so please follow this link to get to the 1.8 update guidance: https://github.com/MultiChat/Development/wiki/Updates#updating-to-v18-from-v175

Other than that, I just want to wish everyone well in these strange and unprecedented times. I hope that you are your familes are healthy. Make the most of this infinite online community to maintain contact with your friends across the world.

I am of course, still as busy as always, but I will try to make the most of being stuck at home during this situation, and who knows, v1.9 may come sooner than expected.

I am trying to keep on top of all the support messages coming through, but MultiChat has gone from being a small staff chat plugin for 1 server, to being used on over 300 bungeecord networks controlling over 2000 individual spigot / sponge servers. I am happy that so many of you are making use of the plugin, but unfortunately I am still only one (very busy) person. So I thank the community for helping me out with providing support where required, particularly stw222 who has served as the Discord "community support" guru lately! If anyone else wants to be listed as a "community support" helper on discord, then all you need to do is keep being active on there and helping out as many people as you can. I will notice, that I can guarantee.

Thanks as always for using MultiChat, and I will give you as many more features and updates as I can as soon as possible!

~ Revilo

Hi everyone,

Firstly you have my apologies for not being active in Discord, I could give you a million excuses but I don't see much point. The short version is that I have just had so much on my plate and could not find the time to be checking it regularly. For this you have my apologies as I hate to let you guys down. But I would like to say a massive thank you as always to the great community who always step up to help others when they are having issues.

Secondly, as far as I know, the old version 1.7.4 was still working fine with MC 1.15, but just to make sure it is all running smoothly I have now released version 1.7.5 which is 100% compatible with the latest MC versions. It also has a couple of minor tweaks to fix some errors etc.

I am hoping to be able to spend more time working on the plugin again soon, but I just can't make any promises of when as it is unfair on you guys. I will do my best, that I promise!

Thank you for using the plugin, and I am really sorry about the lack of support from me. I am really happy to see the number of people who use the plugin and I am so glad that I have been able to help you all with it. It started off as a very small project, and has now grown to more. I will always maintain the plugin so you guys are not left with something that doesn't work. It will just be a bit slow for me to add the new features right now. Hopefully that will change soon!

Many thanks,
Revilo

Hello everyone,

Firstly, my apologies for the delayed responses to all your questions recently! It has been an extremely busy time for me finishing my university studies. However; I now have some more time, and I have updated the plugin to fix the issue that prevented it from working with Minecraft 1.14 (as far as I can tell).

This update also includes some other features I was working on before hand!

• Nickname max length configurable in spigot config (allows better compatibility with Minecraft 1.7 where there is a limit on display name length)
  
• Plugin messaging channels renamed to be 1.7 compatible
• Fixed an issue which prevented display names being fetched when not using Vault
• Plugin now works with Minecraft 1.14 API
• Server name for the %SERVER% placeholder must now be specified in the spigotconfig.yml. This is because 1.14 has removed the server-name option from the properties file!
  
• Added bstats metrics

So the long and short of this update is, MultiChat should now be compatible all the way from 1.7-1.14!

It is best to let MultiChat re-generate a new spgiotconfig.yml file to get all the new options. But otherwise you need to add the "server_name" field to configure this aspect of the plugin. The other new options in the spigotconfig.yml are "nickname_length_limit" (The maximum length for nicknames) which defaults to 20, and "nickname_length_limit_formatting" (Should formatting codes such as "&3" be counted in the length of the nickname?) which defaults to false.

I will update the wiki accordingly ASAP.

If you have any questions please let me know and I will get back to you ASAP. And if you have any issues with the plugin and have already reported them please know I will get to those too! I have been busy but am doing my best to catch up now!

As always thanks for using MultiChat!

~ Revilo

Hi All,

As you can see, my "hopefully 1.7.2 will be the last update before 1.8" didn't last very long!

This update is only relevant if you are using Sponge, so do not worry about updating otherwise. It fixes an issue that caused all chat colours to disappear from the global chat messages. This was due to a bug in the code that handled PlaceholderAPI placeholders.

The update also includes some corrections to the French translations from Nogapra (thanks again!). Just delete the files in the translations directory for new ones to be generated.

Thanks!

~Revilo

Hello everyone!

This is (hopefully) the last 1.7 update before version 1.8. The purpose of this update is to fix some important bugs, as well as provide some much requested features for things like the nickname system.

Firstly, the bug fixes:

• Fixed an issue that caused the translations directory to be created incorrectly on Unix systems
• Fixed a bug that prevented freezechat from blocking messages
• Added better error handling for malformed regex in realname and username commands

Now for the nicknames improvements (Spigot & Sponge):

• Checks are now properly in place to prevent duplication of nicknames
• Added a feature to prevent players impersonating other peoples real names with their nickname. A permission exists (multichatspigot/multichatsponge.nick.impersonate) to allow players to overcome this.
• Added an option to specify a "prefix" for nicknames, like in the spigot plugin "Essentials". This could be used to make all nicknames have the "~" character in front of them to differentiate them from real names.
• Added a nickname black list which works using regular expressions to prevent players using specific names.

Other new features:

• There is now an option in the chatcontrol.yml file to prevent players sending links in chat unless they have the multichat.chat.link permission node.
• There are more helpful debug messages for troubleshooting issues with chat messages not correctly displaying.

HOW TO UPDATE SAFELY AND CORRECTLY:

• Always make a backup of your MultiChat plugin folders and config files before updating in case an error occurs!
• The easiest way to update is to delete all your current config files and let new ones be regenerated. However; this loses your settings.
• If you want to keep your current config files then that is fine, follow these steps to update safely from 1.7.1 to 1.7.2!

1. Add the following to the bottom of your chatcontrol.yml file:

2. Add the following to the bottom of your spigotconfig.yml or multichatsponge.yml files:

After performing these steps, your plugin should work as if you had deleted the config files to generate fresh ones. It is acceptable (but not recommended) to change the config version (the bit that says DO NOT EDIT!) from 1.7.1 to 1.7.2 in order to stop the plugin complaining about an outdated config on startup. However; it is always safest to freshly regenerate the config!

As of version 1.8, I hope to have a system that will automatically update config files (this has been requested by a few different people).

I hope that this version works well for you and adds stability to your servers! Unless any major errors arise then this will be the last version before 1.8.

As always thank you for using MultiChat, and if you have any issues then please let me know! (Either on discord, by private message on here, on github, or literally anywhere other than the reviews section as this is not how bug reports should be submitted!)

~ Revilo

Hi all,

This is just a brief update to bring a few "extras" to the plugin, and to fix a bug with Sponge.

CHANGELOG:

• Fixed a bug that prevented Sponge from saving nickname data persistently
  
• Added "MultiChat Placeholders" (more below)
• Added more debug messages
• Added French translations by Nogapra (thank you for your work!)
• Added a /username command to go along with the /realname command

MultiChat placeholders allow you to define new placeholders that can be used in other plugins such as EssentialsChat. This also allows you to use PlaceholderAPI placeholders in plugins that it might not have been possible before (like EssentialsChat).

To take advantage of these, re-generate your spigotconfig.yml file, or add the following to the bottom:

The French translations are for the messages.yml file and the joinmessages.yml file and were written by Nogapra. If you would like to contribute your translations for other languages then please contact me and I would be very happy to add them to the plugin!

The /username command functions like the /realname command, except it allows you to look up the username of a player, as opposed to their nickname. The permissions mirror those for /realname, except instead of multichatspigot.realname, it is multichatspigot.username. The same subpermissions like multichatspigot.username.partial exist. See the wiki for the full permissions list as usual.

I am busy with university at the moment but am working on more features for the plugin and will update as soon as I can

Thanks for using MultiChat!

~ Revilo

It is with great pleasure that I present the most long-awaited update to MultiChat yet...

This version of MultiChat goes beyond the capabilities of any * bungeecord chat management plugin to date. ( *As far as I have ever seen) Version 1.7 adds compatibility for local spigot chat formatting plugins. This means that MultiChat now supports the following:

• PlaceholderAPI
  
• DiscordSRV
• Most factions/clans plugins
• Towny prefixesMessage translation plugins
• MultiVerse chat functionality
• VanishNoPacket chat functionality
• EssentialsChat functionality
• And more...

This solves the long standing issue with bungeecord chatting plugins where they would cancel the chat event, preventing the messages ever reaching spigot plugins. For MultiChat, this is no longer the case. Messages are formatted by all your local plugins in addition to by MultiChat, resulting in a huge range of new opportunities.

In addition to this, there are other new features. Please read this post very carefully to ensure your update process goes smoothly!

Full Changelog:
https://github.com/MultiChat/Development/wiki/Changelog

1. Backup your plugin files carefully
2. Make sure MultiChat 1.7 is installed on ALL your servers
   
3. Remove your current config files so that the newest versions can be generated
4. If you use spigot, copy the nicknames data file from the MultiChatBridge folder to a new folder called MultiChatSpigot. MultiChatBridge is no longer used and can be deleted.
5. Replace all permissions starting with "multichatbridge" with "multichatspigot".

Ensure all your permissions are up-to-date using the latest information: https://github.com/MultiChat/Development/wiki/Permissions

Ensure your configuration files are up-to-date using the latest information:
https://github.com/MultiChat/Development/wiki/Configuration

Most notable changes include:

• Player meta updates immediately (i.e. when you update a players prefix)
• Local chat has been completely re-designed! See: https://github.com/MultiChat/Development/wiki/Global-Chat for the latest information.
• Added a "first-join" welcome message
• Added channel command to manage chat channels (local and global channels)

***

Despite all these new features, there is ONE major feature which is missing. Many people have requested support for SQLite and MySQL databases. This is 100% something I agree with, and it WILL be coming soon. They are likely to be the focus point of Multichat v1.8. It is not a trivial change and will take time. It unlocks new opportunities for the plugin so I need to decide that best way to implement the change.

The reason it was not the focus for 1.7 is that I believe supporting local chat plugins is far more important and will let people use the plugin for a whole new range of use cases. 1.8 will be used to refine the functionality developed so far, and if all goes to plan make sure that data is stored in databases efficiently so your files do not get too large.

***

Thank you all for your continued support to the plugin. I have invested MANY hours into this update. I am a busy university student so cannot always make time to work on MultiChat as much as I'd like. If you ever have any issues with the plugin just let me know in the discussion here, on the github issues pages, or in our discord. DO NOT USE THE REVIEWS FOR BUG REPORTS, that is not what they are for and it doesn't help anyone!

That said, if you do like the plugin please leave us a review! Additionally, there is a donations link for the plugin if anyone ever wishes to make a contribution. I don't like to push for donations, but even the smallest amount will buy me a coffee to help me get through late night development! ( https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=P3YFE76932TXJ) ( https://www.patreon.com/multichat)

I am excited to push the bounds of bungeecord plugins and hope that you all enjoy using the new update.

Revilo410 - Author of MultiChat

Hello everyone!

As lots of you know, I am very busy at the moment with university amongst other things, but I wanted to address a few minor issues that had been brought up about the plugin. Work will resume on the 1.7 update as soon as I physically have the time.

CHANGELOG:

• Staff list now only shows worlds where a staff member is online
• Added the %WORLD% placeholder for message formats
• Added a config option to disable the /msg toggle feature which caused an issue with some muting plugins
• Re-designed all the console logging messages
• Made console logging formats customisable in messages.yml

I know this is not a feature-heavy update, but I hope it will keep the plugin ticking over nicely until 1.7.

If you have any bugs to report, or features to suggest for 1.7 (or possibly a 1.6.3) then please let me know

Thanks for using the plugin!

~ Revilo

Hello everyone,

Sorry for the late release (I said this would be out last weekend), I had too much uni work to catch up on to get it done any sooner.

This is an update with some minor bug fixes for 1.6, BUT it also introduces some changes and new features.

That means read this post carefully to make sure your update process goes smoothly!

Change Log:

• Fixed a minor bug in nickname permissions [spigot only]
  
• The /realname command can now find partial matches (and even works with regex) [spigot only]
  
• The permissions for nicknames have been improved and split up. This means your old permissions for nicknames may no longer be correct!!! SEE UPDATED PERMISSIONS LIST BELOW...
  
• Private messaging can now be used from the console! (This lets you send messages to your players as a result of regex matches etc. )
• Introduction of the "multichat execute" command which allows execution of commands across your entire network.
• Introduces some custom events for other plugins to hook into - these are targeted towards IRC plugins. (PurpleBungeeIRC mainly!)

Updated permission node list:

(The wiki will be updated to contain more detailed descriptions of each node shortly! This list is just provided to identify the new nodes!)

- multichat.group
- multichat.group.create
- multichat.staff.list
- multichat.staff.listgroups
- multichat.staff.mod
- multichat.staff.spy
- multichat.staff.admin
- multichat.admin
- multichat.staff.display
- multichat.chat.mode
- multichat.chat.color/colour
- multichat.chat.msg
- multichat.chat.freeze
- multichat.chat.always
- multichat.staff
- multichat.chat.helpme
- multichat.staff.silentjoin
- multichat.chat.clear
- multichat.chat.clear.all
- multichat.chat.clear.server
- multichat.chat.clear.global
- multichat.announce
- multichat.bulletin
- multichat.cast.<CAST NAME>
- multichat.cast.admin
- multichatbridge.nick.others [SPIGOT]
- multichatsponge.nick.others [SPONGE]
- multichatbridge.nick.self [SPIGOT]
- multichatsponge.nick.self [SPONGE]
- multichat.staff.spy.bypass
- multichatbridge.realname [SPIGOT]
- multichatbridge.nick.special (Ability to use special characters in nicknames (anything other than "^[a-zA-Z0-9&_]+$")) [SPIGOT]
- multichatbridge.nick.color/colour (Ability to use colour codes in nicknames) (&a &b &1 &2 etc.) [SPIGOT]
- multichatbridge.nick.format (Ability to use format codes in nicknames) (&l &o etc.) [SPIGOT]
- multichat.bypass (Ability to use the /multichatbypass command)
- multichat.mute (Ability to use /mute <player>)
- multichat.mute.bypass (Prevents player from being muted)
- multichat.ignore (Ability to use /ignore <player>)
- multichat.ignore.bypass (Prevents player from being ignored)
- multichat.spam.bypass (Prevents anti-spam triggering for this player)
- multichatbridge.nick.anylength (Allows nickname longer than 20 characters) [SPIGOT]
- multichatbridge.realname.partial (Allows partial nicknames to be found for a /realname query) [SPIGOT]
- multichatbridge.realname.nolimit (Allows ALL matches for a realname query to be shown instead of limit 10) [SPIGOT]
- multichat.execute (Allows the player to use the multichat execute command)

Realname Command:

The realname command now supports partial matches (if you have the permission above).

These are by default limited to 10 results, but you can list ALL the results that match if you have the right permission also from above. 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...

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:

1. MultiChat searches for any nicknames starting with the search term
2. If no matches were found then MultiChat searches for nicknames containing the search term
3. 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 ! Its not perfect, but it is better than only having exact matches!

MultiChat Excecute Command

This command is included just because so many people have asked for it over time. It isn't strictly chat related, however it is simple to implement. This command allows you to execute a command across all of your servers.

So for example, if you want to kick everyone on your network, you can do /mce kickall. This will make all your server consoles execute the /kickall command.

It is simple, but can be used for a few useful tasks.

I have added some more powerful options to this command as well though! For example, you can limit what servers the command executes on using regular expressions. Simply use the -s flag.

For example /mce -s minigames.* broadcast You are on a minigames server! Will execute the broadcast command on all servers whose names start with "minigames".

There is also a function to cause players to execute the command instead of the console. This is using the -p flag. Like the -s flag you provide it with a regex to decide what players will use the command. /mce -p .* spawn will cause all your players to execute the /spawn command.

If you dont understand regular expressions (regex), just Google it!

Custom Events

MultiChat now provides custom events for use by other plugins. I WILL BE EXPANDING THESE EVENTS TO INCLUDE MORE FUNCTIONS IN THE FUTURE. This update only provides "Post Message Events", i.e. events with details of a messag that has ALREADY been sent on MultiChat. This means it is useful for IRC plugins etc, but they cannot be used to change the messages multichat sends. This functionality will come in later updates.

You can see the events here: https://github.com/MultiChat/Develo...java/xyz/olivermartin/multichat/bungee/events

If you have any questions please contact me on this site, in the github issues, in the plugin discussion or on discord. Discord will probably get you the fastest answer!

---

That is all for now! As always please take backups before updating. Please note to add aliases for the multichat execute command you will need to delete your config.yml file and let multichat re-generate it!

If you have any bugs (which is always likely in new updates), let me know ASAP.

Thanks for using MultiChat, and I hope this update is useful!
Revilo

P.S.

I haven't forgotten about 1.7! This is the update to finally go beyond previous bungeecord chat plugins and actually work properly alongside spigot chat plugins which add custom tags, send your messages to discord, etc. etc.

I am very busy at the moment, but I do have it in the back of my mind to get done. I will post progress in the discord #updates channel.

Hello everyone,

It is with great pleasure that I can now release MultiChat v1.6! This has been in the works for a while, and includes many frequently requested features.

Firstly, here is the change log!

• A huge number of back-end optimisations, bug fixes, and code refactoring.
• A much more powerful nicknaming system (for Spigot only) including: /realname can now be used on offline players, /realname now works regardless of format codes, nicknames are more compatible with other plugins, a permission node to prevent players using format codes in their nicknames and more...
• All plugin messages are now completely customisable! This means MultiChat can now be used in any language.
• Improved configuration files
• /staff can now be disabled via a config option
• /multichat reload now reloads ALL config options including command aliases
• Debug mode added for better plugin troubleshooting
• Placeholders added for prefix, suffix and nickname
• You can now stop MultiChat setting the displayname of players via config option (BungeeCord, Spigot and Sponge)
  
• You can now customise the format MultiChat uses to set the display name (BungeeCord, Spigot and Sponge)
  
• Added MultiChat BYPASS command - This is a "quick fix" to allow you to send chat directly to the spigot chat stream, and not have it handled by multichat. This can be used to type into plugins such as quests which require access to chat events. A better solution will be implemented in future updates.
  
• Chat Control rules to allow find and replace of phrases via regex
• Chat Control rules to trigger commands on regex match
• A light-weight mute command for people without a dedicated bungeecord ban management plugin. This can be configured to prevent players using global chat, private messages, group chats, helpme, etc.
• A full fledged /ignore command to allow players to ignore each others messages with many config options!
• A basic Anti-Spam feature for people without a dedicated plugin to do so. It also has many config options to customise it to work how you want.

Yes this is a feature packed version, however; this means caution must be taken when updating!

To safely update your plugin please follow this guide:

1. BACKUP all your MultiChat files. This includes nickname data from MultiChatBridge.
2. Delete your config files (config.yml and joinmessages.yml) to let MultiChat regenerate the new ones. (This is not strictly required, the plugin is designed to work with the old ones as well, HOWEVER; this is not supported and future versions will not function with the old config files)
3. Install the new MultiChat 1.6 jar on ALL your servers. Older versions of MultiChatBridge are not compatible with MultiChat 1.6 due to changes in the messaging system.
4. If you removed your old config files, then copy over your settings into the new files to make sure the plugin works correctly for you. Remember to do /multichat reload.
5. Because this is a large update there are likely to be bugs despite my own testing, and testing on real servers. Please report them on the GitHub issues page. ( https://github.com/MultiChat/Development/issues )
6. DO NOT POST BUG REPORTS IN THE REVIEWS SECTION, if you speak to me then I will fix it for you (if I can!). Leaving a bad review is unlikely to make me want to help you! Especially since most bug reports are in fact not even bugs with the plugin.

This was used to post many updates while I was in the process of developing MultiChat 1.6. You can come here for fast support, and also be kept up to date on the latest plugin news.

There are of course some new permissions!

The wiki ( https://github.com/MultiChat/Development/wiki) will be updated soon to include all the new 1.6 information, but at the moment it is still out of date! If you have any questions about how features of the plugin work, please just message me on this website, on the discord, or go to the discussion section of the plugin. You can also use the GitHub issues page if you feel it is appropriate. Again, don't leave it in a review!

So... Even though this update has a LOT of new stuff in it, there are still things missing right?

Yes.

Definitely.

A major issue with all the BungeeCord chatting plugins I have ever used, MultiChat included, is that they cancel the chat event on the bungeecord side. This prevents spigot plugins like DiscordSRV from actually ever seeing the chat, and hence they are incompatible. There is no easy way to fix this due to the nature of BungeeCord and Spigot....

HOWEVER; I have a few ideas, and the focus of the next update will be to try and fix this issue. Will it be 1.7? I don't know, it could be called 2.0 instead if I think the plugin has evolved enough. I have a lot of other requested features which I will be working into the next updates.

Another popular request was SQL. SQLite and MySQL are on my list. Unfortunately it is no simple change, and requires a lot of re-coding to how the plugin stores and manages data. This will also be a focus of future updates, but I confess I am not looking forward to trying to refactor all that code...

The state of the code before version 1.6 was appaling, I started the plugin when I could barely program in Java. This update has not only added features for you to use, its added features in the code for me to use. I have tidied it up a LOT, and this will make future updates much easier. Its still not where I'd like it to be though, so in these future updates I will be spending more time to make the plugin's code a lot easier to manage, and generally more efficient.

I apologise for the very very long update message, but I wanted to keep everyone in the loop with the plans for the plugin, and make sure I covered all of the changes.

Again, if you have any issues with the update please let me know, I'm sure a 1.6.1 will be on the horizon to fix any small bugs I missed.

Thank you as ever for using MultiChat, and I hope to continue to provide a top-notch bungeecord chat management system with the most advanced features you can find!

~ Revilo

Hello everyone,

This is a small update which fixes issues with Sponge on the previous 1.5.1 version.

Additionally there has been a lot of code refactoring and back-end improvements. This is in preparation for the upcoming version 1.6 which will include lots of new features like /ignore. This is part of my plan to produce smaller releases first, rather than one HUGE 2.0 release.

Keep your eyes peeled for the 1.6 update, COMING SOON

Hello everyone,

This is a quick update which makes MultiChat fully compatible with version 1.13!

As briefly noted in the dicussions section I am sorry for the delay in version 2.0. Every time I get some free time it is fleeting, I begin to make a start but am prevented from finishing. I promise I will finish it eventually, I just can't say when I'll have the time yet. I am going into my last year of university and am attending the European and World championships for my sport this year.

I hope this update suffices for the mean time, even though its very sparse on new features. (i.e. none!)

As ever thank you for your support and I hope you continue to enjoy using MultiChat.

Best Regards,
Oliver

Hello everyone,

As promised the other day, I present MultiChat version 1.5. This isn't a huge update but what it brings is a very stable build of MultiChat with some new features to keep everything running smoothly while I work on version 2.0.

When I started programming this plugin I barely even knew how to write Java programs. Now I have done an entire year of a university course where our programming language focus was Java! As such there was a lot of code that was very poorly written (and still is...) I have managed to clean some areas that should prevent those annoying null pointer exceptions, but the total re-code will come with 2.0.

Whats new?

• Hyperlinks no longer need to start with www. to be recognized in chat!
• You can use multiple hyperlinks in the same message and click on whichever one you want!
• I have put an end to losing colour onto the second line of a long message in the main chat once and for all
• Messages sent from players with permission to chat in colours will not take up more lines than they should
• On SPIGOT (not Sponge... yet...) you can now nickname yourself by omitting the player in the command. I.e. /nick THISISMYNICKNAME/
• On SPIGOT (not Sponge... yet...) you can use the /realname command to figure out a player's real name from their nickname. (multichatbridge.realname).
• IMPORTANT (!) - To be able to make group chats players will now need the multichat.group.create permission! multichat.group will cover all other aspects of group chats. This is to allow diversity in your ranking systems.
• Nicknames now will be recognised properly by plugins such as essentials and used in /who, and in the messages for things such as /tp. (make sure if you are using ESSENTIALS, to change set-displayname in the ESSENTIALS config to false!)
• Nicknames now show up in the tab list!
• Console logs are now readable and not littered with quite as many colour codes!
• And finally, you can use the custom broadcasts (casts) from console by using the /usecast command. I.e. /usecast mybroadcast Hello everyone!

That is all for 1.5, but as I said, 2.0 is on its way and it will be filled with practically all the requested features I've been getting. If you have any suggestions please let me know so I can bare it in mind while developing the new version!

Hope you enjoy version 1.5, and please report any bugs to me on this discussion thread or via PM or the github issues area.

Thanks again!

Hi all, sorry for the quick update successions!

This update is a feature brought up in the discussion. There was before only 1 permission node for nicknames that allowed you to set anyones nickname, multichatbridge.nick (or multichatsponge.nick depending on what software you are using). I have now ammended this so you can let players only set their own nicknames.

THIS WILL MESS UP YOUR PERMISSIONS!

There are now 2 permission nodes in place of the old one.

multichatbridge.nick.self : Allows you to set your own nickname only!
(multichatsponge.nick.self : For sponge)

multichatbridge.nick.others : Allows you to set anyones nickname including yourself!
(multichatsponge.nick.others)

This means the old permission will no longer work, you need to change it.

I also removed some annoying DEBUG text in the sponge console!

That's all for now Hope you find this update useful.

Hello everyone!

I am aiming to work on MultiChat 2.0 a lot over the coming Summer but for now I present you with MultiChat version 1.4.1!

With this update I have fixed several null pointer exceptions, made the second group chat help page show up! (Somehow I had deleted all those messages?!) Stopped the new /cast command spamming your consoles, and some new features!

NICKNAMES ARE NOW IN SPONGE! multichatsponge.nick
Use /nick <playername> <nickname> and /nick <playername> off

Console now displays the chat in its full correct colours!

And a slight alteration is that if global chat is disabled upon start up, the /global and /local commands will NOT enable as this was causing some issues for people who didn't want to use them.

And finally, there are some new chatformat options for the global chat!

%MODE% will display either Global or Local depending on what mode the player has set their chat (using /local and /global). And %M% will do the same but with L or G instead of the full words!

Thats all for now! I doubt there will be a 1.4.2 unless issues arise, so look forward to 2.0 coming this Summer!

Thanks for using multichat, any suggestions, feature requests, issues, let me know by messaging me privately, or on the github issues page!

Hello everyone!

It is with great pleasure I present to you, MultiChat 1.4. This update is not as feature filled as when we updated to 1.3, but I think the work that has gone into it is even more!

MultiChat 1.4 is so titled the "perfectionist" update as it fixes many small issues with the plugin that have been present throughout the versions. Many errors have been wiped out, code cleaned up, in general this update focuses on quality of life features. But I won't bore you with that anymore, of course I have implemented some new features to make the plugin better than ever! Lets have a look at what is new...

NEW FEATURE
BUG FIX
OTHER

CHANGE LOG:

• Fixed issue where long chat messages would lose colour completely on the second line if the format ended in any code other than &f
• Added /announcement list to view all avaliable announcements
• In order for staff to appear in /staff they MUST have multichat.staff as a permission (They used to appear automatically if they had multichat.staff.mod or multichat.staff.admin)
• Added custom broadcasts that can easily be created in game using the /cast command
• Added feedback to the bulletin command to verify when actions have taken place
• Added feedback to the helpme command to let players know staff have been informed
• Fixed an issue where the plugin would throw an exception and potentially kick players
• FULL support for LuckPerms through Vault on spigot
• Fixed double prefixes showing up in chat when they were changed.
• Implemented the /nick command into MultiChatBridge for Spigot to allow you to nickname players.
• Fixed an issue where silent quit messages might not show correctly
• Added a social spy bypass node: multichat.staff.spy.bypass
• Reduced console output to stop the plugin spamming you all so much
• Improved the /local command so that players who activate local mode will only have their messages sent to people on the same server as them, as well as only receiving messages from people on the same server. People in global mode will see local messages if they are on the same server as the person in question.
• New logos for MultiChat!

The next update planned for MultiChat is version 2.0... This is where all those requested features are going to start appearing in masses! Multiple chat streams, /ignore, all of those things, you name it! If you have a requested feature then let me know, it will probably already be on my list!

Thank you all for the continued support of the plugin, and I hope this update delivers for you. If you have any issues report them on the GitHub page for MultiChat Development

~ Ollie

Due to a disagreement between plugins on using the § symbol or the & symbol for colour codes there was an issue when sending the correct vault/essentials/minecraft display names to MultiChat.

This has now been fixed and those of you who had issues with displaynames or nicknames not showing correctly should now not have the issue!

Thanks to the reporter of this issue!

Sorry for the very small updates, they have just been touching up some rough edges on the last few quite large ones!

I hope to bring new features soon

Hello everyone!

While this is a VERY small update, it is one that has become increasingly required.

Some permissions plugins seem not to update player's displaynames correctly and as such MultiChat was unable to get their display names correctly.

I have now added full support for Vault, meaning that any chat plugin that supports vault will be able to have prefixes, suffixes, etc. fetched by MultiChat to use!

MULTICHAT DOES NOT REQUIRE VAULT!
It is 100% optional and MultiChat will still work perfectly well without it.

That is all for now!

Hello everyone!

It is with great pleasure that I present you with MultiChat 1.3.2

Right in time for Minecraft 1.11 it would seem!

Version 1.3.2 features bulletins using the /bulletin command. These are continuous message loops that you can add and remove messages from. They display at a fixed interval that you can set.

We also added announcements, these are similar to bulletins but you can control how often specific "announcement" messages display.

/Clearchat <all/server/self/global> can clear various chat streams.

We added TAB COMPLETE for private messaging and made the code for group chats a lot more efficien.

Console can now send messages to your staff/admin chat streams, this ammends a previous limitation.

And finally...

MultiChat now fully supports SPONGE. Sponge is an alternative to Bukkit/Spigot that lets you run modded servers with plugins etc. and it is growing in popularity. As such MultiChat can now fetch displayNames/prefixes/suffixes from Sponge servers to use in the public chat. If you are writing a prefix pugin for sponge then you need to set the option "prefix" for players and MultiChat will pick it up.

The wiki will be updated in due course but until then here are the new permission nodes:

- multichat.chat.clear (Ability to clear own chat stream)
- multichat.chat.clear.all (Ability to clear ALL chat from every server and player on the network)
- multichat.chat.clear.server (Ability to clear chat from the specific server you are connected to)
- multichat.chat.clear.global (Ability to clear chat from all servers connected to the global chat stream)
- multichat.announce (Add, remove, start and stop announcements)
- multichat.bulletin (Use all bulletin commands)

Thank you for using MultiChat! And as always, if you have any issues, bugs or general suggestions, just drop me a private message and I'll get back to you ASAP

This small update to MultiChat fixes a number of bugs including:

• An issue preventing muting plugins from working correctly
• An issue that made disabling PM toggles very difficult if a player logged off
• Fixed an issue preventing staff viewing the mod chat even when they had the correct permission.

This update also includes a couple of handy additions to keep the plugin improving and growing:

• A barebones /helpme <message> command for players to alert staff members of an issue which is global to the whole network. This will become configurable in the future.
• A new permission "multichat.staff" allows you to appear in the /staff list and is also how the players who receive /helpme messages are determined.
• Network join and quit messages that can be completely configured to your needs.
• Silent joining for staff members to bypass the join/quit messages but allows other staff to see they joined.

Full information can be found on our WIKI as always!

Thanks for using multichat

Hello everyone!

I have finally completed MultiChat version 1.3 and am now pleased to release it to you!

MultiChat 1.3 adds many new features including global chat which you can disable if needed to make all your servers share 1 chat stream, private messages that can span across your entire network, commands to toggle viewing local and global chat, commands to display messages to the entire network, all the regular group chats and staff chats, now all customization via your config files!

There is so much that I have compiled a github wiki for MultiChat 1.3. Just follow the order of the pages listed here to get going with MultiChat 1.3!

If you previously used MultiChat Im sorry to say that it was not possible for me to transfer over group chats and staff chat preferences with this version. They will have to be re-created. It was not my intention originally but I encountered some issues.

Just drop the Jar file into your bungeecord plugins folder and if you wish to use spigot display names then also put it into each individual server's plugins folder.

Here is the wiki to get you set up! https://github.com/MultiChat/MultiChat-1.3/wiki