@opengamehq/cli 0.12.0 → 0.13.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/AGENTS.md CHANGED
@@ -101,7 +101,7 @@ opengame init . --title "My game" --json
101
101
  opengame init . --title "Doom but blue" --kind mod --based-on "Doom" --json
102
102
  ```
103
103
 
104
- 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.
104
+ Do not ask the creator for a description or a genre before deploying. When you know them, pass `--description` (40 characters or more), `--genre` and `--players`; 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.
105
105
 
106
106
  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:
107
107
 
package/CHANGELOG.md CHANGED
@@ -1,5 +1,16 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.13.0
4
+
5
+ - `opengame.json` says how the game is played with `players`: `"single"`, or
6
+ `{ "mode": "private", "min": 2, "max": 8 }` for friends who join by a code or a link, or
7
+ `"mode": "online"` for players matched with strangers. `min` 1 is a game that can also be
8
+ played alone. Left out, or `"auto"`, review works it out and the deploy's page offers it. A
9
+ file with the older `"multiplayer": { "mode": "none" | "p2p" }` deploys as before.
10
+ - `opengame init` writes `"players": "auto"`, or what `--players`, `--min-players` and
11
+ `--max-players` say, and `opengame publish` takes the same three flags.
12
+ - `opengame pull` writes the website's players back as `players`.
13
+
3
14
  ## 0.12.0
4
15
 
5
16
  - Unreal Engine 5.9 Wasm packages. `opengame init` recognises a `.uproject`, sets the export