Skip to content
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

Closed
ilsubyeega opened this issue Oct 25, 2019 · 51 comments · Fixed by #1162
Closed

Add custom status #1160

ilsubyeega opened this issue Oct 25, 2019 · 51 comments · Fixed by #1162

Comments

@ilsubyeega
Copy link

Since I could not find about when a guild member changed custom status on Change Log.

@SIGSTACKFAULT
Copy link

SIGSTACKFAULT commented Oct 25, 2019

It seems to be in the (undocumented) /users/@me/settings endpoint.
image

Correction: that endpoint causes persistence into the next session, but not the current one.
there's a gateway thing to do too.

@infi
Copy link

infi commented Oct 25, 2019

Blocked before being processed with a bot account. This documentation only documents bot endpoints, so far.

@SIGSTACKFAULT
Copy link

[~] » curl 'https://discordapp.com/api/v6/users/@me/settings' -H "Authorization: Bot $token"
{"message": "Bots cannot use this endpoint", "code": 20001}

@Lymia
Copy link

Lymia commented Oct 26, 2019

Custom statuses are activities with a type of 4, a name of Custom Status, the actual custom status in the state field, and a new emoji field for the main emoji. Bots aren't blocked from doing this, but... well, read the docs: https://discordapp.com/developers/docs/topics/gateway#activity-object.

Bots are only able to send name, type, and optionally url.

As bots cannot send states or emojis, they can't make effective use of custom statuses. The header for a "Custom Status" shows up on their profile, but there is no actual custom status, because those fields are ignored.

r i p

@jhgg
Copy link
Contributor

jhgg commented Oct 26, 2019

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.

@SIGSTACKFAULT
Copy link

@jhgg what file does that go in? I'm a bit lost.

@VisualEhrmanntraut
Copy link
Contributor

@SIGSTACKFAULT there's a PR open already for custom status, #1162

@Zoddo
Copy link
Contributor

Zoddo commented Nov 10, 2019

@jhgg Any news from the product team? ;)

@evnsh
Copy link
Contributor

evnsh commented Nov 19, 2019

Still nothing after nearly a month any news on that?

@oldunresisting
Copy link

Hopefully soon!

@ghost
Copy link

ghost commented Nov 29, 2019

cant wait.

@evnsh
Copy link
Contributor

evnsh commented Dec 10, 2019

Still no news from the product team? @jhgg

@ItsFlare
Copy link

ItsFlare commented Jan 2, 2020

Sad story...

@aozkinay
Copy link

aozkinay commented Jan 5, 2020

Is it possible to hide a user's status in the members list?

@jan-tennert
Copy link

Would be cool if there is a server side custom status like nicknames

@ilsubyeega
Copy link
Author

@jhgg any news?

@Taarek
Copy link
Contributor

Taarek commented Feb 9, 2020

I think it's pretty unnecessary to mention him multiple times, he'll let us know once he has an update for us. patience

@MidSpike
Copy link
Contributor

MidSpike commented Mar 3, 2020

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.

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.

@MinnDevelopment

This comment has been minimized.

@Celtiaa

This comment has been minimized.

@fjeddy
Copy link

fjeddy commented Apr 5, 2020

@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 :)

@advaith1
Copy link
Contributor

advaith1 commented Apr 5, 2020

Here's an update from Jake


@broman
Copy link
Contributor

broman commented Apr 5, 2020

77103178-4ce52100-6a1a-11ea-9cf7-65893e403f8a

@evnsh
Copy link
Contributor

evnsh commented Apr 5, 2020

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.

@KokoseiJ
Copy link

If we can't still use those fields yet, Wouldn't it be better to reopen this issue?

@PixelHir
Copy link

H-Hello? Shouldn't this be open?

@invalidCards
Copy link

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.

@advaith1
Copy link
Contributor

No, this repo is also for API bugs and feature requests

@ghost
Copy link

ghost commented Sep 19, 2020

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.

@advaith1
Copy link
Contributor

night closed #1801 as a duplicate of this issue

@yungcomputerchair
Copy link

Is this still a planned feature? This issue is over a year old now...

@KingSupernova31
Copy link

I too would be interested in this feature.

@ghost
Copy link

ghost commented Mar 15, 2021

Its over two years now

@boroworx

This comment has been minimized.

@NovaLynxie
Copy link

NovaLynxie commented May 23, 2021

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.

(referring to this particular comment above)
Guys, stop bumping this issue thread it's just making this re-appear as a new notification for everyone else watching.
Things like these take time, considering the priorities of the developers and scale of the API it will most likely be a while before such a feature could possibly be added. I too am waiting but I respect the devs taking their time to focus on other things first.

@fjeddy
Copy link

fjeddy commented May 23, 2021

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.

@TheYoungSeth

This comment has been minimized.

@tominal

This comment has been minimized.

@discord discord locked as too heated and limited conversation to collaborators Jun 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.