Unknown MC Version

This should never occur. If it does, please report it in the UC Discord.

Invalid Config

Your config is invalid, and UC can't read it. This is often caused by accidentally adding or removing a '.

Resolution: To find out what the issue is, you can paste your config into a site like this. It should point out the error.

Invalid Messages File

Same as "Invalid Config," but concerns your messages_xx.yml file rather than config.yml

Resolution: To find out what the issue is, you can paste your messages file into a site like this. It should point out the error.

Unsupported MC Version

UC was not built for this version of Minecraft. It will try to continue running, but some features will be unavailable.

Resolution: Check for updates to UC or dev builds in the UC Discord.

NMS Load Failure

UC was built for this version, but it couldn't load correctly. It will try to continue running.

Resolution: Check for an update or new dev build for UltraCosmetics. Check for a Spigot/Paper/etc. update.

Bad Mappings Version

UC was built for a version similar to this, but not this one exactly (for example, if you're running 1.19.1 but UC was built for 1.19.2.)

Resolution: Check for an update or new dev build for UltraCosmetics. Check for a Spigot/Paper/etc. update.

Tall Disguises Disabled

The config option TallSelfDisguises is disabled in LibsDisguises's config. This will cause morphs taller than one block to have the "view own disguise" option forcefully disabled by LibsDisguises.

Resolution: Set TallSelfDisguises: true in plugins/LibsDisguises/configs/players.yml

SQL Init Failure

UC couldn't connect to the SQL server given in the config. Flatfile will be used instead until the issue is fixed.

Resolution: Check console log for hints about what the exact issue is, and double-check the SQL settings in the config.

WorldGuard Hook Failure

WorldGuard was not enabled when UC tried to hook into it. This could be caused by a number of things.

Resolution: Check log to see when WorldGuard is enabling.

• If WorldGuard disables itself, update WorldGuard
• If WorldGuard enables successfully after UltraCosmetics enables:
  • If on Paper, check if there is a mention of "legacy plugin loading." If so, figure out why it's using legacy plugin loading and disable it (so it goes back to standard plugin loading.)
  • If you're using any Songoda plugins, temporarily remove them and see if it fixes the issue. If so, one or more of them has WorldGuard in both the loadbefore and softdepend lists in their plugin.yml, which breaks other plugins. You can fix this by unzipping the jar, removing WorldGuard from the loadbefore list, and then re-zipping it.
  • (Not recommended) If you don't need WorldGuard support, you can disable it in UC's config. However, this doesn't fix the issue, it only prevents UC from bothering you about it, so other plugins may still have WorldGuard-related issues.

SQL Migration Required

In UC v3.0, SQL support was almost completely rewritten and has different settings now. Tables produced by UC 2.x cannot be read by UC 3.x. You can convert your SQL data from UC 2.x to UC 3.x by using /uc migrate flatfile on UC 2.x, then upgrading to 3.x, then running /uc migrate sql.

Resolution: After double-checking your SQL settings, remove the line Legacy: true from the MySQL block.

MobChip Error

UltraCosmetics uses MobChipLite to manage pet AI, and each version of UltraCosmetics includes a version of MobChipLite inside it.

If you're seeing this error, it means that the version of MobChipLite included in this version of UltraCosmetics doesn't support the version of Minecraft your server is running. Make sure you're running the latest version of Spigot/Paper/etc and the latest version of UltraCosmetics.