Stargate Standards of Placement

Table of Contents

• Key Definitions
• General Enforcement Rules
  • ASN Hub Access
  • Avatar Attachments
• Public Access Stargates
  • Quick Reference Checklist
  • Land access
  • Access Control Systems
  • Aerial Placement
  • Visibility & Teleportation
  • Security Systems
  • Public Script Usage
  • Gate Dialling Puzzles
  • Exceptions for Roleplay
• Monitoring & Reporting

Key Definitions

• ASN Hub: The Stargate that represents the entire ASN service.
• GDO: A HUD or handheld device allowing users to dial and interact with Stargates.
• RP (Role Play) Gate: A Stargate used primarily for thematic or storyline scenarios (for example, "space gates" or fantasy realms).
• Random Dialling: A feature enabling the gate to establish random connections across the network.

General Enforcement Rules

These rules apply to all Stargates, whether they allow random or manual dialling.

ASN Hub Access

Blocking the ASN Hub or preventing your gate from connecting to it will result in gate deactivation until fixed.

Avatar Attachments

Stargates should not be worn or attached to avatars; they must be placed in-world.

Public Access Stargates

These are for Stargates that meet the following criteria:

• Are not set to offline.
• Do not have a shield raised.
• Configured to exist in the Random dialling pool (enabled by default; you can deactivate it in Settings → Random).

Quick Reference Checklist

• Use: Use the Stargate to visit and leave (no IDC/GDO).
• Scripting: Public scripts are enabled close to the gate.
• Security: No automatic eject/ban systems within gate range.
• Visibility: The gate is easily spotted from the Telehub or arrival point.
• Land Access: The parcel is open to the public (not group-only or private).
• Aerial Placement: A safe landing mechanism is present if the gate is above ground.

Land access

Rule: Stargates must be placed on a land that is publicly accessible (i.e. not access only land/region).

Exception: Stargates can be placed in private no-access regions that have the experience key "Matter stream" configured as a "Key Experience" in the Region/Estate panel.

Reason: Ensures anyone can visit and use the gate, regardless of group affiliation or land permissions.

Implementation Tips:

• Check your parcel's "About Land" → "Access" settings to confirm that public entry is allowed.
• Check the "Region/Estate" → "Experiences" options to confirm that "Matter stream" is configured if "Allow only residents and groups listed in the access tab" is selected in the "Estate tab".

Access Control Systems

Rule: When an Access Control System, such as an IDC/GDO system, is enabled, which requires the user to be authorised to visit, these Stargates must not appear on the random dial list.

Random can be turned back on after turning off an access control system.

It's strongly suggested that IDC/GDO server developers use the in-world API to set the Stargate to no random when enabling the IDC system.

Exception: If this is a puzzle that no pre-approved user can resolve, a hint for access must be provided over the radio.

Reason: IDC/GDO systems have been leading to negative experiences with using random dials and serve little of a purpose for random dialling.

Aerial Placement

Rule: Do not place Stargates in mid-air unless there is a precise, safe mechanism for travellers to land or disembark.

Exception: [RP] "Space Gates" with "power pods" or other thematic support.

Implementation Tips:

• Provide a platform or teleporter if your gate is above ground level.
• Consider adding "Space Gate" or "[RP]" in the gate name or alias for easy identification.
• For space gates, you can place a 10x10x1 meter invisible platform right under where the event horizon should be to catch visitors.

Visibility & Teleportation

Rule: The Stargate should be visible from the region's telehub or primary landing point.

Reason: It prevents confusion and makes locating the gate easy for new arrivals.

Implementation Tips:

• Do not use teleport routing on the parcel where the Stargate sits.
• If you use teleport routing on the parcel that the Stargate sits on, ensure the user has a direct line of sight.

Security Systems

Rule: Avoid placing Stargates within areas with automatic security or ban systems that teleport or eject users on entry.

Reason: Users risk being expelled immediately upon arrival, rendering the gate unusable.

Implementation Tips:

• Deactivate security orbs in the gate's vicinity.
• Move Stargate or 'secured' zone away from affecting each other.

Public Script Usage

Rule: Stargates must be placed on land where public scripts are enabled.

Reason: Prevents interference with GDOs and other scripted interactions.

Implementation Tips:

• In "About Land" → "Options", confirm "Scripts allowed" is checked for public users.
• If you cannot enable public scripts for the entire region, consider isolating the gate on a dedicated parcel where scripts are permitted.

Gate Dialling Puzzles

Rule: Dialling puzzles or unique interactive mechanisms are allowed but must not be overly hidden or complicated.

Reason: Encourages Stargate play but keeps the gate accessible to casual visitors.

Implementation Tips:

• Provide in-world hints as to why a Stargate may not behave as intended.
• For incoming connections, use radio messages to provide information for access.

Exceptions for Roleplay

If you use a gate in a roleplay setting, clearly mark it with "[RP]" in the gate's name or alias. You may use special rules. Just be sure to communicate these differences to visitors through the gate name.

Monitoring & Reporting

• You can report a gate directly by clicking on it.
• You can find the gate using the ASN Database and report it through that interface.
• You can view tickets against your gates or tickets you've opened against other gates via the SSoP support portal