Skip to content

Commit c9ff241

Browse files
committed
Social SDK: Reorganize Rich Presence requirements section
Move requirements section before the setup instructions for better flow and readability in the Rich Presence without authentication guide.
1 parent d6870a1 commit c9ff241

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

docs/discord-social-sdk/development-guides/setting-rich-presence.mdx

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -207,6 +207,14 @@ Unlike most other features of the Discord Social SDK, **Rich Presence can be set
207207
using [`Client::Connect`] to authenticate with Discord, you can use Rich Presence functionality by directly communicating
208208
with a running Discord desktop client through RPC (Remote Procedure Call).
209209

210+
### Requirements
211+
212+
* Discord desktop client must be running on the user's machine
213+
* Your application must be registered with Discord and have a valid Application ID
214+
215+
This direct approach makes Rich Presence integration much simpler for developers who only need basic presence
216+
functionality while Discord desktop clients are running.
217+
210218
### Setting Up Direct Rich Presence
211219

212220
To use Rich Presence without authentication, simply:
@@ -237,15 +245,6 @@ client->UpdateRichPresence(
237245
}
238246
});
239247
```
240-
241-
### Requirements
242-
243-
* Discord desktop client must be running on the user's machine
244-
* Your application must be registered with Discord and have a valid Application ID
245-
246-
This direct approach makes Rich Presence integration much simpler for developers who only need basic presence
247-
functionality while Discord desktop clients are running.
248-
249248
---
250249
251250
## Next Steps

0 commit comments

Comments
 (0)