Skip to content

Commit 4c72523

Browse files
committed
docs: remove hybrid commands
1 parent 69659ca commit 4c72523

File tree

1 file changed

+0
-19
lines changed

1 file changed

+0
-19
lines changed

docs/src/Guides/03 Creating Commands.md

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -472,22 +472,3 @@ There also is `on_command` which you can overwrite too. That fires on every inte
472472
If your bot is complex enough, you might find yourself wanting to use custom models in your commands.
473473

474474
To do this, you'll want to use a string option, and define a converter. Information on how to use converters can be found [on the converter page](/Guides/08 Converters).
475-
476-
## I Want To Make A Prefixed Command Too
477-
478-
You're in luck! You can use a hybrid command, which is a slash command that also gets converted to an equivalent prefixed command under the hood.
479-
480-
To use it, simply replace `@slash_command` with `@hybrid_command`, and `InteractionContext` with `HybridContext`, like so:
481-
482-
```python
483-
@hybrid_command(name="my_command", description="My hybrid command!")
484-
async def my_command_function(ctx: HybridContext):
485-
await ctx.send("Hello World")
486-
```
487-
488-
Suggesting you are using the default mention settings for your bot, you should be able to run this command by `@BotPing my_command`.
489-
490-
As you can see, the only difference between hybrid commands and slash commands, from a developer perspective, is that they use `HybridContext`, which attempts
491-
to seamlessly allow using the same context for slash and prefixed commands. You can always get the underlying context via `inner_context`, though.
492-
493-
There are only two limitations with them: they only support one attachment option, and they do not support autocomplete.

0 commit comments

Comments
 (0)