Publishing Games

G3Engine makes it effortless to publish your game across multiple platforms. With one click, export your creation to X/Twitter, Telegram Mini Apps, standalone web URLs, and more.

Publishing Overview

When you publish a game, G3Engine:

Serializes your scene to JSON format
Uploads to decentralized storage (Arweave via Irys)
Generates a permanent URL for your game
Creates platform-specific metadata (Twitter Player Cards, Telegram manifests, etc.)
Returns a shareable link instantly

Your game becomes playable directly in social media feeds, messaging apps, or standalone browsers.

The Publish Button

Complete your game in the G3Engine editor

Click Publish in the Top Bar (top-right corner)

The Publish Modal opens

Choose Your Platform

The modal displays 6 publishing destinations:

🐦 X (Twitter) - Popular

Publish as a Twitter Player Card

Game plays inline in Twitter feeds

No app download required

✈️ Telegram

Deploy as Telegram Mini App

Embedded in Telegram chats

Full-screen WebGL experience

🟠 Reddit

Embed in Reddit posts

Playable widget in threads

🟣 Farcaster - Web3

Share as Farcaster Frame

On-chain social gaming

🔵 Base App - Web3

Deploy to Base ecosystem

Optimized for Base network

🌐 Web (URL)

Standalone shareable URL

Works anywhere (Discord, email, websites)

Click a platform card to select it. The card highlights with a purple border and checkmark.

Publish

Click 🚀 Publish button (bottom-right)

A loading spinner appears with “Publishing…”

Behind the scenes:

Your scene serializes to JSON
Assets upload to Arweave (permanent, decentralized storage)
Platform-specific metadata generates
Permanent URL creates

Success screen appears (10-30 seconds)

Get Your Link

The success screen shows:

✅ Published!

Your game is live on X (Twitter)

https://engine.gg/play/g_abc123

[Copy] [Done]

Copy - Copies the URL to clipboard

Done - Closes the modal

Your game is now live and shareable!

Platform-Specific Publishing

X (Twitter) Player Cards

What is a Twitter Player Card?

A Twitter Player Card embeds interactive content (like games) directly in tweets. When someone posts your game link:

Twitter loads the URL

Detects Player Card metadata

Renders the game in an iframe

Users play without leaving Twitter

Publish to Twitter

Click Publish → Select X (Twitter)

Click 🚀 Publish

Copy the generated URL

Post the URL in a tweet

The game embeds automatically

Twitter Metadata

G3Engine auto-generates:

<meta name="twitter:card" content="player" />
<meta name="twitter:title" content="My Awesome Game" />
<meta name="twitter:description" content="Play now!" />
<meta name="twitter:player" content="https://engine.gg/play/g_abc123" />
<meta name="twitter:player:width" content="800" />
<meta name="twitter:player:height" content="600" />
<meta name="twitter:image" content="https://engine.gg/thumbnails/g_abc123.png" />

Best Practices

Keep game size under 10MB for fast loading

Design for 800×600 or 16:9 aspect ratios

Add a clear “How to Play” in the first 5 seconds

Mobile players can tap to fullscreen

Telegram Mini Apps

What are Telegram Mini Apps?

Telegram Mini Apps are web-based apps that run inside Telegram. They occupy the full chat window and feel like native apps.

Publish to Telegram

Click Publish → Select Telegram

Click 🚀 Publish

Copy the URL

Share in any Telegram chat

Users click the link → Game opens in Telegram WebView

Telegram Optimizations

G3Engine automatically:

Forces 100vw × 100vh viewport (fills the screen)

Removes all external UI chrome

Optimizes touch controls

Adds Telegram back button integration

Telegram-Specific Features

You can access Telegram APIs:

User info (first name, username, avatar)

Share game to other chats

In-app purchases (Telegram Stars)

Telegram Mini Apps require HTTPS. G3Engine handles this automatically.

Standalone Web URL

Universal Web Publishing

Click Publish → Select Web (URL)

Click 🚀 Publish

You receive a permanent, shareable link:

https://engine.gg/play/g_abc123

Discord - Paste in channels, game auto-embeds

Websites - Embed via iframe:

<iframe 
  src="https://engine.gg/play/g_abc123" 
  width="800" 
  height="600" 
  frameborder="0"
></iframe>

Email - Send the link directly

Portfolio - Add to your game dev portfolio

Game jams - Submit to itch.io, Newgrounds, etc. (via embed)

Custom Domains

You can use a custom domain:

Set up a CNAME record: games.yourdomain.com → engine.gg

Contact G3Engine support to configure SSL

Your games appear at https://games.yourdomain.com/play/g_abc123

Farcaster Frames (Web3)

What are Farcaster Frames?

Farcaster Frames are interactive embeds on Farcaster (decentralized social network). Frames support:

Interactive buttons

Transaction requests

On-chain actions

Publish to Farcaster

Enable Web3 in your game (see Web3 Wallet Setup)

Click Publish → Select Farcaster

Click 🚀 Publish

Share on Warpcast or other Farcaster clients

Frame Features

Your game frame can:

Connect wallets (one-click with Privy)

Request transactions (token rewards, NFT mints)

Display on-chain data (leaderboards, balances)

Base App (Web3)

Publishing to Base Ecosystem

Base is an Ethereum L2 network. Publishing to Base:

Optimizes for Base RPC endpoints

Enables Base-specific wallet integrations

Registers your game in the Base app directory

Use Case: Games with EVM smart contracts, Base NFTs, or Base tokens

Scene Export Format

When you publish, your scene serializes to this JSON structure:

{
  "version": 1,
  "exportedAt": "2026-03-04T10:30:00.000Z",
  "objects": [
    {
      "id": "uuid-1",
      "name": "Ground",
      "type": "plane",
      "position": { "x": 0, "y": 0, "z": 0 },
      "rotation": { "x": -1.5708, "y": 0, "z": 0 },
      "scale": { "x": 10, "y": 10, "z": 1 },
      "material": {
        "color": "#2a2a3e",
        "roughness": 0.8,
        "metalness": 0.0
      },
      "visible": true
    },
    {
      "id": "uuid-2",
      "name": "Player",
      "type": "box",
      "position": { "x": 0, "y": 0.5, "z": 0 },
      "rotation": { "x": 0, "y": 0, "z": 0 },
      "scale": { "x": 1, "y": 1, "z": 1 },
      "material": {
        "color": "#6366f1",
        "roughness": 0.4,
        "metalness": 0.1
      },
      "visible": true
    }
  ],
  "metadata": {
    "objectCount": 2,
    "hasLights": true,
    "hasWeb3": false
  }
}

This JSON:

Uploads to Arweave (permanent, immutable storage)
Generates a permanent URL (never expires, never changes)
Loads client-side in the published game player

Decentralized Storage (Arweave)

Why Arweave?

G3Engine uses Arweave for game storage because:

Permanent - Files stored forever (pay once, store forever)

Decentralized - No single point of failure

Immutable - Published games can’t be altered or censored

Free for users - G3Engine pays the storage fees (gasless uploads)

How It Works

You click Publish

G3Engine backend receives your scene JSON

Backend signs the Arweave transaction (using platform wallet)

Scene uploads to Arweave via Irys (fast, scalable Arweave bundler)

Irys returns a permanent transaction ID

G3Engine generates your play URL: https://engine.gg/play/[txID]

Your game is now permanently on-chain and always accessible.

Verifying on Arweave

To verify your game is on Arweave:

Extract the transaction ID from your URL

Example: https://engine.gg/play/g_abc123 → abc123

Visit Arweave Explorer

Search for the transaction ID

View the raw JSON data

Updating Published Games

Republish to Update

Arweave uploads are immutable (can’t be changed). To update a game:

Make changes in the editor

Click Publish again

Choose the same platform

A new URL generates with the updated game

Share the new URL

The old URL remains live with the old version. Arweave never deletes data.

Version Control

G3Engine tracks your published versions:

Dashboard → Your project → Published Versions

See all past publishes with timestamps

Click any version to get its URL

Restore an old version by publishing it again

Embedding Games

Iframe Embedding

Embed your game on any website:

<iframe 
  src="https://engine.gg/play/g_abc123" 
  width="800" 
  height="600" 
  frameborder="0"
  allowfullscreen
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
></iframe>

Responsive Embed:

<div style="position: relative; padding-bottom: 75%; height: 0; overflow: hidden;">
  <iframe 
    src="https://engine.gg/play/g_abc123" 
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen
  ></iframe>
</div>

Permissions

Add these iframe allow attributes for full functionality:

accelerometer - Device motion (for mobile tilt controls)

autoplay - Auto-play audio/video

clipboard-write - Copy game data to clipboard

encrypted-media - DRM content

gyroscope - Device orientation

picture-in-picture - PiP mode

web-share - Web Share API

xr-spatial-tracking - WebXR/VR (future)

Publishing Best Practices

Test Before Publishing

Always test your game thoroughly in Play mode before publishing. Published games are immutable.

Optimize Asset Size

Keep your game under 10MB for fast loading. Use optimized materials and limit object count.

Add Instructions

Include in-game tutorials or “How to Play” text. Not all platforms show external descriptions.

Mobile-Friendly

Test on mobile devices. Use larger touch targets and simplified controls for touch screens.

Analytics and Tracking

View Game Stats

Go to your Dashboard

Click your published game

See analytics:

Plays - Total play count
Unique Players - Distinct users
Avg. Session - Average play time
Platform Breakdown - Where players found your game

Embed Analytics Code

Add custom analytics (Google Analytics, Plausible, etc.):

In Settings, add your tracking ID

G3Engine injects the tracking script into published games

Track events: game start, level complete, etc.

Troubleshooting

Publish button grayed out

Check that:

You have at least one object in the scene
You’re connected to the internet
Your project has been saved

Twitter card not showing

Wait 24-48 hours for Twitter to cache the metadata. Use Twitter Card Validator to debug.

Game loads but nothing appears

Verify:

Scene has a camera
Objects are visible (visible: true)
Scene has lighting (add Ambient + Directional Light)
Camera is positioned correctly

Web3 features don't work in published game

Ensure:

Web3 is enabled (toggle in Top Bar)
Game published with web3Enabled: true
Players connect wallet before using Web3 features
Correct network (Devnet vs Mainnet)

Game too slow on mobile

Optimize:

Reduce object count (< 100 objects)
Limit lights (2-3 max)
Disable expensive features (real-time shadows, etc.)
Use simpler materials (higher roughness)

Example: Full Publishing Workflow

1. Build game in editor
   ├─ Add objects, lights, camera
   ├─ Create visual scripts
   └─ Test in Play mode

2. (Optional) Enable Web3
   ├─ Toggle Web3 on
   ├─ Launch token
   └─ Add reward nodes

3. Publish
   ├─ Click Publish button
   ├─ Select X (Twitter)
   ├─ Click 🚀 Publish
   └─ Wait for success screen

4. Share
   ├─ Copy URL
   ├─ Post on Twitter
   └─ Game embeds in feed

5. Monitor
   ├─ Check Dashboard analytics
   ├─ Read player feedback
   └─ Iterate and republish

Advanced: Custom Deployment

For advanced users, you can self-host:

Export Scene JSON

Click File → Export Scene

Download the .json file

Host it on your own server

Build Custom Player

Use the G3Engine runtime (open-source):

npm install @g3engine/runtime

import { G3Runtime } from '@g3engine/runtime';

const runtime = new G3Runtime({
  sceneUrl: 'https://yourdomain.com/scene.json',
  container: document.getElementById('game-container')
});

runtime.load();
runtime.play();

This gives you full control over:

Custom domains

Custom UI/branding

Advanced analytics

Server-side logic

Next Steps

Congratulations! You’ve published your game to the world. What’s next:

Share your game on social media
Gather player feedback
Iterate on your design
Build more complex games
Explore Web3 monetization
Join the G3Engine community

Continue Learning:

Creating Your First Game - Build another game
Web3 Wallet Setup - Monetize with crypto
Adding Interactivity - Advanced visual scripting

Get Started

Core Features

Guides

Web3

Publishing Games

Publishing Games

Publishing Overview

The Publish Button

Platform-Specific Publishing

X (Twitter) Player Cards

Telegram Mini Apps

Standalone Web URL

Farcaster Frames (Web3)

Base App (Web3)

Scene Export Format

Decentralized Storage (Arweave)

Updating Published Games

Embedding Games

Publishing Best Practices

Test Before Publishing

Optimize Asset Size

Add Instructions

Mobile-Friendly

Analytics and Tracking

Troubleshooting

Example: Full Publishing Workflow

Advanced: Custom Deployment

Next Steps

Build docs developers (and LLMs) love

Get Started

Core Features

Guides

Web3

​Publishing Games

​Publishing Overview

​The Publish Button

​Platform-Specific Publishing

​X (Twitter) Player Cards

​Telegram Mini Apps

​Standalone Web URL

​Farcaster Frames (Web3)

​Base App (Web3)

​Scene Export Format

​Decentralized Storage (Arweave)

​Updating Published Games

​Embedding Games

​Publishing Best Practices

Test Before Publishing

Optimize Asset Size

Add Instructions

Mobile-Friendly

​Analytics and Tracking

​Troubleshooting

​Example: Full Publishing Workflow

​Advanced: Custom Deployment

​Next Steps

Build docs developers (and LLMs) love

Publishing Games

Publishing Overview

The Publish Button

Platform-Specific Publishing

X (Twitter) Player Cards

Telegram Mini Apps

Standalone Web URL

Farcaster Frames (Web3)

Base App (Web3)

Scene Export Format

Decentralized Storage (Arweave)

Updating Published Games

Embedding Games

Publishing Best Practices

Analytics and Tracking

Troubleshooting

Example: Full Publishing Workflow

Advanced: Custom Deployment

Next Steps