Member object in voice state object has old mute/deaf state

[itsTyrion]

Description

The member object in the voice-state-object has mute/deaf properties. It appears that their values represent the previous (guild) mute/deaf state, not the current one.

Since this is an update ..packet?, it would make sense to include the previous state, but this being an oversight is equally possible, so I'm unsure if this is by-design or not.

Steps to Reproduce

Observe voice-state-updates while changing a guild member's mute/deaf state

Expected Behavior

Again, I'm not sure if I should expect different behavior. If the member object has the previous state by-design, it should be noted in the docs imo. It feels like it's a bug but could also be a documentation issue

Current Behavior

--

Screenshots/Videos

Client and System Information

I was observing this with the library Javacord on Windows 10 LTSC 2021 (21H2), which shouldn't matter as I printed the raw JSON response

[night]

Thanks for the report. I have flagged this issue to our real-time team as it is not clear if this is intended or a bug.

[hemu]

A change was put in to ensure the included member fields reflect the latest updated values rather than the old values. This should be live soon. Going to close this out, ty for reporting this :)