Custom LGS

What AbstractLgs ownsCopy Anchor Link

AbstractLgs holds everything that does not depend on the wire format of an RGS: the configuration, the registered games, sessions, wallets, bets, the outcome draw, the management endpoints and the standalone server. EngineLgs adds the HTTP routes of the Engine RGS on top. A subclass for another RGS does the same with its own routes.

Implement a subclassCopy Anchor Link

A subclass provides three members:

import { AbstractLgs, LgsError, type LgsOptions } from "@slot-engine/lgs"
import { Hono } from "hono"

export class MyLgs extends AbstractLgs {
  readonly name = "MyRgs"
  protected readonly routePrefixes = ["/api/*"]

  constructor(opts: LgsOptions) {
    super(opts)
  }

  protected rgsRouter(): Hono {
    const app = new Hono()

    app.post("/api/spin", async (c) => {
      const { session, mode, bet } = await c.req.json()
      try {
        const { wallet, bet: round } = await this.placeBet(session, mode, bet)
        return c.json({ balance: wallet.amount, events: round.state, win: round.payout })
      } catch (error) {
        if (error instanceof LgsError) return c.json({ code: error.kind }, 400)
        throw error
      }
    })

    return app
  }
}

The subclass runs standalone with start() and inside the panel through the lgs option, like EngineLgs.

OperationsCopy Anchor Link

The session operations take a session ID and return storage records. Every operation of one wallet runs after the previous one has finished. replay and createReplay need no session and touch no storage.

The configuration is available as this.bets, this.balance, this.languages, this.currencies, this.defaultLanguage and this.defaultCurrency, with amounts as six-decimal integers.

ErrorsCopy Anchor Link

Every operation throws an LgsError with a kind. The subclass maps the kind to the status and the error format of its RGS.

EngineLgs keeps its mapping in one table, ENGINE_ERRORS, which turns each kind into an Engine error code and status.