Differences

This shows you the differences between two versions of the page.

--- touchbound_system:cage [2018/12/22 11:44] – New config kyrahabattoir
+++ touchbound_system:cage [2024/02/28 10:41] (current) – [Supported locks] Added heavy lock support. kyrahabattoir
@@ Line 16: / Line 16: @@
    * [[touchbound_system:FingerprintPadlock|Fingerprint padlocks]].
    * [[touchbound_system:keyedpadlock|Keyed padlocks]].
+   * [[touchbound_system:heavyduty|Heavy Duty Padlock]].
+If **The KDC Experiment** Second Life experience is enabled on the current parcel, it will also use this feature to recapture avatars that manage to get out of the cell.
+//NOTE: If RLV-Relay teleport is enabled, the cell will only attempt to use RLV teleport if it cannot use experience teleport.//
+====== RLV & Experience ======
+By default, the KDC Lattice Cage will attempt to apply RLV restrictions to its occupant(s) with an RLV Relay, as soon as the door is closed.
+  - Touch distance to 1.5m maximum.
+  - Cannot use landmarks to teleport.
+  - Cannot be teleported by others.
+  - Cannot teleport home.
+  - Cannot edit the Lattice Cage itself.
 ====== Anchors ======
 {{:touchbound_system:cage_anchor.png  }}
@@ Line 36: / Line 48: @@
 **IMPORTANT!! As of version 5, the configuration is adjusted by RENAMING the different configuration notecards rather than editing their content. With the exception of the "config.whitelist" notecard.
+===== Master Key =====
 <code>
-config.allow-everyone=YES : Disables access control.
+config.masterkey= : No master key is set.
-config.allow-everyone=NO : The user will have to be whitelisted or part of the group to lock this object.
+config.masterkey=<LockID>: Keys that match the lockcode <LockID> will always be able to unlock the cage.
+NOTE: Multiple LockIDs can be defined one after the other.
+Example: "config.masterkey=<LockID1>,<LockID2>,<LockID3>"
 </code>
+===== Secure Lock =====
 <code>
-config.allow-group=NO : Group members are not allowed to lock this object.
+config.securelock=: (default) No lock restriction.
-config.allow-group=YES : Group members are allowed to lock this object.
+config.securelock=<LockID>: Only the Lock <LockID> can be installed on the cage locking points.
+NOTE: Multiple LockIDs can be defined one after the other.
+Example: "config.securelock=<LockID1>,<LockID2>,<LockID3>"
 </code>
-<code>
+On keyed lock and key sets, the LockID will be written in the locks & keys description after they have been initialized.
-config.allow-whitelist=NO : config.whitelist will be ignored.
-config.allow-whitelist=YES : Users entered in config.whitelist will be able to lock this object.
-</code>
-if you enable the whitelist, you can then add people to "config.whitelist"
-You can use either user names such "John Doe" and "Mary Resident" or account names such as "john.doe" and "mary"
+===== Auto Open =====
 <code>
-config.door.auto-open=YES : Then door will auto-open when the lock is removed.
+config.door.auto-open=Yes : Then door will auto-open when the lock is removed.
-config.door.auto-open=NO : The door have to be manually opened when unlocked.
+config.door.auto-open=No : The door have to be manually opened when unlocked.
 </code>
 <code>
-config.hatch.auto-open=YES : Then hatch will auto-open when the lock is removed.
+config.hatch.auto-open=Yes : Then hatch will auto-open when the lock is removed.
-config.hatch.auto-open=NO : The hatch have to be manually opened when unlocked.
+config.hatch.auto-open=No : The hatch have to be manually opened when unlocked.
 </code>
+===== Lock Time =====
 <code>
 config.max-locktime=0 : Locks will behave normally.
 config.max-locktime=<minutes> : Any lock used on this object will be converted into "time release locks" so they can be removed after the configured time has elapsed.
 </code>
+===== RLV Force-teleport =====
+IMPORTANT! Do not enable this feature unless parcel teleport routing is set to "Anywhere"!
+(About Land > Options > Teleport Routing)
 <code>
-config.rlv.force-teleport=YES : The cage will try to teleport escapees.
+config.rlv.teleport=Yes : The cage will try to teleport escapees using their RLV relay.
-config.rlv.force-teleport=NO : The cage will ignore escape attempts.
+config.rlv.teleport=No : The cage will only use experience powers to teleport escapees, if possible.
 </code>
+//NOTE: The cell will only attempt to use RLV teleport if it cannot use experience teleport.//
+===== RLV Build/Edit prevention =====
+<code>
+config.rlv.nobuild=Yes : Cage occupants with a relay won't be able to build or edit objects.
+config.rlv.nobuild=No : Default.
+</code>
+===== Appearance =====
 These two notecards determinate which skin texture will be loaded by the cage color script, possible values are:
-AGED,BLACK,BLUE,GREY,OLIVE,PINK,PURPLE,RED,WHITE,YELLOW
+Aged,Black,Blue,Grey,Olive,Pink,Purple,Red,White,Yellow
 <code>
-config.texture-base=AGED
+config.texture-base=Aged
-config.texture-cage=AGED
+config.texture-cage=Aged
 </code>
 These two notecards determinate which tint will be loaded by the cage color script, values are expressed in RGB colors <R,G,B>, if you prefer to use manual tinting, you can safely delete those two notecards.