hopple 0.1.0-rc.5 → 0.1.0-rc.7
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 +46 -4
- package/THIRD-PARTY-NOTICES.txt +25 -0
- package/hopple.js +847 -381
- package/package.json +5 -1
package/README.md
CHANGED
|
@@ -186,6 +186,48 @@ like `/?server=<server url>&game=<owner>/<name>@<version>` (or `@beta`). The dev
|
|
|
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.
|
|
188
188
|
|
|
189
|
+
#### Playing with others
|
|
190
|
+
|
|
191
|
+
`hopple dev` runs Hopple's own relay, at `/net` on its port, so a game
|
|
192
|
+
declaring the network preview gets parties and matches on the same rules as
|
|
193
|
+
on the site, with no server and no account. The sheet has the site's
|
|
194
|
+
**Party** tab.
|
|
195
|
+
|
|
196
|
+
A networked game opens on **two players tiled in one window**, each a whole
|
|
197
|
+
dev shell in a frame of its own, already in one party:
|
|
198
|
+
|
|
199
|
+
- **Tiling** works as in an IDE. Drag a player's title bar onto the edge of
|
|
200
|
+
another to split that pane there, or onto its middle to swap the two; drag
|
|
201
|
+
a divider to resize; double-click a title bar (or ⤢) to play that player
|
|
202
|
+
full size. The bar above has side by side, stacked and grid, and **add a
|
|
203
|
+
player**, up to 8. The layout is kept for the game.
|
|
204
|
+
- **The focused player** (the one clicked last, outlined) is the only one
|
|
205
|
+
heard and the one the keyboard reaches. A real pad goes to its player:
|
|
206
|
+
the first pad to Player 1, the second to Player 2.
|
|
207
|
+
- **Each player keeps their own** id, save and connection, as a separate
|
|
208
|
+
device would. A pane's × takes that player out of the party and the match.
|
|
209
|
+
- **`/?player=N`** opens one player alone, at full size. A party's or a
|
|
210
|
+
match's link opens one shell as a guest, which is how a phone on the same
|
|
211
|
+
network joins.
|
|
212
|
+
|
|
213
|
+
The Dev tab's **Network** part, for each player:
|
|
214
|
+
|
|
215
|
+
- **Network**: `none`, `lan`, `wired`, `wifi`, `mobile`, `weak` or `far`,
|
|
216
|
+
the delays, jitter, loss, stalls and bandwidth of `@hopple/netlab`'s
|
|
217
|
+
profiles, put between the player and the relay.
|
|
218
|
+
- **Faults**: drop the connection (it comes back on its own), stall it for
|
|
219
|
+
3 s, take it offline for 35 s (past the 30 s the relay holds for a player
|
|
220
|
+
coming back), switch away for 5 s, or reload.
|
|
221
|
+
- **Match**: its code, seats, lock, kept messages, and its people with who
|
|
222
|
+
hosts it and who is away or gone.
|
|
223
|
+
- **Traffic**: what the game sent and heard, against the relay's limits (a
|
|
224
|
+
message at most 4096 bytes, 60 a second in bursts of 120), with a warning
|
|
225
|
+
when it comes near them and every refusal counted, and the latest messages
|
|
226
|
+
each way.
|
|
227
|
+
|
|
228
|
+
The shell a server hosts as plain files, with no `hopple dev` behind it, has
|
|
229
|
+
no relay and offers no matches.
|
|
230
|
+
|
|
189
231
|
### `hopple check`
|
|
190
232
|
|
|
191
233
|
```bash
|
|
@@ -373,10 +415,10 @@ handle or the corner button) has:
|
|
|
373
415
|
- **Manifest**: what the game declares.
|
|
374
416
|
- **The log**: every analytics event, every refusal, every save read, write and
|
|
375
417
|
clear (with sizes), every share link, and every error the game threw, with
|
|
376
|
-
its stack.
|
|
377
|
-
printed in the terminal `hopple dev` runs in: once
|
|
378
|
-
only when it has been thrown 10, 100, 1000…
|
|
379
|
-
restart.
|
|
418
|
+
its stack. A new error is also said over the game in a notice that goes
|
|
419
|
+
away on its own, and is printed in the terminal `hopple dev` runs in: once
|
|
420
|
+
with its stack, then again only when it has been thrown 10, 100, 1000…
|
|
421
|
+
times, and whole again after a restart.
|
|
380
422
|
|
|
381
423
|
Switches that make the host misbehave on purpose, so you can see your game
|
|
382
424
|
cope:
|
package/THIRD-PARTY-NOTICES.txt
CHANGED
|
@@ -162,3 +162,28 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
162
162
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
163
163
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
164
164
|
SOFTWARE.
|
|
165
|
+
|
|
166
|
+
--------------------------------------------------------------------------------
|
|
167
|
+
|
|
168
|
+
ws 8.21.1 (MIT)
|
|
169
|
+
|
|
170
|
+
Copyright (c) 2011 Einar Otto Stangvik <einaros@gmail.com>
|
|
171
|
+
Copyright (c) 2013 Arnout Kazemier and contributors
|
|
172
|
+
Copyright (c) 2016 Luigi Pinca and contributors
|
|
173
|
+
|
|
174
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy of
|
|
175
|
+
this software and associated documentation files (the "Software"), to deal in
|
|
176
|
+
the Software without restriction, including without limitation the rights to
|
|
177
|
+
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
|
|
178
|
+
the Software, and to permit persons to whom the Software is furnished to do so,
|
|
179
|
+
subject to the following conditions:
|
|
180
|
+
|
|
181
|
+
The above copyright notice and this permission notice shall be included in all
|
|
182
|
+
copies or substantial portions of the Software.
|
|
183
|
+
|
|
184
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
185
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
|
|
186
|
+
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
|
|
187
|
+
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
|
|
188
|
+
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
|
|
189
|
+
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|