-
-
Notifications
You must be signed in to change notification settings - Fork 27
Updates
This page provides instructions for updating MultiChat from one version to another. Please read and follow these instructions very carefully to prevent data loss or corruption.
MultiChat 1.8 adds several new features and if you do not follow these steps to update carefully then you may corrupt your server files!
Firstly, as with all MultiChat updates... BACKUP ALL YOUR SERVER FILES! Just in case.
Many of the config files now have new options. There are 3 courses of action you can take.
-
BACKUP all your config files from multichat, then delete the original copies from the multichat folders and the newest versions will be automatically generated by the plugin. You can then manually re-enter all your config options from the backups you took.
-
Look at the wiki pages for each of the multichat config files and manually add any new options to your existing files. If you are 100% confident you have done this correctly then you can change the version number at the top of the file to 1.8 (Yes... The one that says DO NOT EDIT!) But be warned, if you do this incorrectly then you could run into lots of issues!
-
Leave your config files as they are (not recommended)... They should still work just fine, but you will obviously not have access to all the new options and this way of running your server is not supported.
If you wish to take option (2) then here is a brief summary of all the new changes to config files to help you with your manual updating process:
- In config.yml, added
globalcommandandlocalcommandoptions for aliases in the "Chat Channels" section. Addedprivacy_settingsoption to the end of the file in the "Other" section. - In joinmessages.yml, added
broadcast_welcome_messageoption to the end of the file. - In spigotconfig.yml, added
nickname_length_minoption in the "Nicknames" section, and also addednickname_sql, and various MySQL options at the bottom. - In multichatsponge.yml, added
nickname_length_limit,nickname_length_minandnickname_length_limit_formattingoptions in the "Nicknames" section, and also addednickname_sql, and various MySQL options at the bottom.
The biggest feature of this new update is MySQL and SQLite functionality for Spigot and Sponge nicknames. In order to use this, PLEASE BACKUP YOUR FILES FIRST! We provide a migration command to convert from the old file based storage to SQL, but errors can occur with any process like this so it is not worth risking losing your data!
Please see the new SQL wiki page for more details on this process.
This update includes a load of new features for Sponge. Sponge has lagged behind spigot in terms for functionality, especially for things like nicknames, but no longer! This however does mean there could be lots of new bugs introduced!
Please pay careful attention to the permissions page which features lots of new permissions for sponge!
All of the features for nicknames are now available for sponge as well as spigot.
This update includes lots of bug fixes and smaller changes. Commands such as /local and /global can now be used to send messages directly to those channels without swapping to them. You can use /local for example. There are also now aliases for these commands in config.yml to let you use things like /g as a shortcut.
This update adds the /pexecute command that lets you execute commands on your proxy server from spigot / sponge servers. This is the opposite of the /mce (multichat execute) command that was introduced a while ago now that lets you run spigot / sponge commands from the proxy server.
Please see the changelog here for a full list of changes.
- No major steps required, just backup all folders as usual in case of errors
MultiChat is developed by Revilo410 (Oliver Martin)
To download the latest release:
Click Here