Skip to content
OMXOMX Docs

Trust and limits

Resources are trusted code

Section titled “Resources are trusted code”

A resource is a .NET assembly running inside OMX or the dedicated server, with the same access to the computer as the program itself. Permissions decide which SDK calls a resource may make; they are not an operating-system sandbox. Only install resources you trust.

OMX loads resources from local folders only. It never downloads a resource from a server or runs one automatically: installing a resource is always a deliberate step by the player or the server operator. C# is the only supported resource language.

What the SDK does not do

Section titled “What the SDK does not do”
  • Scenery, map layout, AI traffic, pedestrians and passengers can be read but not changed. OMX does not yet have a stable public way to change them, so the SDK exposes their real state rather than fake objects.
  • Drawing and general-purpose UI are not exposed. Text overlays and declarative panels are the supported way to show things, so resources keep working as OMX’s renderer and interface change.
  • A server cannot place an OMSI bus into another player’s game. A server resource that needs a bus asks that player’s client half, which uses the normal spawn path and stays subject to the server’s content checks.