Engine Types and Aliases

Engine declarations

Import from xray16 when you want names that match the Lua binding dump.

import { game_object, level } from "xray16";

export function isActorVisible(object: game_object): boolean {
  return object.see(level.get_target_obj());
}

Declarations describe the TypeScript-visible API shape. C++ engine bindings define runtime behavior, so check the engine source when declaration syntax is ambiguous.

Browse the full surface in the engine types API reference.

Aliases

Use xray16/alias when application code benefits from shorter, more TypeScript-friendly names.

import type { GameObject, ServerObject, Vector } from "xray16/alias";

export interface SpawnPoint {
  object: ServerObject;
  position: Vector;
  owner: GameObject;
}

Aliases erase at build time. Virtual enums fold in game builds with the inline plugin; Jest and Node can import their runtime objects from alias.js.

Browse the exported names in the alias API reference.

Refreshing binding dumps

To compare declarations with a live engine, run the game engine with -dump_bindings, open the generated scriptbindings_*.txt files in the user data directory, and diff them against this package's declarations.

Next steps

• Use macros and shared lib for compile-time helpers and shared values.
• Use testing when running script code under Node.