User Tools

Site Tools


builders:doors

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
builders:doors [2021/12/08 20:45] – [properties:] amandabuilders:doors [2025/04/30 17:28] (current) amanda
Line 21: Line 21:
 | 32 | Restricted | do not allow user to lock/unlock. Locked doors need a key in hand to pass. | | 32 | Restricted | do not allow user to lock/unlock. Locked doors need a key in hand to pass. |
  
-set connection field to the region id of the normal destination.+(Currently AA does not implement Lock/Unlock. You may only pass through if holding a key. Oracle permissions needed to edit the object to add/remove the Locked flag.)
  
-===== properties: =====+===== Destination: ===== 
 + 
 +set "connection" field (In Special properties) to the region id of the normal destination. 
 + 
 +===== Additional properties: ===== 
 + 
 +Normally, key locked doors only allow avatar to pass through if the correct key is held.  This operation cane be altered by setting the following properties -
  
 **connectionKey//nn//**  - (key locked doors only) alternate destination if specific key held. \\ **connectionKey//nn//**  - (key locked doors only) alternate destination if specific key held. \\
 **connectionInvalidKey** - (key locked doors only) alternate destination when no valid key held.  If more than one destinations is specified, separated by spaces, a random one will be picked. **connectionInvalidKey** - (key locked doors only) alternate destination when no valid key held.  If more than one destinations is specified, separated by spaces, a random one will be picked.
  
builders/doors.1638996349.txt.gz · Last modified: 2021/12/08 20:45 by amanda