GDevelop

Engine guide

GDevelop

No-code, exports directly to web

GDevelop exports HTML5 as a static folder with index.html. You integrate the SDK by dropping a script tag in the exported template and firing JS from JavaScript events inside GDevelop's editor.

1. Add the SDK to the export

After File → Export → Web upload, open the exported index.html and add before </head>:

<script src="https://pixlland.com/sdk/v1/pixlland.js" defer></script>

Or use GDevelop's Game properties → Additional HTML header so every export already ships with it.

2. JavaScript event at scene start

Scene events → Add event → JavaScript code:

if (window.PixllandSDK) {
  window.PixllandSDK.init().then(() => {
    window.PixllandSDK.gameLoadingFinished();
    window.PixllandSDK.gameplayStart();
  });
}

3. Fire happyTime every frame

In the same scene, add a JavaScript code event inside a Conditions: true (every frame) branch:

if (window.PixllandSDK) {
  const dt = runtimeScene.getTimeManager().getElapsedTime() / 1000;
  window.PixllandSDK.happyTime(dt);
}

4. Commercial break between levels

// Trigger on "Change to scene" actions:
if (window.PixllandSDK) {
  window.PixllandSDK.gameplayStop();
  window.PixllandSDK.commercialBreak().then(() => {
    window.PixllandSDK.gameplayStart();
  });
}

Common pitfalls

• MultiplayerP2P / CloudStorage plugins. They point at their own backends which our iframe sandbox doesn't whitelist. Swap CloudStorage for Pixlland data API.
• Mobile HTML5 export vs Desktop. Both land on our iframe; pick whichever performs better. We serve the same artifact on both device classes.