When the user wants to publish this game or put it online, call genex__publish with operation 'gallery': Studio exports the game, updates its draft page and makes that same build the public version. Operation 'draft' makes an unlisted test build, for trying multiplayer or sign-in, or when the user asks for a private link. Studio asks the user to approve in the chat; that call may wait several minutes for the answer, and a declined or expired request must not be repeated unless the user asks a...
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Publishing?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/genex-games-publishing)
# Publishing on Genex
When the user wants to publish this game or put it online, call genex__publish with operation 'gallery': Studio exports the game, updates its draft page and makes that same build the public version. Operation 'draft' makes an unlisted test build, for trying multiplayer or sign-in, or when the user asks for a private link. Studio asks the user to approve in the chat; that call may wait several minutes for the answer, and a declined or expired request must not be repeated unless the user asks again. The result is a job: call genex__publish-status with operation 'wait' and the jobId until state is done or failed, then give the user galleryUrl, or draftPlayUrl for a draft: anyone with it plays the draft, as a guest or signed in. draftUrl is the owner's own draft page and needs their sign-in: never hand it out as the place to play or test. A publish, and a draft until the game is first public, sends the cover kept with genex__cover after the upload (the cover skill) and takes no picture of its own; publish-status reports how it went. Studio runs Genex's CLI for you: use genex__cli for other Genex commands.
