You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|||
32
-
| The data wraps onto multiple lines. It’s repetitive, slower to read, and messy. | The data all fits on one line per string. Clean! |
29
+
33
30
34
31
### Make it Actionable!
35
32
@@ -39,10 +36,7 @@ The data in your players’ profiles is the first thing that others on Discord w
|||
45
-
| While Rank 9999 is impressive, it doesn’t present any actionable data for their friends. | This player is in queue for something I want to play. Let's ask to join that open spot! |
39
+
46
40
47
41
### Use ALL of the fields (where applicable)!
48
42
@@ -52,10 +46,7 @@ The data in your players’ profiles is the first thing that others on Discord w
|||
58
-
| The map name takes up space and makes the player's status harder to read at a glance. | Moving the name of the map to the tooltip makes the data cleaner and frees up space for the score. |
49
+
59
50
60
51
### Have interesting, expressive art!
61
52
@@ -66,10 +57,7 @@ The data in your players’ profiles is the first thing that others on Discord w
|||
72
-
| The image is dark and unfocused. Highly-detailed images can be hard to see. | This image is bright and matches the details. Let's help! |
60
+
73
61
74
62
75
63
## Launch Checklist
@@ -97,7 +85,7 @@ Ready to launch a Rich Presence integration for your game? If so, we recommend l
97
85
#### Joining
98
86
99
87
> info
100
-
> Since all Activities presence data has a **Join Activity** button, Join Invites are only applicable when building with the [Game SDK](#DOCS_RICH_PRESENCE_USING_WITH_THE_GAME_SDK)
88
+
> Since all Activities presence data has a **Ask to Join** button, Join Invites are only applicable when building with the [Game SDK](#DOCS_RICH_PRESENCE_USING_WITH_THE_GAME_SDK)
101
89
102
90
- Have you successfully implemented join invites for your game if applicable?
103
91
- Does the state of the invite properly represent the party/group in-game with regards to:
Copy file name to clipboardExpand all lines: docs/rich_presence/Using_with_the_Embedded_App_SDK.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The rest of the guide assumes you've already developed an [app](#DOCS_QUICK_STAR
17
17
18
18
### Default Rich Presence Data
19
19
20
-
By default, when a user is connected to your Activity, the app's icon will appear on their profile. If the user viewing the profile has the ability to join, a "Join Activity" button will be displayed as well.
20
+
By default, when a user is connected to your Activity, the app's icon will appear on their profile. If the user viewing the profile has the ability to join, an "Ask to Join" button will be displayed as well.
21
21
22
22
23
23
@@ -32,7 +32,7 @@ Now let's see what custom presence data can look like when a user joins your Act
32
32
A few small things to note about the above image:
33
33
1.`large_image` and `small_image` are both in the `assets` object, which you can see below in the [table below](#DOCS_RICH_PRESENCE_USING_WITH_THE_EMBEDDED_APP_SDK/activity-partial-object). They're labeled with the object's keys to make it more clear how they appear in a Discord profile.
34
34
2. You can't set App Name when setting presence—it's always the name configured in your [app's settings](https://discord.com/developers/applications).
35
-
3.Depending on the `type` you set when updating presence, the behavior and layout for some fields (particularly `small_image` and `large_text`).
35
+
3.The state `(1 of max_party)` badge will only render when a party field is provided. Otherwise, state will be shown in a line of text below details.
36
36
37
37
## Updating Presence
38
38
@@ -108,13 +108,13 @@ To create this sort of Rich Presence, here is what the `setActivity()` code woul
| Second row below title | state |If provided with no `partySize` or `partyMax`|
25
+
|First badge in last row below title | startTimestamp | Converted to a `mm:ss` format such as `12:01`|
26
+
| Second badge in last row below title | state| If provided with a `partySize` and `partyMax`|
27
+
|Second badge in last row below title | partySize| In parenthesis next to the `state`, first number in the format `(1 of 4)`|
28
+
|Second badge in last row below title| partyMax|In parenthesis next to the `state`, second number in the format `(1 of 4)`|
29
+
|Button at the bottom | joinSecret | Button has the text **Ask to Join**|
30
+
| Large image to the left of any content | largeImageKey | Four rows high, includes the title but not the bottom buttons |
31
+
| Small image to the left of any content | smallImageKey | Small icon inset on the bottom right of the `largeImageKey`|
32
32
33
33
Note that this layout may be subject to change without warning. This information is only provided to help those with
34
34
impaired eyesight to understand the potential layout of this information in a user interface.
@@ -87,10 +87,7 @@ Our code sample in this section is based on the data from the example from befor
87
87
88
88
89
89
90
-
This example contains two buttons—the **Ask to Join** button and the **Spectate** button. The **Ask to Join** button will be covered more in the following sections, but if you don't want it included, you can remove the `Party` and `Secret` fields.
91
-
92
-
> warn
93
-
> While the example shows a **Spectating** button, support for spectating was removed and you can ignore references to it.
90
+
The **Ask to Join** button will be covered more in the following sections, but if you don't want it included, you can remove the `Party` and `Secret` fields.
SecurityisoftheutmostimportancetoushereatDiscord, andweknowitisforyou, too. That's why we want to make sure that you properly understand `ActivitySecrets.Join` so that your game data is safe and secure over the wire.
184
+
SecurityisoftheutmostimportancetoushereatDiscord, andweknowitisforyou, too. That's why we want to make sure that you properly understand `ActivitySecrets.Join` so that your game data is safe and secure over the wire.
@@ -207,7 +204,7 @@ Throughout development, make sure you have your `errored()` and `disconnected()`
207
204
208
205
The application that connected _first_ is displayed.
209
206
210
-
However, invite functionality across multiple connected applications now works no matter which app is display on a user's profile. For example, if you are hosting a Spotify listening party, playing Game A that allows you to send Join invites, and playing Game B that allows you to send Spectate invites, you'll be able to send invites to all three simultaneously!
207
+
However, invite functionality across multiple connected applications now works no matter which app is display on a user's profile. For example, if you are hosting a Spotify listening party and playing Game A that allows you to send **Ask to Join** invites, you'll be able to send invites to both simultaneously!
211
208
212
209
#### Q: What if someone looking at my profile or an invite doesn't own the game?
0 commit comments