Introduction

Discord Activities are build around an iframe, like a standard webgl game. But there are some key differences :

• Network requests are severely limited by a discord proxy. You can't reach a random domain.
• There is no ads network, so all ads-related mechanism in your game should be disabled.
• The storage (like the one used by PlayerPrefs) is not guaranteed, in size or in durability.
• You can't access user data directly (like user id/cookies...).
• OnApplicationQuit is not called when the game is closed.
• There is no notion of “quitting your game”, discord offers a way to close the activity already and activity can’t close themselves.
• In App Purchases (IAP) have to be made through Discord’s payment rails after having setup SKUs in Discord’s Developer Portal.
• The same webgl build of your game will be used on mobile and desktop, so the game must dynamically adapt itself to 2 platforms for keyboard or touch screen controls. (Using Mee6Platform you code will know if you are on mobile or desktop).

To go through the limitations we offer 5 objects :

• Mee6Storage : a PlayerPrefs like class (exactly the same api SetString, GetString, SetInt, GetInt, Save...) storing data in MEE6 backend.
• Mee6IAP : a class to handle in-app purchases with a Purchase.
• Mee6Analytics : a class to send analytics events to Game analytics through the MEE6 backend.
• Mee6Platform : a class to get details from the platform. Mobile/desktop and a user_name.
• Mee6NextScene : a class to exit pre-flight scene when underlying system is ready

We offer as weel a dev tool, so you can test the integration of MEE6 SDK with your game.