Closed ImDarkDiamond closed 1 year ago
I reloaded guild 961365597344657458 so it should be fixed once you reconnect to it
Unfortunately I am still seeing the same behavior. I've also checked with Eris & its rawWS event.
This has also been repeatedly reported with JDA. I've implemented a fix in the library to mitigate the issue.
We've made some changes in the last couple months, is this still an issue?
Closing for now since we believe the issue is resolved.
It is! Meant to respond yesterday but got busy. Thanks ❤️
@yonilerner i'm still getting this for guild 410479299347480576 (forum tag id 1027892492105941023)
I reloaded that guild, if you restart your bot (just to force it to get a new GUILD_CREATE), do you still have the bad forum tag id?
I no longer get the bad forum tag, thanks!
I'm getting this problem on one of the guilds my bot is in (638540406577037332) on forum tags 1021805861808648193, 1021805910647119902, 1021805961826029598, 1021806027127148624, and 1021806142273364039.
@CircuitSacul I think you need to reconnect your bot You probably didn't reconnect since we fixed the problem so you have stale state cache in memory We just pulled the emoji_id values for each of these tags, and they are all nil, not 0
Description
Docs state that
emoji_id
andemoji_name
will not be both set. See: https://discord.com/developers/docs/resources/channel#forum-tag-object-forum-tag-structureThe gateway seems to send the tag with
emoji_id: 0
Fetching the channel in Postman (GET https://discord.com/api/v10/channels/961365597344657458) from the REST API returns the forum tag correctly. (emoji_id: null)
Steps to Reproduce
Connect to the gateway and wait for GUILD_CREATES to be sent after identifying.
Expected Behavior
When
emoji_name
is setemoji_id
should be null and not 0. (See images above)Current Behavior
When
emoji_name
is setemoji_id
is being returned as 0. (See images above)Screenshots/Videos
No response
Client and System Information
Used Postman for fetching from REST and Twilight for connecting to the gateway.