Nickname sync isn't working for some users
Discord's hard-coded rules around owner nicknames and role hierarchy.
First check that nickname sync is on: Project settings → Server setup → Network → Sync nicknames. Each sub-server can also opt out on the Sub-Servers page — an opted-out server neither receives nor sends nicknames. What nickname sync does and leaves alone is explained in Nickname sync; when it runs, in How the sync works.
Discord limits
Discord has hard-coded rules that CloudMod can't bypass:
- Server owner nicknames can't be changed by any bot — it's a Discord-side restriction. CloudMod skips them automatically. This applies on the main server too: a nickname changed on a sub-server can't be copied to the main server's owner.
- The bot role must be above the user's role. If the user has a role ranked higher than the bot, Manage Nicknames doesn't apply. Move the bot role up.
- The bot must have the Manage Nicknames permission on that specific sub-server. Re-check in Discord's role settings.
When the bot fails to sync a nickname, it DMs that sub-server's owner a fix guide — at most once a day per server.
Good to know
- Nicknames sync both ways: a change on a sub-server goes to the main server and from there to all other sub-servers.
- When someone joins a sub-server, their main-server nickname is applied right away — roles and nickname arrive together. Members who were already on the sub-server before you switched nickname sync on are caught up by the next auto-sync (with Auto-fix on) or with
/sync nick. - Bots are never synced.
- In Dry-run mode nicknames and roles aren't changed — CloudMod only logs what it would do. Other plugins keep working.