plun1331

This should be fixed in the latest release

> > This should be fixed in the latest release > > Well, I tested that code in py-cord version 2.1.1 with 1️⃣ emoji but it raised this error >...

Try upgrading to 2.2.2 and see if the issue is resolved

You're reusing the same sink objects, you should use a new sink each time instead

> `@bot.slash_command()` is not correct it requires the name parameter so `@bot.slash_command(name='name')` `@bot.slash_command()` requires no parameters.

> > What I was referring to was `BridgeExtContext._respond()`, which currently uses `self._get_super("reply")(*args, **kwargs)` to send a reply. A possible fix would be `except`ing an HTTPException here, and using `self._get_super("_get_channel")().send(*args,...

> > > When would a reply not be possible? > > > > > > When the invocation message is deleted > > Won't that just make it reply...

The diff I'm looking at displays the entire API reference as modified, and as such I can't really see what changes were made.

Dupe of #1502

You can pass the checks to the `checks` kwarg when creating a group.