Skip to main content

Migrating from Triton v3 to v4

warning

Before proceeding, make sure to backup your Triton folder on all servers in case something goes wrong during the migration! If you are using MySQL, it is recommended to backup the database as well.

This guide is focused on the migration steps to update to Triton v4. Everyone is encouraged to also read the accompanying blog post detailing new features and improvements.

Changelog​

Below are the highlights of this update that might require your attention:

  • messages.yml and language display names now use MiniMessage syntax instead of legacy color codes (💥 Breaking Change);
  • multilanguageplugin.* permissions are no longer checked and therefore have no effect. Please migrate to triton.* equivalents (💥 Breaking Change); and
  • There is a new parser based on Adventure that is the default for new installations; see below for details.

Contrary to previous major Triton updates, this update requires manual intervention.

Download the new version​

Follow the instructions in the installation guide.

Make sure to update Triton on all servers and the proxy, as some of the bridge messages have changed from Triton v3.

Update messages.yml​

note

Keep in mind the MiniMessage changes below do NOT affect your translations. Legacy color codes are still the default for your translations on TWIN and in the translations folder, so no action is required for those.

The messages.yml file has been updated to use MiniMessage instead of legacy color codes.

If you have not changed any of these messages, you can simply delete your messages.yml and let Triton regenerate it with the new defaults. Otherwise, you might need to perform the migration manually. Alternatively, you can attempt to use automated tools, which may not be perfect. The default messages.yml can be found on GitHub as a reference.

Furthermore, the following messages have been renamed:

  • error.bungee-reload-invalid-mode to error.proxy-reload-invalid-mode
  • success.bungee-reload to success.proxy-reload
  • twin.failed-bungeecord to twin.failed-behind-proxy

Update language display names​

Similarly to the previous section, the display name of languages also only supports MiniMessage as of Triton v4.0.0. As a result, config.yml needs to be updated respectively.

For example:

-    display-name: '&3English (UK)'
+    display-name: '<dark_aqua>English (UK)'

Enable the legacy parser​

The new Adventure parser is enabled by default. However, it is likely desirable to use the legacy parser instead, to ensure full compatibility with existing translations.

To achieve this, change the value of the new message-parser option on config:

message-parser: "legacy"

Remove deprecated permissions​

If you are still using multilanguageplugin.* permissions, you must switch to the equivalent triton.* permissions instead.

The Commands and Permissions page details all the available permissions.

After Migration 🎉​

Congrats, you've made it!
You should now be running Triton v4.0.0!

If you've encountered any issue during the migration process, please ask for help in our Discord server.

Below are some resources that might be useful: