Difference between revisions of "Headphone"
(Created page with "__TOC__") |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| + | [[File:Headphone logo.png|center]] | ||
| + | <h1><p style="text-align:center; color: #fe5656;font-size: 60px"> [PFS] Headphone v1</p></h1> | ||
| + | <p>The [PFS] Headphone is an unrigged bondage gear to restrict listening, it can be used in many ways and in many disciplines, up to you to choose it. You will be able to:</br> | ||
| + | * lock/unlock with RLV or RLVa</br> | ||
| + | * Access mode: private, public, public ask, owner, group or PFS</br> | ||
| + | * Deaf with an unique encryption listening algorythm and with some options like encrypt listening past a distance only, encrypt rezzed objects, remove punctuation, restrict get IM, hide names, keyholder exception for encryption, list of words for encryption exception, encrypt OOC, and encrypt emotes</br> | ||
| + | * Includes a learn word mode which adds to the allowed words the most heard one et delete the one that are not heard anymore</br> | ||
| + | * Includes the famous [PFS] Network to allows communication between users inside a 100m range. Redirection of the talked chat channel can be adjusted to the gag if used</br> | ||
| + | * use RL/SL timer</br> | ||
| + | * colorize & texture over menu, accessible by both user and keyholder</br> | ||
| + | * add your own access script (example is provided)</br> | ||
| + | * up to 16 material textures to customize it to your likings</br> | ||
| + | * uses the standard script v1.3</br></p> | ||
| + | </br> | ||
| + | </br> | ||
| + | </br> | ||
| + | </br> | ||
| + | </br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1. Generalities --> | ||
| + | <!--=====================================================--> | ||
| + | <h1><p style="text-align:center; color: #fe5656;font-size: 60px">1. Generalities</p></h1> | ||
| + | <p> | ||
| + | <p>This bondage gear is the result of the cooperation with Filly Heartsong who did the mesh design. We both put together our long experience in mesh design and scripting to provide you an unique gear. Because we care we are open to listen all your comments and suggestions, as long it will help to get a better product!</p> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.1 RLV --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.1 RLV</p></h2> | ||
| + | <p>As a viewer standard, RLV restrictions are filtered to the object UUID and if your object uses same restrictions for several functions, you may run into trouble and the result may look a way different than expected. That's why RLV, here, is managed to the script level. You can have several scripts triggering restrictions w/o any interactions between them. You can easily follows the object restrictions table from the RLV menu.</br>Both RLV and RLVa are supported here but for some special features like screen overlay an addition attachement is required for RLV users. Even if most of us uses RLVa viewers today we still need to make things compatible to previous standards.</p> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.2 Access --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.2 Access</p></h2> | ||
| + | <p>The menu access is build in an inovative way. As standard, everyone can access the menu, with different access levels. Access levels are:</br> | ||
| + | * public</br> | ||
| + | * locker</br> | ||
| + | * keyholder</br> | ||
| + | * selftouch</br> | ||
| + | Depending on the lock state of the object, you may get different access levels (they are cumulable) which allows you to do things or not. The not allowed functions are strikethrough but the positive side is you can still read every parameter and setting, including the user.</br> | ||
| + | The menu is mono user but the keyholder has always the priority to access it.</br> | ||
| + | You can access it using the command line over channel 7, just hit /7##headphoneto get access to the main menu of the object. Replace ## with the user 2 first letters of the user name.</br> | ||
| + | The use of the API allows you to override the actual keyholder, this will help you to implement your own access list from wherever you want. You can implement "key grabbing" scripts as much you want they are asked one after the other. For more info look at the included public access script "plug.access.public".</br> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.3 Configurable --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.3 Configurable</p></h2> | ||
| + | <p>The object includes notecards to configure it, you can modify them at your own risk:</br> | ||
| + | * config: general configuration of the object, you can chnage the color palette..</br> | ||
| + | * words: list of words that can be added as exception to the encrypting listening..</br> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.4 API --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.4 API</p></h2> | ||
| + | <p>Objects you cannot mod are no fun, that's why you will find here an integrated API that will allows you make your own key grabbing script. plug.access.public is a script, full mod and documented, to make your own.</br> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.5 Integrated help --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.5 Integrated help</p></h2> | ||
| + | <p>To make it accessible and easy to use, the object menus have a "help" feature to stream in your chat window some general informations regarding the actual menu displayed to help you to understand what does every buttons.</br> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--1.6 Truekey --> | ||
| + | <!--=====================================================--> | ||
| + | <h2><p style="text-align:center; color: #fe5656;font-size: 40px">1.6 Truekey</p></h2> | ||
| + | <p>The only way to unlock the object is the use of the key held by the keyholder. In case you are stuck or the keyholder not showing back you can, if set up previously, use the Truekey feature to get unlocked by everyone having the key password. You can access it, set it up and use it fromt he "Tools" menu.</br> | ||
| + | <br><hr><br> | ||
| + | <!--=====================================================--> | ||
| + | <!--2. Headphone features --> | ||
| + | <!--=====================================================--> | ||
| + | <h1><p style="text-align:center; color: #fe5656;font-size: 60px">2. Headphone features</p></h1> | ||
Revision as of 08:51, 7 May 2024
Contents
[PFS] Headphone v1
The [PFS] Headphone is an unrigged bondage gear to restrict listening, it can be used in many ways and in many disciplines, up to you to choose it. You will be able to:
- lock/unlock with RLV or RLVa
- Access mode: private, public, public ask, owner, group or PFS
- Deaf with an unique encryption listening algorythm and with some options like encrypt listening past a distance only, encrypt rezzed objects, remove punctuation, restrict get IM, hide names, keyholder exception for encryption, list of words for encryption exception, encrypt OOC, and encrypt emotes
- Includes a learn word mode which adds to the allowed words the most heard one et delete the one that are not heard anymore
- Includes the famous [PFS] Network to allows communication between users inside a 100m range. Redirection of the talked chat channel can be adjusted to the gag if used
- use RL/SL timer
- colorize & texture over menu, accessible by both user and keyholder
- add your own access script (example is provided)
- up to 16 material textures to customize it to your likings
- uses the standard script v1.3
1. Generalities
This bondage gear is the result of the cooperation with Filly Heartsong who did the mesh design. We both put together our long experience in mesh design and scripting to provide you an unique gear. Because we care we are open to listen all your comments and suggestions, as long it will help to get a better product!
1.1 RLV
As a viewer standard, RLV restrictions are filtered to the object UUID and if your object uses same restrictions for several functions, you may run into trouble and the result may look a way different than expected. That's why RLV, here, is managed to the script level. You can have several scripts triggering restrictions w/o any interactions between them. You can easily follows the object restrictions table from the RLV menu.
Both RLV and RLVa are supported here but for some special features like screen overlay an addition attachement is required for RLV users. Even if most of us uses RLVa viewers today we still need to make things compatible to previous standards.
1.2 Access
The menu access is build in an inovative way. As standard, everyone can access the menu, with different access levels. Access levels are:
- public
- locker
- keyholder
- selftouch
Depending on the lock state of the object, you may get different access levels (they are cumulable) which allows you to do things or not. The not allowed functions are strikethrough but the positive side is you can still read every parameter and setting, including the user.
The menu is mono user but the keyholder has always the priority to access it.
You can access it using the command line over channel 7, just hit /7##headphoneto get access to the main menu of the object. Replace ## with the user 2 first letters of the user name.
The use of the API allows you to override the actual keyholder, this will help you to implement your own access list from wherever you want. You can implement "key grabbing" scripts as much you want they are asked one after the other. For more info look at the included public access script "plug.access.public".
1.3 Configurable
The object includes notecards to configure it, you can modify them at your own risk:
- config: general configuration of the object, you can chnage the color palette..
- words: list of words that can be added as exception to the encrypting listening..
1.4 API
Objects you cannot mod are no fun, that's why you will find here an integrated API that will allows you make your own key grabbing script. plug.access.public is a script, full mod and documented, to make your own.
1.5 Integrated help
To make it accessible and easy to use, the object menus have a "help" feature to stream in your chat window some general informations regarding the actual menu displayed to help you to understand what does every buttons.
1.6 Truekey
The only way to unlock the object is the use of the key held by the keyholder. In case you are stuck or the keyholder not showing back you can, if set up previously, use the Truekey feature to get unlocked by everyone having the key password. You can access it, set it up and use it fromt he "Tools" menu.
