Area Search: Script Info is neutered (needs FS LSL bridge, not in our tree) -- port a reviewed bridge/helper or remove #425

Closed
opened 2026-10-05 11:23:52 +00:00 by sky_line · 1 comment
Owner

Area Search's Script Info action is always disabled (the wiki notes it as a known limitation).

Why

indra/newview/fsareasearch.cpp (~line 53) says: "fslslbridge.h not present in Alchemy; the 'get script info' action is neutered below (uses FS's in-world LSL helper script which we don't ship)." Area Search was ported from Firestorm via Alchemy, without Firestorm's LSL bridge. Firestorm's Script Info works by attaching a hidden "bridge" object whose script calls llGetObjectDetails(OBJECT_RUNNING_SCRIPT_COUNT, OBJECT_TOTAL_SCRIPT_COUNT, OBJECT_SCRIPT_MEMORY, OBJECT_SCRIPT_TIME, ...) and returns the results to the viewer.

Options

  1. Port Firestorm's LSL bridge (fslslbridge.* + the bridge script/object creation, its communication channel and security checks). This is the full FS feature, and it unlocks other bridge-based features (e.g. some RLV / movelock / radar helpers). It's large: it creates an inventory object, attaches it, and has security and attachment-slot implications. Review it carefully (it runs a script on the user's behalf; the bridge must be opt-in or clearly disclosed, and must never be exploitable by other objects).
  2. No bridge: use what the viewer can already get.
    • Region-owner tools: the estate "Top Scripts" capability needs estate rights, so it isn't general.
    • A per-request helper: have the viewer rez / attach a tiny temporary script on demand, only when the user clicks Script Info. A lighter cousin of the bridge.
    • Check whether any viewer capability exposes per-object script counts/memory/time without a script. As far as known, none does.
  3. Hide Script Info until one of the above exists (and keep the wiki's limitation note).

Done when

  • Area Search > Script Info works (counts / memory / time for the selected objects), via a reviewed bridge or helper; or the action is removed cleanly.
Area Search's **Script Info** action is always disabled (the wiki notes it as a known limitation). ## Why `indra/newview/fsareasearch.cpp` (~line 53) says: *"fslslbridge.h not present in Alchemy; the 'get script info' action is neutered below (uses FS's in-world LSL helper script which we don't ship)."* Area Search was ported from Firestorm via Alchemy, **without** Firestorm's LSL bridge. Firestorm's Script Info works by attaching a hidden "bridge" object whose script calls `llGetObjectDetails(OBJECT_RUNNING_SCRIPT_COUNT, OBJECT_TOTAL_SCRIPT_COUNT, OBJECT_SCRIPT_MEMORY, OBJECT_SCRIPT_TIME, ...)` and returns the results to the viewer. ## Options 1. **Port Firestorm's LSL bridge** (`fslslbridge.*` + the bridge script/object creation, its communication channel and security checks). This is the full FS feature, and it unlocks other bridge-based features (e.g. some RLV / movelock / radar helpers). It's large: it creates an inventory object, attaches it, and has security and attachment-slot implications. **Review it carefully** (it runs a script on the user's behalf; the bridge must be opt-in or clearly disclosed, and must never be exploitable by other objects). 2. **No bridge:** use what the viewer can already get. - **Region-owner tools:** the estate "Top Scripts" capability needs estate rights, so it isn't general. - **A per-request helper:** have the viewer rez / attach a tiny temporary script on demand, only when the user clicks Script Info. A lighter cousin of the bridge. - Check whether any viewer capability exposes per-object script counts/memory/time without a script. As far as known, none does. 3. **Hide Script Info** until one of the above exists (and keep the wiki's limitation note). ## Done when - [ ] Area Search > Script Info works (counts / memory / time for the selected objects), via a reviewed bridge or helper; or the action is removed cleanly.
sky_line added this to the Slipstream project 2026-10-06 15:04:13 +00:00
Author
Owner

Shipped in 1.4.0 Beta 1. Closing; reopen if it misbehaves.

Shipped in 1.4.0 Beta 1. Closing; reopen if it misbehaves.
sky_line 2026-10-20 15:03:20 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#425
No description provided.