Godot 4.3+ plugin for integration of the latest version of Google Play Game Services SDK.
If you want to download the plugin for a previous version of Godot 4.x, use the branch selector in the repository. For Godot 3.x versions, look here!
- Forewords
- Contributing
- Install the plugin
- The Demo project
- Building the plugin yourself
- Documentation
- Troubleshooting
- Contact me
The whole project started as a collaboration with Rafa Laguna, and this plugin is the updated version of the old one for Godot 3.5+.
With Godot 4.2+, the way android plugins work has changed, so I had to update this plugin to match the new requirements. Now there's only one editor plugin (this one), instead of having two separate plugins like before, one android plugin and one godot plugin.
Thanks also to the Godot Foundation for allowing me to host this plugin in their organization. I'm still the maintainer of the plugin, but it was moved to this repository on October 2024.
If you want to contribute, please read the CONTRIBUTING.md file.
Using the plugin requires downloading the assets in the releases section of the repository and following the steps described there to copy the plugin folder to your Godot project.
There is a Godot Project in the demo folder of the repository. It contains its own documentation on how to use it, so please, take a look if you want to see how I implemented the basic features of this plugin in a real Godot game.
If you want to modify something in the code or collaborate, and then you want to try your changes, you can also build the plugin files for yourself.
To download the repository you can use git to clone it, or just download the repository in a zip file from GitHub.
After making your changes, or if you just want to manually build the plugin, follow these steps. In a terminal window, navigate to the project's root directory and run the following command:
./gradlew assemble
The output files can be found in plugin/demo/addons. The plugin itself, that you can copy to your project to use, is in the plugin/demo/addons/GodotPlayGameServices, just copy the whole GodotPlayGameServices folder into the addons folder of your Godot project and activate the plugin in Project -> Project Settings... -> Plugins
You can also use the included Godot demo project to test the built Android plugin.
- Open the demo in Godot (4.2 or higher)
- Navigate to
Project->Project Settings...->Plugins, and ensure the plugin is enabled - Follow the steps on Configuring the plugin
- Install the Godot Android build template by clicking on
Project->Install Android Build Template... - Connect an Android device to your machine and run the demo on it
Before configuring the plugin, you have to create a Google developer account, which involves a one time payment to google, and then you must create a game. The explanation on how to do all of these is out of the scope of this documentation. Please refer to Google for those steps.
Once that's done, you will need to create some achievements and leaderboards in your game, which will generate some IDs. You will need those IDs later in your game, but for the plugin, the one that's important is the Game ID, which can be found in your game configuration, in the Google Dev Console:
In order to make the configuration easier, the plugin adds a new dock to the bottom panel of your Godot editor, where you can add the Game ID. Once you click on the submit button, the configuration will be saved and loaded every time you reopen the editor.
⚠️ Beware of not changing the Game Id and submitting by mistake, since that will break the integration with Google Game Services.
To be able to use the plugin, you need to use a custom gradle build. Please note that The steps to do so, are explained with detail in the Godot Documentation.
An additional configuration has to be made in order to connect with Google Game Services. In the Google App, you have to configure an Android OAuth client. Google describes the steps here, but at some point you have to introduce the package name of your game, as well as the SHA-1 of your signing key. Both things need to be introduced also in the Godot Export configuration for Android:
You can find the technical documentation of the kotlin code in the GitHub Pages of this repository. It's generated with Dokka from the KDocs documentation on the source code.
The GDScript code is documented in the code itself, so you can access it via the Godot Editor. I'm working to publish it in a static webpage too.
Google provides lots of documentation for integrating with Google Play Game Services, creating an app, etc.
The main page for Game Services is this one. There you can find the Guides section and the Reference section, which contains the technical documentation of their API.
When it comes to Google Play Console, the main page is here, but the Google Play Game Services documentation also provides a good setup guide here.
Here I will add common problems and possible solutions, if any. Thanks to all the people that have opened issues with their problems, so now we can help others in the future to avoid common pitfalls.
This is one of the major problems when testing and using the plugin. In order to properly use Google Play Games Services, you have to:
- Create your app of type
gamein your Google Play Console. - Add and configure the Games Services in your Google Play Console.
- This involves creating your game assets such as achievements, leaderboards, etc
- This also, AND MOST IMPORTANTLY, includes adding credentials.
- Create the credentials in your Google Cloud and link them in your game in your Google Play Console.
- Make sure that you sign your
.aabor.apkwith the correct credentials (in Godot AND in the Play Store!)
Creating and linking credentials is a source of confusion, as the process includes many steps. Please refer to the Google docs for further information about creating credentials.
You will know that your app is failing due to authentication problems, because you will see a message like this in the adb logs:
**** APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES
**** DEVELOPER_ERROR
**** This is usually caused by one of these reasons:
**** (1) Your package name and certificate fingerprint do not match
**** the client ID you registered in Developer Console.
**** (2) Your App ID was incorrectly entered.
**** (3) Your game settings have not been published and you are
**** trying to log in with an account that is not listed as
**** a test account.
**** (4) A server auth code was requested, but an incorrect client
**** id was provided. The client id for server auth codes should
**** be the client id for the game server (not the android app).
****
**** To help you debug, here is the information about this app
**** Package name : your.package.name
**** Cert SHA1 fingerprint: AA:AA:11:AA:A1:11:11:11:11:A!:1A:AA:A1:11:1A:A1:1A:A1:11:1A
**** App ID from manifest : 111111111111
****
**** Check that the above information matches your setup in
**** Developer Console. Also, check that you're logging in with the
**** right account (it should be listed in the Testers section if
**** your project is not yet published).
****
**** For more information, refer to the troubleshooting guide:
**** http://developers.google.com/games/services/android/troubleshooting
****
⚠️ This error log can also appear if you have not properly configured the plugin to use your Game id, which is actually in the logs (App ID from manifest). Make sure you followed the Configuring the plugin steps if you see this error in the logs.
To solve this problem, you have to create an OAuth2 Android Client in your Google Cloud that matches the package name of your game AND the SHA1 certificate of any keystore you are using to sign your app.
You can create as many credentials as you want, so usually my recommendation is to have three credentials:
- One credential for the debug keystore, to use while developing and testing the debug build variant.
- One credential for the release keystore, to use while testing the release build variant.
- One credential with the Play Store certificate, to use when you publish your app to the Play Store.
This is how it looks in Google Cloud (ignore the web auth client autogenerated by Google):
And this is how it looks in the Google Play Console:
The one that causes more problems is the client with the Google Play Store credentials. The process to sign your app and publish it to the Play Store generates a new public certificate that you don't control, and this is the one that many people is missing, and the most important one. To be able to locate the SHA1 of this certificate, you can see it in the Release > Setup > App signing section of your Play Console:
Creating the OAuth2 Client in your Google Cloud and linking it to a new credential in your App in your Google Play Console, will solve the problem, and you will be able to log in from your game.
If you have any questions or want to propose changes, features, or found a bug, please feel free to open an issue.
I try to answer in the same day and provide all the help I can, even if it's out of scope of the plugin, like guiding over some Google configurations, etc.
Please, be kind and respectful when creating issues.