Hey Construct Team. Sorry to bother.
I would like to ask for a feature request to add expressions for the Access Token and ServerAuthCode on the Google Play plugin and an expression for the Access Token on the Facebook plugin.
The amazing thing about the current Facebook plugin and Google Play plugin is that they already have the prerequisites needed to achieve the features.
So, it may just be a minor get call and editor enhancement for some great new features.
[See screenshot 1].
The benefits to getting these features is that we can extend the Facebook plugin or the Google Play plugin without having to re-create the built-in addons for the Web. I believe the Construct Team recommended this approach, so this might be the best approach.
We could already extend it just by getting the plugin properties but it's also great to have features built-in to enable server-side features.
We could unlock cloud features using the built-in Facebook and Google Play plugins to sync data and lots more, for games.
Construct Team Intervention ::
The developers could make their own like that, like what I did for the mobile platform where I made my own social plugins, the Mobile Google Plus and the Mobile Facebook. But, I've noticed that it is such a waste to re-create or fork the 2 well working web plugins just to enhance its features.
[See screenshot 2].
[See screenshot 3].
Since these are supposed to be main features, I believe with confidence that having these features implemented officially by the Construct Team is the best approach.
Thanks in advance for looking into this.
Facebook and Google Play are two different cases. Since there is only one suggestion filed for both, we cannot track them separately. We have implemented the access token for the Facebook plugin and this has shipped, so we are now marking this feature as shipped. Google Play is a different and more complicated case which needs to be handled separately.
The Google Play plugin actually uses two APIs: the web API and the Android app API (via Cordova). We were forced to implement the Android app API separately since Google disabled access to the web API from Android apps and refused to reinstate it, requiring us to reimplement the plugin with a second API. The web API simply involves methods on a global object (gapi); any third-party addon can simply use this as well and make its own calls, therefore no further extensibility ought to be required.
If you think there still need to be further changes, please file a separate suggestion specific to Google Play, and include the precise technical details of why the above approaches won't work, and exactly which access token available from which APIs you want to use, in both the web and Android API cases.