Difference between revisions of "* Initialisation and Core"
Line 2: | Line 2: | ||
'''Supported platforms:''' html5<br/> | '''Supported platforms:''' html5<br/> | ||
'''Available since:''' Gideros 2018.3<br/> | '''Available since:''' Gideros 2018.3<br/> | ||
− | === Description === | + | === <translate>Description</translate> === |
<translate><br /> | <translate><br /> | ||
You need to do two things to target Facebook Instant Games:<br /><br /> | You need to do two things to target Facebook Instant Games:<br /><br /> | ||
Line 28: | Line 28: | ||
FBInstant.player.getID()<br /><br /> | FBInstant.player.getID()<br /><br /> | ||
To help do this you could create a variable called FBInstantAPI and set it to true once startGameAsync has been resolved - then only call other API commands if FBInstant is true and then if FBInstantAPI is true.</translate> | To help do this you could create a variable called FBInstantAPI and set it to true once startGameAsync has been resolved - then only call other API commands if FBInstant is true and then if FBInstantAPI is true.</translate> | ||
− | === Examples === | + | === <translate>Examples</translate> === |
'''Initialisation and removal of the Facebook loading progress indicator.'''<br/> | '''Initialisation and removal of the Facebook loading progress indicator.'''<br/> | ||
<source lang="lua"> | <source lang="lua"> | ||
Line 42: | Line 42: | ||
{|- | {|- | ||
| style="width: 50%; vertical-align:top;"| | | style="width: 50%; vertical-align:top;"| | ||
− | === Methods === | + | === <translate>Methods</translate> === |
[[Special:MyLanguage/FBInstant.canCreateShortcutAsync|FBInstant.canCreateShortcutAsync]] ''<translate>Returns whether or not the user is eligible to have shortcut creation requested.</translate>''<br/> | [[Special:MyLanguage/FBInstant.canCreateShortcutAsync|FBInstant.canCreateShortcutAsync]] ''<translate>Returns whether or not the user is eligible to have shortcut creation requested.</translate>''<br/> | ||
[[Special:MyLanguage/FBInstant.checkCanPlayerMatchAsync|FBInstant.checkCanPlayerMatchAsync]] ''<translate>Checks if the current player is eligible for the matchPlayerAsync API.</translate>''<br/> | [[Special:MyLanguage/FBInstant.checkCanPlayerMatchAsync|FBInstant.checkCanPlayerMatchAsync]] ''<translate>Checks if the current player is eligible for the matchPlayerAsync API.</translate>''<br/> | ||
Line 66: | Line 66: | ||
[[Special:MyLanguage/FBInstant.updateAsync|FBInstant.updateAsync]] ''<translate>Informs Facebook of an update that occurred in the game.</translate>''<br/> | [[Special:MyLanguage/FBInstant.updateAsync|FBInstant.updateAsync]] ''<translate>Informs Facebook of an update that occurred in the game.</translate>''<br/> | ||
| style="width: 50%; vertical-align:top;"| | | style="width: 50%; vertical-align:top;"| | ||
− | === Events === | + | === <translate>Events</translate> === |
− | === Constants === | + | === <translate>Constants</translate> === |
|} | |} |
Revision as of 07:29, 24 August 2018
Supported platforms: html5
Available since: Gideros 2018.3
Description
You need to do two things to target Facebook Instant Games:
1. Tick the Facebook Instant Game tickbox when exporting to HTML5, you can also specify the percentage indicator that the game will show it has loaded before you take control.
2. Require the FBInstant library code, see the example below.
You can upload, debug and test your game by creating a player and uploading to Facebook servers as a game. The player will interact with the Gideros Studio similar to any other player.
The only restriction with the player is that it only works on the computer viewing the html5 game (localhost) - this would normally rule out actual phones but there is a workaround for Android:
1. Connect your Android phone to your computer using ADB.
2. Type in this command in a command console shell (Windows) or terminal (Mac): adb reverse tcp:15001 tcp:15001
3. The Android device now will see the Gideros Studio when testing the game when a player is launched from within Facebook Messenger.
Please refer to the <a href="https://developers.facebook.com/docs/games/instant-games/getting-started/quickstart">original Facebook documentation</a> for more information about testing and uploading.
Please note that the offical Facebook documentation mentions having to wait for initializeAsync, with Gideros this has already been done for you before your game starts.
It is very important that the only the following API calls are made before startGameAsync has resolved:
FBInstant.getSDKVersion()
FBInstant.initializeAsync()
FBInstant.getPlatform()
FBInstant.setLoadingProgress()
FBInstant.getSupportedAPIs()
FBInstant.quit()
FBInstant.onPause()
FBInstant.player.getID()
To help do this you could create a variable called FBInstantAPI and set it to true once startGameAsync has been resolved - then only call other API commands if FBInstant is true and then if FBInstantAPI is true.
Examples
Initialisation and removal of the Facebook loading progress indicator.
pcall(function() FBInstant=require "FBInstant" end)
if FBInstant then
FBInstant.startGameAsync(function()
print("Loading screen removed")
FBInstantAPI=true
end)
else
print("FBInstant not loaded")
end
MethodsFBInstant.canCreateShortcutAsync Returns whether or not the user is eligible to have shortcut creation requested. |
EventsConstants |