hopple 0.1.0-rc.7 → 0.1.0-rc.8
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/README.md +15 -10
- package/hopple.js +108 -81
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -86,7 +86,7 @@ hopple create <dir>
|
|
|
86
86
|
hopple dev [project] [--port <n>] [--server <url>] [--no-build]
|
|
87
87
|
hopple check [project] [--no-build]
|
|
88
88
|
hopple upload [project] [--server <url>] [--no-build]
|
|
89
|
-
hopple publish [project] [@<
|
|
89
|
+
hopple publish [project] [@<build>] [--beta] [--server <url>] [--no-build]
|
|
90
90
|
hopple versions [project] [--server <url>]
|
|
91
91
|
hopple withdraw [project] [--beta] [--server <url>]
|
|
92
92
|
hopple untag beta [project] [--server <url>]
|
|
@@ -181,7 +181,7 @@ stylesheet, images), but says in the terminal that it can't be published like
|
|
|
181
181
|
that.
|
|
182
182
|
|
|
183
183
|
**With no project to be found**, the shell starts empty and waits for a URL
|
|
184
|
-
like `/?server=<server url>&game=<owner>/<name>@<
|
|
184
|
+
like `/?server=<server url>&game=<owner>/<name>@<build>` (or `@beta`). The dev shell link
|
|
185
185
|
`hopple-admin review` prints for each waiting version is exactly that, and so
|
|
186
186
|
can a link you write for any uploaded game (yours or someone else's). The shell downloads the game and its
|
|
187
187
|
manifest from that server's feed and runs it exactly as it would a local build.
|
|
@@ -267,7 +267,7 @@ game, and over 10 MB `publish` refuses it.
|
|
|
267
267
|
|
|
268
268
|
```bash
|
|
269
269
|
npx hopple upload # this project's game, built: uploaded, not published
|
|
270
|
-
npx hopple publish @3 # publish
|
|
270
|
+
npx hopple publish @3 # publish build 3, the one the upload printed
|
|
271
271
|
npx hopple publish # build, upload, and publish in one go
|
|
272
272
|
npx hopple publish --beta # the same, as the beta
|
|
273
273
|
npx hopple publish path/to/project
|
|
@@ -282,14 +282,15 @@ npx hopple publish path/to/project
|
|
|
282
282
|
game's collaborators may upload it. The game's title and description are
|
|
283
283
|
the manifest's `title` and `description`: to change them, change the
|
|
284
284
|
manifest.
|
|
285
|
-
3. Prints the version
|
|
286
|
-
|
|
285
|
+
3. Prints the version, as the manifest's `version` and the build the server
|
|
286
|
+
numbered it (`owner/name 1.5.2 (build 3)`), a link that opens that exact
|
|
287
|
+
version, and how to publish it (`hopple publish @3`).
|
|
287
288
|
|
|
288
289
|
The version is not published: nobody browsing the site finds it, and only
|
|
289
290
|
people given the link can play it. Until an admin approves it, it plays
|
|
290
291
|
without scores, saves or achievements. Files and a manifest the game already
|
|
291
|
-
has are that version again, not a new one: uploading
|
|
292
|
-
|
|
292
|
+
has are that version again, not a new one: uploading files already uploaded
|
|
293
|
+
prints the build they are.
|
|
293
294
|
|
|
294
295
|
`publish` uploads the same way, then asks for **`latest`** to point at the
|
|
295
296
|
version: `latest` is what the game's address opens, and what the feed shows
|
|
@@ -297,10 +298,14 @@ while the game is listed. With `--beta` it asks for **`beta`**: a newer
|
|
|
297
298
|
version that players who opted in get, while it is newer than `latest`, with
|
|
298
299
|
its own boards and achievements. A beta no newer than `latest` is refused, and
|
|
299
300
|
publishing `latest` at the beta or past it ends the beta. With
|
|
300
|
-
`@<
|
|
301
|
-
uploaded. A `publish` after an `upload` of the same
|
|
301
|
+
`@<build>` it builds and uploads nothing, and asks for that build, already
|
|
302
|
+
uploaded. A `publish` after an `upload` of the same files asks for the
|
|
302
303
|
uploaded version, since the upload is that version again.
|
|
303
304
|
|
|
305
|
+
A published version names one build: a version whose manifest `version` is
|
|
306
|
+
already a published build's is refused, and its `upload` warns about it. Raise
|
|
307
|
+
`version` and upload again.
|
|
308
|
+
|
|
304
309
|
- **A trusted user's or an admin's request** moves the tag at once, whoever
|
|
305
310
|
owns the game, and so does a request for a version already approved: that
|
|
306
311
|
is a rollback (`hopple publish @2`).
|
|
@@ -314,7 +319,7 @@ to the version. `hopple withdraw` takes back a request still waiting.
|
|
|
314
319
|
|
|
315
320
|
Publishing needs an account. Without `hopple login`, `publish` uploads as
|
|
316
321
|
`upload` does, asking for nothing, and says to sign in, then `hopple publish
|
|
317
|
-
@<
|
|
322
|
+
@<build>`; `publish @<build>` uploads nothing, says to sign in and fails.
|
|
318
323
|
`upload` uploads, says it was anonymous, and says to sign in before
|
|
319
324
|
publishing. Sign in before or after: the games uploaded anonymously from this
|
|
320
325
|
machine move into your account.
|