The TestClock is meant for debugging interactions in excalibur that require precise timing to replicate or test

Hierarchy

Constructors

Properties

fpsSampler: FpsSampler
tick: ((elapsedMs: number) => any)

Type declaration

    • (elapsedMs: number): any
    • Parameters

      • elapsedMs: number

      Returns any

Methods

  • Get the elapsed time for the last completed frame

    Returns number

  • Run a number of steps that tick the clock, optionally specify an elapsed time in milliseconds

    Parameters

    • numberOfSteps: number
    • Optional overrideUpdateMs: number

    Returns void

  • Schedule a callback to fire given a timeout in milliseconds using the excalibur Clock

    This is useful to use over the built in browser setTimeout because callbacks will be tied to the excalibur update clock, instead of browser time, this means that callbacks wont fire if the game is stopped or paused.

    Parameters

    • cb: (() => any)

      callback to fire

        • (): any
        • Returns any

    • timeoutMs: number = 0

      Optionally specify a timeout in milliseconds from now, default is 0ms which means the next possible tick

    Returns void

  • Parameters

    • handler: ((e: unknown) => any)
        • (e: unknown): any
        • Parameters

          • e: unknown

          Returns any

    Returns void

  • Start the clock, it will then periodically call the tick(elapsedMilliseconds) since the last tick

    Returns void

  • Manually step the clock forward 1 tick, optionally specify an elapsed time in milliseconds

    Parameters

    • Optional overrideUpdateMs: number

    Returns void

  • Parameters

    • Optional overrideUpdateMs: number

    Returns void