-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add custom status #1160
Comments
Blocked before being processed with a bot account. This documentation only documents bot endpoints, so far. |
|
Custom statuses are activities with a type of
As bots cannot send r i p |
Feel free to add docs for custom emoji (the emoji struct + new type) in the activities docs. As for bot support for custom status. It should be trivial for us to add and I'll loop back the product team into adding it. |
@jhgg what file does that go in? I'm a bit lost. |
@SIGSTACKFAULT there's a PR open already for custom status, #1162 |
@jhgg Any news from the product team? ;) |
Still nothing after nearly a month any news on that? |
Hopefully soon! |
cant wait. |
Still no news from the product team? @jhgg |
Sad story... |
Is it possible to hide a user's status in the members list? |
Would be cool if there is a server side custom status like nicknames |
@jhgg any news? |
I think it's pretty unnecessary to mention him multiple times, he'll let us know once he has an update for us. patience |
I know I'm just adding onto the storm that is requests for Custom Statuses to be added for bots, but... For F-s sake Discord just add it already. We are all waiting to use it. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@passcod Let's please remember that this issue was closed 5 months ago, and you will never get an email informing you about any progress :) |
Can we just stop shitposting in here? Most of us have notifications on and it's certainly not to receive crying baby images or random people complaining about features Discord adds, there's a feedback page for this, which is a way better way to give your input than commenting on a closed issue. |
If we can't still use those fields yet, Wouldn't it be better to reopen this issue? |
H-Hello? Shouldn't this be open? |
This repo is for the API docs, and not for actual changes to the API. As the API behaviour has been documented, this issue is correctly closed. |
No, this repo is also for API bugs and feature requests |
While this repo does also handle feature requests, this issue shouldn't be open as it's not a feature request but a documentation request. There's a few other (closed) issues that would meet the standards for being an open feature request, but it seems they have all been closed by the OPs. |
night closed #1801 as a duplicate of this issue |
Is this still a planned feature? This issue is over a year old now... |
I too would be interested in this feature. |
Its over two years now |
This comment has been minimized.
This comment has been minimized.
(referring to this particular comment above) |
The issue is closed, there is no point in posting here at all. It's CLOSED, meaning, it's no one looking at it, or an identical existing issue exists. Besides; it's quite normal to "bump" issues saying you want a feature, it's one of the ways devs know what feature to prioritize. But bumping a closed issue will do nothing. |
Since I could not find about when a guild member changed custom status on Change Log.
The text was updated successfully, but these errors were encountered: