1Click Maker
Get 1Click Maker

Second Life Quirks ​

Things Second Life does that shape how 1Click Maker works. Knowing them explains most "why" questions.

Data can be lost in attached objects ​

Objects store script data in memory that is saved with the object. When an object is attached and modified (scripts changed, contents edited, some property changes), that save can be skipped or reverted, and stored data is lost. This is why 1Click Maker only builds on rezzed objects, and why you should edit the copy on the ground and wear another copy for tests.

Attachments and permissions ​

  • Animation and attach/detach permissions are granted automatically to scripts in attached objects owned by the wearer. On the ground, the viewer asks.
  • A script keeps its permissions until it is reset. 1Click Maker asks again when the project starts.

Chat ranges and channels ​

  • Whisper 10 m, say 20 m, shout 100 m. Owner messages have no range (they go straight to the owner).
  • HUD ↔ target communication uses region-wide private channels, so the target can be anywhere in the region, but not in another region.
  • Chat messages are capped at 1,024 bytes; 1Click Maker splits its own traffic accordingly.

Movement limits ​

  • A script can move an object at most 10 m per call. Longer moves need several steps.
  • The root prim of an attachment cannot be moved in world coordinates; use local positions.
  • Physical objects and objects on land without rights refuse to move.

Re-uploading, re-linking or importing a rig for another body renumbers prims. That is why 1Click Maker addresses prims by name since 1.2.0.

Animations ​

  • An object can only play animations that are in its own Content.
  • Animation priority (set at upload, 0–6) decides who wins when two animations move the same bones. Nothing a script can do changes it.
  • Stop all in 1Click Maker only stops animations that the same object started.

Faces ​

  • A cube has faces 0–5; sculpts and some mesh have up to 8. Face numbers on mesh follow the material order at export.
  • Face 7 exists only on some shapes (hollow, cut). All (−1) is safe everywhere.

PBR (glTF materials) ​

  • Blinn-Phong and PBR are two separate layers on a face. A face with a PBR material shows PBR; removing it reveals Blinn-Phong.
  • Changing the material and its overrides in the same instant can drop the overrides (the "PBR texture vanished" bug fixed in 1.2.2); the PBR Manager now applies them in the correct order.
  • An override on a face without a material is ignored, which is why PBR Alpha Mode only affects faces that have a material.
  • Partial transparency on PBR requires Blend mode; 1Click Maker switches the face to Blend while its alpha is below 1.
  • Viewers without PBR support fall back to Blinn-Phong, which is why PBR Custom offers Also apply in Blinn-Phong.

Script memory ​

Every LSL script has 64 KB. The core 1Click scripts run close to that by design, which is why project memory is limited and why heavy features live in add-ons. If a script ever prints Stack-Heap Collision, the object holds more than it can; reduce and rebuild.

Sound ​

  • Sound clips are short (10 s, or 30 s on newer uploads). Loop for longer audio.
  • Sounds play by UUID, so the sound file can be removed from the object after Finish.

Rez and login ​

  • Attaching at login re-fires the Attach event.
  • Objects rezzed by a rezzer fire Rez like hand-rezzed ones.