Common questions about building, flashing, and using your Stargate.
Every time your ESP32 starts up, it automatically checks whether a new firmware version is available. You don't need to do anything except click Update if prompted. Once the update is complete, the ESP32 will reboot automatically.
Depends on the moment — sometimes yes, sometimes not. Easiest is just to ask on the Discord.
Short answer: Yes.
Long answer: Yes, because you can still create your own MQTT broker for free and connect Stargates to it — but you won't be able to connect to the whole network, more like a LAN.
The voluntary donation to join the official network is kept close to nothing — it allows gates to share their addresses publicly on the website, pays for the dedicated server that lets them communicate, and funds future features (physical DHD, new Stargate models...). If you want to support the project, you can do so at buymeacoffee.com/opengateproject!
Depends on your printer, budget, and how much soldering/assembly you want to take on. The Tutorials page rates every model on print difficulty, assembly difficulty, and material cost — worth a look before you commit to one.
As a rule of thumb: Orlin is the smallest and easiest build by far (great first gate) ; SG-1 (Basic) and Tollan sit in the middle ; Atlantis (Pegasus) and SG-1 (motorized) ask more of you — the motorized ring in particular adds real electronics and assembly work on top of everything a static gate needs.
The SG1_basic is a minimalist version of the SG-1 Stargate. Like the off-world gates seen in the series, the ring does not rotate. Instead, it only features LEDs for the chevrons and the event horizon.
It was originally designed while working on a version with a rotating glyph ring, but it also serves as a way to test compatibility between 36-glyph and 39-glyph Stargates.
Functionally, they're the same gate on the network — same address, same DHD, same everything from the outside. The difference is entirely physical: the Basic version lights up chevrons directly like an off-world gate, while the motorized version has an actual NEMA17 stepper turning the glyph ring, the way the "real" Stargate does.
The motorized ring adds a driver board, wiring, and a calibration step (ring direction and speed can both be tuned from the DHD's Motor Calibration panel — no rewiring needed if the ring turns the wrong way). It's a meaningfully bigger build; see the Tutorials page for the difficulty comparison.
There are 2 ways to dial:
If your gate is already assembled and your glyph ring isn't correctly placed, you can use the calibration tool to correct this.
That's a safety guard, not a crash: the firmware you flashed doesn't match the gate type your board has already registered in memory (for example, flashing an Atlantis build onto a board that previously ran as SG-1). Re-flash the correct build for that gate, or erase the ESP32's flash storage to let it register fresh — either clears it.
Yes. By default, all addresses are assigned using only the first 36 glyphs, ensuring compatibility between every Stargate.
On SG-1 (or any other 39-glyph Stargate), you'll be able to enable an option to use the three additional glyphs in addresses. If this option is enabled, 36-glyph Stargates will no longer be able to dial that gate.
Handled automatically, nothing for you to do. Every gate checks the network's registry for collisions shortly after booting — if its address (7, 8, or 9-symbol) turns out to already be taken, it draws a new one and re-subscribes on its own. This is also why two gates that lose power at the same time and reboot together won't collide: each one waits a short random delay before checking, so their checks don't land at the exact same moment.
Yes, any time, from the web interface — no reflash needed. Moving to one of the built-in clusters (like "Pegasus" or "MilkyWay") is always free; creating your own custom cluster name unlocks at level 7.
Only your 7-symbol address changes when you move cluster (it's redrawn if it happens to already be taken in the new one) — your 8 and 9-symbol addresses stay exactly the same, since those don't depend on cluster.
From the web interface, you can choose to make your Stargate address public and assign it a public name.
Your Stargate will then appear on the public directory. You can also choose whether the listing shows your global 8-chevron address, or your 7-chevron address plus your cluster name.
Your address remains listed whether your Stargate is online or offline. If you no longer want it to appear, simply uncheck the Public option in the web interface.
Your gate levels up as you use it, from Level 0 to Level 10. Features unlock gradually rather than all at once, so a brand-new gate stays simple and gains depth as you actually use it. Progress is stored on the ESP32 itself — there's no account, and nothing is tied to the network.
What each level unlocks:
How you earn XP:
XP needed per level:
| Level | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| XP | 100 | 300 | 600 | 1000 | 1600 | 2400 | 3400 | 4600 | 6000 | 8000 |
Don't want to wait? See the next question — everything can be unlocked immediately.
Yes! You can use the following cheat codes by dialing these addresses:
24 4 19 9 5 6 116 10 12 15 18 5 14 7The Midway Station is a shared communication space that works like a public chat room.
Dial the following address to join it: 18 10 20 25 13 1 5 12
A solar flare mimics the eruptions seen in the show: whatever you send through gets displaced in time and space. Dial 1 2 3 5 8 13 21 34 and the wormhole opens normally — but it only holds for 3 minutes, and anything you send is redirected to a random online gate, delivered anywhere from 5 minutes to a few days later.
This works for naquadah too — send some through the "Send Naquadah" button while connected to a flare, and it'll land in a random gate's balance once it arrives, not necessarily yours.
There's also a small chance that any normal dial gets caught in a flare instead of reaching its intended target — you'll know it happened if your log shows a solar flare warning.
Naquadah is a resource your gate slowly refines just by staying online and connected to the network — the longer your uptime streak runs, the faster you earn it. Your balance and total lifetime earnings are visible on your own DHD, and on the public leaderboard.
You spend it at the Trading Post, and can send it directly to whoever you're connected to with the "Send Naquadah" button.
Dial 2 4 6 8 10 12 14 and a menu appears in your message log. On offer: cosmetic skins, a gate address (usually another player's — occasionally a hidden naquadah deposit scattered somewhere on the network), a supply cartridge (a gamble: naquadah, XP, a skin, an EMP charge, or a breach that costs you some naquadah), EMP charges, Distress Signal charges, and naquadah boosters (temporarily boost your own earning rate, your whole cluster's, or the entire network's).
EMP and Distress Signal charges are stored on your gate and used later from their own dedicated buttons — no need to dial the Trading Post again each time.
A gate trapped in a black hole's gravity well. Dial 20 5 35 26 25 34 30 and the wormhole opens normally — but it won't disengage on its own.
You'll need to either cut power to your gate, or discharge an EMP charge (bought at the Trading Post) from the dedicated button to break free — doing the latter successfully rewards you with a burst of XP.
Dial 2 3 5 7 11 13 17. Deposit up to 200 naquadah, and it grows over time — +5% every 6 hours, up to double.
The catch: anyone who dials in, including someone else entirely, can claim whatever's sitting in there right then. Only deposit what you're willing to risk someone else reaching first.
Dial 11 36 25 33 14 18 29 — an asynchronous message drop. You'll always receive the last message someone left there, and you can leave your own in return, rewarded with a small amount of naquadah (once per hour per gate).
A temporal capsule. Dial 21 15 14 7 29 35 1, pick a delay in hours, then send yourself messages or naquadah through it. Everything comes back to your own gate once the delay passes — even if you're offline when it's due, it waits for you to reconnect.
Didn't find your answer? Ask on the Discord.