Summary
This event is "made up" by Pycord and partly hides what is going on on the API
What is the feature request for?
The core library
The Problem
For both Member and User updates, Discord fires this event. Pycord splits this into two events, which can sometimes still "interfere", e.g. on_user_update being called twice by sharing 2 guilds with the bot, despite the underlying user only being updated once. This happens particularly when updating the Primary Guild, as @Paillat-dev and me found out
The Ideal Solution
on_user_update is removed and on_member_update is the leading update event that users use, following the API
The Current Solution
No response
Additional Context
No response
Summary
This event is "made up" by Pycord and partly hides what is going on on the API
What is the feature request for?
The core library
The Problem
For both Member and User updates, Discord fires this event. Pycord splits this into two events, which can sometimes still "interfere", e.g.
on_user_updatebeing called twice by sharing 2 guilds with the bot, despite the underlying user only being updated once. This happens particularly when updating the Primary Guild, as @Paillat-dev and me found outThe Ideal Solution
on_user_updateis removed andon_member_updateis the leading update event that users use, following the APIThe Current Solution
No response
Additional Context
No response