Join our channel

Follow 3DCGHUB on Telegram for new resource drops, migration updates, and community notices.

Join Telegram
Engine Tools

Discord Rich Presence

Integrate Discord Rich Presence in Unreal Engine via Blueprints. Configure OAuth2, initialize your Client ID, and broadcast maps, modes, and player counts.

Categories: Unreal Engine, Engine ToolsPublished Nov 21, 2026
Resource overview

Broadcasting Match Data with Discord Rich Presence

When players launch an Unreal Engine project, standard desktop chat clients often display nothing more than a static application title. Discord Rich Presence changes this baseline behavior by establishing a real-time data link between an active game session and a user's Discord profile card. Rather than leaving friends and community members guessing about what is happening in a session, the integration broadcasts granular, live game information directly to their friends list. Through this interface, an active project can communicate essential gameplay context, specifically the active map name, the current player count participating in the match, and the selected game mode.

For titles featuring multiplayer modes, cooperative campaigns, or competitive arenas, exposing live session parameters serves a functional social purpose. When prospective teammates glance at a player's profile, they can immediately evaluate whether a match is currently in progress, how many player slots are occupied, which battlefield is currently active, and what specific ruleset or game mode is being played. By transmitting the map, game mode, and current player count, the game provides immediate situational awareness to external communities. The plugin makes this continuous status broadcast accessible inside Unreal Engine by exposing a straightforward Blueprint interface designed to control Discord Presence without complex custom network programming.

Configuring the Discord Developer Application and OAuth2 Redirect

Before any logic can be executed inside Unreal Engine's visual scripting graphs, developers must establish the application's profile within the Discord ecosystem. This process begins on the Discord Developer portal, where the creator creates a new Discord Developer App. The creation process is straightforward and consists of completing the standard developer registration form to register the project as an official application. Generating this application yields a unique Client ID, which acts as the foundational identifier required by the engine to associate running game sessions with the specific Discord application profile.

Following the creation of the application profile, developers must configure its network authorization settings to allow local client communication. Navigating to the OAuth2 settings tab within the newly generated app's configuration dashboard reveals the Redirects configuration area. Here, developers must input a specific local loopback address as an authorized redirect:

Http://127.0.0.1

Entering this specific address ensures that local authorization requests properly resolve back to the host machine running the game client. Once this redirect URL is saved within the OAuth2 dashboard, the external platform setup is complete, and the application is fully prepared to communicate with Unreal Engine instances using the assigned Client ID.

Initializing the Discord Connection on Game Startup

With the developer application configured and the redirect established, the Unreal Engine integration begins at the entry point of the project's execution flow. To establish the bridge between the running game instance and the user's local Discord desktop client, developers place the Initialize Discord Blueprint node early in their startup logic. Common integration locations include the Game Instance initialization event, project startup routines, or early splash and loading screen sequences that run as the game launches.

The Initialize Discord node takes the Client ID generated in the developer portal as its primary input parameter. When called on game startup, the node establishes the underlying handshake with the local Discord process running on the user's operating system. Executing this node ensures that subsequent presence commands are recognized and accepted by the client. If the initialization node is not executed at launch with a valid Client ID, any downstream attempts to broadcast or modify activity data will fail to update the player's Discord profile.

Managing Runtime Presence with Set Activity and Clear Activity

Once the initialization handshake is established at startup, developers manage the continuous lifecycle of the player's status through two dedicated Blueprint nodes: Set Activity and Clear Activity. These nodes provide complete control over what information is shown on the profile card and when that information should be removed or reset.

The Set Activity node functions as the primary vehicle for updating social telemetry during active gameplay. Whenever a player enters a new environment, a server registers incoming or outgoing participants, or the match phase changes, calling Set Activity pushes the latest session parameters outward. Developers pass the relevant variables into this node—such as the name of the current map, the live player count, and the active game mode—allowing the profile card to reflect changing conditions in real time. For example, when a match transitions from a pre-game lobby to an active round, or when a new player joins an open slot, firing Set Activity with updated parameters keeps external observers fully informed.

Complementing the update node is Clear Activity, which acts as a dedicated wipe command for active status data. While Set Activity populates the Discord profile with granular match specifics, Clear Activity strips those custom variables away. This node is typically called when a match concludes, when a player disconnects from an active server, or when the player returns to an idle state such as a main menu. Calling Clear Activity ensures that obsolete data, such as a previous map name or an old match player count, does not linger on the player's profile once the gameplay session has officially ended.

Integrating Discord SDK Binaries in the 2.0 Update

Developers implementing this integration should take note of significant structural updates introduced in version 2.0 of the plugin. With the release of the 2.0 update, the required Discord SDK binaries are no longer packaged directly within the plugin download. Instead, developers are required to acquire the official Discord SDK binaries independently.

To facilitate this requirement, comprehensive documentation is provided that guides creators through sourcing and placing the necessary binary files into their project directory. The documentation outlines the exact steps needed to properly locate, download, and position the binaries so that Unreal Engine can locate them during compilation and packaging. In addition to standard documentation, a dedicated German tutorial is also available for German-speaking developers, offering step-by-step visual and procedural explanations of the setup workflow and binary management process.

Visual Scripting Architecture and Workflow Implementation

The core advantage of this plugin lies in its user-friendly Blueprint interface. Rather than forcing gameplay programmers to construct custom C++ network sockets or manage local inter-process communication threads with Discord, all interaction is handled through native visual scripting nodes. This allows solitary game creators, technical designers, and gameplay scripters to wire status updates directly into existing Game Mode Blueprints, Level Blueprints, or custom player state managers.

Because the system relies on simple execution pins and standard data inputs, setting up a reactive presence pipeline can be accomplished with minimal overhead. Developers can bind Set Activity triggers to map transition events, round start delegates, and player connection events, while tying Clear Activity to session teardown functions. For developers who encounter edge cases, need setup clarification, or have questions regarding binary placement or node execution, community assistance and direct guidance are accessible through the creator's dedicated Discord server.

Related Resources Worth Checking