JavaScript

The JavaScript SDK is @mugon/sdk. It is what every other SDK builds on, and it works on its own for games written in TypeScript or JavaScript.

With a bundlerCopy Anchor Link

The typescript template is a Vite project. The relevant parts:

// src/index.ts -- the SDK must be imported first
import { Mugon } from "@mugon/sdk";

Mugon.start(async (ctx) => {
  ctx.on("connect", (peerId) => console.log("peer connected", peerId));
  // ... create your game, then:
  ctx.progress.done();
});

// package.json
"scripts": { "build": "vite build --base ./ --outDir dist" }

Without a bundlerCopy Anchor Link

The minimal template has a plain index.html and script. The SDK is loaded as the first script, which makes the global Mugon available:

<script src="./mugon.iife.js"></script>
<script src="./index.js"></script>

Things to get rightCopy Anchor Link

• Build with a relative base (--base ./). The platform serves your game from a folder, not from the root of a domain, so /assets/x.js style absolute URLs won't resolve.
• Keep the SDK first. If your bundler splits chunks, the entry chunk must contain the SDK import before anything that loads big files. mugon publish warns if the first script of index.html doesn't contain the SDK.
• Call ctx.progress.done() when the game is playable, unless your callback returns then.

In this sectionCopy Anchor Link

• Mugon.start and the context: everything your game gets from the platform.
• Loading progress: feed the loading overlay.
• The file proxy: how your game's files are loaded and cached.
• SDK versions: how the version you build with maps to the platform's behaviour.