@maka/maka-cli 5.231.0 → 5.232.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.231.0",
+  "version": "5.232.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",

package/bundle/typescript/src/commands/game/sideQuest/engine-version.js

@@ -1418,5 +1418,42 @@
 //   alone would be a fresh canon violation wearing a feature's clothes.
 //   A technomancer still comes up on the living persona, which is what
 //   the reporter's point 4 asks for.
-export const ENGINE_VERSION = '1.83.0';
+// 1.84.0 (2026-09-16): HIDING IS SLEAZE, NOT FIREWALL
+//   (eJANPpm7qCaCAJBJw, fourth rejection.) The reporter read the
+//   mechanics line and did the arithmetic out loud:
+//     "Device Rating + Firewall on the Camera is 2d6? so, the firewall
+//      of the host is a 1 (1 + 1 = 2 dice)?"
+//   No -- and the question exposed something bigger than the number.
+//   FIREWALL WAS NEVER THE RIGHT ATTRIBUTE. p.235-236 and p.241 both
+//   give the opposed roll as Computer + Intuition [Data Processing] v.
+//   LOGIC + SLEAZE. Firewall resists an INTRUSION (p.238/p.240) and has
+//   nothing to do with being seen. silent-icons.ts had been reusing
+//   deviceDefensePool -- the intrusion pool -- as the hide pool since
+//   1.80.0, so every hide roll in the game rolled the wrong attribute
+//   and then printed its name on the line the reporter was reading.
+//   The 2d6 was Device Rating twice (1 + 1), not a host Firewall of 1.
+//   - A PLAIN DEVICE HAS NO SLEAZE AT ALL (p.226: "most devices have
+//     only two Matrix attributes: Data Processing and Firewall" --
+//     Attack and Sleaze belong to decks and hosts). So a LOOSE camera
+//     or maglock hides behind one number: its rating standing in for
+//     the Logic it has not got. A p.356 camera with no host rolls a
+//     single die, which is right. A stray lens is not hard to find.
+//   - A SLAVED one borrows, and this is the reporter's ruling on p.233:
+//     "either its own or its master's rating for each rating in the
+//     test ... whichever is higher." Its Sleaze of nothing loses to the
+//     host's, which p.247 gives as a real number off the Host Rating
+//     array. A lens on a HR 3 host now hides behind Rating 3 + Sleaze 3
+//     = 6 dice, and the line says so.
+//   THIS IS WHY 1.80.1 WAS WRONG TO REMOVE THE BORROW. The first cut
+//   handed cameras their master's FIREWALL and produced 16 dice at HR 8
+//   against a sweep capped near 5 -- zero finds in twelve looks -- and
+//   the fix was to cut the host out entirely. The borrow was never the
+//   mistake; the attribute was. With Sleaze it is the same rule that
+//   makes a corporate lens hard and a stray one easy, instead of a
+//   balance knob pretending to be canon.
+//   The icon still prints the LENS's own rating ([DR 1], p.356) while
+//   the roll shows what the network lends it. Those are two different
+//   facts on purpose, and there is a test pinning them apart so nobody
+//   "fixes" one to match the other.
+export const ENGINE_VERSION = '1.84.0';
 //# sourceMappingURL=engine-version.js.map

package/bundle/typescript/src/commands/game/sideQuest/utilities/matrix-intrusion.js

@@ -92,6 +92,58 @@ export function parseMarkDeclaration(words) {
 export function deviceDefensePool(device) {
     return { label: 'Device Rating + Firewall', pool: Math.max(0, device.rating * 2) };
 }
+/**
+ * WHAT A SILENT ICON ROLLS TO STAY HIDDEN -- and it is NOT a Firewall
+ * test (eJANPpm7qCaCAJBJw, fourth rejection: "Device Rating + Firewall
+ * on the Camera is 2d6? so, the firewall of the host is a 1?").
+ *
+ * The reporter was reading the label and doing the arithmetic, and the
+ * label was naming the wrong attribute. p.235-236 and p.241 both give
+ * the opposed roll as Computer + Intuition [Data Processing] v. LOGIC +
+ * SLEAZE. Firewall resists an intrusion (p.238/p.240); it has nothing
+ * to do with being seen. silent-icons.ts was reusing deviceDefensePool
+ * -- the intrusion pool -- for the hiding roll, so every hide test in
+ * the game rolled the wrong attribute and printed its name.
+ *
+ * AND A PLAIN DEVICE HAS NO SLEAZE AT ALL. p.226: "most devices have
+ * only two Matrix attributes: Data Processing and Firewall" -- Attack
+ * and Sleaze belong to decks and hosts. So a loose camera or maglock
+ * hides behind its Device Rating standing in for the Logic it has not
+ * got, and nothing more. One die for a p.356 camera, which is correct:
+ * a lens with no host behind it is not a hard thing to find.
+ */
+export function deviceHidePool(device) {
+    return { label: 'Device Rating for Logic; p.226 gives it no Sleaze', pool: Math.max(0, device.rating) };
+}
+/**
+ * A SLAVED icon hiding, which is where the dice actually come from
+ * (reporter's ruling 2026-09-16, on p.233): "whenever a slaved device is
+ * called on to make a defense test, it uses either its own or its
+ * master's rating for each rating in the test ... whichever is higher in
+ * each instance." Resisting a sweep IS the slave defending, so it
+ * borrows per rating: its own Rating against the host's Rating, and its
+ * own Sleaze -- which p.226 says is nothing -- against the host's, which
+ * p.247 gives as a real number off the Host Rating array.
+ *
+ * That is what makes a corporate lens hard to find and a loose one easy,
+ * out of one rule rather than a balance knob. 1.80.1 removed the host's
+ * contribution entirely because the first version borrowed the host's
+ * FIREWALL and produced 16 dice against a sweep capped near 5 (zero
+ * finds in twelve looks). The borrow was never the mistake; the
+ * attribute was.
+ *
+ * Only from the grid: inside the host you are directly connected and a
+ * slave "cannot use its master's ratings" (p.233), which is
+ * deviceHidePool.
+ */
+export function wanHidePool(device, host) {
+    const rating = Math.max(device.rating, host.rating);
+    // The device's own Sleaze is 0 (p.226), so the master's always wins
+    // this half -- written as a max anyway, because the rule is per
+    // rating and a future device WITH a Sleaze must not lose it.
+    const sleaze = Math.max(0, host.attributes().sleaze);
+    return { label: "Rating + Sleaze, the master's where higher, p.233", pool: Math.max(0, rating + sleaze) };
+}
 /**
  * A SLAVE ATTACKED THROUGH ITS MASTER (SR5 p.233, PANs and WANs):
  * "Whenever a slaved device is called on to make a defense test, it

package/bundle/typescript/src/commands/game/sideQuest/utilities/silent-icons.js

@@ -1,12 +1,17 @@
 import { rollPool, formatRoll } from './dice.js';
-import { deviceDefensePool } from './matrix-intrusion.js';
-import { isWatched } from './surveillance.js';
-function hiddenDevice(device) {
+import { deviceHidePool, wanHidePool } from './matrix-intrusion.js';
+import { isWatched, cameraMasterHost } from './surveillance.js';
+function hiddenDevice(device, master) {
+    // p.235-236: the hider rolls LOGIC + SLEAZE. Not Firewall -- that
+    // resists an intrusion (p.238/p.240) and has nothing to do with being
+    // seen. This used to call deviceDefensePool, the INTRUSION pool, so
+    // the hide test rolled the wrong attribute and then printed its name
+    // (eJANPpm7qCaCAJBJw: "Device Rating + Firewall on the Camera is 2d6?
+    // so, the firewall of the host is a 1?").
+    const hide = master ? wanHidePool(device, master) : deviceHidePool(device);
     return {
         name: device.name,
-        // Its rating stands in for the Mental attribute it has not got
-        // (p.237-238) -- the same pool it defends an intrusion with.
-        hide: { pool: deviceDefensePool(device).pool, label: 'Device Rating (no Logic to hide behind)' },
+        hide: { pool: hide.pool, label: hide.label },
         reveal: (viewer) => { device.spottedBy.add(viewer); },
     };
 }
@@ -28,20 +33,22 @@ function hiddenPersona(actor) {
  * body does.
  */
 export function hiddenIconsIn(scene, room, viewer) {
+    // A device in a room with a host is slaved to it (p.233), and from
+    // the grid it borrows the master's ratings. Inside the host you are
+    // directly connected and it stands alone -- deviceHidePool.
+    const deviceMaster = viewer.hostInside ? undefined : room.host;
     const out = room.devices
         .filter(d => d.isHiddenFrom(viewer.name))
-        .map(hiddenDevice);
+        .map(d => hiddenDevice(d, deviceMaster));
     // THE CAMERAS, which p.217 names FIRST. They are not a Device -- the
     // cluster is derived from the room (surveillance.ts isWatched) -- so
     // the rating rides the ROOM (Room.cameraRating), seeded per site.
     //
-    // THE FIRST CUT GAVE THEM THEIR MASTER HOST'S RATING and that was
-    // wrong twice over. Canon first: p.233's slaving rule is about what a
-    // slave DEFENDS AN ATTACK with, and hiding is not an attack being
-    // defended. Then arithmetic: a rating-8 host gave its lenses 16 dice
-    // against a sweep the Data Processing limit caps near 5, so a camera
-    // on any corporate host was not hard to find, it was impossible --
-    // measured at zero finds in twelve looks.
+    // THE FIRST CUT GAVE THEM THEIR MASTER HOST'S FIREWALL, and the
+    // borrow was right while the attribute was wrong -- which took three
+    // versions to see. A rating-8 host gave its lenses 16 dice against a
+    // sweep the Data Processing limit caps near 5: not hard to find,
+    // impossible, measured at zero finds in twelve looks.
     //
     // THE SECOND CUT hard-coded a 4 in here, which fixed the arithmetic
     // and left the engine holding THREE answers to one question: this
@@ -51,9 +58,23 @@ export function hiddenIconsIn(scene, room, viewer) {
     // printed. One seeded number feeds all three now, so what the player
     // reads is what it rolls (reporter's ruling: per-site, not global).
     if (isWatched(room) && !room.camerasSpottedBy.has(viewer.name)) {
+        // THE THIRD CUT, and the reporter found it by doing the arithmetic
+        // out loud: "Device Rating + Firewall on the Camera is 2d6? so, the
+        // firewall of the host is a 1?" No -- Firewall was never the right
+        // attribute. p.235-236 hides behind Logic + Sleaze, p.226 gives a
+        // plain device no Sleaze at all, and p.233 lets a slave borrow its
+        // master's rating for each rating in the test. So a lens on a host
+        // hides behind the HOST's Rating and Sleaze, and a loose one behind
+        // its own single die. That is why a corporate camera is hard and a
+        // stray one is easy -- one rule, not a balance knob (reporter's
+        // ruling 2026-09-16).
+        const masterRoom = scene ? cameraMasterHost(scene.getRooms(), room) : undefined;
+        const master = viewer.hostInside ? undefined : masterRoom?.host;
+        const lens = { rating: room.cameraRating };
+        const hide = master ? wanHidePool(lens, master) : deviceHidePool(lens);
         out.push({
             name: 'Camera cluster',
-            hide: { pool: Math.max(0, room.cameraRating * 2), label: 'Device Rating + Firewall' },
+            hide: { pool: hide.pool, label: hide.label },
             reveal: (v) => { room.camerasSpottedBy.add(v); },
         });
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.231.0",
+  "version": "5.232.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",