@opengamehq/skills 1.1.0 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +26 -0
- package/dist/skills/manifest.json +23 -23
- package/dist/skills/opengame-api/CHANGELOG.md +4 -0
- package/dist/skills/opengame-api/SKILL.md +2 -2
- package/dist/skills/opengame-cli/CHANGELOG.md +36 -0
- package/dist/skills/opengame-cli/SKILL.md +79 -5
- package/dist/skills/opengame-deploy/CHANGELOG.md +10 -0
- package/dist/skills/opengame-deploy/SKILL.md +6 -6
- package/dist/skills/opengame-deploy/references/manifest.md +9 -3
- package/dist/skills/opengame-deploy/references/packaging.md +4 -4
- package/dist/skills/opengame-jam/CHANGELOG.md +4 -0
- package/dist/skills/opengame-jam/SKILL.md +4 -4
- package/dist/skills/opengame-router/CHANGELOG.md +4 -0
- package/dist/skills/opengame-router/SKILL.md +2 -2
- package/dist/skills/opengame-sdk/CHANGELOG.md +4 -0
- package/dist/skills/opengame-sdk/SKILL.md +2 -2
- package/dist/skills/opengame-sdk/references/leaderboards.md +11 -1
- package/dist/skills/opengame-sdk/references/radio.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.4.0
|
|
4
|
+
|
|
5
|
+
- `opengame-sdk` 1.0.10 teaches `og.player.stats()`, which reads the player's own entry on
|
|
6
|
+
every board in one request, a career board's row included, so a game can read XP and
|
|
7
|
+
levels back. It also has the higher event and score budgets and the 25-board limit, and
|
|
8
|
+
drops the request to credit OG Radio's music.
|
|
9
|
+
- `opengame-cli` 1.8.0 and `opengame-deploy` 1.1.0: `opengame init` asks a person only the
|
|
10
|
+
game's name, and the description, genre and jam entry are filled in on the deploy's page
|
|
11
|
+
afterwards. Do not ask the creator for a description or genre before deploying.
|
|
12
|
+
- `opengame-deploy` 1.1.1 and `opengame-jam` 1.0.7: a build can be 4 GiB zipped, 5 GiB
|
|
13
|
+
unpacked and 25,000 files, from 1 GiB, 1.5 GiB and 10,000.
|
|
14
|
+
- `opengame-api` 1.0.5, `opengame-cli` 1.8.1, `opengame-deploy` 1.1.1, `opengame-jam` 1.0.7
|
|
15
|
+
and `opengame-router` 1.0.6: OpenGame opens on 18 November 2026, the jam's kickoff, all
|
|
16
|
+
at once.
|
|
17
|
+
|
|
18
|
+
## 1.3.0
|
|
19
|
+
|
|
20
|
+
- `opengame-cli` 1.2.0 teaches `opengame unpublish` and `opengame restore`, run only when
|
|
21
|
+
the person asks, 1.3.0 `opengame details` and `opengame handle`, 1.4.0 `opengame jam
|
|
22
|
+
withdraw` and `opengame jam reenter`, 1.5.0 `opengame delete`, 1.6.0 `opengame achievements`, and 1.7.0 `opengame stats --csv`.
|
|
23
|
+
|
|
24
|
+
## 1.2.0
|
|
25
|
+
|
|
26
|
+
- `opengame-cli` 1.1.0 teaches `opengame releases` and `opengame rollback`, and says to
|
|
27
|
+
roll a live game back only with the person's go-ahead.
|
|
28
|
+
|
|
3
29
|
## 1.1.0
|
|
4
30
|
|
|
5
31
|
- `opengame-sdk` 1.0.9 teaches OG Radio (`og.radio` and its picker, in
|
|
@@ -21,14 +21,14 @@
|
|
|
21
21
|
"family": "platform",
|
|
22
22
|
"default": false,
|
|
23
23
|
"description": "Call the OpenGame creator API directly over HTTPS. Covers the base URL, creator tokens and scopes, the OpenAPI document, the error shape and retry fields, deploying without the CLI, and checking whether OpenGame is open. Use when the person wants to deploy from their own tool or CI without the CLI, asks about the OpenGame REST API, api/v1, openapi.json or a creator token, or an API call returned an error code you need to read.",
|
|
24
|
-
"version": "1.0.
|
|
24
|
+
"version": "1.0.5",
|
|
25
25
|
"files": [
|
|
26
26
|
{
|
|
27
27
|
"path": "SKILL.md",
|
|
28
|
-
"sha256": "
|
|
28
|
+
"sha256": "b93dbe0e69ec6004b4cdb1d83e30718d3e631ccf95cdedd00ac935a554040e40"
|
|
29
29
|
}
|
|
30
30
|
],
|
|
31
|
-
"digest": "
|
|
31
|
+
"digest": "839d0ffffeb1b61c514781651c2a8da7930d9fa988dce043d0d1403e2c245103"
|
|
32
32
|
},
|
|
33
33
|
{
|
|
34
34
|
"name": "opengame-assets",
|
|
@@ -118,26 +118,26 @@
|
|
|
118
118
|
"name": "opengame-cli",
|
|
119
119
|
"family": "platform",
|
|
120
120
|
"default": false,
|
|
121
|
-
"description": "Drive the OpenGame command line tool from an agent. Covers installing it, signing in with the person, every command, JSON and JSONL output, exit codes, findings and how to retry. Use when the person mentions the opengame command, the OpenGame CLI, installing @opengamehq/cli, opengame login, check, dev, deploy, status, submit or token, or a command exited with an error you need to read.",
|
|
122
|
-
"version": "1.
|
|
121
|
+
"description": "Drive the OpenGame command line tool from an agent. Covers installing it, signing in with the person, every command, JSON and JSONL output, exit codes, findings and how to retry. Use when the person mentions the opengame command, the OpenGame CLI, installing @opengamehq/cli, opengame login, check, dev, deploy, status, submit, releases, rollback, unpublish, restore, delete, details, achievements, handle, jam or token, or a command exited with an error you need to read.",
|
|
122
|
+
"version": "1.8.1",
|
|
123
123
|
"files": [
|
|
124
124
|
{
|
|
125
125
|
"path": "SKILL.md",
|
|
126
|
-
"sha256": "
|
|
126
|
+
"sha256": "a233e44dde59b033654a22d3fb900bf5d8aa45cd2265dc4bd6dacd3e258f068f"
|
|
127
127
|
}
|
|
128
128
|
],
|
|
129
|
-
"digest": "
|
|
129
|
+
"digest": "29985f7f32360e8e731ec7998eb0dbacd8c120f03d714e14632f1b29af3e75de"
|
|
130
130
|
},
|
|
131
131
|
{
|
|
132
132
|
"name": "opengame-deploy",
|
|
133
133
|
"family": "platform",
|
|
134
134
|
"default": true,
|
|
135
135
|
"description": "Put a browser game online with OpenGame, the marketplace and game jam for browser games. Packages the game, checks it locally, uploads it to a private preview only the owner can play, reads and fixes findings, then submits one exact release for review. Use when the person says deploy my game, put it online, host it, share it, upload it, publish it, get me a link, make it playable for friends, or asks where to put a browser game or a Three.js game.",
|
|
136
|
-
"version": "1.
|
|
136
|
+
"version": "1.1.1",
|
|
137
137
|
"files": [
|
|
138
138
|
{
|
|
139
139
|
"path": "SKILL.md",
|
|
140
|
-
"sha256": "
|
|
140
|
+
"sha256": "dfd28b0c0296c14948d18c68b301dd2f6bc375de29d78356efda3758184e4a7f"
|
|
141
141
|
},
|
|
142
142
|
{
|
|
143
143
|
"path": "references/json-events.md",
|
|
@@ -145,14 +145,14 @@
|
|
|
145
145
|
},
|
|
146
146
|
{
|
|
147
147
|
"path": "references/manifest.md",
|
|
148
|
-
"sha256": "
|
|
148
|
+
"sha256": "3f651d06ca8e1aa7e9fc69c6c4b327f017661472cbadb692ba8ffad8f19da798"
|
|
149
149
|
},
|
|
150
150
|
{
|
|
151
151
|
"path": "references/packaging.md",
|
|
152
|
-
"sha256": "
|
|
152
|
+
"sha256": "82c2ec30ab27d6a08c167e09a4af68134e6ef4207859b9e8655d6213d4bb2114"
|
|
153
153
|
}
|
|
154
154
|
],
|
|
155
|
-
"digest": "
|
|
155
|
+
"digest": "5c1fb58d7baf3fffec4e335e255a688c2b23d1d757a171dd2efd55156c39b849"
|
|
156
156
|
},
|
|
157
157
|
{
|
|
158
158
|
"name": "opengame-depth",
|
|
@@ -235,14 +235,14 @@
|
|
|
235
235
|
"family": "platform",
|
|
236
236
|
"default": false,
|
|
237
237
|
"description": "Enter a game in an OpenGame jam. Finds the open jams, their tracks and rules, checks the game against them, and submits one exact release as an entry with the person's own answers, leaving the certification to the person. Use when the person says enter the jam, submit to the jam, which track should I pick, am I eligible, what are the jam rules, or mentions the OpenGame Global AI Game Jam.",
|
|
238
|
-
"version": "1.0.
|
|
238
|
+
"version": "1.0.7",
|
|
239
239
|
"files": [
|
|
240
240
|
{
|
|
241
241
|
"path": "SKILL.md",
|
|
242
|
-
"sha256": "
|
|
242
|
+
"sha256": "2c4145df9bc8ac28b1ccebf8889b12a39c83cca7c1a89df5a0fb4129fe8d31f7"
|
|
243
243
|
}
|
|
244
244
|
],
|
|
245
|
-
"digest": "
|
|
245
|
+
"digest": "ff0bce8f6aa6627c7511e65235ac4644081bf27777d7e8b70e36fd2c569dd335"
|
|
246
246
|
},
|
|
247
247
|
{
|
|
248
248
|
"name": "opengame-lighting",
|
|
@@ -375,18 +375,18 @@
|
|
|
375
375
|
"family": "platform",
|
|
376
376
|
"default": true,
|
|
377
377
|
"description": "Build, test and submit a browser game on OpenGame. Routes game work to the deploy guide, whole-game review and relevant craft skills. Use when someone asks to make a game, improve a game, check it, deploy it or enter an OpenGame jam.",
|
|
378
|
-
"version": "1.0.
|
|
378
|
+
"version": "1.0.6",
|
|
379
379
|
"files": [
|
|
380
380
|
{
|
|
381
381
|
"path": "SKILL.md",
|
|
382
|
-
"sha256": "
|
|
382
|
+
"sha256": "508c246139ba17b55ddac4cf6d544b26dd853f71a91c494d51532738d7db013b"
|
|
383
383
|
},
|
|
384
384
|
{
|
|
385
385
|
"path": "references/process.md",
|
|
386
386
|
"sha256": "3462bdd5a87f81eee69ffb12ca04519b35404f67c920b182443e81a8904100dd"
|
|
387
387
|
}
|
|
388
388
|
],
|
|
389
|
-
"digest": "
|
|
389
|
+
"digest": "0e111fd2d182e0a8a9c9d5a2d1e8a48e43249e8a1df8db09412b056f2ccf9558"
|
|
390
390
|
},
|
|
391
391
|
{
|
|
392
392
|
"name": "opengame-scene-audit",
|
|
@@ -411,11 +411,11 @@
|
|
|
411
411
|
"family": "platform",
|
|
412
412
|
"default": false,
|
|
413
413
|
"description": "Integrate a browser game with OpenGame through @opengamehq/sdk, the injected global or a native engine bridge. Covers start-up, the player and their OG at load, names, leaderboards, achievements, events, pause, mute, fullscreen, keys inside the frame and threaded builds. Use when the person says integrate with OpenGame, add the SDK, show the player's name or OG, add a leaderboard or achievement, track events, fix fullscreen or keys in the game frame, or asks how a game talks to OpenGame.",
|
|
414
|
-
"version": "1.0.
|
|
414
|
+
"version": "1.0.10",
|
|
415
415
|
"files": [
|
|
416
416
|
{
|
|
417
417
|
"path": "SKILL.md",
|
|
418
|
-
"sha256": "
|
|
418
|
+
"sha256": "2a35ccbefce9194e63e8ec7c85a2a70cf3a5a06d534b8cab34dd3f6c9c6c0326"
|
|
419
419
|
},
|
|
420
420
|
{
|
|
421
421
|
"path": "references/engines.md",
|
|
@@ -431,14 +431,14 @@
|
|
|
431
431
|
},
|
|
432
432
|
{
|
|
433
433
|
"path": "references/leaderboards.md",
|
|
434
|
-
"sha256": "
|
|
434
|
+
"sha256": "4439937932acd12fe0e8009fc6616621b0466e4292398005fe675c9a39b4f327"
|
|
435
435
|
},
|
|
436
436
|
{
|
|
437
437
|
"path": "references/radio.md",
|
|
438
|
-
"sha256": "
|
|
438
|
+
"sha256": "ff8a2db8fe57b0ba0ba0c804419e5c13d7ebee187e268f26fa148c82fad00cd7"
|
|
439
439
|
}
|
|
440
440
|
],
|
|
441
|
-
"digest": "
|
|
441
|
+
"digest": "c7eb939a609ba292e1fec5d880e6d1f109ead5ef998a2d5d64ade5a3b5881c8a"
|
|
442
442
|
},
|
|
443
443
|
{
|
|
444
444
|
"name": "opengame-stability",
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-api changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.5
|
|
4
|
+
|
|
5
|
+
OpenGame opens on 18 November 2026, the jam's kickoff, not 17 November: the site no longer opens a day before the rest.
|
|
6
|
+
|
|
3
7
|
## 1.0.4
|
|
4
8
|
|
|
5
9
|
The site opens on one day and the CLI, uploads and the creator API on the next, the jam's kickoff. Until then an account outside the team is told that day, read from the launch clock.
|
|
@@ -2,12 +2,12 @@
|
|
|
2
2
|
name: opengame-api
|
|
3
3
|
description: Call the OpenGame creator API directly over HTTPS. Covers the base URL, creator tokens and scopes, the OpenAPI document, the error shape and retry fields, deploying without the CLI, and checking whether OpenGame is open. Use when the person wants to deploy from their own tool or CI without the CLI, asks about the OpenGame REST API, api/v1, openapi.json or a creator token, or an API call returned an error code you need to read.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.0.
|
|
5
|
+
version: "1.0.5"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Call the OpenGame creator API
|
|
9
9
|
|
|
10
|
-
OpenGame opens on
|
|
10
|
+
OpenGame opens on 18 November 2026, and the creator API on 18 November. Until 18 November, every route except the status route and sign-in answers 403
|
|
11
11
|
with the error `not_launched` and the message "OpenGame opens for creators on 18 November." for any account
|
|
12
12
|
outside the OpenGame team. Check before anything else:
|
|
13
13
|
|
|
@@ -1,5 +1,41 @@
|
|
|
1
1
|
# opengame-cli changelog
|
|
2
2
|
|
|
3
|
+
## 1.8.1
|
|
4
|
+
|
|
5
|
+
OpenGame opens on 18 November 2026, the jam's kickoff, not 17 November: the site no longer opens a day before the rest.
|
|
6
|
+
|
|
7
|
+
## 1.8.0
|
|
8
|
+
|
|
9
|
+
`opengame init` asks a person only the game's name, and `opengame submit` sends a person with no jam answers to the deploy's page, where the description, genre and jam entry are filled in.
|
|
10
|
+
|
|
11
|
+
## 1.7.0
|
|
12
|
+
|
|
13
|
+
Teaches `opengame stats --csv`.
|
|
14
|
+
|
|
15
|
+
## 1.6.0
|
|
16
|
+
|
|
17
|
+
Teaches `opengame achievements` and `opengame achievements retire`.
|
|
18
|
+
|
|
19
|
+
## 1.5.0
|
|
20
|
+
|
|
21
|
+
Teaches `opengame delete`: only when the person asks for that game to be deleted, with the title they confirmed, and unpublish offered first.
|
|
22
|
+
|
|
23
|
+
## 1.4.0
|
|
24
|
+
|
|
25
|
+
Teaches `opengame jam withdraw` and `opengame jam reenter`.
|
|
26
|
+
|
|
27
|
+
## 1.3.0
|
|
28
|
+
|
|
29
|
+
Teaches `opengame details` and `opengame handle`: changing a game's words on the website, and renaming the person's handle with their go-ahead.
|
|
30
|
+
|
|
31
|
+
## 1.2.0
|
|
32
|
+
|
|
33
|
+
Teaches `opengame unpublish` and `opengame restore`: taking a game off the gallery and putting it back, only when the person asks.
|
|
34
|
+
|
|
35
|
+
## 1.1.0
|
|
36
|
+
|
|
37
|
+
Teaches `opengame releases` and `opengame rollback`: listing a game's releases and making one that was live before live again, only with the person's go-ahead.
|
|
38
|
+
|
|
3
39
|
## 1.0.4
|
|
4
40
|
|
|
5
41
|
The site opens on one day and the CLI, uploads and the creator API on the next, the jam's kickoff. Until then an account outside the team is told that day, read from the launch clock.
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: opengame-cli
|
|
3
|
-
description: Drive the OpenGame command line tool from an agent. Covers installing it, signing in with the person, every command, JSON and JSONL output, exit codes, findings and how to retry. Use when the person mentions the opengame command, the OpenGame CLI, installing @opengamehq/cli, opengame login, check, dev, deploy, status, submit or token, or a command exited with an error you need to read.
|
|
3
|
+
description: Drive the OpenGame command line tool from an agent. Covers installing it, signing in with the person, every command, JSON and JSONL output, exit codes, findings and how to retry. Use when the person mentions the opengame command, the OpenGame CLI, installing @opengamehq/cli, opengame login, check, dev, deploy, status, submit, releases, rollback, unpublish, restore, delete, details, achievements, handle, jam or token, or a command exited with an error you need to read.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.
|
|
5
|
+
version: "1.8.1"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Use the OpenGame CLI
|
|
9
9
|
|
|
10
|
-
OpenGame opens on
|
|
10
|
+
OpenGame opens on 18 November 2026, and the CLI on 18 November. Until 18 November, every command except `version`, `help`, `login`, `logout` and `whoami` prints
|
|
11
11
|
"OpenGame opens for creators on 18 November." for anybody outside the OpenGame team, and exits with the
|
|
12
12
|
`not_launched` code (7) that `opengame help --json` lists. That is the platform's answer,
|
|
13
13
|
not a broken install: tell the person, and do not retry, reinstall or look for a way round it.
|
|
@@ -61,7 +61,7 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
61
61
|
|
|
62
62
|
| Command | What it does |
|
|
63
63
|
| --- | --- |
|
|
64
|
-
| `opengame init [dir]` | Create opengame.json for an existing game. |
|
|
64
|
+
| `opengame init [dir]` | Create opengame.json for an existing game. Asks a person only the game's name; the rest is filled in on the deploy's page. |
|
|
65
65
|
| `opengame check [dir]` | Find local build and asset problems before uploading. |
|
|
66
66
|
| `opengame dev [dir]` | Serve a local export with the game runtime's headers. |
|
|
67
67
|
| `opengame login` | Sign in through the browser. |
|
|
@@ -69,8 +69,17 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
69
69
|
| `opengame status [dir]` | Show the latest deploy for this folder, with its findings. |
|
|
70
70
|
| `opengame deployments [dir]` | List the linked game's deploys, newest first. |
|
|
71
71
|
| `opengame open [dir]` | Open the linked game's private page. |
|
|
72
|
-
| `opengame submit [dir]` | Send one release to review, and enter it in a jam. |
|
|
72
|
+
| `opengame submit [dir]` | Send one release to review, and enter it in a jam with flags. A deploy goes to review by itself; a person enters the jam on the deploy's page. |
|
|
73
73
|
| `opengame jams [slug]` | List open jams, or show one jam's tracks and flags. |
|
|
74
|
+
| `opengame jam <withdraw\|reenter>` | Withdraw the linked game's jam entry, or put a withdrawn one back. |
|
|
75
|
+
| `opengame releases [dir]` | List the linked game's releases: which is live, which were live before, and which can be made live again. |
|
|
76
|
+
| `opengame rollback <release>` | Make a release that was live before live again, for every player. |
|
|
77
|
+
| `opengame unpublish [dir]` | Take the linked game off the gallery and stop serving it. Reversible. |
|
|
78
|
+
| `opengame restore [dir]` | Put a game the person unpublished back on the gallery. |
|
|
79
|
+
| `opengame delete [dir]` | Delete the linked game for good, with its title typed to confirm. |
|
|
80
|
+
| `opengame achievements [retire <id>]` | List the game's achievements, or retire one. |
|
|
81
|
+
| `opengame details [dir]` | Print the game's title, tagline and description as the website shows them, or change them. |
|
|
82
|
+
| `opengame handle <name>` | Rename the person's handle. |
|
|
74
83
|
| `opengame games` | List your games and their latest deploy. |
|
|
75
84
|
| `opengame link [dir]` | Connect this folder to an existing game. |
|
|
76
85
|
| `opengame pull [dir]` | Bring website metadata into this folder. |
|
|
@@ -84,6 +93,71 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
84
93
|
| `opengame upgrade` | Install the current CLI, or print the line that does. |
|
|
85
94
|
| `opengame version` | Print the CLI version. |
|
|
86
95
|
|
|
96
|
+
## Roll back
|
|
97
|
+
|
|
98
|
+
When a new version of a live game is broken, `opengame releases --json` lists every
|
|
99
|
+
release with `rollback: true` on the ones that can be made live again. Confirm with the
|
|
100
|
+
person which one they want, then run `opengame rollback <release> --yes --json` with the
|
|
101
|
+
eight characters the list prints or the whole id. It changes what every player gets from
|
|
102
|
+
their next load, so never run it without the person's go-ahead, and never to undo a
|
|
103
|
+
refusal: a release that was never live goes through `opengame submit`. It needs a token
|
|
104
|
+
with `read` or `deploy`, and `submit`, which `opengame login` gives. A refusal's `message`
|
|
105
|
+
says why, for example the game is not live, or a release is being published right now. If
|
|
106
|
+
it answers `host_failed`, run the same command again: the second run writes only the
|
|
107
|
+
game's address.
|
|
108
|
+
|
|
109
|
+
## Take a game down, or put it back
|
|
110
|
+
|
|
111
|
+
`opengame unpublish --yes --json` takes the linked game (or `--game <id>`) off the gallery
|
|
112
|
+
and stops serving it; its build, uploads and review record are kept. `opengame restore
|
|
113
|
+
--yes --json` puts a game the person unpublished back, serving the version it was on. Both
|
|
114
|
+
change what every player gets, so run either only when the person asks for it. Both need a
|
|
115
|
+
token with `read` or `deploy`, and `submit`, which `opengame login` gives. A refusal's `message` is the website's
|
|
116
|
+
own reason, for example the game is not on the gallery, OpenGame took it down, a report is
|
|
117
|
+
open, or it is under a hold. Do not try to get round one: write to team@opengame.io is the
|
|
118
|
+
way on when the message says so. `unpublish_incomplete` and `restore_incomplete` mean the
|
|
119
|
+
first half happened; run the same command again.
|
|
120
|
+
|
|
121
|
+
`opengame delete --title "<title>" --yes --json` deletes a game for good. It cannot be
|
|
122
|
+
undone, so run it only when the person has asked for that game to be deleted, and pass the
|
|
123
|
+
title they confirmed rather than reading it off the game yourself. Unpublishing is the
|
|
124
|
+
reversible way to take a game down; offer it first. Delete works only with the `opengame
|
|
125
|
+
login` token. `delete_refused` says why, for example a legal hold or a reviewer holding it.
|
|
126
|
+
|
|
127
|
+
## Change a game's words, or the person's handle
|
|
128
|
+
|
|
129
|
+
`opengame details --json` prints the title, tagline and description the website shows.
|
|
130
|
+
`opengame details --title "<text>" --tagline "<text>" --description "<text>" --json` saves
|
|
131
|
+
any of them, as the Details tab does; a field left out stays, and `--clear-tagline` removes
|
|
132
|
+
the tagline. On a published game players
|
|
133
|
+
see it at once, so change only what the person asked for. To keep `opengame.json` in step,
|
|
134
|
+
run `opengame pull` afterwards. `opengame handle <name> --yes --json` renames the person's
|
|
135
|
+
handle. Ask first: their old handle stays theirs and is never reissued, and renames are
|
|
136
|
+
limited per day. It works only with the `opengame login` token, not a token made in
|
|
137
|
+
settings. A refusal's `message` says why, for example the name is taken.
|
|
138
|
+
|
|
139
|
+
## Retire an achievement
|
|
140
|
+
|
|
141
|
+
Removing an achievement from `opengame.json` does not switch it off. `opengame achievements
|
|
142
|
+
--json` lists them; `opengame achievements retire <id> --yes --json` retires one when the
|
|
143
|
+
person asks. Players keep what they unlocked, and declaring it again and deploying turns it
|
|
144
|
+
back on. Retiring needs `deploy` and `submit`, which `opengame login` gives.
|
|
145
|
+
|
|
146
|
+
## Withdraw a jam entry, or put it back
|
|
147
|
+
|
|
148
|
+
`opengame jam withdraw --yes --json` takes the linked game's entry out of the jam and frees
|
|
149
|
+
its place; the entry, its build and its certifications are kept. Run it only when the person
|
|
150
|
+
asks. `opengame jam reenter --json` puts the newest withdrawn entry back while the jam is
|
|
151
|
+
open, with the same reference and build. Both need `read` or `deploy`, and `submit`.
|
|
152
|
+
`at_entry_limit` means every place is taken: ask the person which entry to withdraw first.
|
|
153
|
+
`reenter_closed` means the jam is not taking entries; wait for it to open, and do not
|
|
154
|
+
re-enter after it closes. `jam_entry_taken` means a newer entry of the game is already in.
|
|
155
|
+
|
|
156
|
+
## Stats as a file
|
|
157
|
+
|
|
158
|
+
`opengame stats --csv week.csv` writes the week's figures as the CSV the Stats tab
|
|
159
|
+
downloads; it takes the same `--game` and `--period` and never writes over a file.
|
|
160
|
+
|
|
87
161
|
## Read the output
|
|
88
162
|
|
|
89
163
|
Add `--json` for one final object, or `--jsonl` for progress events with the result
|
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# opengame-deploy changelog
|
|
2
2
|
|
|
3
|
+
## 1.1.1
|
|
4
|
+
|
|
5
|
+
A build can be 4 GiB zipped, 5 GiB unpacked and 25,000 files, from 1 GiB, 1.5 GiB and 10,000 files. The manifest and packaging references now say a game may declare 25 leaderboards, as 1.1.0 did, where they still said 10. OpenGame opens on 18 November 2026, the jam's kickoff, not 17 November: the site no longer opens a day before the rest.
|
|
6
|
+
|
|
7
|
+
## 1.1.0
|
|
8
|
+
|
|
9
|
+
Do not ask the creator for a description or a genre before deploying. init writes a placeholder description and a provisional genre when the game says neither, the deploy's page asks for both, and `opengame details --description` sets the description once the game exists.
|
|
10
|
+
|
|
11
|
+
A game may declare up to 25 leaderboards.
|
|
12
|
+
|
|
3
13
|
## 1.0.9
|
|
4
14
|
|
|
5
15
|
The site opens on one day and the CLI, uploads and the creator API on the next, the jam's kickoff. Until then an account outside the team is told that day, read from the launch clock.
|
|
@@ -2,12 +2,12 @@
|
|
|
2
2
|
name: opengame-deploy
|
|
3
3
|
description: Put a browser game online with OpenGame, the marketplace and game jam for browser games. Packages the game, checks it locally, uploads it to a private preview only the owner can play, reads and fixes findings, then submits one exact release for review. Use when the person says deploy my game, put it online, host it, share it, upload it, publish it, get me a link, make it playable for friends, or asks where to put a browser game or a Three.js game.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.
|
|
5
|
+
version: "1.1.1"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Deploy a browser game to OpenGame
|
|
9
9
|
|
|
10
|
-
OpenGame opens on
|
|
10
|
+
OpenGame opens on 18 November 2026. The CLI, uploads and jam entries open on 18 November.
|
|
11
11
|
Until then, every CLI command except `version`, `help`, `login`, `logout` and `whoami`
|
|
12
12
|
prints "OpenGame opens for creators on 18 November." for anybody outside the OpenGame team, and the API
|
|
13
13
|
refuses with `not_launched`. Nothing is wrong with the game or the install: tell the
|
|
@@ -100,14 +100,14 @@ opengame login --continue --json
|
|
|
100
100
|
|
|
101
101
|
Run these from the game folder.
|
|
102
102
|
|
|
103
|
-
If the folder has no `opengame.json`, create one.
|
|
103
|
+
If the folder has no `opengame.json`, create one. The title is all it needs. A decomp or a mod says so with `--kind` and names the game it is based on:
|
|
104
104
|
|
|
105
105
|
```bash
|
|
106
106
|
opengame init . --title "My game" --json
|
|
107
107
|
opengame init . --title "Doom but blue" --kind mod --based-on "Doom" --json
|
|
108
108
|
```
|
|
109
109
|
|
|
110
|
-
|
|
110
|
+
Do not ask the creator for a description or a genre before deploying. When you know them, pass `--description` (40 characters or more) and `--genre`; when you do not, init writes a placeholder description and a provisional genre, and the deploy prints its page, where the creator writes the description, chooses the genre and enters the jam. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists, leave `init` alone and edit the file.
|
|
111
111
|
|
|
112
112
|
For a game that already exists on OpenGame, in a new checkout, link the folder first so the deploy does not create a second game:
|
|
113
113
|
|
|
@@ -123,7 +123,7 @@ opengame check . --build --json
|
|
|
123
123
|
opengame deploy . --json
|
|
124
124
|
```
|
|
125
125
|
|
|
126
|
-
`deploy` runs the manifest's build command, checks the output and uploads it, up to
|
|
126
|
+
`deploy` runs the manifest's build command, checks the output and uploads it, up to 4 GiB zipped. It returns once the upload is in, with exit 0 and `data.done: false`, while the checks run on the server. Keep `.opengame/`: later commands resume and follow the same deploy from it. Use `--no-build` only when the creator says the export is already built and its build cannot run here, never to get past a failing build.
|
|
127
127
|
|
|
128
128
|
| Field | What it holds |
|
|
129
129
|
| --- | --- |
|
|
@@ -177,7 +177,7 @@ opengame jams --json
|
|
|
177
177
|
opengame submit --release <releaseId> --no-wait --json
|
|
178
178
|
```
|
|
179
179
|
|
|
180
|
-
OpenGame decides where submissions go. When that is a jam, the
|
|
180
|
+
OpenGame decides where submissions go, and a ready deploy goes to review by itself. When that is a jam, the creator usually enters it on the deploy's page (`data.deploymentUrl`). To enter it from here instead, read the form with `opengame jams <slug> --json` and pass the track, the models they used and any sponsor evidence as `--track`, `--models`, `--sponsor` and `--evidence-<sponsor>`. A missing answer exits 2 and names the flag. A decomp or a mod cannot enter a jam.
|
|
181
181
|
|
|
182
182
|
When `data.state` is `needs_certification`, give the creator `data.certifyUrl`, which the CLI also prints as a `certify_required` notice. They certify in their own browser that they have the rights to the game. You cannot do it for them. Follow the review with:
|
|
183
183
|
|
|
@@ -32,7 +32,7 @@ they belong to one entry, not to the game.
|
|
|
32
32
|
| `cover` | Not used. OpenGame makes the cover after approval. A file that still names one passes `check`, and the CLI does not upload it; leave the field out |
|
|
33
33
|
| `controls` | One or more of `keyboard`, `mouse`, `gamepad`, each once |
|
|
34
34
|
| `requires` | Optional. `threads: true` for a build that cannot start without them, `renderer` (`webgl`, `webgl2` or `webgpu`), `desktopOnly`, `gamepad`. The game page lists them, and a browser that cannot run threads is told so instead of getting a black frame |
|
|
35
|
-
| `leaderboards` | Up to
|
|
35
|
+
| `leaderboards` | Up to 25 boards: `key` (lowercase, starts with a letter, up to 48 characters), `order` (`asc` or `desc`), `label` (up to 60 characters), optional `min` and `max` |
|
|
36
36
|
| `achievements` | Up to 100: `id` (lowercase letters, digits, `-` and `_`, up to 48 characters), `title`, optional `description`. A deploy saves them when its preview is ready |
|
|
37
37
|
| `sdk` | Optional. A version string, or `{ "inject": false, "version": "..." }`. `inject: false` is honoured only on the older contract whose serving tree the pipeline rewrites; the contracts that add `/_og/sdk.js` at the edge always add it |
|
|
38
38
|
| `runtimes` | Optional. Settings for a runtime the platform serves pinned (js-dos, Ruffle, Pyodide, wasmoon, Flutter's CanvasKit); the engine's guide says which |
|
|
@@ -69,8 +69,14 @@ it plays.
|
|
|
69
69
|
| `decomp` | An existing game rebuilt from its decompiled code | Required | No |
|
|
70
70
|
| `mod` | Changes to an existing game, like new levels, rules or art | Required | No |
|
|
71
71
|
|
|
72
|
-
`opengame init --kind mod --based-on "Doom"` writes both. Without `--kind`, init
|
|
73
|
-
|
|
72
|
+
`opengame init --kind mod --based-on "Doom"` writes both. Without `--kind`, init makes a
|
|
73
|
+
game; it asks a person nothing but the game's name.
|
|
74
|
+
|
|
75
|
+
A folder with no description of its own gets a placeholder sentence, which the deploy marks
|
|
76
|
+
provisional, and so does a genre init could not read from the game's words. Do not ask the
|
|
77
|
+
creator for either before deploying: the deploy's page asks them, and `opengame details
|
|
78
|
+
--description` sets the description from here once the game exists. A game cannot publish
|
|
79
|
+
with the placeholder.
|
|
74
80
|
|
|
75
81
|
## Who owns which value
|
|
76
82
|
|
|
@@ -9,9 +9,9 @@ also published at opengame.io/agent.md.
|
|
|
9
9
|
| Rule | Limit | What happens |
|
|
10
10
|
| --- | --- | --- |
|
|
11
11
|
| Entry point | `index.html` at the root of the build output | Refused |
|
|
12
|
-
| Compressed size |
|
|
13
|
-
| Uncompressed size |
|
|
14
|
-
| File count |
|
|
12
|
+
| Compressed size | 4096 MiB | Refused |
|
|
13
|
+
| Uncompressed size | 5120 MiB | Refused |
|
|
14
|
+
| File count | 25,000 | Refused |
|
|
15
15
|
| Compression ratio | 200 : 1 | Refused, as a zip bomb guard |
|
|
16
16
|
| Paths | Case matches the file on disk; no `../`, no symlinks, no absolute paths | Refused |
|
|
17
17
|
| Excluded | `node_modules/`, `.git/`, `.env*`, source maps, OS junk | Stripped, with a `files_excluded` notice |
|
|
@@ -114,4 +114,4 @@ game at 1920 x 1080 (primary), 1366 x 768, 2560 x 1440, 3440 x 1440, 1024 x 640
|
|
|
114
114
|
## Manifest limits
|
|
115
115
|
|
|
116
116
|
`opengame.json` itself is at most 64 KiB, with at most
|
|
117
|
-
|
|
117
|
+
25 leaderboards. See [manifest.md](manifest.md).
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-jam changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.7
|
|
4
|
+
|
|
5
|
+
A build can be 4 GiB zipped, 5 GiB unpacked and 25,000 files, from 1 GiB, 1.5 GiB and 10,000 files. OpenGame opens on 18 November 2026, the jam's kickoff, not 17 November: the site no longer opens a day before the rest.
|
|
6
|
+
|
|
3
7
|
## 1.0.6
|
|
4
8
|
|
|
5
9
|
The site opens on one day and the CLI, uploads and the creator API on the next, the jam's kickoff. Until then an account outside the team is told that day, read from the launch clock.
|
|
@@ -2,12 +2,12 @@
|
|
|
2
2
|
name: opengame-jam
|
|
3
3
|
description: Enter a game in an OpenGame jam. Finds the open jams, their tracks and rules, checks the game against them, and submits one exact release as an entry with the person's own answers, leaving the certification to the person. Use when the person says enter the jam, submit to the jam, which track should I pick, am I eligible, what are the jam rules, or mentions the OpenGame Global AI Game Jam.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.0.
|
|
5
|
+
version: "1.0.7"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Enter an OpenGame jam
|
|
9
9
|
|
|
10
|
-
OpenGame opens on
|
|
10
|
+
OpenGame opens on 18 November 2026. Jam entries open on 18 November and close on
|
|
11
11
|
18 December, 11:59 pm PT; after the close every deploy path answers `entries_closed`.
|
|
12
12
|
|
|
13
13
|
Until 18 November, entries stay closed: the CLI and the API answer
|
|
@@ -48,8 +48,8 @@ the authority):
|
|
|
48
48
|
- **Free to play, with no crypto, ads or tracking.** No payments, tips or donations, no
|
|
49
49
|
wallets or tokens, no ads or ad pixels, no session recording. `opengame-deploy` has
|
|
50
50
|
the full rules.
|
|
51
|
-
- **Inside the bundle limits:**
|
|
52
|
-
|
|
51
|
+
- **Inside the bundle limits:** 4096 MiB zipped,
|
|
52
|
+
5120 MiB unzipped, 25,000 files.
|
|
53
53
|
- **The person owns the art, audio, models, fonts and code**, or holds a licence to
|
|
54
54
|
ship them.
|
|
55
55
|
- **A game or a world, not a decomp or a mod.** Read `kind` in `opengame.json`. A decomp
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-router changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.6
|
|
4
|
+
|
|
5
|
+
OpenGame opens on 18 November 2026, the jam's kickoff, not 17 November: the site no longer opens a day before the rest.
|
|
6
|
+
|
|
3
7
|
## 1.0.5
|
|
4
8
|
|
|
5
9
|
The site opens on one day and the CLI, uploads and the creator API on the next, the jam's kickoff. Until then an account outside the team is told that day, read from the launch clock.
|
|
@@ -2,12 +2,12 @@
|
|
|
2
2
|
name: opengame-router
|
|
3
3
|
description: Build, test and submit a browser game on OpenGame. Routes game work to the deploy guide, whole-game review and relevant craft skills. Use when someone asks to make a game, improve a game, check it, deploy it or enter an OpenGame jam.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.0.
|
|
5
|
+
version: "1.0.6"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Work on an OpenGame game
|
|
9
9
|
|
|
10
|
-
OpenGame opens on
|
|
10
|
+
OpenGame opens on 18 November 2026. The CLI, uploads and jam entries open on 18 November.
|
|
11
11
|
Until then, the CLI and the creator API answer "OpenGame opens for creators on 18 November."
|
|
12
12
|
to everybody outside the OpenGame team. That is the platform's answer, not a fault in the
|
|
13
13
|
game: tell the person, and keep working on the game itself, which they can still build and
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-sdk changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.10
|
|
4
|
+
|
|
5
|
+
og.player.stats() reads the player's own entry on every board in one request, a career board's row for all runs included, so XP and levels can be read back into a game. Higher event and score budgets, up to 25 boards a game, and no need to credit OG Radio's music.
|
|
6
|
+
|
|
3
7
|
## 1.0.9
|
|
4
8
|
|
|
5
9
|
OG Radio: `og.radio` and its drop-in picker, so players can pick stations and songs in a game's menu and listen while they play. Sound needs the player's press and stays off while the game is muted. A new reference, `references/radio.md`, has the calls, scopes, theming and codes.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: opengame-sdk
|
|
3
3
|
description: Integrate a browser game with OpenGame through @opengamehq/sdk, the injected global or a native engine bridge. Covers start-up, the player and their OG at load, names, leaderboards, achievements, events, pause, mute, fullscreen, keys inside the frame and threaded builds. Use when the person says integrate with OpenGame, add the SDK, show the player's name or OG, add a leaderboard or achievement, track events, fix fullscreen or keys in the game frame, or asks how a game talks to OpenGame.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.0.
|
|
5
|
+
version: "1.0.10"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Integrate a game with OpenGame
|
|
@@ -190,7 +190,7 @@ og.track('wave_cleared', { level: 14, duration_ms: 81234 })
|
|
|
190
190
|
Event names are lowercase with underscores, up to 48
|
|
191
191
|
characters. Properties are limited to `level`, `mode`, `difficulty`, `score`, `duration_ms`, `result`, `step`, `board`, `fps`, `heap_mb`, `sample_rate` and
|
|
192
192
|
1,024 bytes per event, at most
|
|
193
|
-
|
|
193
|
+
600 events a minute; anything else is dropped
|
|
194
194
|
rather than sent, and `og.track` returns `unavailable` before `og.init()`. Events are batched and
|
|
195
195
|
flushed every 10 seconds and on page exit. Plays, sessions and play
|
|
196
196
|
time are measured by the page; do not track them yourself.
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
## Declare the board
|
|
4
4
|
|
|
5
5
|
Every board the game uses is declared in `opengame.json`, up to
|
|
6
|
-
|
|
6
|
+
25 of them:
|
|
7
7
|
|
|
8
8
|
```json
|
|
9
9
|
{ "leaderboards": [{ "key": "rounds", "order": "desc", "label": "Rounds survived", "min": 0, "max": 75 }] }
|
|
@@ -34,6 +34,16 @@ const nearby = await board.around() // entries around the pl
|
|
|
34
34
|
- `source` is always `game_reported`. Show it as the game's own scoreboard, never as a
|
|
35
35
|
verified result or a prize standing.
|
|
36
36
|
|
|
37
|
+
## The player's own stats
|
|
38
|
+
|
|
39
|
+
`og.player.stats()` reads the player's entry on every declared board in one request:
|
|
40
|
+
`value.boards` is `[{ board, label, keep, entry }]`, `entry` being `{ score, stats, tags,
|
|
41
|
+
meta, createdAt, imported }` or `null`. A career board answers the player's row for all
|
|
42
|
+
runs, so XP and levels can live on one: submit each match's XP as a run to a `runs` board,
|
|
43
|
+
feed a career board from it with `scoreAgg: "sum"`, and compute the level in the game from
|
|
44
|
+
the career `entry.score`. The request names no player or game (the session decides both),
|
|
45
|
+
it shares `me()`'s allowance, and the local mock reads career boards as empty.
|
|
46
|
+
|
|
37
47
|
## Columns, variants and runs
|
|
38
48
|
|
|
39
49
|
A board can declare stat `columns` beside its score, `variants` a run is tagged with, and
|
|
@@ -68,4 +68,4 @@ radio.onChange(state => render(state.playing, state.track))
|
|
|
68
68
|
searches up to 64 characters, `timeout` after
|
|
69
69
|
5 seconds.
|
|
70
70
|
- `not_found` for an unknown station, genre or song id; `invalid_request` for a bad argument.
|
|
71
|
-
-
|
|
71
|
+
- A game does not have to credit the music. `attribution` is there for a now-playing line.
|