@indiegems/gem-web-sdk 23.1.1 → 23.1.2

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.
@@ -62,7 +62,8 @@ and nothing has changed; hide the upsell.
62
62
  `try`/`catch` to write.
63
63
 
64
64
  - **Say nothing on `declined`.** The player saw the prompt and closed it. A "sign-in failed"
65
- message after a deliberate Cancel reads as a bug.
65
+ message after a deliberate Cancel reads as a bug. Keep the button where it was: if the player
66
+ changes their mind and presses it again a few seconds later, the prompt shows again (section 4).
66
67
  - **You are told no reason**, and one will not be added. Why a sign-in did not happen is between
67
68
  the player and the Arcade.
68
69
  - **`unavailable` is ordinary**, not a fault. It is what every call returns outside the Arcade, and
@@ -76,6 +77,14 @@ never as the price of continuing to play. The Arcade decides whether a prompt ap
76
77
  one at a time, and is free to answer `declined` without showing anything to a game that asks too
77
78
  often.
78
79
 
80
+ Right after the player closes the prompt, the Arcade answers your next ask `declined` at once, with
81
+ nothing shown, for a few seconds (3 s today). That catches an ask repeated by accident: a double
82
+ press, or a game that asks again as soon as it hears `declined`. Once those seconds have passed,
83
+ the next ask shows the prompt again, so a player who closed it and then presses your Sign in button
84
+ on purpose gets the prompt, not a button that does nothing. Only the player closing the prompt
85
+ starts this wait; a `declined` answered at once does not start it again. Your game needs no code
86
+ for it: say nothing on `declined`, as above, and leave the button working.
87
+
79
88
  Pressing two upsell buttons does not open two prompts. A second call made while the first is still
80
89
  open joins it, and both resolve with the same answer.
81
90
 
@@ -80,8 +80,8 @@ To check the download yourself: the package npm serves is, byte for byte, the fi
80
80
  also publishes on its download host, with the hash beside it:
81
81
 
82
82
  ```bash
83
- curl -fsSL -O https://downloads.gemarcade.com/sdk/v23.1.1/gem-web-sdk.tgz
84
- curl -fsSL https://downloads.gemarcade.com/sdk/v23.1.1/gem-web-sdk.tgz.sri
83
+ curl -fsSL -O https://downloads.gemarcade.com/sdk/v23.1.2/gem-web-sdk.tgz
84
+ curl -fsSL https://downloads.gemarcade.com/sdk/v23.1.2/gem-web-sdk.tgz.sri
85
85
  openssl dgst -sha384 -binary gem-web-sdk.tgz | openssl base64 -A
86
86
  ```
87
87
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@indiegems/gem-web-sdk",
3
- "version": "23.1.1",
3
+ "version": "23.1.2",
4
4
  "description": "postMessage bridge contract between gem-web and browser-playable games",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",