touchbound_system:lock_api
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| touchbound_system:lock_api [2020/05/18 16:14] – created kyrahabattoir | touchbound_system:lock_api [2020/05/18 16:50] (current) – kyrahabattoir | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | I swear I'll fill this out before tomorrow. | + | ====== Why? ====== |
| + | |||
| + | The idea of the lock api is to allow users of KDC padlocks and keys to integrate them with other scripts in their home, or as part of a public venue. | ||
| + | |||
| + | It all started when I discovered that using llSetScriptState() to pause a script, actually pose a risk of losing its memory, which means losing the key/lock pairing. | ||
| + | |||
| + | As it turns out, if the object changes region, or if the region is restarted, the script' | ||
| + | |||
| + | ====== How? ====== | ||
| + | |||
| + | The lock APi doesn' | ||
| + | |||
| + | All TouchBound locks/keys are sold " | ||
| + | |||
| + | ===== SetScriptState ===== | ||
| + | * **Format:** llMessageLinked(LINK_SET,< | ||
| + | * **id**: Must be set to the exact name of the script targeted by the command. | ||
| + | * **num**: TRUE/FALSE whether the script should run normally or become inactive. | ||
| + | |||
| + | //Sending SetScriptState-> | ||
| + | |||
| + | ===== SetLockTime ===== | ||
| + | //This is only supported by the time-release padlock.// | ||
| + | |||
| + | * **Format:** llMessageLinked(LINK_SET,< | ||
| + | * **id**: Must be set to the exact name of the script targeted by the command. | ||
| + | * **num**: The number of minutes to set the timer as. | ||
| + | |||
| + | // | ||
| + | |||
| + | //This command will be ignored is SetScriptState is false// | ||
touchbound_system/lock_api.1589818484.txt.gz · Last modified: by kyrahabattoir
