@opengamehq/skills 1.6.0 → 1.7.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 +10 -0
- package/README.md +5 -1
- package/dist/skills/manifest.json +29 -29
- package/dist/skills/opengame-all-in-one/CHANGELOG.md +8 -0
- package/dist/skills/opengame-all-in-one/SKILL.md +4 -4
- package/dist/skills/opengame-all-in-one/references/opengame-cli/README.md +8 -6
- package/dist/skills/opengame-all-in-one/references/opengame-deploy/README.md +16 -9
- package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/json-events.md +11 -10
- package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/manifest.md +17 -12
- package/dist/skills/opengame-all-in-one/references/opengame-jam/README.md +2 -2
- package/dist/skills/opengame-all-in-one/references/opengame-performance/README.md +3 -3
- package/dist/skills/opengame-all-in-one/references/opengame-router/README.md +7 -5
- package/dist/skills/opengame-all-in-one/references/opengame-router/references/process.md +5 -2
- package/dist/skills/opengame-cli/CHANGELOG.md +8 -0
- package/dist/skills/opengame-cli/SKILL.md +8 -6
- package/dist/skills/opengame-deploy/CHANGELOG.md +8 -0
- package/dist/skills/opengame-deploy/SKILL.md +16 -9
- package/dist/skills/opengame-deploy/references/json-events.md +11 -10
- package/dist/skills/opengame-deploy/references/manifest.md +17 -12
- package/dist/skills/opengame-jam/CHANGELOG.md +4 -0
- package/dist/skills/opengame-jam/SKILL.md +2 -2
- package/dist/skills/opengame-performance/CHANGELOG.md +4 -0
- package/dist/skills/opengame-performance/SKILL.md +3 -3
- package/dist/skills/opengame-router/CHANGELOG.md +4 -0
- package/dist/skills/opengame-router/SKILL.md +7 -5
- package/dist/skills/opengame-router/references/process.md +5 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.7.0
|
|
4
|
+
|
|
5
|
+
- Matched to the CLI, the SDK and the API on 17 Nov 2026: `opengame-cli` 1.9.2, `opengame-deploy`
|
|
6
|
+
1.1.9, `opengame-jam` 1.1.1, `opengame-router` 1.0.9, `opengame-performance` 1.1.2 and
|
|
7
|
+
`opengame-all-in-one` 1.0.7 describe Auto details, the scopes jam withdraw takes, exit 7,
|
|
8
|
+
`--json` against `--jsonl`, every review state, and `opengame setup` installing every skill.
|
|
9
|
+
- `opengame-cli` 1.9.1 and `opengame-deploy` 1.1.8: installing the CLI is followed by
|
|
10
|
+
`opengame setup`, which gives every coding agent on the machine the OpenGame skills in its own
|
|
11
|
+
home folder, and the CLI keeps them current. `opengame-all-in-one` 1.0.6 carries both.
|
|
12
|
+
|
|
3
13
|
## 1.6.0
|
|
4
14
|
|
|
5
15
|
- `opengame-cli` 1.9.0, `opengame-deploy` 1.1.7, `opengame-jam` 1.1.0 and `opengame-api`
|
package/README.md
CHANGED
|
@@ -12,7 +12,10 @@ npx skills add opengamehq/opengame
|
|
|
12
12
|
```
|
|
13
13
|
<!-- /install -->
|
|
14
14
|
|
|
15
|
-
Through the CLI, `opengame
|
|
15
|
+
Through the CLI, `opengame setup` installs every skill (all but `opengame-all-in-one`) into
|
|
16
|
+
each coding agent's own skills folder and keeps them current as the CLI updates;
|
|
17
|
+
`opengame setup --no-skills` stops that. To commit skills with one project instead,
|
|
18
|
+
`opengame skills add .` installs the starting set for the agent you use,
|
|
16
19
|
`opengame skills add . --all` installs every skill once, each in its own folder (not
|
|
17
20
|
`opengame-all-in-one`, which would repeat them), and
|
|
18
21
|
`opengame skills add . --skill opengame-all-in-one` installs all of them as one.
|
|
@@ -22,6 +25,7 @@ Through the CLI, `opengame skills add .` installs the starting set for the agent
|
|
|
22
25
|
<!-- install:cli -->
|
|
23
26
|
```bash
|
|
24
27
|
npm i -g @opengamehq/cli
|
|
28
|
+
opengame setup
|
|
25
29
|
```
|
|
26
30
|
<!-- /install -->
|
|
27
31
|
|
|
@@ -127,40 +127,40 @@
|
|
|
127
127
|
"family": "platform",
|
|
128
128
|
"default": false,
|
|
129
129
|
"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.",
|
|
130
|
-
"version": "1.9.
|
|
130
|
+
"version": "1.9.2",
|
|
131
131
|
"files": [
|
|
132
132
|
{
|
|
133
133
|
"path": "SKILL.md",
|
|
134
|
-
"sha256": "
|
|
134
|
+
"sha256": "ef96641849c0f1f50e4f515cd94ef21bd37a712ef14e0a291e3316f2788e75ab"
|
|
135
135
|
}
|
|
136
136
|
],
|
|
137
|
-
"digest": "
|
|
137
|
+
"digest": "0f5629565203c35ed80d57fa35cc6de365cc9eb706eb79569b6b5d65ff655ad6"
|
|
138
138
|
},
|
|
139
139
|
{
|
|
140
140
|
"name": "opengame-deploy",
|
|
141
141
|
"family": "platform",
|
|
142
142
|
"default": true,
|
|
143
143
|
"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 hands the creator the page where they confirm the details after 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.",
|
|
144
|
-
"version": "1.1.
|
|
144
|
+
"version": "1.1.9",
|
|
145
145
|
"files": [
|
|
146
146
|
{
|
|
147
147
|
"path": "SKILL.md",
|
|
148
|
-
"sha256": "
|
|
148
|
+
"sha256": "a9d85d5db189840ebcf8d519fb3a112c936201ac1ebc29997776042f1ec55607"
|
|
149
149
|
},
|
|
150
150
|
{
|
|
151
151
|
"path": "references/json-events.md",
|
|
152
|
-
"sha256": "
|
|
152
|
+
"sha256": "de9fe8c7ed88ad39731117856492b47c22f57fb76d5b50958613bd24601d9258"
|
|
153
153
|
},
|
|
154
154
|
{
|
|
155
155
|
"path": "references/manifest.md",
|
|
156
|
-
"sha256": "
|
|
156
|
+
"sha256": "c48230590f39a82b4d2583651e0e06119f397807a79b53bc6ec13ff0ecb268d0"
|
|
157
157
|
},
|
|
158
158
|
{
|
|
159
159
|
"path": "references/packaging.md",
|
|
160
160
|
"sha256": "20fb37b9a8d1bb2ae72e96c233d3df8cd4338e3d32c8ba8d923caf1280738431"
|
|
161
161
|
}
|
|
162
162
|
],
|
|
163
|
-
"digest": "
|
|
163
|
+
"digest": "cf3f56f08ebcc1960f86eda5fa989f7be5ff98a1e55362e113685229a4f88c5c"
|
|
164
164
|
},
|
|
165
165
|
{
|
|
166
166
|
"name": "opengame-depth",
|
|
@@ -251,14 +251,14 @@
|
|
|
251
251
|
"family": "platform",
|
|
252
252
|
"default": false,
|
|
253
253
|
"description": "Enter a game in an OpenGame jam. Finds the open jams, their tracks and rules, checks the game against them, deploys one exact release, and enters it with the person's own answers, with opengame publish or on the deploy's page. 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.",
|
|
254
|
-
"version": "1.1.
|
|
254
|
+
"version": "1.1.1",
|
|
255
255
|
"files": [
|
|
256
256
|
{
|
|
257
257
|
"path": "SKILL.md",
|
|
258
|
-
"sha256": "
|
|
258
|
+
"sha256": "d85112cb9bc43cfe8014ee0a2476c17c88ae8c216db1a16fede726119436105f"
|
|
259
259
|
}
|
|
260
260
|
],
|
|
261
|
-
"digest": "
|
|
261
|
+
"digest": "d3f7631feea6c8a3f0aa87dcbfa5ad04f12069d5ab728d874c1e7fb3603d915c"
|
|
262
262
|
},
|
|
263
263
|
{
|
|
264
264
|
"name": "opengame-lighting",
|
|
@@ -595,11 +595,11 @@
|
|
|
595
595
|
"family": "craft",
|
|
596
596
|
"default": false,
|
|
597
597
|
"description": "Keep a browser game smooth on an ordinary laptop and a shared GPU, with three.js and WebGPU specifics. Covers frame-time tails counted from frames the engine ran, bare timing runs, cost over frame rate, frame pacing by what lands, draw calls per pass, a fixed light set and warm-up, uploads that never stall, the world lowered before the gameplay layer, and whole-tab memory. Use when the game stutters, hitches, drops frames, swings between rates, has a slow menu or a mouse that feels slow.",
|
|
598
|
-
"version": "1.1.
|
|
598
|
+
"version": "1.1.2",
|
|
599
599
|
"files": [
|
|
600
600
|
{
|
|
601
601
|
"path": "SKILL.md",
|
|
602
|
-
"sha256": "
|
|
602
|
+
"sha256": "8c22c63f7222a2fedda2ea420757f6b3773dee9804b79a6b7218a4d77079c931"
|
|
603
603
|
},
|
|
604
604
|
{
|
|
605
605
|
"path": "helpers/landing-pacer.mjs",
|
|
@@ -614,7 +614,7 @@
|
|
|
614
614
|
"sha256": "dd3d9d83f978ddff5a44854ded59630e434d9e5ff6cab74ead8fc260d0f44448"
|
|
615
615
|
}
|
|
616
616
|
],
|
|
617
|
-
"digest": "
|
|
617
|
+
"digest": "07c1882634eb06c00c43cd3c48831b6f78dd5610eeb423a9e00a1886e6f2182a"
|
|
618
618
|
},
|
|
619
619
|
{
|
|
620
620
|
"name": "opengame-production",
|
|
@@ -691,18 +691,18 @@
|
|
|
691
691
|
"family": "platform",
|
|
692
692
|
"default": true,
|
|
693
693
|
"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.",
|
|
694
|
-
"version": "1.0.
|
|
694
|
+
"version": "1.0.9",
|
|
695
695
|
"files": [
|
|
696
696
|
{
|
|
697
697
|
"path": "SKILL.md",
|
|
698
|
-
"sha256": "
|
|
698
|
+
"sha256": "86afd8aad697c13b13a37d0503d74693c605f93ec6480e502bf0423fd837ebff"
|
|
699
699
|
},
|
|
700
700
|
{
|
|
701
701
|
"path": "references/process.md",
|
|
702
|
-
"sha256": "
|
|
702
|
+
"sha256": "a6f05ed2280c37bad58480aede468ed1ca8202f78707e5aadc4089d821fa09ee"
|
|
703
703
|
}
|
|
704
704
|
],
|
|
705
|
-
"digest": "
|
|
705
|
+
"digest": "df839971a0c9fcd99303dd97864480b3f5e5832334d01676fe6d462eb8f7793b"
|
|
706
706
|
},
|
|
707
707
|
{
|
|
708
708
|
"name": "opengame-scene-audit",
|
|
@@ -1067,11 +1067,11 @@
|
|
|
1067
1067
|
"family": "bundle",
|
|
1068
1068
|
"default": false,
|
|
1069
1069
|
"description": "Every OpenGame skill in one install, with the order to use them in, for taking a browser game from an idea to a AAA-feeling release, a trailer and a montage. Carries the platform, craft and video skills whole. Use when someone wants one skill that covers everything, says make it AAA or make it game of the year, starts a big game with agents, or does not know which OpenGame skill to load.",
|
|
1070
|
-
"version": "1.0.
|
|
1070
|
+
"version": "1.0.7",
|
|
1071
1071
|
"files": [
|
|
1072
1072
|
{
|
|
1073
1073
|
"path": "SKILL.md",
|
|
1074
|
-
"sha256": "
|
|
1074
|
+
"sha256": "4589fc2e7422422414d8825165abb1c8aa8c190231000326d29bdf7591851ca2"
|
|
1075
1075
|
},
|
|
1076
1076
|
{
|
|
1077
1077
|
"path": "references/opengame-accessibility/README.md",
|
|
@@ -1135,19 +1135,19 @@
|
|
|
1135
1135
|
},
|
|
1136
1136
|
{
|
|
1137
1137
|
"path": "references/opengame-cli/README.md",
|
|
1138
|
-
"sha256": "
|
|
1138
|
+
"sha256": "f5adb85d241a320e191d761881e020c0214bc04c0382af2e95ad2e097f82f316"
|
|
1139
1139
|
},
|
|
1140
1140
|
{
|
|
1141
1141
|
"path": "references/opengame-deploy/README.md",
|
|
1142
|
-
"sha256": "
|
|
1142
|
+
"sha256": "cd4295f052e1248f72e3d6c97f671b9c4de271cc3e97ae03ab426fe451a482a5"
|
|
1143
1143
|
},
|
|
1144
1144
|
{
|
|
1145
1145
|
"path": "references/opengame-deploy/references/json-events.md",
|
|
1146
|
-
"sha256": "
|
|
1146
|
+
"sha256": "de9fe8c7ed88ad39731117856492b47c22f57fb76d5b50958613bd24601d9258"
|
|
1147
1147
|
},
|
|
1148
1148
|
{
|
|
1149
1149
|
"path": "references/opengame-deploy/references/manifest.md",
|
|
1150
|
-
"sha256": "
|
|
1150
|
+
"sha256": "c48230590f39a82b4d2583651e0e06119f397807a79b53bc6ec13ff0ecb268d0"
|
|
1151
1151
|
},
|
|
1152
1152
|
{
|
|
1153
1153
|
"path": "references/opengame-deploy/references/packaging.md",
|
|
@@ -1199,7 +1199,7 @@
|
|
|
1199
1199
|
},
|
|
1200
1200
|
{
|
|
1201
1201
|
"path": "references/opengame-jam/README.md",
|
|
1202
|
-
"sha256": "
|
|
1202
|
+
"sha256": "8eb297acca68e468819b14e854baceea89bf04a1627244206e741139f3d6cab1"
|
|
1203
1203
|
},
|
|
1204
1204
|
{
|
|
1205
1205
|
"path": "references/opengame-lighting/README.md",
|
|
@@ -1443,7 +1443,7 @@
|
|
|
1443
1443
|
},
|
|
1444
1444
|
{
|
|
1445
1445
|
"path": "references/opengame-performance/README.md",
|
|
1446
|
-
"sha256": "
|
|
1446
|
+
"sha256": "3c0fcbaa4054ff22a8ff22980c9191640f97b1097e010549b79f00ba9b0432e3"
|
|
1447
1447
|
},
|
|
1448
1448
|
{
|
|
1449
1449
|
"path": "references/opengame-performance/helpers/landing-pacer.mjs",
|
|
@@ -1499,11 +1499,11 @@
|
|
|
1499
1499
|
},
|
|
1500
1500
|
{
|
|
1501
1501
|
"path": "references/opengame-router/README.md",
|
|
1502
|
-
"sha256": "
|
|
1502
|
+
"sha256": "b3426ddbaaaff62db62dc5096c96e5001918a0479184ee35f7281e2ea36f023f"
|
|
1503
1503
|
},
|
|
1504
1504
|
{
|
|
1505
1505
|
"path": "references/opengame-router/references/process.md",
|
|
1506
|
-
"sha256": "
|
|
1506
|
+
"sha256": "a6f05ed2280c37bad58480aede468ed1ca8202f78707e5aadc4089d821fa09ee"
|
|
1507
1507
|
},
|
|
1508
1508
|
{
|
|
1509
1509
|
"path": "references/opengame-scene-audit/README.md",
|
|
@@ -1774,7 +1774,7 @@
|
|
|
1774
1774
|
"sha256": "e3cbba13f31a92ae73bc33ccef413276b4c2d98039285d67e393223dc7d2b8e5"
|
|
1775
1775
|
}
|
|
1776
1776
|
],
|
|
1777
|
-
"digest": "
|
|
1777
|
+
"digest": "228328efb929ee6776b5ce5bb5a9cc0c67834ba1505ada006c38286e0d618793"
|
|
1778
1778
|
}
|
|
1779
1779
|
]
|
|
1780
1780
|
}
|
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# opengame-all-in-one changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.7
|
|
4
|
+
|
|
5
|
+
Carries opengame-cli 1.9.2, opengame-deploy 1.1.9, opengame-jam 1.1.1, opengame-router 1.0.9 and opengame-performance 1.1.2, and says `opengame setup` leaves this skill out too. (17 Nov 2026)
|
|
6
|
+
|
|
7
|
+
## 1.0.6
|
|
8
|
+
|
|
9
|
+
Carries opengame-cli 1.9.1 and opengame-deploy 1.1.8.
|
|
10
|
+
|
|
3
11
|
## 1.0.5
|
|
4
12
|
|
|
5
13
|
Carries `opengame-api` 1.0.8, `opengame-cli` 1.9.0, `opengame-deploy` 1.1.7 and `opengame-jam` 1.1.0, which publish with `opengame publish` (16 Nov 2026).
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: opengame-all-in-one
|
|
3
3
|
description: Every OpenGame skill in one install, with the order to use them in, for taking a browser game from an idea to a AAA-feeling release, a trailer and a montage. Carries the platform, craft and video skills whole. Use when someone wants one skill that covers everything, says make it AAA or make it game of the year, starts a big game with agents, or does not know which OpenGame skill to load.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.0.
|
|
5
|
+
version: "1.0.7"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Make a browser game that feels AAA
|
|
@@ -184,12 +184,12 @@ core loop first, then every generated asset, then the front end, then playtest.
|
|
|
184
184
|
| Long builds with agents and rounds of notes | [production](references/opengame-production/README.md) |
|
|
185
185
|
| Which skill for a task | [router](references/opengame-router/README.md) |
|
|
186
186
|
| The SDK in the frame | [SDK](references/opengame-sdk/README.md) |
|
|
187
|
-
| Check, deploy, preview | [deploy](references/opengame-deploy/README.md), [CLI](references/opengame-cli/README.md) |
|
|
187
|
+
| Check, deploy, preview, publish | [deploy](references/opengame-deploy/README.md), [CLI](references/opengame-cli/README.md) |
|
|
188
188
|
| Your own tools and CI | [API](references/opengame-api/README.md) |
|
|
189
189
|
| Jam fields and eligibility | [jam](references/opengame-jam/README.md) |
|
|
190
190
|
| A launch trailer | [plan](references/opengame-trailer-plan/README.md), [make](references/opengame-trailer-make/README.md), [review](references/opengame-trailer-review-and-improve/README.md) |
|
|
191
191
|
| A gameplay montage | [plan](references/opengame-montage-plan/README.md), [make](references/opengame-montage-make/README.md), [review](references/opengame-montage-review-and-improve/README.md) |
|
|
192
192
|
|
|
193
193
|
Each carried skill says, in its first line, the version it was carried at. The separate
|
|
194
|
-
skills are the same text, so install this one or those, not both: `opengame
|
|
195
|
-
--all`
|
|
194
|
+
skills are the same text, so install this one or those, not both: `opengame setup` and
|
|
195
|
+
`opengame skills add --all` leave this one out for that reason.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
> Carried from `opengame-cli` 1.9.
|
|
1
|
+
> Carried from `opengame-cli` 1.9.2. Read it when: 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.
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
# Use the OpenGame CLI
|
|
@@ -16,6 +16,7 @@ for the tool itself.
|
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
18
|
npm i -g @opengamehq/cli
|
|
19
|
+
opengame setup
|
|
19
20
|
```
|
|
20
21
|
|
|
21
22
|
Once `opengame` is installed, confirm it and read the command reference:
|
|
@@ -58,7 +59,7 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
58
59
|
|
|
59
60
|
| Command | What it does |
|
|
60
61
|
| --- | --- |
|
|
61
|
-
| `opengame init [dir]` | Create opengame.json for an existing game.
|
|
62
|
+
| `opengame init [dir]` | Create opengame.json for an existing game. Every field it is not given is `auto`: review writes it from the game, and the creator accepts or changes it on the deploy's page or with `opengame publish`. Asks a person only the game's name. |
|
|
62
63
|
| `opengame check [dir]` | Find local build and asset problems before uploading. |
|
|
63
64
|
| `opengame dev [dir]` | Serve a local export with the game runtime's headers. |
|
|
64
65
|
| `opengame login` | Sign in through the browser. |
|
|
@@ -87,7 +88,8 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
87
88
|
| `opengame logout` | Revoke this device's token and remove it. |
|
|
88
89
|
| `opengame limits` | Show bundle limits and the account's remaining allowance. |
|
|
89
90
|
| `opengame vendor [dir]` | Make a separate export with dependencies downloaded and pinned. |
|
|
90
|
-
| `opengame
|
|
91
|
+
| `opengame setup` | Install every OpenGame skill for the coding agents on this machine, and keep them current with the CLI. Other commands do the same on first run and after an update; `--no-skills` stops it for good, `OPENGAME_SKILLS_AUTO=0` for one run, and CI never gets it. |
|
|
92
|
+
| `opengame skills add or list` | Install the OpenGame skills into one project, to commit them with the game. |
|
|
91
93
|
| `opengame upgrade` | Install the current CLI, or print the line that does. |
|
|
92
94
|
| `opengame version` | Print the CLI version. |
|
|
93
95
|
|
|
@@ -146,7 +148,7 @@ back on. Retiring needs `deploy` and `submit`, which `opengame login` gives.
|
|
|
146
148
|
`opengame jam withdraw --yes --json` takes the linked game's entry out of the jam and frees
|
|
147
149
|
its place; the entry, its build and its certifications are kept. Run it only when the person
|
|
148
150
|
asks. `opengame jam reenter --json` puts the newest withdrawn entry back while the jam is
|
|
149
|
-
open, with the same reference and build. Both need `
|
|
151
|
+
open, with the same reference and build. Both need `submit`, which `opengame login` gives.
|
|
150
152
|
`at_entry_limit` means every place is taken: ask the person which entry to withdraw first.
|
|
151
153
|
`reenter_closed` means the jam is not taking entries; wait for it to open, and do not
|
|
152
154
|
re-enter after it closes. `jam_entry_taken` means a newer entry of the game is already in.
|
|
@@ -172,9 +174,9 @@ helps, `retry`, `retryAfterSeconds` and `next`, the command to run next.
|
|
|
172
174
|
| 4 | `rateLimited` | An allowance is used. Wait `retryAfterSeconds`, then run the same command. |
|
|
173
175
|
| 5 | `server` | Our side or the network; the game is fine. Follow `retry`. |
|
|
174
176
|
| 6 | `upgrade` | This CLI is too old. Run `opengame upgrade --json`. |
|
|
177
|
+
| 7 | `notLaunched` | OpenGame is not open to creators yet, and the error's code is `not_launched`. Run `opengame login`, then the same command again. |
|
|
175
178
|
|
|
176
|
-
|
|
177
|
-
error's `code` rather than the number wherever you can.
|
|
179
|
+
Branch on the error's `code` rather than the number wherever you can.
|
|
178
180
|
|
|
179
181
|
## Act on findings
|
|
180
182
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
> Carried from `opengame-deploy` 1.1.
|
|
1
|
+
> Carried from `opengame-deploy` 1.1.9. Read it when: 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 hands the creator the page where they confirm the details after 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.
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
# Deploy a browser game to OpenGame
|
|
@@ -16,6 +16,7 @@ Deploy the creator's game to a private preview and give them its link. Review st
|
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
18
|
npm i -g @opengamehq/cli
|
|
19
|
+
opengame setup
|
|
19
20
|
```
|
|
20
21
|
|
|
21
22
|
Once `opengame` is installed, confirm it and read the command reference:
|
|
@@ -27,7 +28,9 @@ opengame help --json
|
|
|
27
28
|
|
|
28
29
|
`help --json` lists every command, flag, exit code, environment variable and event, with the finding schema. Read it rather than guessing a flag.
|
|
29
30
|
|
|
30
|
-
|
|
31
|
+
`opengame setup` installs every OpenGame skill in the home folder of each coding agent it finds (Claude Code, Codex, Cursor and OpenCode), and later commands keep them current. If your session started before that, read `opengame-router/SKILL.md` in the folder it names.
|
|
32
|
+
|
|
33
|
+
To commit the skills with the game instead:
|
|
31
34
|
|
|
32
35
|
```bash
|
|
33
36
|
opengame skills add .
|
|
@@ -105,7 +108,7 @@ opengame init . --title "My game" --json
|
|
|
105
108
|
opengame init . --title "Doom but blue" --kind mod --based-on "Doom" --json
|
|
106
109
|
```
|
|
107
110
|
|
|
108
|
-
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, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists,
|
|
111
|
+
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, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. A title or description you pass is offered back with its casing and grammar tidied, and `opengame publish --keep-words` keeps it as written. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists, `init` fills in only the fields it leaves blank; edit the file to change the rest.
|
|
109
112
|
|
|
110
113
|
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:
|
|
111
114
|
|
|
@@ -128,7 +131,7 @@ opengame deploy . --json
|
|
|
128
131
|
| `data.deploymentUrl` | The deploy's page. Give it to the creator straight away: it shows each check and plays the preview once they pass. |
|
|
129
132
|
| `data.state` | `uploading`, `queued`, `checking`, `ready`, `failed` or `expired`. |
|
|
130
133
|
| `data.done` | `true` once the server has finished. |
|
|
131
|
-
| `data.releaseId` | The release. Keep it
|
|
134
|
+
| `data.releaseId` | The release. Keep it: `opengame publish --release` takes it. |
|
|
132
135
|
| `data.previewUrl` | The private preview link, once `state` is `ready`. It can be `null` on a ready release the server will not play; the deploy's page says why. |
|
|
133
136
|
| `data.gameOrigin` | The origin the published game runs at, such as `https://k3v9q2m7x4ab.opengame.gg`. Give it to the creator when the game talks to their own servers. `null` when the server sent none, or sent one this CLI cannot read. |
|
|
134
137
|
|
|
@@ -172,16 +175,16 @@ Review starts automatically once a deploy is ready, so you submit no release. Re
|
|
|
172
175
|
|
|
173
176
|
When review passes, a game's first release waits to be published. `opengame status --json` shows `data.review.state: "awaiting_details"`, `data.review.next: "opengame publish"` and the deploy's page in `data.review.url`.
|
|
174
177
|
|
|
175
|
-
- **The creator asked you to publish it.** Run `opengame publish --json`. It confirms the title, description and genre review wrote, publishes, waits until the game is live and prints the address to share in `data.url`. Change what review wrote with `--description`, `--genre` and the other flags in `opengame publish --help`. While a new game goes on OpenGame only as a jam entry, pass the jam's track and the models used with `--track` and `--models`; `opengame jams <slug> --json` lists them.
|
|
178
|
+
- **The creator asked you to publish it.** Run `opengame publish --json`. It confirms the title, description and genre review wrote, publishes, waits until the game is live and prints the address to share in `data.url`. Change what review wrote with `--description`, `--genre` and the other flags in `opengame publish --help`. While a new game or an update goes on OpenGame only as a jam entry, pass the jam's track and the models used with `--track` and `--models`; `opengame jams <slug> --json` lists them.
|
|
176
179
|
- **They did not ask.** Give them `data.review.url`. Signed in, they check the details, enter the jam and publish on that page.
|
|
177
180
|
|
|
178
181
|
To publish in one step, `opengame deploy --publish --json` stays until review passes, then publishes, and takes the same jam flags.
|
|
179
182
|
|
|
180
183
|
An update to a game that is already live publishes by itself once it passes review. It keeps the live game's details, including the genre when the deploy left it to Auto, and its jam entry. The token that deployed it has to hold `submit`, as the `opengame login` token does. When the creator asked only for a preview of an update to a live game, deploy with a token made in their settings with `deploy` alone, set as `OPENGAME_TOKEN`, so the release waits for them.
|
|
181
184
|
|
|
182
|
-
`opengame submit` does not confirm a release that is already in review. The server keeps that submission and prints a `jam_answers_unused` notice: the jam answers you passed were not used. Pass them to `opengame publish` once review passes.
|
|
185
|
+
`opengame submit` does not confirm a release that is already in review. The server keeps that submission, and the CLI prints a `jam_answers_unused` notice: the jam answers you passed were not used. Pass them to `opengame publish` once review passes.
|
|
183
186
|
|
|
184
|
-
While Game Jam #1 runs, a new game goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
|
|
187
|
+
While Game Jam #1 runs, a new game or an update goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
|
|
185
188
|
|
|
186
189
|
Follow the release to the end:
|
|
187
190
|
|
|
@@ -192,10 +195,14 @@ opengame status --watch --json
|
|
|
192
195
|
| `data.review.state` | What to do |
|
|
193
196
|
| --- | --- |
|
|
194
197
|
| `review`, `playtesting`, `waiting` | Review is running. Watch again. |
|
|
198
|
+
| `approved` | Review passed. When `data.review.next` is `opengame publish`, do as for `awaiting_details`; otherwise watch again. |
|
|
195
199
|
| `awaiting_details` | Run `opengame publish --json` when the creator asked you to publish. Otherwise give them `data.review.url`, and watch again once they say they have published. |
|
|
196
200
|
| `needs_certification` | Give the creator `data.review.url`. Watch again once they say they have done it. |
|
|
197
|
-
| `publishing`, `published` | The game is going live. `data.submission.
|
|
198
|
-
| `returned` | Read the findings
|
|
201
|
+
| `publishing`, `published` | The game is going live. Once it is, `data.submission.live.url` is the address to share. |
|
|
202
|
+
| `returned` | Read the findings and run `data.review.next`. Usually that means fix the game and deploy again, and the new deploy is reviewed automatically. A jam entry returned for a fault on our side gets `opengame submit --release <id>` instead: the game needs no change, and the command names any jam answer it still needs. |
|
|
203
|
+
| `blocked` | Review refused the game. Give the creator `data.review.message`. |
|
|
204
|
+
| `withdrawn` | The creator withdrew this submission. Nothing more happens to it unless they ask you to enter it again. |
|
|
205
|
+
| `superseded` | Another submission took its place, and `data.submission.replacedBy` names it. Run `opengame status --json` again to follow that one. |
|
|
199
206
|
|
|
200
207
|
## What a game may do
|
|
201
208
|
|
package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/json-events.md
CHANGED
|
@@ -1,11 +1,13 @@
|
|
|
1
1
|
# Reading the CLI's JSON
|
|
2
2
|
|
|
3
|
-
With `--
|
|
4
|
-
last line, and the last line is always a `result` or an `error`.
|
|
3
|
+
With `--jsonl` every line of output is one JSON object. Four kinds can appear before the
|
|
4
|
+
last line, and the last line is always a `result` or an `error`. With `--json`, the default
|
|
5
|
+
in an agent, the command prints only that last object, carrying the same findings and
|
|
6
|
+
notices in its `findings` and `notices` arrays.
|
|
5
7
|
|
|
6
8
|
| `type` | Meaning | What to do |
|
|
7
9
|
| --- | --- | --- |
|
|
8
|
-
| `progress` | A stage started or moved on: `build`, `check`, `upload`, then the server's own stages for the deploy, `
|
|
10
|
+
| `progress` | A stage started or moved on: `install`, `build`, `package`, `check`, `upload`, then the server's own stages for the deploy, `review:<state>` while publish or submit follows review, `approval` for a login | Nothing; it is a heartbeat |
|
|
9
11
|
| `notice` | Something the person should know: excluded files, kept website metadata, a resumed upload, a sign-in URL | Read `code` and `message`; pass sign-in and kept-metadata notices on |
|
|
10
12
|
| `finding` | One problem in the game or one check that could not decide | Fix or report it, by its `fault`, `certainty` and `retry` |
|
|
11
13
|
| `result` | The command finished; `data` holds its answer | Read `data` |
|
|
@@ -28,22 +30,21 @@ last line, and the last line is always a `result` or an `error`.
|
|
|
28
30
|
|
|
29
31
|
A game whose `index.html` loads `./Game.js` while the file on disk is `game.js`. It runs
|
|
30
32
|
on the creator's Mac, because the Mac's file system ignores case, and is a missing file for every
|
|
31
|
-
player. `opengame check . --
|
|
33
|
+
player. `opengame check . --jsonl` prints:
|
|
32
34
|
|
|
33
35
|
```json
|
|
34
36
|
{"type":"finding","finding":{"release":null,"check":"case-mismatch","checkVersion":"packaging@1","state":"failed","certainty":"certain","fault":"game","evidence":{"observed":"index.html line 1 asks for Game.js, but the file is game.js.","file":"index.html:1"},"fix":"macOS and Windows do not care about capitalisation. The servers that hand your game to a player do. So this loads on your machine and the file is missing for everybody else. Fix the reference or rename the file so the two match exactly.","verify":"opengame check, then opengame deploy","retry":"after-fix"}}
|
|
35
|
-
{"type":"
|
|
37
|
+
{"type":"notice","code":"platform-engine","message":"Browser compatibility needs a playtest. Custom browser export: custom code. Static browser exports from any engine, or none, go to review, where a playtest checks that this one runs. Every game must pass the same runtime and safety checks before publication."}
|
|
36
38
|
{"type":"error","code":"check_failed","message":"This build has blockers. Fix them, then run opengame check again.","exitCode":1,"retry":"after-fix"}
|
|
37
39
|
```
|
|
38
40
|
|
|
39
41
|
Reading it:
|
|
40
42
|
|
|
41
|
-
1. The
|
|
43
|
+
1. The finding is `failed`, `certain` and `fault: "game"`, so it is the game's to
|
|
42
44
|
fix. `evidence.file` says `index.html:1`. Change `./Game.js` to `./game.js` there
|
|
43
45
|
(or rename the file), then run what `verify` says.
|
|
44
|
-
2. The
|
|
45
|
-
|
|
46
|
-
it go away; the playtest in review checks that the game runs.
|
|
46
|
+
2. The `platform-engine` line is a notice, not a finding. It blocks nothing. Do not add a
|
|
47
|
+
fake engine import to change it; the playtest in review checks that the game runs.
|
|
47
48
|
3. After the fix, `opengame check . --json` ends in a `result` and exits 0.
|
|
48
49
|
|
|
49
50
|
## Findings that are ours
|
|
@@ -58,6 +59,6 @@ exists to prevent.
|
|
|
58
59
|
|
|
59
60
|
- `deploy`: `operationId`, `state` (`uploading`, `queued`, `checking`, `ready`,
|
|
60
61
|
`failed`, `expired`), `gameId`, `releaseId`, `url`, and `timingsMs` when it finished.
|
|
61
|
-
Keep `releaseId`:
|
|
62
|
+
Keep `releaseId`: `opengame publish --release` and `opengame submit --release` name it.
|
|
62
63
|
- `check`: `files`, `bytes`, `excluded` and `findings`.
|
|
63
64
|
- `whoami`: the signed-in handle and the token's scopes.
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
The game's manifest, committed with its code. `opengame init` writes it; the website
|
|
4
4
|
edits the same fields. The game's id is never in this file: it lives in
|
|
5
5
|
`.opengame/project.json`, which is git-ignored, so a fork never deploys over somebody
|
|
6
|
-
else's game. Jam answers (track,
|
|
6
|
+
else's game. Jam answers (track, models, sponsors) are never stored here either, because
|
|
7
7
|
they belong to one entry, not to the game.
|
|
8
8
|
|
|
9
9
|
```json
|
|
@@ -21,16 +21,16 @@ they belong to one entry, not to the game.
|
|
|
21
21
|
|
|
22
22
|
| Field | Rule |
|
|
23
23
|
| --- | --- |
|
|
24
|
-
| `title` | 3 to 40 characters |
|
|
25
|
-
| `tagline` | Optional, up to 140 characters |
|
|
26
|
-
| `description` | 40 to 500 characters
|
|
27
|
-
| `genre` | Exactly one slug from the table below |
|
|
24
|
+
| `title` | 3 to 40 characters, or `auto` |
|
|
25
|
+
| `tagline` | Optional, up to 140 characters, or `auto` |
|
|
26
|
+
| `description` | 40 to 500 characters, or `auto`. Say what the player does |
|
|
27
|
+
| `genre` | Exactly one slug from the table below, or `auto` |
|
|
28
28
|
| `kind` | Optional. One of the four kinds below; leaving it out means `game`. `opengame init` always writes it |
|
|
29
29
|
| `basedOn` | The name of the game a `decomp` or a `mod` is made from, up to 60 characters, shown as "Mod of Doom". Required for a `decomp` or a `mod`, and not allowed for a `game` or a `world` |
|
|
30
30
|
| `build.command` | Optional, up to 1,000 characters. Run before checking; may read environment variables but must not contain a secret |
|
|
31
31
|
| `build.output` | The folder holding `index.html` after the build, or `.` |
|
|
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
|
-
| `controls` | One or more of `keyboard`, `mouse`, `gamepad`, each once |
|
|
33
|
+
| `controls` | One or more of `keyboard`, `mouse`, `gamepad`, each once, or `auto` |
|
|
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
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 |
|
|
@@ -72,12 +72,17 @@ it plays.
|
|
|
72
72
|
`opengame init --kind mod --based-on "Doom"` writes both. Without `--kind`, init makes a
|
|
73
73
|
game; it asks a person nothing but the game's name.
|
|
74
74
|
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
75
|
+
## Auto
|
|
76
|
+
|
|
77
|
+
`title`, `tagline`, `description`, `genre` and `controls` take `"auto"`, and a field that is
|
|
78
|
+
blank or left out means the same. `opengame init` writes `"auto"` for every one of them it is
|
|
79
|
+
not given. Review writes an Auto field from the game itself, and the creator accepts or
|
|
80
|
+
changes what it wrote on the deploy's page before anything publishes; the subgenre is always
|
|
81
|
+
review's. Do not ask the creator for a description or a genre before deploying. Once review
|
|
82
|
+
passes, `opengame publish --description` and `--genre` answer from here instead, and
|
|
83
|
+
`opengame details --description` changes the words once the game exists. A title or
|
|
84
|
+
description the creator typed is theirs: review offers a tidied copy on a first publish, and
|
|
85
|
+
`opengame publish --keep-words` keeps theirs.
|
|
81
86
|
|
|
82
87
|
## Who owns which value
|
|
83
88
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
> Carried from `opengame-jam` 1.1.
|
|
1
|
+
> Carried from `opengame-jam` 1.1.1. Read it when: Enter a game in an OpenGame jam. Finds the open jams, their tracks and rules, checks the game against them, deploys one exact release, and enters it with the person's own answers, with opengame publish or on the deploy's page. 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.
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
# Enter an OpenGame jam
|
|
@@ -105,7 +105,7 @@ its deploy already sent to review: it answers with that submission and a
|
|
|
105
105
|
## What only the person can do
|
|
106
106
|
|
|
107
107
|
Nobody certifies or attests to anything to enter. The person decides whether they are eligible (age, one account), whether they own
|
|
108
|
-
the assets, which track they want, and
|
|
108
|
+
the assets, which track they want, and which account they used at each sponsor.
|
|
109
109
|
|
|
110
110
|
## After submitting
|
|
111
111
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
> Carried from `opengame-performance` 1.1.
|
|
1
|
+
> Carried from `opengame-performance` 1.1.2. Read it when: Keep a browser game smooth on an ordinary laptop and a shared GPU, with three.js and WebGPU specifics. Covers frame-time tails counted from frames the engine ran, bare timing runs, cost over frame rate, frame pacing by what lands, draw calls per pass, a fixed light set and warm-up, uploads that never stall, the world lowered before the gameplay layer, and whole-tab memory. Use when the game stutters, hitches, drops frames, swings between rates, has a slow menu or a mouse that feels slow.
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
# Performance
|
|
@@ -20,8 +20,8 @@ upload ring) are in [references/webgpu.md](references/webgpu.md).
|
|
|
20
20
|
|
|
21
21
|
## Measure the running game
|
|
22
22
|
|
|
23
|
-
|
|
24
|
-
|
|
23
|
+
`opengame setup` installs `opengame-verification`; to add it to one project, run
|
|
24
|
+
`opengame skills add . --skill opengame-verification`. Use its `opengame-verification/helpers/browser-evidence.mjs` for frame-time samples and input evidence.
|
|
25
25
|
Set a frame-time tolerance from the target hardware's measured baseline. Record the
|
|
26
26
|
CPU throttle and soak duration alongside the result. Compare the same scene and
|
|
27
27
|
player route before and after a change. Inspect memory separately when diagnosing a
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
> Carried from `opengame-router` 1.0.
|
|
1
|
+
> Carried from `opengame-router` 1.0.9. Read it when: 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.
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
# Work on an OpenGame game
|
|
@@ -11,13 +11,15 @@ That is not a fault in the game.
|
|
|
11
11
|
Read [the working process](references/process.md) before changing the game. Keep the
|
|
12
12
|
user's scope and budget. Read only the specialists that apply to the next change.
|
|
13
13
|
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
`opengame
|
|
14
|
+
`opengame setup` installs every OpenGame skill for the agents on the machine, and the CLI
|
|
15
|
+
keeps them current. `opengame skills add .` installs a starting set into one project: this
|
|
16
|
+
router, `opengame-deploy` and `opengame-quality-bar`. Run `opengame skills list --json` to
|
|
17
|
+
see the installed CLI's catalog, and add a specialist to the project with
|
|
18
|
+
`opengame skills add . --skill <name>`.
|
|
17
19
|
|
|
18
20
|
| Work | Skill |
|
|
19
21
|
| --- | --- |
|
|
20
|
-
| Check, deploy, private preview,
|
|
22
|
+
| Check, deploy, private preview, publish | `opengame-deploy` |
|
|
21
23
|
| A CLI command, its output or its exit code | `opengame-cli` |
|
|
22
24
|
| Calling the API from your own tool or CI | `opengame-api` |
|
|
23
25
|
| Review the whole game | `opengame-quality-bar` |
|
|
@@ -6,8 +6,11 @@ ownership before editing. Use the host's permissions and available tools.
|
|
|
6
6
|
|
|
7
7
|
Choose the smallest change that completes the request. Ask for missing information
|
|
8
8
|
only when it changes what can be done safely or correctly. Keep publication and
|
|
9
|
-
account actions within the user's authorization. A deploy is a private
|
|
10
|
-
|
|
9
|
+
account actions within the user's authorization. A deploy of a new game is a private
|
|
10
|
+
preview, and publishing it needs the user's approval. An update of a game that is already
|
|
11
|
+
live publishes by itself once it passes review when the token can submit, as the
|
|
12
|
+
`opengame login` token can, so deploy one only when the user wants players to get it, or
|
|
13
|
+
follow `opengame-deploy` to deploy it as a preview.
|
|
11
14
|
|
|
12
15
|
Use the user's time, spend and reporting limits. Set a bounded checkpoint before
|
|
13
16
|
starting uncertain research or a paid call. Stop at that checkpoint and report the
|
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# opengame-cli changelog
|
|
2
2
|
|
|
3
|
+
## 1.9.2
|
|
4
|
+
|
|
5
|
+
`opengame jam withdraw` and `reenter` need a token with `submit` alone. The exit table has 7 (`not_launched`). `init` writes Auto for the fields it is not given, and `setup` keeps the skills current until `--no-skills` or `OPENGAME_SKILLS_AUTO=0` stops it. (17 Nov 2026)
|
|
6
|
+
|
|
7
|
+
## 1.9.1
|
|
8
|
+
|
|
9
|
+
The install is two lines: `npm i -g @opengamehq/cli`, then `opengame setup`, which installs every OpenGame skill in each coding agent's home folder. Later commands keep them current with the CLI; `opengame setup --no-skills` stops that. `opengame skills add` is for committing the skills with one project.
|
|
10
|
+
|
|
3
11
|
## 1.9.0
|
|
4
12
|
|
|
5
13
|
`opengame publish` publishes a release that passed review from the terminal, with the jam's answers as flags, and `opengame deploy --publish` waits for review and publishes in one command. An update of a live game publishes by itself (16 Nov 2026).
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: opengame-cli
|
|
3
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.9.
|
|
5
|
+
version: "1.9.2"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Use the OpenGame CLI
|
|
@@ -20,6 +20,7 @@ for the tool itself.
|
|
|
20
20
|
|
|
21
21
|
```bash
|
|
22
22
|
npm i -g @opengamehq/cli
|
|
23
|
+
opengame setup
|
|
23
24
|
```
|
|
24
25
|
|
|
25
26
|
Once `opengame` is installed, confirm it and read the command reference:
|
|
@@ -62,7 +63,7 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
62
63
|
|
|
63
64
|
| Command | What it does |
|
|
64
65
|
| --- | --- |
|
|
65
|
-
| `opengame init [dir]` | Create opengame.json for an existing game.
|
|
66
|
+
| `opengame init [dir]` | Create opengame.json for an existing game. Every field it is not given is `auto`: review writes it from the game, and the creator accepts or changes it on the deploy's page or with `opengame publish`. Asks a person only the game's name. |
|
|
66
67
|
| `opengame check [dir]` | Find local build and asset problems before uploading. |
|
|
67
68
|
| `opengame dev [dir]` | Serve a local export with the game runtime's headers. |
|
|
68
69
|
| `opengame login` | Sign in through the browser. |
|
|
@@ -91,7 +92,8 @@ token in a command argument, a file in the project, a log or a reply.
|
|
|
91
92
|
| `opengame logout` | Revoke this device's token and remove it. |
|
|
92
93
|
| `opengame limits` | Show bundle limits and the account's remaining allowance. |
|
|
93
94
|
| `opengame vendor [dir]` | Make a separate export with dependencies downloaded and pinned. |
|
|
94
|
-
| `opengame
|
|
95
|
+
| `opengame setup` | Install every OpenGame skill for the coding agents on this machine, and keep them current with the CLI. Other commands do the same on first run and after an update; `--no-skills` stops it for good, `OPENGAME_SKILLS_AUTO=0` for one run, and CI never gets it. |
|
|
96
|
+
| `opengame skills add or list` | Install the OpenGame skills into one project, to commit them with the game. |
|
|
95
97
|
| `opengame upgrade` | Install the current CLI, or print the line that does. |
|
|
96
98
|
| `opengame version` | Print the CLI version. |
|
|
97
99
|
|
|
@@ -150,7 +152,7 @@ back on. Retiring needs `deploy` and `submit`, which `opengame login` gives.
|
|
|
150
152
|
`opengame jam withdraw --yes --json` takes the linked game's entry out of the jam and frees
|
|
151
153
|
its place; the entry, its build and its certifications are kept. Run it only when the person
|
|
152
154
|
asks. `opengame jam reenter --json` puts the newest withdrawn entry back while the jam is
|
|
153
|
-
open, with the same reference and build. Both need `
|
|
155
|
+
open, with the same reference and build. Both need `submit`, which `opengame login` gives.
|
|
154
156
|
`at_entry_limit` means every place is taken: ask the person which entry to withdraw first.
|
|
155
157
|
`reenter_closed` means the jam is not taking entries; wait for it to open, and do not
|
|
156
158
|
re-enter after it closes. `jam_entry_taken` means a newer entry of the game is already in.
|
|
@@ -176,9 +178,9 @@ helps, `retry`, `retryAfterSeconds` and `next`, the command to run next.
|
|
|
176
178
|
| 4 | `rateLimited` | An allowance is used. Wait `retryAfterSeconds`, then run the same command. |
|
|
177
179
|
| 5 | `server` | Our side or the network; the game is fine. Follow `retry`. |
|
|
178
180
|
| 6 | `upgrade` | This CLI is too old. Run `opengame upgrade --json`. |
|
|
181
|
+
| 7 | `notLaunched` | OpenGame is not open to creators yet, and the error's code is `not_launched`. Run `opengame login`, then the same command again. |
|
|
179
182
|
|
|
180
|
-
|
|
181
|
-
error's `code` rather than the number wherever you can.
|
|
183
|
+
Branch on the error's `code` rather than the number wherever you can.
|
|
182
184
|
|
|
183
185
|
## Act on findings
|
|
184
186
|
|
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# opengame-deploy changelog
|
|
2
2
|
|
|
3
|
+
## 1.1.9
|
|
4
|
+
|
|
5
|
+
`opengame.json` takes `auto` for the title, tagline, description, genre and controls, which review writes. The JSON reference tells `--json` (one object) from `--jsonl` (one event a line), lists the stages the CLI emits, and shows `platform-engine` as a notice. The procedure says what each review state means, `approved`, `blocked`, `withdrawn` and `superseded` included, and keeps `releaseId` for `opengame publish --release`. (17 Nov 2026)
|
|
6
|
+
|
|
7
|
+
## 1.1.8
|
|
8
|
+
|
|
9
|
+
Install runs `opengame setup` after the CLI, which gives every agent on the machine the OpenGame skills and keeps them current. `opengame skills add .` stays for a project that commits its skills.
|
|
10
|
+
|
|
3
11
|
## 1.1.7
|
|
4
12
|
|
|
5
13
|
An agent publishes with `opengame publish` or `opengame deploy --publish` when the creator asks, and otherwise gives them the deploy's page. An update of a live game publishes by itself, keeping its details and jam entry (16 Nov 2026).
|
|
@@ -2,7 +2,7 @@
|
|
|
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 hands the creator the page where they confirm the details after 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.1.
|
|
5
|
+
version: "1.1.9"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Deploy a browser game to OpenGame
|
|
@@ -20,6 +20,7 @@ Deploy the creator's game to a private preview and give them its link. Review st
|
|
|
20
20
|
|
|
21
21
|
```bash
|
|
22
22
|
npm i -g @opengamehq/cli
|
|
23
|
+
opengame setup
|
|
23
24
|
```
|
|
24
25
|
|
|
25
26
|
Once `opengame` is installed, confirm it and read the command reference:
|
|
@@ -31,7 +32,9 @@ opengame help --json
|
|
|
31
32
|
|
|
32
33
|
`help --json` lists every command, flag, exit code, environment variable and event, with the finding schema. Read it rather than guessing a flag.
|
|
33
34
|
|
|
34
|
-
|
|
35
|
+
`opengame setup` installs every OpenGame skill in the home folder of each coding agent it finds (Claude Code, Codex, Cursor and OpenCode), and later commands keep them current. If your session started before that, read `opengame-router/SKILL.md` in the folder it names.
|
|
36
|
+
|
|
37
|
+
To commit the skills with the game instead:
|
|
35
38
|
|
|
36
39
|
```bash
|
|
37
40
|
opengame skills add .
|
|
@@ -109,7 +112,7 @@ opengame init . --title "My game" --json
|
|
|
109
112
|
opengame init . --title "Doom but blue" --kind mod --based-on "Doom" --json
|
|
110
113
|
```
|
|
111
114
|
|
|
112
|
-
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, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists,
|
|
115
|
+
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, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. A title or description you pass is offered back with its casing and grammar tidied, and `opengame publish --keep-words` keeps it as written. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists, `init` fills in only the fields it leaves blank; edit the file to change the rest.
|
|
113
116
|
|
|
114
117
|
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:
|
|
115
118
|
|
|
@@ -132,7 +135,7 @@ opengame deploy . --json
|
|
|
132
135
|
| `data.deploymentUrl` | The deploy's page. Give it to the creator straight away: it shows each check and plays the preview once they pass. |
|
|
133
136
|
| `data.state` | `uploading`, `queued`, `checking`, `ready`, `failed` or `expired`. |
|
|
134
137
|
| `data.done` | `true` once the server has finished. |
|
|
135
|
-
| `data.releaseId` | The release. Keep it
|
|
138
|
+
| `data.releaseId` | The release. Keep it: `opengame publish --release` takes it. |
|
|
136
139
|
| `data.previewUrl` | The private preview link, once `state` is `ready`. It can be `null` on a ready release the server will not play; the deploy's page says why. |
|
|
137
140
|
| `data.gameOrigin` | The origin the published game runs at, such as `https://k3v9q2m7x4ab.opengame.gg`. Give it to the creator when the game talks to their own servers. `null` when the server sent none, or sent one this CLI cannot read. |
|
|
138
141
|
|
|
@@ -176,16 +179,16 @@ Review starts automatically once a deploy is ready, so you submit no release. Re
|
|
|
176
179
|
|
|
177
180
|
When review passes, a game's first release waits to be published. `opengame status --json` shows `data.review.state: "awaiting_details"`, `data.review.next: "opengame publish"` and the deploy's page in `data.review.url`.
|
|
178
181
|
|
|
179
|
-
- **The creator asked you to publish it.** Run `opengame publish --json`. It confirms the title, description and genre review wrote, publishes, waits until the game is live and prints the address to share in `data.url`. Change what review wrote with `--description`, `--genre` and the other flags in `opengame publish --help`. While a new game goes on OpenGame only as a jam entry, pass the jam's track and the models used with `--track` and `--models`; `opengame jams <slug> --json` lists them.
|
|
182
|
+
- **The creator asked you to publish it.** Run `opengame publish --json`. It confirms the title, description and genre review wrote, publishes, waits until the game is live and prints the address to share in `data.url`. Change what review wrote with `--description`, `--genre` and the other flags in `opengame publish --help`. While a new game or an update goes on OpenGame only as a jam entry, pass the jam's track and the models used with `--track` and `--models`; `opengame jams <slug> --json` lists them.
|
|
180
183
|
- **They did not ask.** Give them `data.review.url`. Signed in, they check the details, enter the jam and publish on that page.
|
|
181
184
|
|
|
182
185
|
To publish in one step, `opengame deploy --publish --json` stays until review passes, then publishes, and takes the same jam flags.
|
|
183
186
|
|
|
184
187
|
An update to a game that is already live publishes by itself once it passes review. It keeps the live game's details, including the genre when the deploy left it to Auto, and its jam entry. The token that deployed it has to hold `submit`, as the `opengame login` token does. When the creator asked only for a preview of an update to a live game, deploy with a token made in their settings with `deploy` alone, set as `OPENGAME_TOKEN`, so the release waits for them.
|
|
185
188
|
|
|
186
|
-
`opengame submit` does not confirm a release that is already in review. The server keeps that submission and prints a `jam_answers_unused` notice: the jam answers you passed were not used. Pass them to `opengame publish` once review passes.
|
|
189
|
+
`opengame submit` does not confirm a release that is already in review. The server keeps that submission, and the CLI prints a `jam_answers_unused` notice: the jam answers you passed were not used. Pass them to `opengame publish` once review passes.
|
|
187
190
|
|
|
188
|
-
While Game Jam #1 runs, a new game goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
|
|
191
|
+
While Game Jam #1 runs, a new game or an update goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
|
|
189
192
|
|
|
190
193
|
Follow the release to the end:
|
|
191
194
|
|
|
@@ -196,10 +199,14 @@ opengame status --watch --json
|
|
|
196
199
|
| `data.review.state` | What to do |
|
|
197
200
|
| --- | --- |
|
|
198
201
|
| `review`, `playtesting`, `waiting` | Review is running. Watch again. |
|
|
202
|
+
| `approved` | Review passed. When `data.review.next` is `opengame publish`, do as for `awaiting_details`; otherwise watch again. |
|
|
199
203
|
| `awaiting_details` | Run `opengame publish --json` when the creator asked you to publish. Otherwise give them `data.review.url`, and watch again once they say they have published. |
|
|
200
204
|
| `needs_certification` | Give the creator `data.review.url`. Watch again once they say they have done it. |
|
|
201
|
-
| `publishing`, `published` | The game is going live. `data.submission.
|
|
202
|
-
| `returned` | Read the findings
|
|
205
|
+
| `publishing`, `published` | The game is going live. Once it is, `data.submission.live.url` is the address to share. |
|
|
206
|
+
| `returned` | Read the findings and run `data.review.next`. Usually that means fix the game and deploy again, and the new deploy is reviewed automatically. A jam entry returned for a fault on our side gets `opengame submit --release <id>` instead: the game needs no change, and the command names any jam answer it still needs. |
|
|
207
|
+
| `blocked` | Review refused the game. Give the creator `data.review.message`. |
|
|
208
|
+
| `withdrawn` | The creator withdrew this submission. Nothing more happens to it unless they ask you to enter it again. |
|
|
209
|
+
| `superseded` | Another submission took its place, and `data.submission.replacedBy` names it. Run `opengame status --json` again to follow that one. |
|
|
203
210
|
|
|
204
211
|
## What a game may do
|
|
205
212
|
|
|
@@ -1,11 +1,13 @@
|
|
|
1
1
|
# Reading the CLI's JSON
|
|
2
2
|
|
|
3
|
-
With `--
|
|
4
|
-
last line, and the last line is always a `result` or an `error`.
|
|
3
|
+
With `--jsonl` every line of output is one JSON object. Four kinds can appear before the
|
|
4
|
+
last line, and the last line is always a `result` or an `error`. With `--json`, the default
|
|
5
|
+
in an agent, the command prints only that last object, carrying the same findings and
|
|
6
|
+
notices in its `findings` and `notices` arrays.
|
|
5
7
|
|
|
6
8
|
| `type` | Meaning | What to do |
|
|
7
9
|
| --- | --- | --- |
|
|
8
|
-
| `progress` | A stage started or moved on: `build`, `check`, `upload`, then the server's own stages for the deploy, `
|
|
10
|
+
| `progress` | A stage started or moved on: `install`, `build`, `package`, `check`, `upload`, then the server's own stages for the deploy, `review:<state>` while publish or submit follows review, `approval` for a login | Nothing; it is a heartbeat |
|
|
9
11
|
| `notice` | Something the person should know: excluded files, kept website metadata, a resumed upload, a sign-in URL | Read `code` and `message`; pass sign-in and kept-metadata notices on |
|
|
10
12
|
| `finding` | One problem in the game or one check that could not decide | Fix or report it, by its `fault`, `certainty` and `retry` |
|
|
11
13
|
| `result` | The command finished; `data` holds its answer | Read `data` |
|
|
@@ -28,22 +30,21 @@ last line, and the last line is always a `result` or an `error`.
|
|
|
28
30
|
|
|
29
31
|
A game whose `index.html` loads `./Game.js` while the file on disk is `game.js`. It runs
|
|
30
32
|
on the creator's Mac, because the Mac's file system ignores case, and is a missing file for every
|
|
31
|
-
player. `opengame check . --
|
|
33
|
+
player. `opengame check . --jsonl` prints:
|
|
32
34
|
|
|
33
35
|
```json
|
|
34
36
|
{"type":"finding","finding":{"release":null,"check":"case-mismatch","checkVersion":"packaging@1","state":"failed","certainty":"certain","fault":"game","evidence":{"observed":"index.html line 1 asks for Game.js, but the file is game.js.","file":"index.html:1"},"fix":"macOS and Windows do not care about capitalisation. The servers that hand your game to a player do. So this loads on your machine and the file is missing for everybody else. Fix the reference or rename the file so the two match exactly.","verify":"opengame check, then opengame deploy","retry":"after-fix"}}
|
|
35
|
-
{"type":"
|
|
37
|
+
{"type":"notice","code":"platform-engine","message":"Browser compatibility needs a playtest. Custom browser export: custom code. Static browser exports from any engine, or none, go to review, where a playtest checks that this one runs. Every game must pass the same runtime and safety checks before publication."}
|
|
36
38
|
{"type":"error","code":"check_failed","message":"This build has blockers. Fix them, then run opengame check again.","exitCode":1,"retry":"after-fix"}
|
|
37
39
|
```
|
|
38
40
|
|
|
39
41
|
Reading it:
|
|
40
42
|
|
|
41
|
-
1. The
|
|
43
|
+
1. The finding is `failed`, `certain` and `fault: "game"`, so it is the game's to
|
|
42
44
|
fix. `evidence.file` says `index.html:1`. Change `./Game.js` to `./game.js` there
|
|
43
45
|
(or rename the file), then run what `verify` says.
|
|
44
|
-
2. The
|
|
45
|
-
|
|
46
|
-
it go away; the playtest in review checks that the game runs.
|
|
46
|
+
2. The `platform-engine` line is a notice, not a finding. It blocks nothing. Do not add a
|
|
47
|
+
fake engine import to change it; the playtest in review checks that the game runs.
|
|
47
48
|
3. After the fix, `opengame check . --json` ends in a `result` and exits 0.
|
|
48
49
|
|
|
49
50
|
## Findings that are ours
|
|
@@ -58,6 +59,6 @@ exists to prevent.
|
|
|
58
59
|
|
|
59
60
|
- `deploy`: `operationId`, `state` (`uploading`, `queued`, `checking`, `ready`,
|
|
60
61
|
`failed`, `expired`), `gameId`, `releaseId`, `url`, and `timingsMs` when it finished.
|
|
61
|
-
Keep `releaseId`:
|
|
62
|
+
Keep `releaseId`: `opengame publish --release` and `opengame submit --release` name it.
|
|
62
63
|
- `check`: `files`, `bytes`, `excluded` and `findings`.
|
|
63
64
|
- `whoami`: the signed-in handle and the token's scopes.
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
The game's manifest, committed with its code. `opengame init` writes it; the website
|
|
4
4
|
edits the same fields. The game's id is never in this file: it lives in
|
|
5
5
|
`.opengame/project.json`, which is git-ignored, so a fork never deploys over somebody
|
|
6
|
-
else's game. Jam answers (track,
|
|
6
|
+
else's game. Jam answers (track, models, sponsors) are never stored here either, because
|
|
7
7
|
they belong to one entry, not to the game.
|
|
8
8
|
|
|
9
9
|
```json
|
|
@@ -21,16 +21,16 @@ they belong to one entry, not to the game.
|
|
|
21
21
|
|
|
22
22
|
| Field | Rule |
|
|
23
23
|
| --- | --- |
|
|
24
|
-
| `title` | 3 to 40 characters |
|
|
25
|
-
| `tagline` | Optional, up to 140 characters |
|
|
26
|
-
| `description` | 40 to 500 characters
|
|
27
|
-
| `genre` | Exactly one slug from the table below |
|
|
24
|
+
| `title` | 3 to 40 characters, or `auto` |
|
|
25
|
+
| `tagline` | Optional, up to 140 characters, or `auto` |
|
|
26
|
+
| `description` | 40 to 500 characters, or `auto`. Say what the player does |
|
|
27
|
+
| `genre` | Exactly one slug from the table below, or `auto` |
|
|
28
28
|
| `kind` | Optional. One of the four kinds below; leaving it out means `game`. `opengame init` always writes it |
|
|
29
29
|
| `basedOn` | The name of the game a `decomp` or a `mod` is made from, up to 60 characters, shown as "Mod of Doom". Required for a `decomp` or a `mod`, and not allowed for a `game` or a `world` |
|
|
30
30
|
| `build.command` | Optional, up to 1,000 characters. Run before checking; may read environment variables but must not contain a secret |
|
|
31
31
|
| `build.output` | The folder holding `index.html` after the build, or `.` |
|
|
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
|
-
| `controls` | One or more of `keyboard`, `mouse`, `gamepad`, each once |
|
|
33
|
+
| `controls` | One or more of `keyboard`, `mouse`, `gamepad`, each once, or `auto` |
|
|
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
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 |
|
|
@@ -72,12 +72,17 @@ it plays.
|
|
|
72
72
|
`opengame init --kind mod --based-on "Doom"` writes both. Without `--kind`, init makes a
|
|
73
73
|
game; it asks a person nothing but the game's name.
|
|
74
74
|
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
75
|
+
## Auto
|
|
76
|
+
|
|
77
|
+
`title`, `tagline`, `description`, `genre` and `controls` take `"auto"`, and a field that is
|
|
78
|
+
blank or left out means the same. `opengame init` writes `"auto"` for every one of them it is
|
|
79
|
+
not given. Review writes an Auto field from the game itself, and the creator accepts or
|
|
80
|
+
changes what it wrote on the deploy's page before anything publishes; the subgenre is always
|
|
81
|
+
review's. Do not ask the creator for a description or a genre before deploying. Once review
|
|
82
|
+
passes, `opengame publish --description` and `--genre` answer from here instead, and
|
|
83
|
+
`opengame details --description` changes the words once the game exists. A title or
|
|
84
|
+
description the creator typed is theirs: review offers a tidied copy on a first publish, and
|
|
85
|
+
`opengame publish --keep-words` keeps theirs.
|
|
81
86
|
|
|
82
87
|
## Who owns which value
|
|
83
88
|
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-jam changelog
|
|
2
2
|
|
|
3
|
+
## 1.1.1
|
|
4
|
+
|
|
5
|
+
Ask for the account email the person used at each sponsor, which `--sponsor-email` takes, not sponsor evidence. (17 Nov 2026)
|
|
6
|
+
|
|
3
7
|
## 1.1.0
|
|
4
8
|
|
|
5
9
|
The entry is made with `opengame publish --track ... --models ...` when the person asks, or on the deploy's page. Nobody certifies anything to enter (16 Nov 2026).
|
|
@@ -2,7 +2,7 @@
|
|
|
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, deploys one exact release, and enters it with the person's own answers, with opengame publish or on the deploy's page. 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.1.
|
|
5
|
+
version: "1.1.1"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Enter an OpenGame jam
|
|
@@ -109,7 +109,7 @@ its deploy already sent to review: it answers with that submission and a
|
|
|
109
109
|
## What only the person can do
|
|
110
110
|
|
|
111
111
|
Nobody certifies or attests to anything to enter. The person decides whether they are eligible (age, one account), whether they own
|
|
112
|
-
the assets, which track they want, and
|
|
112
|
+
the assets, which track they want, and which account they used at each sponsor.
|
|
113
113
|
|
|
114
114
|
## After submitting
|
|
115
115
|
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-performance changelog
|
|
2
2
|
|
|
3
|
+
## 1.1.2
|
|
4
|
+
|
|
5
|
+
`opengame setup` already installs `opengame-verification`; `opengame skills add . --skill opengame-verification` adds it to one project. (17 Nov 2026)
|
|
6
|
+
|
|
3
7
|
## 1.1.1
|
|
4
8
|
|
|
5
9
|
`landing-pacer.mjs` lets a frame whose promise rejects leave the queue, so two failed submits no longer hold every later frame; `stats()` counts them as `failed`.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: opengame-performance
|
|
3
3
|
description: Keep a browser game smooth on an ordinary laptop and a shared GPU, with three.js and WebGPU specifics. Covers frame-time tails counted from frames the engine ran, bare timing runs, cost over frame rate, frame pacing by what lands, draw calls per pass, a fixed light set and warm-up, uploads that never stall, the world lowered before the gameplay layer, and whole-tab memory. Use when the game stutters, hitches, drops frames, swings between rates, has a slow menu or a mouse that feels slow.
|
|
4
4
|
metadata:
|
|
5
|
-
version: "1.1.
|
|
5
|
+
version: "1.1.2"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Performance
|
|
@@ -24,8 +24,8 @@ upload ring) are in [references/webgpu.md](references/webgpu.md).
|
|
|
24
24
|
|
|
25
25
|
## Measure the running game
|
|
26
26
|
|
|
27
|
-
|
|
28
|
-
|
|
27
|
+
`opengame setup` installs `opengame-verification`; to add it to one project, run
|
|
28
|
+
`opengame skills add . --skill opengame-verification`. Use its `opengame-verification/helpers/browser-evidence.mjs` for frame-time samples and input evidence.
|
|
29
29
|
Set a frame-time tolerance from the target hardware's measured baseline. Record the
|
|
30
30
|
CPU throttle and soak duration alongside the result. Compare the same scene and
|
|
31
31
|
player route before and after a change. Inspect memory separately when diagnosing a
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# opengame-router changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.9
|
|
4
|
+
|
|
5
|
+
`opengame setup` installs every skill; the starting set is what `opengame skills add .` puts in one project. An update of a game that is already live publishes by itself. (17 Nov 2026)
|
|
6
|
+
|
|
3
7
|
## 1.0.8
|
|
4
8
|
|
|
5
9
|
Routes maps to `opengame-maps`, multiplayer to `opengame-multiplayer`, rhythm games to `opengame-rhythm`, trailers and montages to the six video skills, and names `opengame-all-in-one`, which carries every skill as one install.
|
|
@@ -2,7 +2,7 @@
|
|
|
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.9"
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Work on an OpenGame game
|
|
@@ -15,13 +15,15 @@ That is not a fault in the game.
|
|
|
15
15
|
Read [the working process](references/process.md) before changing the game. Keep the
|
|
16
16
|
user's scope and budget. Read only the specialists that apply to the next change.
|
|
17
17
|
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
`opengame
|
|
18
|
+
`opengame setup` installs every OpenGame skill for the agents on the machine, and the CLI
|
|
19
|
+
keeps them current. `opengame skills add .` installs a starting set into one project: this
|
|
20
|
+
router, `opengame-deploy` and `opengame-quality-bar`. Run `opengame skills list --json` to
|
|
21
|
+
see the installed CLI's catalog, and add a specialist to the project with
|
|
22
|
+
`opengame skills add . --skill <name>`.
|
|
21
23
|
|
|
22
24
|
| Work | Skill |
|
|
23
25
|
| --- | --- |
|
|
24
|
-
| Check, deploy, private preview,
|
|
26
|
+
| Check, deploy, private preview, publish | `opengame-deploy` |
|
|
25
27
|
| A CLI command, its output or its exit code | `opengame-cli` |
|
|
26
28
|
| Calling the API from your own tool or CI | `opengame-api` |
|
|
27
29
|
| Review the whole game | `opengame-quality-bar` |
|
|
@@ -6,8 +6,11 @@ ownership before editing. Use the host's permissions and available tools.
|
|
|
6
6
|
|
|
7
7
|
Choose the smallest change that completes the request. Ask for missing information
|
|
8
8
|
only when it changes what can be done safely or correctly. Keep publication and
|
|
9
|
-
account actions within the user's authorization. A deploy is a private
|
|
10
|
-
|
|
9
|
+
account actions within the user's authorization. A deploy of a new game is a private
|
|
10
|
+
preview, and publishing it needs the user's approval. An update of a game that is already
|
|
11
|
+
live publishes by itself once it passes review when the token can submit, as the
|
|
12
|
+
`opengame login` token can, so deploy one only when the user wants players to get it, or
|
|
13
|
+
follow `opengame-deploy` to deploy it as a preview.
|
|
11
14
|
|
|
12
15
|
Use the user's time, spend and reporting limits. Set a bounded checkpoint before
|
|
13
16
|
starting uncertain research or a paid call. Stop at that checkpoint and report the
|