| The status reads “Not initialised” and Sign in is disabled | Discord Social has not initialised. It is a subsystem that starts itself, so check Project Settings, Subsystems, Discord Social: the Application Id must be set, and the start mode must be Automatic (or you must call DiscordSocialApp.Initialize yourself). |
| A “Setup needed” box appears at the top | The Application Id is zero. Set it in Project Settings, Subsystems, Discord Social and press Play again. |
| Sign in opens the browser but nothing completes | The Discord desktop client must be running. In the Discord developer portal the application needs the Social SDK enabled and a redirect address Discord accepts for the SDK. |
| Signing in every time | Check that Remember Sign In is on in Project Settings, Subsystems, Discord Social. The saved token is tied to the device and kept in PlayerPrefs, so clearing PlayerPrefs, or pressing Sign out, removes it. |
| The status label under your name does not follow the dropdown | Update the Toolkit. Discord does not raise an event for your own status, so the profile checks it twice a second when useLocalUser is on. |
| The label reads “Idle” for Invisible or Do Not Disturb | Update the Toolkit. Older versions showed every non-online state as Idle. |
| The friends list is empty | Discord only returns friends it has relationship data for in this application. Add or accept a friend and check the Requests lists. |
| Everyone is under Offline | Invisible friends appear as Offline. Statuses arrive shortly after the status becomes Ready. |
| Invite is greyed out | You are not in a lobby. Create or join one first. A tooltip says so when a DiscordTooltip is in the scene. |
| Create lobby shows “Sign in to Discord first.” | The status is not Ready. Sign in, wait for Ready, then create. |
| The friend gets an invite in Discord that says “Join from a supported device” | That is Discord’s own invite card, and what it allows depends on how the application is configured in the developer portal. Have the other player run the demo and sign in first: their game then shows the in-game invite prompt, which does not use that button. |
| The friend never sees the in-game invite prompt | The other player’s demo must be running, signed in and not already in a lobby. The prompt is ignored while in a lobby. |
| Start session does nothing | Only the host can start. Start session is enabled only for the lobby’s creator. A member who joined with a code or an invite cannot start it. |
| A member does not enter the session when the host presses Start | The announcement is a lobby message. The member must be in the lobby, and the message must come from the host. A heathen.host value of 0 (unreadable lobby metadata) accepts any author. |
| Members enter the session but cannot see each other move | Expected with PlaceholderNetwork. Plug in your networking library, see Integrating Networking. |
DemoNetwork.Current is null and Start fails with “There is no DemoNetwork in the scene” | The scene needs one component that derives from DemoNetwork. The shipped scene has PlaceholderNetwork on the Discord Social object. |
| A client cannot reach the host | Discord has no relay. The address the host announces must be reachable: the same network, a VPN or a forwarded port. |
| Capsules do not move | DemoPawn reads the Input System when it is installed and active, otherwise the legacy Input Manager. If both are off, no input is read. |
| The demo does not compile, or the sample scripts are missing | The Foundation, the Discord Social SDK (1.10.0 or newer) and the Game Framework must all be installed. Without the SDK the Foundation and Toolkit assemblies are skipped and a window explains what to install. |
| Join voice is greyed out | You are not in a lobby. Create or join one first. |
| The voice list is empty after Join voice | The call is still connecting. The list fills when the call reaches Connected. Check the Console for the Discord Voice log category. |
| The speaking light never lights | Speak into the microphone chosen in Settings. Check that the right microphone is selected and the Discord client is not holding it. Push to talk mode needs the button held. |
| The noise, echo and gain switches show off but behave as on | Discord only reports their state when the SDK is connected to the Discord desktop client over RPC. Without that they keep the values you last chose in the panel. |
| Voice settings log “Not connected to a Discord client over RPC” | Same cause. The volumes and devices are still read and set normally. |
| With 3D voice on, nobody is heard | Check that 3D voice was ticked before pressing Join voice, and that the other player’s capsule exists in the session (the source plays only people who are bound to a capsule). A person with no capsule is still played through the device. |
| With 3D voice on, someone is heard twice | The audio was not muted on the device. Leave voice and join again with 3D voice ticked before joining. |
| 3D voice sounds delayed or crackles | The voice goes through a small buffer, about 60 ms before it starts and at most half a second. Heavy frame hitches can still starve it. |