@opengamehq/cli 0.11.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
 
@@ -219,7 +219,9 @@ OpenGame runs no game server or rooms. A multiplayer game brings its own, throug
219
219
 
220
220
  ## Engines
221
221
 
222
- OpenGame supports games built with Three.js, Unity, Godot, Kaigen and WebAssembly, and static web builds from any JavaScript engine. `opengame check` and the server detect the engine from the build. Any other static browser export uploads as a custom build, under the same file and runtime checks.
222
+ OpenGame supports games built with Three.js, Unity, Godot, Unreal Engine, Kaigen and WebAssembly, and static web builds from any JavaScript engine. `opengame check` and the server detect the engine from the build. Any other static browser export uploads as a custom build, under the same file and runtime checks.
223
+
224
+ Any web framework works once it builds static files: Vite, React, React Three Fiber, webpack, Parcel, Astro, SvelteKit with adapter-static, Nuxt with `nuxt generate`, and Next.js with `output: "export"` in `next.config`, which writes `out/`. `init` reads the framework's config and writes the folder the build fills. A project configured for a server fails with `static_build_required`, which names the setting to change; change that setting instead of passing `--output`. [Web frameworks](https://docs.opengame.io/guides/web-frameworks) has each one.
223
225
 
224
226
  Run `opengame init . --engine <id>` to record an engine's export folder. `opengame help --json` lists the IDs, and `init` prints the export steps and the guide for the one you choose. The [engine overview](https://docs.opengame.io/engines/overview) links every engine page.
225
227
 
package/CHANGELOG.md CHANGED
@@ -1,5 +1,44 @@
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
+
14
+ ## 0.12.0
15
+
16
+ - Unreal Engine 5.9 Wasm packages. `opengame init` recognises a `.uproject`, sets the export
17
+ folder to `Build/Wasm` and adds `"requires": { "renderer": "webgpu" }`, and run inside a
18
+ package it names Unreal Engine from the package itself. `check` admits the Brotli copies
19
+ Unreal writes beside its `.pak`, `.utoc`, `.ushaderbytecode`, `.stinfo` and `.json` files, and
20
+ leaves out `index.html.br`, a compressed copy of the page that OpenGame never serves.
21
+ - `check` no longer runs out of memory on a large Brotli-compressed `.wasm`: a 140 MB module
22
+ stopped it with "invalid array length" before it printed anything.
23
+ - `opengame init` reads a site framework's own config for the output folder: `out/` for a
24
+ Next.js static export (or `distDir`), `dist/` for Astro, `build/` for SvelteKit's
25
+ adapter-static (or `pages`), `.output/public/` for `nuxt generate`, webpack's
26
+ `output.path`, and parcel's default `dist/`. Until now a Next.js game with three.js in it
27
+ got `dist/`, and a webpack or parcel project could get its source page.
28
+ - A project set to build a server stops with `static_build_required` and the setting to
29
+ change: a Next.js app without `output: "export"`, SvelteKit without adapter-static,
30
+ `nuxt build`, Astro's server output, or a base path such as Next.js `basePath: "/game"`.
31
+ - A multi-page build is one export: pages inside the build folder, and the copy SvelteKit
32
+ keeps under `.svelte-kit/`, are no longer offered as separate choices.
33
+ - `opengame dev` serves `/menu/` as `menu/index.html`, `/about` as `about.html`, and sends
34
+ `/menu` to `/menu/`, the way games are served on OpenGame.
35
+ - `~/.config/opengame/skills.json` records each agent's own CLI version and skills, so
36
+ `opengame setup --agent codex` after an update leaves Claude Code to be refreshed by the next
37
+ command rather than marking it current. A file from before is read as each agent's own.
38
+ - An `opengame setup --no-skills` saved while another command was installing skills stands:
39
+ every change to that file is read and written under a lock, from the file as it is then.
40
+ - Carries the skills from `@opengamehq/skills` 1.7.1.
41
+
3
42
  ## 0.11.0
4
43
 
5
44
  - `opengame setup` gives your coding agents the OpenGame skills: every skill this CLI carries,
@@ -17,11 +56,6 @@
17
56
  - The staging folder an install uses beside an agent's folder must be a real folder, never a
18
57
  link, and is tidied only where an install writes.
19
58
  - Carries the skills from `@opengamehq/skills` 1.7.0, which install the CLI with `opengame setup`.
20
- - `~/.config/opengame/skills.json` records each agent's own CLI version and skills, so
21
- `opengame setup --agent codex` after an update leaves Claude Code to be refreshed by the next
22
- command rather than marking it current. A file from before is read as each agent's own.
23
- - An `opengame setup --no-skills` saved while another command was installing skills stands:
24
- every change to that file is read and written under a lock, from the file as it is then.
25
59
  - `opengame` with no command lists `publish` among the first five, in place of `submit`, which
26
60
  is now only for a release that was not sent to review by itself. `achievements` no longer
27
61
  says the website has a retire control; `opengame achievements retire` is the way.