Home - myflashlab/GameServices-ANE GitHub Wiki

Thanks for your interest in our Games Services Air Native Extension. This Wiki includes all the information you would need to setup these services in your AIR game. Before you start with GamesServices, you need to know that this ANE depends on the GoogleSignIn ANE and you need to implement the GSignIn ANE in your project because GamesServices will no longer take care of user authentication. User authentication happens in the GoogleSignIn ANE and you will not be able to use GamesServices without it. If this is your first time trying Google Games Services, please take your time and first read the Understanding Google Play Games Services concepts section to get an idea of what you can do with this ANE. The second step is to setup your Google Play Games Services in your Google Play Developer Console to receive your OAuth2 client ID which you should later enter into your Air manifest .xml file. This is required so your game can understand how to connect to your game settings. The third step is to configure your services with the data you will need in your app. After you configured your game details, the fourth step would be to test-run your game by adding test users to your console.

After going with the above four steps, you will be ready to publish your game and go live.

NOTE: Whenever you feel comfortable, you may find reading this post very helpful. Google has written a very detailed list of best practices on how you should treat the logic of your game when using the Games Services.

Get started with Games Services

01 Understanding Google Play Games Services concepts
02 Setting up Games Services in Google Play Developer Console
03 Configuring Games Services based on your game needs
04 Testing your app in the development phase