ASN In-World API 1.1.3

Table of Contents

• Stargate in-world API
  • API Levels
    • Public Commands
    • Private Commands
• Command API
  • Command Channels
  • Public Commands
    • dial
    • stargate status
    • send chatter
    • stargate version
    • stargate address
    • stargate name
    • stargate alias
    • stargate probe
    • lookup
    • directdial
    • stargate emp
    • interference
  • Private Commands
    • raise shield
    • lower shield
    • delete stargate
    • offline stargate
    • online stargate
    • reset stargate
    • restart stargate
    • shutdown wormhole
    • cut wormhole
    • test stargate
    • test stargate outgoing
    • test stargate incoming
    • set name
    • set alias
    • set image url
    • ring speed
    • public listen
    • public output
    • random list
    • wormhole control
    • stargate details
• Event API
  • Event Channels
  • Outgoing Events
    • stargate reset
    • status
    • shield
    • ping
    • dial lookup
    • search lookup
    • chevron <#> encoded
    • chevron <#> engaged
    • chevron <#> locked
    • dial
    • stargate close
    • stargate cut
    • wormhole collision
    • stargate restart
    • incoming wormhole
    • stargate version
    • stargate address
    • random listing
    • stargate delete
    • public listen
    • shield type
    • set name
    • set alias
    • set image url
    • stargate registered
    • emp pulse sent
    • invalid api command passed
    • stargate name
    • stargate alias
    • chatter
    • probe
    • stargate test
    • stargate test incoming
    • stargate test outgoing
    • interference
    • wormhole fataility
    • target shield raised
    • target shield lowered
    • destination
    • prompt
    • top gates
    • gate statistics
    • target wormhole collision
    • http error
    • stargate open
    • clearing buffer
    • chatter saved
    • wormhole extended
    • wormhole control
    • details

Stargate in-world API

The Alteran Stargates expose an in-world Application Programming Interface (API) so scripted objects (DHDs, control units, HUDs, etc) can drive the gate and react to what it's doing.

The API is split into two parts:

• Command API, text commands scripts send to the gate on a specific chat channel.
• Event API, text messages the gate sends out when something happens (dial attempt, shield change, wormhole open/close, etc).

All communication happens over LSL chat channels (not normal /0 chat), so it is invisible to regular user chat.

There are two API levels:

• Public commands can be submitted by anyone.
• Private commands only work for the Stargate's owner.

API Levels

Public Commands

Public commands can be used by anyone within 20m of the gate when sent on the correct command channel.
The gate's owner has no distance limit.

Private Commands

Private commands can only be used by the owner of the Stargate (or objects owned by them).

Command API

Commands you send to the gate to control it.

Command Channels

Send all command strings as plain text on the appropriate chat channel:

• Pegasus command channel: -804000
• Milky Way command channel: -904000

These are non-public chat channels. In LSL, you typically use llRegionSay() or llSay() with the channel set to -804000 or -904000 and the message set to the command string.

Make sure you send the command on the channel that matches the network type of the gate (Pegasus vs Milkyway).

Public Commands

dial

Syntax:

dial|<1/0>|<glyph>

Description:

Dials a single glyph on your Stargate, as if a DHD button had been pressed. The third field is the glyph index:

• Milky Way: 0-38 (39 glyphs total, 0 is point of origin)
• Pegasus: 0-35 (36 glyphs total, including point of origin)

The second field controls the ring animation:

• 1 , inner ring spins before locking the chevron.
• 0 , chevron is locked without spinning the ring.

Scripts typically call this command repeatedly (once per glyph) to perform a complete dial sequence.

stargate status

Syntax:

stargate status

Description:

Requests the current status of the Stargate.
The gate responds on the event channel with a status|<state> event, where <state> is one of:

• idle
• dialing
• outgoing
• incoming
• offline

Use this to synchronise HUDs or control units with the gate's real state.

send chatter

Syntax:

send chatter|<name>|<msg>|<1/0>

Description:

Sends a line of text through an active wormhole to the connected Stargate.

• <name> , label to show as the talker's name (often the avatar or device name).
• <msg> , the text you want relayed.
• <1/0> , whether to request that the wormhole be kept open:
  • 1 , keep the wormhole open after sending.
  • 0 , allow the wormhole to close normally.

prefixing the name with _ should be hidden for users, for use with devices like GDO using encrypted payloads etc.

On the event channel you will receive:

• chatter|<name>|<msg> on the remote gate.
• Optionally wormhole extended if EMP/extension flags apply.

Use this for chat relays, RP consoles, or logging systems that communicate through the active wormhole.

stargate version

Syntax:

stargate version

Description:

Requests the software version of the Stargate.
The gate replies with an event:

stargate version|<version>

Use this to check compatibility before using newer API features or scripts that depend on specific versions.

stargate address

Syntax:

stargate address

Description:

Requests the gate's addresses in both its native and cross-network formats.
The gate replies with:

stargate address|<native>|<cross>

• <native> , address used by other gates of the same type (Milky Way ↔ Milky Way, Pegasus ↔ Pegasus).
• <cross> , cross-network address used when dialing from the other network type.

Use this for address displays, HUDs, and tools that need to show or store the gate's glyph addresses.

stargate name

Syntax:

stargate name

Description:

Requests the gate's current name.
The gate replies with:

stargate name|<name>

This is the same name shown on the website and in various UI elements in-world.

stargate alias

Syntax:

stargate alias

Description:

Requests the gate's alias.
The gate replies with:

stargate alias|<alias>

The alias is the human-friendly label used by /dial keyword searches (e.g. "lex's pad", "zach's house").

stargate probe

Syntax:

stargate probe

Description:

Probes the currently targeted Stargate (outgoing only) and requests environment data from the destination region.
When the probe completes, you receive a probe|... event:

probe|<succ/fail>|<fps>|<time>|<parcel name>|<parcel desc>|<agent count>

Use this to check region performance, parcel information, and avatar load before deciding whether to complete or keep a wormhole open.

lookup

Syntax:

lookup|<net>|<kw>

Description:

Performs a search for a Stargate matching the given keyword and network:

• <net> , network to search:
  • milkyway, pegasus, or
  • * to search across all networks.
• <kw> , search keyword; may match name, alias, region, or address.

The result comes back as a:

search lookup|<succ/fail>|<native>|<cross>|<region>|<pos>|<nw>|<name>|<alias>|<owner>|<sgc id>

event on the event channel.

Use this when you want to find a gate but not necessarily dial it immediately (e.g. building address browsers or map UIs).

directdial

Syntax:

directdial|<net>|<kw>|<2/1/0>

Description:

Searches for a Stargate and attempts to dial it in one step.

• <net> , network selection:
  • milkyway, pegasus, or
  • * to search across all networks.
• <kw> , keyword (name/alias/region/address/SGC-ID).
• <2/1/0> , controls the wormhole behaviour and ring spin:
  • 1 or 0 , normal dial; 1 enables inner ring spin, 0 disables it.
  • 2 , forced wormhole (overrides some normal dialing checks, where allowed).

The lookup result comes via:

dial lookup|<succ/fail>|<addr>|<spin>|<region>|<pos>|<nw>|<name>|<alias>|<owner>|<sgc id>

followed by a dial|... event once the gate actually attempts to lock.

Use this for directory consoles or HUDs where users select a destination and the device dials automatically.

stargate emp

Syntax:

stargate emp

Description:

Sends an EMP pulse through the currently open wormhole, requesting that the wormhole remain open 30 seconds longer .

On success you will see the emp pulse sent event, followed by wormhole extended events as the timer is updated.

Use this in situations where ongoing communication or travel is needed but you do not want to redial.

interference

Syntax:

interference

Description:

Forces the gate into a brief "interference" state, causing the gate to flicker and play a zap sound effect.
A corresponding interference event is emitted on the event channel.

Use this for RP effects (disturbed connections, EM storms) or to visually indicate local interference from other devices.

Private Commands

raise shield

Syntax:

raise shield

Description:

Raises the gate's shield/iris (depending on the selected shield type).
This prevents incoming travel unless something on the far side opens the shield via the API.

The gate broadcasts a shield|1 event and, when relevant, target shield raised events to connected devices.

lower shield

Syntax:

lower shield

Description:

Lowers the gate's shield/iris, allowing incoming travel.

The gate broadcasts a shield|0 event and, when relevant, target shield lowered.

delete stargate

Syntax:

delete stargate

Description:

Deletes your gate from the region and deregisters it.
Before disappearing the gate sends:

stargate delete

on the event channel so linked devices can clean up.

Use this only from owner-controlled tools; the action is permanent. People have been banned for sneaking these as backdoors in otherr products.

offline stargate

Syntax:

offline stargate

Description:

Places the Stargate offline without deleting it.
Offline gates:

• Do not accept incoming connections.
• Cannot dial out.
• Still exist in-world and may retain saved settings.

The gate sends a status|offline event and will behave as if it has lost server connectivity until brought online again.

online stargate

Syntax:

online stargate

Description:

Brings an offline Stargate back online, re-enabling dialing and incoming connections (subject to normal failsafes).

The gate sends a status|idle (or other appropriate) event when it is ready.

reset stargate

Syntax:

reset stargate

Description:

Performs a soft reset of the gate:

• Clears transient state (stuck dials, hung wormholes, etc).
• Keeps most configuration settings (name, alias, image URL, etc).

On completion the gate emits:

stargate reset

This is the preferred first step for troubleshooting a misbehaving gate.

restart stargate

Syntax:

restart stargate

Description:

Performs a hard reset of the gate:

• Resets all core scripts.
• May clear some or all cached settings, reverting to defaults where applicable.
• Takes longer than a soft reset.

On completion the gate emits:

stargate restart

Use this only when a soft reset (reset stargate) does not resolve the issue.

shutdown wormhole

Syntax:

shutdown wormhole

Description:

Gracefully shuts down the currently open wormhole from your side.
This corresponds to a normal gate shutdown (as if the timer expired).

The gate emits:

stargate close

and appropriate status changes. Remote side behaviour is handled by the network backend.

cut wormhole

Syntax:

cut wormhole

Description:

Immediately cuts power to the currently open wormhole, causing an abrupt disconnect rather than a standard shutdown.

The gate emits:

stargate cut

and updates its status. Use this for emergency disconnects or canonical "cut the power now" situations.

test stargate

Syntax:

test stargate

Description:

Runs a full chevron lamp test on your gate.
All chevrons cycle as if dialing, and the gate emits a stargate test event.

Use this to check lamp colours, custom light settings, or to verify that scripts controlling visual chevrons are working properly.

test stargate outgoing

Syntax:

test stargate outgoing

Description:

Simulates an outgoing wormhole without actually dialing a remote gate.

The gate behaves as if it had dialed out successfully and emits:

• stargate test outgoing
• status|outgoing
• Related chevron and open/close events.

Useful for testing displays, effects, or Death System integration without needing a real remote gate.

test stargate incoming

Syntax:

test stargate incoming

Description:

Simulates an incoming wormhole from a remote gate.

The gate emits:

• stargate test incoming
• incoming wormhole|...
• Related chevron and open/close events.

Use this to test shield/iris behaviour, event handlers, or warning systems.

set name

Syntax:

set name|<name>

Description:

Changes the gate's name (shown in the web interface, logs, wormhole messages, etc).

Result is reported via:

set name|<successful/failed>|<reason>

and may also cause a stargate name|<name> event.

Names must be unique enough to avoid confusion and may be subject to length or content checks enforced server-side.

set alias

Syntax:

set alias|<alias>

Description:

Changes the gate's alias, which is used by keyword dialing (/dial <keyword>) and some UI displays.

Result is reported via:

set alias|<successful/failed>|<reason>

Aliases are often informal labels ("home", "hub", "lex's pad"), and may be subject to uniqueness and formatting rules.

set image url

Syntax:

set image url|<url>

Description:

Sets the gate's image URL, used on the web interface and in some in-world displays.

Result is reported via:

set image url|<successful/failed>|<reason>

The URL should point to a 256×256-ish image accessible to the backend web server.

ring speed

Syntax:

ring speed|<speed>

Description:

Sets the inner ring spin speed for Milky Way gates.

• Higher values = faster spin.
• Valid input range is effectively 30-300. Any value you send is clamped by the backend into this range to prevent unstable behaviours.
• The value must be sent before you start dialing (i.e. at the beginning of every custom dial sequence).

This setting affects both visual timing and how long dials take, so choose values that still feel canonical within the allowed range.

public listen

Syntax:

public listen|<1/0>

Description:

Enables or disables the gate's listener on channel 0 for text commands (e.g. /stargate reset, /dial foo):

• 1 , listen on channel 0 (normal behaviour).
• 0 , ignore commands spoken on channel 0.

The gate will report state changes via:

public listen|<1/0>

Note that the gate always listens on its internal API channels; this only affects user-visible chat commands.

public output

Syntax:

public output|<1/0>

Description:

Controls whether the gate prints verbose status messages to channel 0 for nearby avatars:

• 1 , verbose output enabled (dial attempts, status messages, etc).
• 0 , gate runs quietly, only using API/event channels.

The gate reports changes with:

public listen|<1/0>

Use this to keep busy regions' chat logs clean while still allowing scripted devices to track events.

random list

Syntax:

random list|<1/0>

Description:

Controls whether the gate can appear in random dial listings:

• 1 , gate is eligible to appear in random dial lists.
• 0 , gate is excluded from random dialing.

State changes are reported via:

random listing|<1/0>

Note: In regions where Direct Teleport is disabled, random listing may be forced off by the system.

wormhole control

Syntax:

wormhole control|<0/1>

Description:

Sets whether only the owner or admins are allowed to issue wormhole-control commands:

• 0 (default), any user can shut down or cut the wormhole by using the dialog option.
• 1 , only the gate owner may issue commands such as shutdown wormhole or cut wormhole.

Changing this setting also causes a wormhole control|anyone or wormhole control|owner event to be emitted on the event channel.

Use this for RP scenarios where a device needs to be disarmed.

stargate details

Syntax:

stargate details

Description:

Requests a compact snapshot of the gate's current state in a single event.
On success, the gate responds on the event channel with:

details|<status>|<shield>|<name>|<alias>|<address>|<multiverse>|<wormhole control>

Where:

• <status> , current gate status, e.g.:
  • offline
  • idle
  • dialing
  • incoming
  • outgoing (Additional values may be added in future).
• <shield> , current shield/iris state:
  • 0 , shield lowered (open)
  • 1 , shield raised (closed)
• <name> , the gate's configured name.
• <alias> , the gate's configured alias (used by keyword dialing).
• <address> , the gate's primary address string (typically its native glyph/SGC-style address as reported by the network).
• <multiverse> , multiverse-region flag:
  • 0 , region is not flagged as a multiverse region.
  • 1 , region is flagged as a multiverse region.
• <wormhole control> , wormhole-control mode:
  • 0 , "anyone" mode (non-owner users/devices may close connections as allowed).
  • 1 , "owner" mode (only the gate owner/admins may close or cut the wormhole).

Use this command when you need to initialise HUDs, control units, or status displays with all key state in one go, instead of querying each value separately.

Event API

Events the gate publishes when things happen.

Event Channels

Events are sent as plain text on the following channels:

• Pegasus event channel: -805000
• Milky Way event channel: -905000

Scripts typically use llListen() on the appropriate channel and parse the incoming strings.

Outgoing Events

stargate reset

Syntax:

stargate reset

Description:

Emitted when the gate completes a soft reset (via /stargate reset or reset stargate API).
Use this as a signal that transient state has been cleared and the gate is ready again.

status

Syntax:

status|<outgoing/incoming/idle/offline/dialing>

Description:

Announces a change in the gate's overall status:

• idle , gate is online and waiting.
• dialing , dialing sequence in progress.
• outgoing , outgoing wormhole is open.
• incoming , incoming wormhole is open.
• offline , gate is offline or server-disconnected.

Listen to this event to drive UI indicators, warning lights, or automation logic.

shield

Syntax:

shield|<0/1>

Description:

Reports a change in local shield/iris state:

• 0 , shield lowered (open to incoming travel).
• 1 , shield raised (blocked).

This event fires whenever raise shield / lower shield are used or the shield auto-changes.

ping

Syntax:

ping

Description:

Periodic heartbeat from the gate indicating that it has checked in with the backend server and is still alive.

Useful for monitoring tools that watch for gates going silent (offline).

dial lookup

Syntax:

dial lookup|<succ/fail>|<addr>|<spin>|<region>|<pos>|<nw>|<name>|<alias>|<owner>|<sgc id>

Description:

Detailed result from a directdial command:

• succ/fail , whether a matching destination was found.
• addr , address that was used.
• spin , spin mode chosen.
• region / pos , destination region name and coordinates.
• nw , target network (milkyway / pegasus).
• name / alias , destination gate name and alias.
• owner , owner of the destination gate.
• sgc id , unique SGC-style ID for the gate.

Use this to update UI before or during the actual dial attempt.

search lookup

Syntax:

search lookup|<succ/fail>|<native>|<cross>|<region>|<pos>|<nw>|<name>|<alias>|<owner>|<sgc id>

Description:

Result from a lookup command that only searches, without dialing:

• native / cross , the gate's native and cross-network addresses.
• Remaining fields mirror dial lookup.

Use this to populate address browsers, maps, or selection menus without opening a wormhole.

chevron <#> encoded

Syntax:

chevron <#> encoded

Description:

Signals that chevron <#> has lit up during DHD-style dialing (glyph entry).

Useful for syncing ring/chevron animations on external props or displays.

chevron <#> engaged

Syntax:

chevron <#> engaged

Description:

Signals that chevron <#> has locked during an incoming dial sequence.
Use this for effects that should differ between incoming and outgoing sequences.

chevron <#> locked

Syntax:

chevron <#> locked

Description:

Signals that chevron <#> has locked during a long-dial/SGC-style sequence.

This is especially useful for Milky Way SGC-style gates where the inner ring spins between each symbol.

dial

Syntax:

dial <succ/fail>|<region>|<pos>|<nw>|<name>|<alias>|<owner>|<sgc id>|<rot>

Description:

Emitted once the gate attempts to lock an address:

• succ , lock succeeded and a wormhole is established.
• fail , dial attempt failed.

The remaining fields describe the attempted destination, including rotation <rot> for arrival orientation.

Use this event to trigger success/failure effects or to log attempted connections.

stargate close

Syntax:

stargate close

Description:

Emitted when the wormhole shuts down normally (timer expired, remote shutdown, or commanded shutdown).

Use this to turn off effects, clear displays, or reset UI state.

stargate cut

Syntax:

stargate cut

Description:

Emitted when the wormhole is forcibly cut (e.g., via cut wormhole).

Ideal for triggering more abrupt/violent shutdown effects compared to stargate close.

wormhole collision

Syntax:

wormhole collision|<type>|<uuid>

Description:

Indicates that something has touched the gate's event horizon on your side:

• <type> , type of collider (e.g., avatar vs object; exact values are implementation-specific).
• <uuid> , key of the avatar or object that collided.

Use this for proximity sensors, hazard systems, or RP logic that reacts to travellers stepping through.

stargate restart

Syntax:

stargate restart

Description:

Emitted when the gate completes a hard restart (restart stargate or equivalent).

All connected devices should assume their state is invalid and re-query any needed information (name, alias, address, etc).

incoming wormhole

Syntax:

incoming wormhole|<region>|<pos>|<owner name>|<name>|<alias>|<address>|<sgc id>

Description:

Announces that an incoming wormhole has been established:

• region / pos , location of the remote gate.
• owner name , owner of the remote gate.
• name / alias , remote gate identity.
• address , address used.
• sgc id , remote gate SGC-ID.

Use this for incoming warning lights, displays, and Death System / shield logic.

stargate version

Syntax:

stargate version|<version>

Description:

Version information output in response to a stargate version command.

Useful for diagnostic consoles and scripts that need to adapt to different versions.

stargate address

Syntax:

stargate address|<native>|<cross>

Description:

Address information output in response to a stargate address command.

The native and cross-network addresses can be shown on DHDs, address displays, or web-driven devices.

random listing

Syntax:

random listing|<1/0>

Description:

Indicates whether the gate is currently eligible for random dial selection:

• 1 , included in random dial listings.
• 0 , excluded.

Emitted when random list is changed or when system rules force a change.

stargate delete

Syntax:

stargate delete

Description:

Emitted just before the gate deletes itself from the world.

Devices listening for this should clean up any references to that gate.

public listen

Syntax:

public listen|<1/0>

Description:

Indicates the current state of listening on channel 0 for user chat commands:

• 1 , gate is listening on channel 0.
• 0 , channel 0 commands are ignored.

Useful for tools that mirror gate configuration or provide remote configuration UIs.

shield type

Syntax:

shield type|<irisrezzed/shield/disabled>

Description:

Reports a change in shield/iris configuration:

• shield , built-in static shield.
• irisrezzed , rezzed animated shield/iris (requires extra prims).
• disabled , built-in shielding disabled (for 3rd-party shields).

Use this to keep external shield controllers or status displays in sync.

set name

Syntax:

set name|<successful/failed>|<reason>

Description:

Result of a set name command:

• successful , the name was changed.
• failed , the change was rejected; the <reason> explains why (e.g., invalid name, conflict, etc).

set alias

Syntax:

set alias|<successful/failed>|<reason>

Description:

Result of a set alias command, with success/failure and explanatory reason.

Use this for configuration UIs where you need to inform the user why a requested alias was rejected.

set image url

Syntax:

set image url|<successful/failed>|<reason>

Description:

Result of a set image url command.
Common failure reasons include unreachable URLs or invalid formats.

stargate registered

Syntax:

stargate registered

Description:

Emitted when the gate successfully (re)registers with the central backend service.

Indicates that network features (address lookup, direct dialing, statistics, etc.) should now be available.

emp pulse sent

Syntax:

emp pulse sent

Description:

Acknowledges that a stargate emp command has been accepted and an EMP pulse has been initiated.

Typically followed by wormhole extended as the open time is updated.

invalid api command passed

Syntax:

invalid api command passed

Description:

Indicates that a command received on the command channel was not recognised or was malformed.

Use this for debugging scripts or validating that you are sending correctly formatted API strings.

stargate name

Syntax:

stargate name|<name>

Description:

Name output in response to stargate name.

Useful when a device first links itself to a particular gate and wants to show which gate it is controlling.

stargate alias

Syntax:

stargate alias|<alias>

Description:

Alias output in response to stargate alias.

Often used on compact HUDs or DHDs where the alias is more readable than the full name.

chatter

Syntax:

chatter|<name>|<msg>

Description:

Wormhole chatter received from the other side of an active gate.

• <name> , sender name or device label.
• <msg> , the message text.

Names that start with _ are reserved for system or hidden senders and can usually be ignored in user-facing UIs.

probe

Syntax:

probe|<succ/fail>|<fps>|<time>|<parcel name>|<parcel desc>|<agent count>

Description:

Result from a stargate probe command:

• succ/fail , whether the probe succeeded.
• fps , reported simulator FPS at the destination.
• time , reported script time or similar metric (implementation-specific).
• parcel name / parcel desc , parcel information at the landing spot.
• agent count , number of avatars present.

Use this to build "scanner" displays, performance indicators, or auto-safety checks before travel.

stargate test

Syntax:

stargate test

Description:

Emitted when a full chevron test sequence is running (test stargate).

You can use this to temporarily adjust sounds/effects for the duration of the test.

stargate test incoming

Syntax:

stargate test incoming

Description:

Emitted while simulating an incoming wormhole (test stargate incoming).

Treat this like a normal incoming wormhole for purposes of displays and shield logic, but without relying on real remote data.

stargate test outgoing

Syntax:

stargate test outgoing

Description:

Emitted while simulating an outgoing wormhole (test stargate outgoing).

Useful for testing dial-out animations or logging without needing a real target.

interference

Syntax:

interference

Description:

Indicates that the gate is currently experiencing or simulating interference (e.g., EM disturbance).

Often paired with visual flicker/zap effects.

wormhole fataility

Syntax:

wormhole fataility|<type>|<uuid>|<what>

Description:

Reports that the wormhole has killed something, typically via the Death System or unstable vortex:

• <type> , type of target.
• <uuid> , key of the avatar or object.
• <what> , additional context (implementation-specific).

Note: The word "fataility" in the event name is a historical spelling mistake and is intentional; do not correct it in your listeners.

target shield raised

Syntax:

target shield raised

Description:

Indicates that the remote gate's shield/iris has been raised while connected.

Use this to show that incoming travellers at the far side will be blocked.

target shield lowered

Syntax:

target shield lowered

Description:

Indicates that the remote gate's shield/iris has been lowered while connected.

Useful for showing when it is safe to step through.

destination

Syntax:

destination|<region>|<pos>|<rot>

Description:

Reports a change in the active wormhole's destination:

• region , region name or "--" when there is no destination.
• pos , relative or absolute target position.
• rot , rotation/orientation for arrival.

If region is "--", there is currently no valid destination (e.g., idle state).

prompt

Syntax:

prompt|<msg>

Description:

Contains general Stargate chat output meant for user-facing displays or consoles.

Use this to mirror messages that would otherwise appear on local chat when public output is enabled.

top gates

Syntax:

top gates|<name,name,name>

Description:

Returns a comma-separated list of up to 20 of the most popular gates (by usage).

Useful for "Top Gates" displays or fast-travel consoles.

gate statistics

Syntax:

gate statistics|<inc>|<out>|<total>

Description:

Basic usage statistics for the current gate:

• <inc> , number of incoming wormholes.
• <out> , number of outgoing wormholes.
• <total> , total number of connections.

Use this to build statistics displays or diagnostics.

target wormhole collision

Syntax:

target wormhole collision|<type>|<uuid>

Description:

Reports a collision with the event horizon on the connected remote gate, not your local gate.

This allows systems on one side to react to collisions happening on the other side of the wormhole.

http error

Syntax:

http error|<error>

Description:

Indicates an error in HTTP communication between the gate and the backend server (e.g., timeout, invalid response).

Scripts can log or display this to help diagnose connectivity issues.

stargate open

Syntax:

stargate open

Description:

Emitted when the wormhole fully opens and is ready for travel.

Typically follows successful dialing and chevron lock sequences.

clearing buffer

Syntax:

clearing buffer

Description:

Indicates that the gate is clearing its internal buffers and resetting scripts (e.g., full script reset across the gate).

Expect a follow-up stargate restart or similar events; devices should be prepared for brief unavailability.

chatter saved

Syntax:

chatter saved

Description:

Indicates that wormhole chatter has been successfully logged for the target gate.

Use this if you are building systems that care about whether messages were persisted by the backend.

wormhole extended

Syntax:

wormhole extended

Description:

Reports that the wormhole's open time has been extended, usually as a result of stargate emp or an EMP flag on chatter.

Can be used to update countdown timers or status displays.

wormhole control

Syntax:

wormhole control|anyone
wormhole control|owner

Description:

Emitted whenever the wormhole-control mode changes (for example, after a wormhole control|<0/1> command):

• wormhole control|anyone, the gate is in open mode; any user can shut down or cut the active wormhole via dialogs (and compatible API calls).
• wormhole control|owner, the gate is in restricted mode; only the gate owner/admins may shut down or cut the active wormhole.

Use this to keep HUDs, control units, and status displays in sync with the current security mode of the gate.

details

Syntax:

details|<status>|<shield>|<name>|<alias>|<address>|<multiverse>|<wormhole control>

Description:

Emitted in response to the stargate details command, providing a single snapshot of the gate's current state:

• <status> , gate status (e.g. offline, idle, dialing, incoming, outgoing).
• <shield> , shield/iris state:
  • 0 , shield lowered (open)
  • 1 , shield raised (closed)
• <name> , current gate name.
• <alias> , current gate alias.
• <address> , primary address string used for dialing (format may vary by network/configuration).
• <multiverse> , multiverse region flag:
  • 0 , region not marked as multiverse.
  • 1 , region marked as multiverse.
• <wormhole control> , wormhole-control mode:
  • 0 , "anyone" mode (open control).
  • 1 , "owner" mode (restricted to owner/admins).

Listeners can parse this event to initialise or resynchronise their UI with the gate's configuration and current security state without issuing multiple separate queries.