Skip to content

Social SDK: Reorganize Rich Presence requirements section #7756

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

Merged
merged 1 commit into from
Aug 14, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,14 @@ Unlike most other features of the Discord Social SDK, **Rich Presence can be set
using [`Client::Connect`] to authenticate with Discord, you can use Rich Presence functionality by directly communicating
with a running Discord desktop client through RPC (Remote Procedure Call).

### Requirements

* Discord desktop client must be running on the user's machine
* Your application must be registered with Discord and have a valid Application ID

This direct approach makes Rich Presence integration much simpler for developers who only need basic presence
functionality while Discord desktop clients are running.

### Setting Up Direct Rich Presence

To use Rich Presence without authentication, simply:
Expand Down Expand Up @@ -237,15 +245,6 @@ client->UpdateRichPresence(
}
});
```

### Requirements

* Discord desktop client must be running on the user's machine
* Your application must be registered with Discord and have a valid Application ID

This direct approach makes Rich Presence integration much simpler for developers who only need basic presence
functionality while Discord desktop clients are running.

---

## Next Steps
Expand Down