@hopple/sdk 0.1.0-rc.3 → 1.0.0-next.1

package/manifest.md

@@ -15,37 +15,40 @@ and the host never asks the game what it is allowed to do.
 
 ```json
 {
-  "schema": 1,
+  "api": "1.0",
   "id": "ping",
   "version": "1.0.0",
   "title": "Ping",
   "orientation": "portrait",
-  "sdk": "^0.1.0",
   "audio": null
 }
 ```
 
-These seven keys are required. Everything else is optional.
+These six keys are required. Everything else is optional. A hopple config may
+leave `api` and `previews` out: the CLI fills `api` from the installed
+`@hopple/sdk`, and `previews` from the preview packages the project installs.
 
 | Key | Rules | Meaning |
 |---|---|---|
-| `schema` | `1` | The manifest format version. |
+| `api` | `MAJOR.MINOR`, or `next` | The API the game is written against: the major picks what the game is served, the minor is the least it needs. `next` is the pre-releases of the next stable release. Left out of a config, the CLI takes it from the installed `@hopple/sdk` (`1.6.2` is `1.6`, a pre-release is `next`), and refuses one that differs. Publishing is refused until the major has a release of that minor, on `next` until it has a release, and on `next` for users who are neither trusted, admins, nor explicitly granted access. |
 | `id` | lowercase letters, digits and single hyphens; at most 64 characters | The game's name. On the server, a game is `<owner>/<id>`. |
 | `version` | `MAJOR.MINOR.PATCH`, optional `-prerelease` | The game's own version. Shown to the game as `sdk.info.game.version`. |
 | `title` | at most 60 characters | What players see. |
 | `description` | optional; at most 500 characters | A sentence or two shown beside the title. |
 | `orientation` | `portrait`, `landscape` or `any` | The shape the game is designed for. Hosts lay the game out to match. |
-| `sdk` | a version, optionally with `^` or `~` | The SDK the game was built against. Recorded, not enforced; the protocol handshake is what checks compatibility. |
 | `audio` | `null`, or an object | Whether the game makes sound, and its volume channels. See [`audio`](#audio). |
 
 ## Validating
 
-`hopple check` validates the manifest and names every problem with its field.
-The CLI, the dev shell, the server and the clients all use the same function,
-so they always agree on whether a manifest is valid.
+`hopple check` validates the manifest and names every problem with its field,
+with the validator of the installed `@hopple/sdk`, which is of the API the
+game declares. The CLI, the dev shell, the server and the clients all use the
+same function, so they agree on whether a manifest is valid.
 
-- **Unknown keys are allowed.** A game built with a newer SDK may declare
-  things an older host doesn't know about, and must still run there.
+- **Unknown keys are refused.** A misspelt key (such as `"orientaton"`) is an
+  error, not silently ignored. A host reading a published manifest ignores
+  keys it doesn't know (`validateManifest(value, { lenient: true })`), since
+  the game may be written against a newer minor than the host.
 - **Known keys are checked strictly.** A misspelt value (such as
   `"draw_under"`) is an error, not silently ignored.
 
@@ -242,6 +245,36 @@ the host's sheet; a tap of Start is still the game's.
 
 Limits: 64 actions, 8 bindings per action, 8 control layouts.
 
+#### Several players on one device
+
+```json
+"players": { "local": 4, "online": 8 },
+"input": {
+  "actions": { "pause": { "bind": ["key.KeyP", "pad.start"] } },
+  "player": {
+    "actions": {
+      "bomb": { "bind": ["pad.south"], "title": "Drop bomb", "join": true }
+    },
+    "keyboard": [
+      { "title": "Left keys", "bind": { "bomb": ["key.Space"] } },
+      { "title": "Arrows", "bind": { "bomb": ["key.Enter"] } }
+    ]
+  }
+}
+```
+
+- **`input.player.actions`**: what each local player does, a copy each. Their
+  `bind` holds pad buttons and on-screen controls only, the same for every
+  pad. An id is never one `input.actions` declares too. `join: true` marks the
+  actions that seat a new player; on none, any does.
+- **`input.player.keyboard`**: the parts of the keyboard players share, one
+  player each (at most 4): a `title` and the keys and mouse buttons of each
+  player action. A key in two parts is refused.
+- **`players.local`**: the most players on one device, 1 by default; more
+  than 1 needs `input.player`.
+
+Limits: 32 player actions.
+
 ### audio
 
 ```json
@@ -262,6 +295,36 @@ Each channel gets its own labelled volume slider in the host's sound controls.
 `title` is required: it is the slider's label. `master` is reserved, since
 every host already has a master volume. At most 8 channels.
 
+### previews
+
+```json
+"previews": { "network": 1 }
+```
+
+The parts of the SDK that are not stable yet, each at the revision the game
+is written against. A preview is its own `0.x` package, versioned apart from
+`api`: revision `R` is `@hopple/sdk-preview-network` `0.R.x`. A game is served a runtime
+with the previews it declares, at those revisions, so a change to a preview
+reaches only the games written against it. A breaking change is a new
+revision. A name nobody knows is refused, and a revision is a whole number
+from 1.
+
+Left out of a config, the CLI fills each preview from its installed package,
+for a project whose `package.json` lists it, as it fills `api`, and refuses
+one that differs from the installed revision, or that names one with none
+installed. Publishing a game that declares any preview needs what `next`
+needs. Once a newer revision of a preview is out, the older one is retired:
+games whose `latest` is on it are unlisted and lose `beta`, keeping their
+approval and links, and an upload declaring it is refused.
+
+- **`network`**: the game plays over the network, in matches: `sdk.match`,
+  typed by `@hopple/sdk-preview-network`. It is the permission a reviewer grants, and what
+  lets a host offer *Play with friends* before the game has loaded. Nothing
+  else is declared: how a match is played, and its size, are chosen when the
+  game makes one.
+  Without it, a game is never told about a match, and `sdk.match` is not
+  there.
+
 ## Changing the manifest in a new version
 
 The server refuses a new version whose manifest would corrupt data players

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hopple/sdk",
-  "version": "0.1.0-rc.3",
+  "version": "1.0.0-next.1",
   "description": "The Hopple SDK: what a game imports to talk to the host that runs it, forwarded to the runtime its page loads.",
   "license": "MIT",
   "homepage": "https://hopple.app",
@@ -21,6 +21,10 @@
       "types": "./index.d.ts",
       "default": "./index.js"
     },
+    "./manifest": {
+      "types": "./manifest.d.ts",
+      "default": "./manifest.js"
+    },
     "./config.schema.json": "./config.schema.json",
     "./package.json": "./package.json"
   },