touchbound_system:cage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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: | * [[touchbound_system: | ||
* [[touchbound_system: | * [[touchbound_system: | ||
+ | * [[touchbound_system: | ||
+ | |||
+ | 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 ====== | ====== Anchors ====== | ||
{{: | {{: | ||
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 " | **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 " | ||
+ | |||
+ | ===== Master Key ===== | ||
< | < | ||
- | 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=< |
+ | |||
+ | NOTE: Multiple LockIDs can be defined one after the other. | ||
+ | Example: " | ||
</ | </ | ||
+ | |||
+ | ===== Secure Lock ===== | ||
+ | |||
< | < | ||
- | 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=< |
+ | |||
+ | NOTE: Multiple LockIDs can be defined one after the other. | ||
+ | Example: " | ||
</ | </ | ||
- | < | + | On keyed lock and key sets, the LockID |
- | config.allow-whitelist=NO : config.whitelist | + | |
- | config.allow-whitelist=YES : Users entered | + | |
- | </ | + | |
- | if you enable | + | |
- | + | ||
- | You can use either user names such "John Doe" and "Mary Resident" | + | |
+ | ===== Auto Open ===== | ||
< | < | ||
- | 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. |
</ | </ | ||
< | < | ||
- | 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. |
</ | </ | ||
+ | |||
+ | ===== Lock Time ===== | ||
+ | |||
< | < | ||
config.max-locktime=0 : Locks will behave normally. | config.max-locktime=0 : Locks will behave normally. | ||
config.max-locktime=< | config.max-locktime=< | ||
</ | </ | ||
+ | |||
+ | ===== RLV Force-teleport ===== | ||
+ | |||
+ | IMPORTANT! Do not enable this feature unless parcel teleport routing is set to " | ||
+ | |||
+ | (About Land > Options > Teleport Routing) | ||
+ | |||
< | < | ||
- | config.rlv.force-teleport=YES : The cage will try to teleport escapees. | + | config.rlv.teleport=Yes : The cage will try to teleport escapees |
- | 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. |
</ | </ | ||
+ | //NOTE: The cell will only attempt to use RLV teleport if it cannot use experience teleport.// | ||
+ | |||
+ | ===== RLV Build/Edit prevention ===== | ||
+ | |||
+ | < | ||
+ | config.rlv.nobuild=Yes : Cage occupants with a relay won't be able to build or edit objects. | ||
+ | config.rlv.nobuild=No : Default. | ||
+ | </ | ||
+ | ===== Appearance ===== | ||
These two notecards determinate which skin texture will be loaded by the cage color script, possible values are: | 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 |
< | < | ||
- | config.texture-base=AGED | + | config.texture-base=Aged |
- | config.texture-cage=AGED | + | config.texture-cage=Aged |
</ | </ | ||
These two notecards determinate which tint will be loaded by the cage color script, values are expressed in RGB colors < | These two notecards determinate which tint will be loaded by the cage color script, values are expressed in RGB colors < |
touchbound_system/cage.1545479091.txt.gz · Last modified: 2018/12/22 11:44 by kyrahabattoir