Sud GIP interactive game platform
Tips
- On the client side, the game and the app are mutually finite state machines with no coupling logically.
- The app can selectively respond to the state sent by the game finite state machine
ISudFSMMG, and make corresponding interactions in the native or do nothing.- The app can selectively synchronize the app state with the app finite state controller
ISudFSTAPP, and games can make corresponding feedback and interactive adjustments, or do nothing.- Since the game server is deployed in the nearest region, if the app is to be launched in multiple regions, it is necessary to generate an app message for each region.
Quick client access
Client documentation
Download the client SDK
Download the client demo
FAQ
Multiple languages for game
- Multiple Languages for Game loadMG language parameters
Tips
- On the server side, JWT standard is recommended for the authentication and data exchange between the game server and the app server. Any other customized methods can also be used.
- Call
SudMGPAuthto implement JWT standard. The app server can retain the original login authentication logic of the client side, and penetrate the login state to the server side, so that the authentication and data exchange between the game server and the app server are all based on the user's login behavior, which maximizes the security of the data. Besides, the app server does not need additional permanent services to deal with complex mapping relations (such as the corresponding relation between the real UID and the virtual UID provided to SudMGP). In theory, only a single point service without storage is required, and the information is actually safely stored in the JWT token.- Customized methods: The app server can customize the generation and exchange method of any long-term or short-term tokens, without calling
SudMGPAuth.