Jump to what interests you:

⚠️ Breaking Changes

The run method has been removed from Preconditions. In it's place, just like for Commands, there are 3 new optional methods you can create: messageRun, chatInputRun and contextMenuRun.

<aside> ⚠️ Just like in Commands, you ought to specify at least one of the methods if you expect the preconditions to work. That could be either the messageRun method, the chatInputRun method or the contextMenuRun method.

</aside>

For TypeScript users, the Precondition class is no longer abstract. This is due to the fact we cannot mark the methods as conditionally abstract sadly, so it's up to you to implement the handlers required.

!!! DO NOT FORGET ABOUT THE OPTIONAL PRECONDITION METHODS !!!

You don't have to worry if you forget to implement a method for your preconditions that is expected to be there for your commands. We air on the side of caution, so if we expect a method to be present, but it is missing, we will immediately prevent the command from being ran and you will see the error in the following events:

• For chat input commands, you will receive a chatInputCommandDenied event
• For context menu commands, you will receive a contextMenuCommandDenied event
• For message commands, you will receive a messageCommandDenied event

This decision was taken to prevent accidental escalations from happening in your commands (think of a ban command that can suddenly be ran by anyone and everyone. I love chaos but this is too much even for me 😄)

<aside> ℹ️ All Sapphire pre-included preconditions, which you can see here, will come with handlers for all 3 possible types of preconditions by default.

</aside>