Skip to content

Preview tool

AI Summary

A short gist of this page, generated for you.

Powered by AI. Summaries can miss nuance — when in doubt, read the page.

The preview in the Developer Portal runs your uploaded build the way it will run on Funox, and shows you exactly which SDK calls it makes. Use it before every submission.

#Open the preview

  1. Sign in to the Developer Portal.
  2. Upload your build with Submit Game, or open a game you already uploaded.
  3. On the game's page, play the build in the Preview panel.

#The SDK checklist

The game's page has a checklist with four items:

Check Ticks when your build calls
SDK initialization FunOxSDK.init()
Round or level begins FunOxSDK.gameplayStart()
Round or level ends FunOxSDK.gameplayStop()
Ad break triggered FunOxSDK.commercialBreak()
  • Each item ticks itself the first time your build makes the call. They cannot be ticked by hand.
  • All four must be green before you can submit the build.
  • The checklist starts again for every new build you upload.

#The live feed

The same page has a feed of every SDK call your build makes, newest first. Click an entry to see the data it sent.

Use it to spot:

  • a call that never happens — for example a missing gameplayStop() before the game-over screen
  • a call at the wrong moment — gameplayStart() firing on the loading screen
  • wrong data — a trackEvent() with the wrong properties, or a save that is larger than you expected

#When to use it

  • After your first integration — confirm that init() appears.
  • Before each submission — play one full round and check that the four calls fire at the right moments.
  • When QA reports an SDK problem — reproduce it and watch the feed.

#What the preview does not show

  • Real ad inventory. Whether an ad actually fills depends on the player and the moment, so commercialBreak() may resolve with shown: false in the preview. The checklist only needs the call to be made.
  • Real players. For anything that depends on who is logged in, also test with the local test page.

#Testing without uploading

For quick iteration on your own machine, run the game on localhost. The SDK switches to standalone mode and every call still works.