Skip to main content
Resource name:

Server exports

Server exports are trusted resource-to-resource calls. They do not apply player ACE checks. Never proxy untrusted client input directly into them.

GetDisplays()

GetDisplay(displayId)

RefreshDisplay(displayId)

SetDisplayPage(displayId, pageId)

The receiving client applies the page only when it is in that display’s saved pageOrder.

SetDisplayServiceFilter(displayId, serviceFilter)

Client exports

Client exports act on the local client’s synchronized, sanitized display/cache state.

GetDisplays()

Returns an array sorted by display name. Treat returned display tables as read-only.

GetDisplay(displayId)

Returns the local display table or nil. Treat it as read-only.

RefreshDisplay(displayId)

Returns no value. If that display has a local active DUI, its state is resent. It does not request server or CAD data.

SetDisplayPage(displayId, pageId)

Returns true when an active local renderer exists and the page is in its saved order; otherwise false. The change is local and not persisted.

OpenDisplayMenu()

Returns false when placement is already active; otherwise true after opening the non-actionable loading state and requesting a fresh server permission snapshot. Actionable menu opening is asynchronous and still requires the configured menu administrative permission.

Supported client observation events

External client resources may listen to these events. Do not trigger the synchronization events to impersonate server state.

Display configuration lifecycle

These are safe to listen to. External resources should mutate displays through supported server exports, not trigger these client events.

Local object lifecycle

Object handles are client-local and can become invalid after the event.

Open the menu

This local event is safe for another client resource to trigger. It performs the same server permission handshake as the command/export.

Runtime page broadcast

The receiving renderer still requires the page to exist in the display’s saved pageOrder.

Display table

Persisted display fields include:

Internal network events

The resource also registers internal synchronization/request events such as:
These are implementation protocol, not a stable public API. Player requests are permission checked, proximity checked where applicable, validated, and rate limited. External resources should not trigger them. See DUI Message Protocol for the browser boundary.