@opengamehq/skills 1.1.0 → 1.3.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 CHANGED
@@ -1,5 +1,16 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.3.0
4
+
5
+ - `opengame-cli` 1.2.0 teaches `opengame unpublish` and `opengame restore`, run only when
6
+ the person asks, 1.3.0 `opengame details` and `opengame handle`, 1.4.0 `opengame jam
7
+ withdraw` and `opengame jam reenter`, 1.5.0 `opengame delete`, 1.6.0 `opengame achievements`, and 1.7.0 `opengame stats --csv`.
8
+
9
+ ## 1.2.0
10
+
11
+ - `opengame-cli` 1.1.0 teaches `opengame releases` and `opengame rollback`, and says to
12
+ roll a live game back only with the person's go-ahead.
13
+
3
14
  ## 1.1.0
4
15
 
5
16
  - `opengame-sdk` 1.0.9 teaches OG Radio (`og.radio` and its picker, in
@@ -118,15 +118,15 @@
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.0.4",
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.7.0",
123
123
  "files": [
124
124
  {
125
125
  "path": "SKILL.md",
126
- "sha256": "ebf6a1a3e35f3cc634fdb3a815da28965ed27ff38c59734a6ac05f1e7afffa97"
126
+ "sha256": "5fb9980e516b888762180bd2179d3da795ca8c1a2b4cb01744741759daec54f1"
127
127
  }
128
128
  ],
129
- "digest": "b51714f57d2e43a6d70ece4444eea19cc2525663968638a7a02060996d034d07"
129
+ "digest": "8b8156881cff565369a5bb21f005c7c5fb3166b726e1b0dfd6f92b050e74f750"
130
130
  },
131
131
  {
132
132
  "name": "opengame-deploy",
@@ -1,5 +1,33 @@
1
1
  # opengame-cli changelog
2
2
 
3
+ ## 1.7.0
4
+
5
+ Teaches `opengame stats --csv`.
6
+
7
+ ## 1.6.0
8
+
9
+ Teaches `opengame achievements` and `opengame achievements retire`.
10
+
11
+ ## 1.5.0
12
+
13
+ Teaches `opengame delete`: only when the person asks for that game to be deleted, with the title they confirmed, and unpublish offered first.
14
+
15
+ ## 1.4.0
16
+
17
+ Teaches `opengame jam withdraw` and `opengame jam reenter`.
18
+
19
+ ## 1.3.0
20
+
21
+ Teaches `opengame details` and `opengame handle`: changing a game's words on the website, and renaming the person's handle with their go-ahead.
22
+
23
+ ## 1.2.0
24
+
25
+ Teaches `opengame unpublish` and `opengame restore`: taking a game off the gallery and putting it back, only when the person asks.
26
+
27
+ ## 1.1.0
28
+
29
+ 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.
30
+
3
31
  ## 1.0.4
4
32
 
5
33
  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,8 +1,8 @@
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.0.4"
5
+ version: "1.7.0"
6
6
  ---
7
7
 
8
8
  # Use the OpenGame CLI
@@ -71,6 +71,15 @@ token in a command argument, a file in the project, a log or a reply.
71
71
  | `opengame open [dir]` | Open the linked game's private page. |
72
72
  | `opengame submit [dir]` | Send one release to review, and enter it in a jam. |
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
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@opengamehq/skills",
3
- "version": "1.1.0",
3
+ "version": "1.3.0",
4
4
  "description": "Agent skills for making browser games and putting them on OpenGame.",
5
5
  "keywords": [
6
6
  "opengame",