Skip to content

Instantly share code, notes, and snippets.

@pseudocoder10
Last active November 10, 2022 21:23
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save pseudocoder10/2f87fc097d5ee3a689cc3889cf5a4bd9 to your computer and use it in GitHub Desktop.
Save pseudocoder10/2f87fc097d5ee3a689cc3889cf5a4bd9 to your computer and use it in GitHub Desktop.
Update on Lockout Bot

Starting 1st September 2022, discord made an update which disallowed verified bot to read messages.

What does this mean? Lockout bot cannot see commands you typed like .match challenge .round challenge etc and hence cannot reply to your messages.

Discord wants every verified bot to move from prefix based commands to their new feature of slash commands. More details here https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ

Unfortunately to migrate lockout bot to slash commands would mean rewriting the whole codebase again for which I don't have enough time at the moment.

There are workarounds to still use the bot which are mentioned below. You can also host your own instance of the bot by following the instructions mentioned here https://github.com/pseudocoder10/Lockout-Bot/wiki/Setup. Having your own instance would work completely fine since the restrictions are for bots with > 100 servers.

The bot no longer works with the prefix . The new way to use the bot is by mentioning it, i.e. @LockoutBot

Demo of how to use handle related commands

Demo of how to use match related commands

Adding text inputs is a bit challenging, you cant directly mention the bot like you did while typing a command (like @LockoutBot 40 in this case). Instead you need to reply to the bot.

To accept the challenge, again you can mention the bot

You can use round and tournament related commands in the exact same way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment