How to publish your game, and how review works
Publishing on Galatrix includes a review. You submit a map, a moderator looks at it, and it goes live once approved. A little preparation makes that step quick and smooth.
Updated · 3 min read
The states a map moves through
There are three, and knowing them makes it easy to see where your map is.
- Pending review. You filled in the publish dialog and submitted. The map is queued for review and stays private to you until it passes.
- Approved. A moderator passed it. It is live: players can find it in the lobby and play it. The Galatrix team also features a selection of games on the Play tab.
- Rejected. A moderator sent it back with feedback on what to change. Read it, update the map, and resubmit, which puts it back into review.
Feedback from review is a to-do list from someone who has just played your game. Plan a little time for the review step when you have a launch date in mind, such as a game you want ready for friends on a Friday.
Play it like a player
Before you submit, play your game the way a newcomer will: from the spawn point, with no idea where anything is. Press Play in the editor and go start to finish, then ask a friend to look over your shoulder while you do it again.
If you built with AI Chat, run its test pass too. It reads the map against your goal and lists anything worth fixing, and the AI can fix that list in one go.
What to have ready before you submit
A review is someone opening your map and playing it. Make that easy.
- A spawn point that works. Players land on solid ground, facing something worth seeing.
- A boundary. Somewhere that keeps players inside the world you built.
- A title and description that say what it is. The description is also the first thing a player reads in the lobby.
- A genre. Pick the one a player would search for. It is how your map is filtered in the lobby, so the right choice puts it in front of the people who want it.
- A thumbnail. It is your first impression in a grid of other people’s games.
- One full run-through of your own. Play it start to finish as a player would. A fresh run catches the small things an author stops noticing.
Map ID: the identity of a published map
Every published map has a Map ID. That, rather than the title, is what the platform means by “this map”.
That matters in three practical ways.
Updates keep it. When you publish again over an existing map, the platform recognises the update from the Map ID and replaces that map in place. You can rename a map freely and it stays the same entry.
Each ID belongs to one map. Identity is enforced on the server, so every published map has exactly one entry.
It is what you quote. When you report a problem, ask about a moderation decision, or need support for one specific map, the Map ID is the exact reference.
Updating a live map
Publishing again over a map you already published updates that map, recognised from its Map ID, so the update lands on the entry players already know.
One habit worth forming early: test the update as an update. Players who already have saved progress from the version before will meet your change mid-stream, so check how it plays for them as well as for a newcomer.
Saves, and whose they are
When you publish you also decide where your game’s player data lives. The default suits most games: this game keeps its own saves, separate from everything else you have made.
The alternative is to share one save bucket across several of your games. That suits a series, or a hub that should carry a shared wallet or unlock. It is opt-in, and it is easiest to decide when you first publish.
Hosting it yourself
Publishing puts your game on play.galatrix.com, where players find it and play it together. For a game on your own website, export a standalone build instead and host the files wherever you like. A standalone game can also connect to servers you run over secure WebSockets, so you can bring your own multiplayer, leaderboards or chat. Both are first-class ways to ship.
Where to go next
Once a map is live, the work shifts from building to learning from players. How to grow your game after you publish covers how discovery works and what the numbers tell you.