@zaisma/game-server

Write a game server once; run it in Zaisma's rooms or on your own Node server. Rooms, players, state sync, chat, the game's database and its requests behave the same in both.

To play your multiplayer game on your own computer before you upload it, run npx @zaisma/game-server@1 play-locally in the game's folder (or npx @zaisma/cli play-locally, which runs it). It serves the game, runs its game server, and opens a test bench: each player on Zaisma's own game page, guests until they sign in with a name, and a dev bar whose Add a player opens another tab as a new player, with passes signed by a key of its own, so two tabs play together with no account, key or internet. Flags: [folder], --port 4800, --game <slug>, --on-network, --no-open, --json; Zaisma's README has the whole of it under "Play it on your own computer".

// server.ts
import { defineGameServer } from "@zaisma/game-server";

export default defineGameServer({
  ticksPerSec: 20,
  setup: () => ({ scores: {} }),
  onJoin: (state, who, room) => ({ ...state, scores: { ...state.scores, [who.id]: 0 } }),
});

On your own server (Node 22.18 or later):

npx @zaisma/game-server@1 ./server.ts --game <your-game-slug> --port 8080

or from code:

import { startServer } from "@zaisma/game-server/node";
import gameServer from "./server.ts";

const running = startServer({ gameServer, gameSlug: "your-game-slug", port: 8080 });
// Later: await running.close(); every room saves first.

For the fast lane (WebTransport, where latest_only sends go as datagrams), install its two optional packages beside the runner and give it all three of --webtransport-port, --certificate-path and --certificate-key-path (startServer({ webtransportPort, certificatePath, certificateKeyPath })):

npm install @fails-components/[email protected] @fails-components/[email protected]
npx @zaisma/game-server@1 ./server.ts --game <your-game-slug> --port 8080 --webtransport-port 443 --certificate-path fullchain.pem --certificate-key-path privkey.pem

Games join it with Zaisma.joinRoom({ serverUrl, transport: "webtransport" }), and fall back to the WebSocket by themselves where it doesn't connect.

A mistake in your game server's code becomes a coded error in the game's logs, never a silent success, and the Node runner behaves the same as Zaisma's rooms. Versions follow semver: within 1.x the package only gains things.

• The game server, handler by handler: the "Game servers" section of the README and docs/DEVELOPER-API.md.
• Every name and option follows docs/NAMING.md.

MIT licensed.