@maka/maka-cli 5.198.0 → 5.200.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/bundle/typescript/package.json +1 -1
- package/bundle/typescript/src/commands/game/sideQuest/commands/attack.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/cast.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/command-registry.js +25 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/command.js +25 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/compile.js +1 -1
- package/bundle/typescript/src/commands/game/sideQuest/commands/decompile.js +3 -3
- package/bundle/typescript/src/commands/game/sideQuest/commands/edit-file.js +1 -1
- package/bundle/typescript/src/commands/game/sideQuest/commands/give.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/grapple.js +49 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/hack.js +4 -4
- package/bundle/typescript/src/commands/game/sideQuest/commands/kill.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/lead.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/order.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/palm.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/subdue.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/commands/take.js +3 -0
- package/bundle/typescript/src/commands/game/sideQuest/engine-version.js +52 -1
- package/bundle/typescript/src/commands/game/sideQuest/factions.js +135 -0
- package/bundle/typescript/src/commands/game/sideQuest/factories/repro-scene.js +24 -0
- package/bundle/typescript/src/commands/game/sideQuest/game.js +78 -7
- package/bundle/typescript/src/commands/game/sideQuest/models/npc.js +165 -14
- package/bundle/typescript/src/commands/game/sideQuest/models/room.js +12 -2
- package/bundle/typescript/src/commands/game/sideQuest/models/scene.js +84 -8
- package/bundle/typescript/src/commands/game/sideQuest/types/repro.js +1 -1
- package/bundle/typescript/src/commands/game/sideQuest/utilities/beat-echo.js +160 -0
- package/bundle/typescript/src/commands/game/sideQuest/utilities/catalog.js +25 -0
- package/bundle/typescript/src/commands/game/sideQuest/utilities/earshot.js +38 -1
- package/bundle/typescript/src/commands/game/sideQuest/utilities/hostile-contact.js +48 -2
- package/bundle/typescript/src/commands/game/sideQuest/utilities/narration-limits.js +235 -0
- package/bundle/typescript/src/commands/game/sideQuest/utilities/npc-authorization.js +122 -0
- package/bundle/typescript/src/commands/game/sideQuest/utilities/presence-gate.js +27 -2
- package/package.json +1 -1
|
@@ -17,12 +17,37 @@
|
|
|
17
17
|
* Game, a hub, or a socket. It is deliberately the WHOLE gate: a caller
|
|
18
18
|
* that reimplements part of it inline is the bug this file exists to
|
|
19
19
|
* prevent coming back.
|
|
20
|
+
*
|
|
21
|
+
* THE ACCOUNT HALF MOVED IN HERE (TLKZKLQ4rJBCnDjrw, 2026-09-15). It was
|
|
22
|
+
* living in Game.startPresenceHeartbeat, guarding only the process that
|
|
23
|
+
* ARMS the timer -- and `returnToHub` beats once directly at every
|
|
24
|
+
* homecoming, past that guard. So a hosted hub, a repro bench and the
|
|
25
|
+
* jest suite alike all dialed www.maka-cli.com on the way home with
|
|
26
|
+
* whatever token the BOX happened to be logged in as. In the suite that
|
|
27
|
+
* is the developer's own account: `loose-ends.test.ts` boots a fixture
|
|
28
|
+
* runner named Vex over the "Legacy Hub Fixture" seed, goes home, and
|
|
29
|
+
* overwrote the developer's real presence row -- so their web sheet read
|
|
30
|
+
* "You are on the street as Vex", a runner belonging to somebody else's
|
|
31
|
+
* account entirely. Two halves of one rule, in two places, is how that
|
|
32
|
+
* happened; both halves live here now.
|
|
33
|
+
*/
|
|
34
|
+
/**
|
|
35
|
+
* IS THIS PROCESS ON THE STREET AT ALL? The account half of the gate --
|
|
36
|
+
* the half that asks whether the credentials on this box belong to the
|
|
37
|
+
* runner in memory. A `false` here means no beat ever, from any caller,
|
|
38
|
+
* at any moment; nothing downstream can re-enable it.
|
|
20
39
|
*/
|
|
21
|
-
export function
|
|
40
|
+
export function presenceProcessOnTheStreet(f) {
|
|
41
|
+
return !f.anonymous && !f.bench && !f.hostedHub;
|
|
42
|
+
}
|
|
43
|
+
/** The WHOLE gate: the account half, then the position half. */
|
|
44
|
+
export function presenceBeatAllowed(f) {
|
|
45
|
+
if (!presenceProcessOnTheStreet(f))
|
|
46
|
+
return false;
|
|
22
47
|
// A solo run stays private, exactly as before. Only a LIVE SEAT keeps
|
|
23
48
|
// the beat alive off-hub -- the narrowest change that fixes the cut,
|
|
24
49
|
// and at that point other real players are sitting at the table, so
|
|
25
50
|
// "the run is nobody's business" no longer describes the situation.
|
|
26
|
-
return atHub || holdsLiveSeat;
|
|
51
|
+
return f.atHub || f.holdsLiveSeat;
|
|
27
52
|
}
|
|
28
53
|
//# sourceMappingURL=presence-gate.js.map
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@maka/maka-cli",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.200.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
|
|
6
6
|
"description": "A command line tool for scaffolding Meteor 3.x applications using React.",
|