Deprecation and Migration to Discord GameSDK

Hey everyone! As you may or may not know, Discord has been [working closely with Game Devs](https://blog.discordapp.com/the-discord-store-beta-9a35596fdd4) for a while to give developers a way to sell their game on Discord. Recently, we announced [our open invitation to publish on Discord to everyone!](https://discordapp.com/sell-your-game). Equally as exciting is the work that we've done to further support the tech behind games with our [Discord GameSDK](https://discordapp.com/developers/docs/game-sdk/sdk-starter-guide). It includes not only Rich Presence, an awesome thing that you all love, but also a host of other useful features for apps and games like: - Lobbies - Networking - Social Graph - Built in Discord Voice tech! The "Come on in everyone!" game publishing announcement also marked our public release of this SDK, and we're quite proud of it. With that public release, it doesn't make a lot of sense for us to maintain two separate SDKs when one (discord-rpc) is just a subset of functionality of the other (GameSDK). So today we're deprecating this SDK in favor of the new one. ## So what's it mean? For most people, this change doesn't mean much. The big takeaway is that we won't be making any new feature additions to _this_ SDK. Those requests should be directed to the new Game SDK, which will be our foundation on which to build. ## Is my stuff gonna break? Nah. The tech behind this SDK—[connection to Discord via IPC/unix sockets and sending commands/listening f

Posted by msciotti on Apr 30, 2019, 12:39 AM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0