After bot updates that introduce new slash commands, the commands are correctly synced and visible in guild 1410939321812258928. However, the same commands do not appear in guild 1263067254153805905.
Additionally, the ?sync command that is intended to manually force command synchronization does not seem to perform any action and does not resolve the issue.
Current Behavior:
- New commands appear and work normally in guild
1410939321812258928
- Commands do not appear in guild
1263067254153805905
- Running
?sync does not trigger command synchronization
- No error messages are shown
Expected Behavior:
- When a bot update adds new slash commands, they should sync to all configured guilds
- Running
?sync should force the bot to resync commands to the current server
Steps to Reproduce:
- Add or update a slash command in the bot
- Restart the bot
- Observe commands appear in guild
1410939321812258928
- Check guild
1263067254153805905
- Notice the new commands are missing
- Run
?sync
- Commands still do not appear
Possible Causes:
- Guild-specific command sync not being triggered for
1263067254153805905
?sync command not calling bot.tree.sync() or equivalent
- Cached command tree preventing update
- Guild not included in sync logic
Expected Fix:
- Ensure the sync command explicitly runs something similar to:
await bot.tree.sync(guild=discord.Object(id=GUILD_ID))
or performs a global sync where necessary.
- Verify the
?sync command actually executes the sync logic and reports success or failure.
Affected Components:
- Command sync system
?sync command
- Guild command registration