Sharing and embedding your game

Every published game has a link anyone can open. On the game's page in Play, the Share button copies three versions of it — the plain link, one that skips the sign-in page, and the code to put the game on your own website.

The play link

https://play.galatrix.com/play/artifact-explorer-nexus-spawn

The last part is your game's name, lowercased with hyphens in place of spaces and punctuation. It is generated from the title when the game is first created and then stays put, so a link you handed out a year ago keeps working even after you rename the game.

The older form, with the game's id in the same position, also still works:

https://play.galatrix.com/play/6204f2b5-580f-4682-9a11-1117150dfa68

Both open the same game and land in the same servers — nobody is split off into a separate copy of the world by which link they followed.

Add ?room=<id> to pin a link to one live server, which is what the Invite button next to each server in the list copies. Use it to send someone to the game you are in right now rather than to whichever server has space.

Instant join

https://play.galatrix.com/play/artifact-explorer-nexus-spawn?autologin=1

autologin=1 means whoever opens the link plays immediately. Someone with an account plays as themselves; someone without one plays as a guest, with no sign-up and nothing to fill in.

Without the parameter, a visitor who is not signed in is offered sign-in first. That is the better default for a link posted somewhere public — it is your game's best chance to turn a visitor into an account — and the wrong one for a link you hand to a specific person so they can join you now.

What a guest can do:

	Guest	Account
Play any published game	yes	yes
Keep game progress	in their own browser	on the platform, on any device
Chat	no	yes
Earn XP, coins, badges	no	yes
Customize an avatar	on that device, and other players see a standard character	yes, seen by everyone

A guest's game progress lives in their browser, which means it is per-device and does not follow them to an account if they sign up later. A name they chose for themselves does carry over. Clearing browser data loses guest progress, so if your game has anything long-running to save, say so on the way in.

Putting your game on your own site

The Copy embed code share option gives you an iframe to paste into any page:

<iframe src="https://play.galatrix.com/play/artifact-explorer-nexus-spawn?embed=1"
  title="Artifact Explorer: Nexus Spawn"
  width="960" height="540"
  allow="fullscreen; pointer-lock; gamepad; autoplay; xr-spatial-tracking"
  allowfullscreen
  style="border:0; border-radius:12px; max-width:100%"
></iframe>

Visitors to your site play the game in place, without leaving the page, and they share servers with everyone playing it on Galatrix.

The allow list is not optional decoration. A browser hands an embedded page only the capabilities the embedding site grants it, and pointer-lock is the one that matters most: without it the visitor can walk but can never turn the camera, which reads as a broken game rather than a missing permission. fullscreen covers the fullscreen button and the touch controls, gamepad covers controllers, and autoplay lets game sound start without a click first.

What changes inside a frame

Browsers keep a site's stored data separate for every site that embeds it. So a visitor arrives on your page as a fresh guest, even if they are signed in to Galatrix in another tab, and the guest they are on your site is a different one from the guest they are on somebody else's. That is why embed=1 implies instant join: the game opens rather than asking for an account first.

They can still get an account without leaving your page. Sign Up in the lobby header opens the ordinary Galatrix sign-in page, right there in the frame, and signing in works from it. Exactly one step happens elsewhere: Continue with Google opens a small window, because Google refuses to display its sign-in page inside somebody else's frame. When they finish there, the game they are already looking at becomes their account — no reload, no lost place. A browser set to block pop-ups will stop that window; the page says so and they can allow it or use a password instead.

Practical consequences for an embedded game:

• treat every arriving visitor as a guest, so do not build the embedded experience around chat or badges;
• a guest's game progress is saved per visitor per site, in their browser, and signing in does not carry it over — only a name they chose for themselves does;
• plays from your site count toward your game's play count like any other.

Sizing it

The snippet uses a fixed size with max-width:100% so it never overflows a narrow page. For a frame that keeps its shape at any width, wrap it instead:

<div style="position:relative; width:100%; aspect-ratio:16/9">
  <iframe src="https://play.galatrix.com/play/artifact-explorer-nexus-spawn?embed=1"
    title="Artifact Explorer: Nexus Spawn"
    allow="fullscreen; pointer-lock; gamepad; autoplay; xr-spatial-tracking"
    allowfullscreen
    style="position:absolute; inset:0; width:100%; height:100%; border:0"
  ></iframe>
</div>

Give it real room. A game in a 300-pixel-wide box is a game nobody plays twice.