Skip to content

Make on_member_update fire even when the member is not cached #3001

@pgcoordinates

Description

@pgcoordinates

Summary

Allow the on_member_update event to trigger even if the member is not in cache. The event should use the full updated member object from Discord instead of depending on local cache.

What is the feature request for?

The core library

The Problem

Right now, on_member_update only fires if the member is cached. When cache and guild chunking are disabled, the event never triggers, so there is no way to detect member updates without manually handling raw socket data.

The Ideal Solution

Make on_member_update fire using the data from the gateway event even when the member is not cached. The “before” object can be None, but the “after” object should contain the updated member data from Discord.

The Current Solution

The only way to handle updates without caching is to use the raw event and manually create the member object, which is more complex and inconsistent with other event handling.

Additional Context

No response

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions