Template:Information

2024-03-02T20:24:20Z

Johnny:

Template:Information

2024-03-02T19:30:00Z

Johnny: Created page with "<div style="display: inline-block; max-width:600px; width: 100%; left:50px; margin:10px; position:relative; border-width:1px; border-style:solid; background-color:#F6F6F6; bor..."

File:Info icon.png

2024-03-02T19:28:05Z

Johnny:

Nexus Moonshine

2023-12-06T17:46:08Z

Johnny:

<div class="center" style="width:auto; margin-left:auto; margin-right:auto;">

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Moonshine is Second Life's first Moonshine Distilling. Bringing you a complete challenge of brewing Corn Mash straight into liquid corn.</div> 
<div style="font-size:1.3em;">Need help with your Moonshine? Look at the documentation below!</div>

{| border="0" cellpadding="40" cellspacing="0"
|[[File:Book.png|link=Nexus_Moonshine/Documentation|32px]]
[[Nexus_Moonshine/Documentation|Product Documentation]]
|[[File:Calendar.png|link=Nexus_Moonshine/Version History|32px]]
[[Nexus_Moonshine/Version History|Version History]]
|[[File:Bug.png|link=Bugs|32px]]
[[Bugs|Bugs]]
|}

</div>

Nexus Burglar Alarm/Documentation

2023-10-13T17:50:42Z

Johnny:

[[Nexus Burglar Alarms|← Nexus Burglar Alarm System]]
{|align=right
|__TOC__
|}
= '''Nexus Burglar Alarm Documentation''' =

This documentation is intended for version: [2023-10-13] If you do not have this version, acquire a redelivery at our [http://maps.secondlife.com/secondlife/Silesia/125/104/2003 Main Store].

Need help navigating this manual better? Please use the table of contents to the right of this page.

Before we get started on using the Burglar Alarm System, we would like to thank you for choosing us!

If you have any questions, please ask in our Second Life Group; if your questions are not answered, please file a ticket by visiting our [https://tickets.nexus-sl.net/ Support Site].

= '''Introduction''' =
Included in your unpacked Burglar Alarm System folder are 5 components:
# Control Panel (required)
#* The Control Panel is used to manage one or more alarm networks within a region, that are owned by you.
# Home Panel (required)
#* The Home Panel is used to arm/disarm the alarm network.
# Straight Sensor / Angled Sensor (required)
#* The Sensors are used to detect intruders within a set range that are not listed on the Whitelist.
#** Note: Aside from appearances, both sensors function exactly the same.
# Alarm (optional)
#* The Speaker that will sound whenever an alarm is triggered.
# Emergency Light (optional)
#* The Emergency Light can be configured to turn on whenever an alarm is triggered. Otherwise, can be controlled manually by using the Control Panel.

= '''Getting Started / Complete Setup''' =
The following setup guide will walk you through how to setup a basic alarm network.

== Control Panel ==
# Rez the "Nexus Burglar Alarm - Control Panel".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
#* You will notice the configuration is divided into the following sections:
#** ALARM IDS
#** ACCESS
#** WHITELIST
#** PAGER KEY
#** PAGER CHANNEL
#** TONE OUT
#** PAGER DEBUG
#** DISCORD WEBHOOK
#** OUTPUT MESSAGE
# Go through each section to configure your Control Panel:
## ALARM IDS
##* Input a unique name for your alarm network. This name will be shared with all other alarm components going forward in your setup, i.e., Home Panel, Sensors, Speaker, and Emergency Light.
##* To add multiple networks, separate the names with a comma (CSV format). For example: <pre>ALARM IDS = Home</pre>
## ACCESS
##* Set the basic access mode for this panel. You can either set it to: <code style="color:#E38A2B">Owner</code>, <code style="color:#E38A2B">Group</code>, or <code style="color:#E38A2B">Anyone</code>.
##* Those with access will be able to enable/disable the system, control lights, and silence any active alarms for any network that the Control Panel is managing.
##* If you opted for <code style="color:#E38A2B">Group</code>, this will allow anyone to access the Control Panel if they have their group tag active/worn, that matches the group that the object is set to. [[File:ObjectSetGroup.png|none|none]] For example: <pre>ACCESS = Owner</pre>
## WHITELIST
##* In addition to the basic access mode, the Whitelist can be used to grant access to specific users by inputting their [https://wiki.secondlife.com/wiki/Category:LSL_Legacy_Name Legacy Name]. You DO NOT need to add yourself.
##* To add multiple users, separate the names with a comma (CSV format).
##* Those with access will be able to enable/disable the system, control lights, and silence any active alarms for any network that the Control Panel is managing. For example: <pre>WHITELIST = Johnny Nexen, Shymus Roffo</pre>
##; The remaining sections are only applicable if you would like to receive Pager and/or Discord alerts* for each time an alarm is triggered
##; * To receive Pager alerts, you must own the [https://marketplace.secondlife.com/p/Nexus-Pager-System-V3/4593342 Nexus Pager System]
##; * To receive Discord alerts, you must have a valid Discord Webhook
## PAGER KEY
##* Input your Pager Network Key
##* Can't find your Network Key? The Network Key is located in the description field of your "Nexus Computer Terminal" object, if you've created a Pager network. For example:<pre>PAGER KEY = #BACEECBE-5F9F-4322-B79E-7414C818BEB5</pre>
## PAGER CHANNEL
##* Input the name of the channel that you would like to have alerts sent to.
##* Note: Channel names are case-sensitive.
##* Can't find your channel name? Click on your Computer Terminal and select <kbd>Channels</kbd> / <kbd>List</kbd> for a full readout of your registered channels. For example:<pre>PAGER CHANNEL = YOUR_CHANNEL_NAME</pre>
## TONE OUT
##* Set the type of alert that you would like to receive: <code style="color:#E38A2B">Pager</code>, <code style="color:#E38A2B">Speaker</code>, or <code style="color:#E38A2B">Both</code>. For example:<pre>TONE OUT = Both</pre>
## PAGER DEBUG
##* Enable this feature temporarily if you are not receiving Pager alerts properly, as it will output any error messages to help you troubleshoot the problem. For example:<pre>PAGER DEBUG = FALSE</pre>
## DISCORD WEBHOOK
##* Input your Discord Webhook URL. For example:<pre>DISCORD WEBHOOK = https://discord.com/api/webhooks/747191624765014036/IrMD-_jTlSTxUlliwmIk3aXYpAv7E4561pFI90kKSSE7o35BeRvyiYAORSuvucS869j1</pre>
## OUTPUT MESSAGE
##* This is the alert message that will be relayed to your Pagers and/or your Discord Server. To include alarm details in your message dynamically, you may include the following keywords:
##** <code style="color:#E38A2B">((LOCATION))</code> — This will insert the "LOCATION" value that has been set in the Home Panel configuration
##** <code style="color:#E38A2B">((SENSOR))</code> — This will insert the "SENSOR NAME" value that has been set in the Home Panel configuration
##** <code style="color:#E38A2B">((INTRUDER))</code> — This will insert the name of the user that was detected by a sensor, that caused the alarm to trigger
##** <code style="color:#E38A2B">((TIME))</code> — This will insert the time of the alarm (Second Life time).
##* If left blank, a default alert will be set. For example:<pre>OUTPUT MESSAGE = BURGLAR ALARM ACTIVATED - [Location: ((LOCATION))] - [Sensor: ((SENSOR))] - [Triggered By: ((INTRUDER))] - [Time: ((TIME))]</pre>
# Your Control Panel is Ready!

== Home Panel ==
# Rez the "Nexus Burglar Alarm - Home Panel".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Home Panel:
## ALARM ID
##* Input the name of your alarm network (aka: alarm ID) that you previously set in your Control Panel configuration. This will allow the Home Panel to sync to your Control Panel. For example: <pre>ALARM ID = Home</pre>
## MASTER PANEL
##* With each alarm network, you must have one Home Panel act as the "Master Panel"; this will effectively make it so additional Home Panels that are rezzed, if needed, to act as relays and will refer to the "Masters" configuration instead of it's own.
##** For instance: If you were setting up an alarm system in a home and wanted a Home Panel located in each room, you would only need to set one of them as the "Master Panel" and have it fully configured. All other Home Panels would simply require just the shared "Alarm ID".
##* Set to <code style="color:#E38A2B">TRUE</code> to make it the primary Home Panel in your setup. For example: <pre>MASTER PANEL = TRUE</pre>
## TIMEOUT
##* Input the amount of <code style="color:#E38A2B">seconds</code> the alarm should sound for, before it is silenced automatically if no users are around to silence it themselves. For example: <pre>TIMEOUT = 300</pre>
## REMAIN ARMED AFTER TIMEOUT
##* If <code style="color:#E38A2B">TRUE</code>, after an alarm has timed-out, the sensors will re-enable automatically and continue to monitor for intruders.
##* Otherwise if <code style="color:#E38A2B">FALSE</code>, the system will require manual user intervention to re-arm the system. For example: <pre>REMAIN ARMED AFTER TIMEOUT = TRUE</pre>
## ACCESS
##* Set the basic access mode for this panel. You can either set it to: <code style="color:#E38A2B">Owner</code>, <code style="color:#E38A2B">Group</code>, or <code style="color:#E38A2B">Anyone</code>.
##* Those with access will be able to arm/disarm the system. For example: <pre>ACCESS = Owner</pre>
## WHITELIST
##* Input the name of user(s) that should NOT trigger an alarm. Including yourself, if you do not want to trigger the alarm when in presence of a sensor.
##* To add multiple users, separate the names with a comma (CSV format). For example: <pre>WHITELIST = Johnny Nexen, Shymus Roffo</pre>
##; The remaining section is only applicable for Pager and/or Discord alerts
## LOCATION
##* Set a location description for this Home Panel. The location value you set will be replaced with <code style="color:#E38A2B">((LOCATION))</code> if set in your "output message". For example: <pre>LOCATION = Nexus Corporate Tower</pre>
# Your Home Panel is Ready!

== Sensors ==
# Rez your preferred style of sensor:
#* "Nexus Burglar Alarm - Straight Sensor".
#* "Nexus Burglar Alarm - Angled Sensor".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Sensor:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## RANGE
##* Input the range for this sensor, you can set the range between <code style="color:#E38A2B">0</code> - <code style="color:#E38A2B">96</code> meters.
##* Unsure what range to set? Use the included "Sensor Range HUD". Simply move your Sensor into it's permanent position and equip the HUD to find the range. For example: <pre>RANGE = 15</pre>
##; The remaining section is only applicable for Pager and/or Discord alerts
## SENSOR NAME
##* Set a name description for this Sensor. The name value you set will be replaced with <code style="color:#E38A2B">((SENSOR))</code> if set in your "output message". For example: <pre>SENSOR = Front Entrance</pre>
# Your Sensor is Ready!

== Speaker ==
This is an optional component
# Rez the "Nexus Burglar Alarm - Speaker".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Alarm:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## ALARM SOUND
##* If you wish to change the default alarm sound, input the UUID for the sound you wish to set.
##* Unsure where to find the UUID? Open your inventory, locate the sound you would like to use, then right-click and select "Copy Asset UUID". For example: <pre>ALARM SOUND = 6e37a900-816a-753e-514c-258eb8e90f85</pre>
# Your Speaker is Ready!

== Emergency Light ==
This is an optional component
# Rez the "Nexus Burglar Alarm - Emergency Light".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Emergency Light:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## TURN ON WHEN ALARM
##* If set to <code style="color:#E38A2B">TRUE</code>, the light will automatically turn on when an alarm is triggered. For example: <pre>TURN ON WHEN ALARM = TRUE</pre>
# Your Emergency Light is Ready!

Nexus Burglar Alarm/Version History

2023-10-13T17:38:37Z

Johnny: [2023-10-13] Update

[[Nexus Burglar Alarms|← Nexus Burglar Alarm System]]
{|align=right
|__TOC__
|}
= '''How to get updates''' =
: When a newer version comes out, our servers will automatically send it to you.

: Don't receive your update? Simply visit our in-world store and select a redelivery from the terminals in any of the stores.

: Looking for your version number of your package? You can find the version number on the box sent by the vendors. If you purchased off the marketplace, the version is displayed in the help notecard supplied.

= '''[2023-10-13]''' =
* Fixed the Control Panel to support multiple Alarm ID's
* Fixed "Group"/"Anyone" access settings for both the Control Panel and Home Panel.
* Fixed a bug that would cause the Controller to spam messages to the owner.
* Improved light control for the Control Panel; you can now turn on/off lights for all lights or a specific network of light.
* Added a way to silence an alarm system using the Control Panel for a specific alarm network.
* Added a "View ID's" option to the Control Panel, to quickly see what alarm networks have been configured to.
* Added a "Timeout" option to the Home Panel to automatically silence alarms after a set amount of time.
* Added an option to the Home Pane to continue monitoring for intruders after an alarm has timed-out.
* Added support for Discord alerts via Webhook.
* Added an option to customize the Pager/Discord alert message, with the option to dynamically pass-in alert information such as: Location, sensor name, intruder name, and time.
* Moved the "Location" setting (for Pager/Discord alerts) to the Home Panel configuration.
* Added a "Sensor Name" setting (for Pager/Discord alerts) to the Sensor configuration.
* Added a Sensor Range HUD to help users set an optimal range value for their sensors.
* Added support for multiple Home Panels in a network.

= '''Version 1.0.1''' =
* v1.0.0's Name2Key service was deprecated. We've replaced the service with a new internal process.
* Fixed Controller and Home Panel access issues
* Fixed listener issues
* Fixed sensor spam

= '''Version 1.0.0''' =
* Initial Release

Nexus Burglar Alarm/Documentation

2023-10-13T17:28:34Z

Johnny: [2023-10-13] Update

[[Nexus Burglar Alarms|← Nexus Burglar Alarm System]]
{|align=right
|__TOC__
|}
= '''Nexus Burglar Alarm Documentation''' =

This documentation is intended for version: [2023-10-13] If you do not have this version, acquire a redelivery at our [http://maps.secondlife.com/secondlife/Silesia/125/104/2003 Main Store].

Need help navigating this manual better? Please use the table of contents to the right of this page.

Before we get started on using the Burglar Alarm System, we would like to thank you for choosing us!

If you have any questions, please ask in our Second Life Group; if your questions are not answered, please file a ticket by visiting our [https://tickets.nexus-sl.net/ Support Site].

= '''Introduction''' =
Included in your unpacked Burglar Alarm System folder are 5 components:
# Control Panel (required)
#* The Control Panel is used to manage one or more alarm networks within a region, that are owned by you.
# Home Panel (required)
#* The Home Panel is used to arm/disarm the alarm network.
# Straight Sensor / Angled Sensor (required)
#* The Sensors are used to detect intruders within a set range that are not listed on the Whitelist.
#** Note: Aside from appearances, both sensors function exactly the same.
# Alarm (optional)
#* The Alarm is a speaker that will sound whenever an alarm is triggered.
# Emergency Light (optional)
#* The Emergency Light can be configured to turn on whenever an alarm is triggered. Otherwise, can be controlled manually by using the Control Panel.

= '''Getting Started / Complete Setup''' =
The following setup guide will walk you through how to setup a basic alarm network.

== Control Panel ==
# Rez the "Nexus Burglar Alarm - Control Panel".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
#* You will notice the configuration is divided into the following sections:
#** ALARM IDS
#** ACCESS
#** WHITELIST
#** PAGER KEY
#** PAGER CHANNEL
#** TONE OUT
#** PAGER DEBUG
#** DISCORD WEBHOOK
#** OUTPUT MESSAGE
# Go through each section to configure your Control Panel:
## ALARM IDS
##* Input a unique name for your alarm network. This name will be shared with all other alarm components going forward in your setup, i.e., Home Panel, Sensors, Speaker, and Emergency Light.
##* To add multiple networks, separate the names with a comma (CSV format). For example: <pre>ALARM IDS = Home</pre>
## ACCESS
##* Set the basic access mode for this panel. You can either set it to: <code style="color:#E38A2B">Owner</code>, <code style="color:#E38A2B">Group</code>, or <code style="color:#E38A2B">Anyone</code>.
##* Those with access will be able to enable/disable the system, control lights, and silence any active alarms for any network that the Control Panel is managing.
##* If you opted for <code style="color:#E38A2B">Group</code>, this will allow anyone to access the Control Panel if they have their group tag active/worn, that matches the group that the object is set to. [[File:ObjectSetGroup.png|none|none]] For example: <pre>ACCESS = Owner</pre>
## WHITELIST
##* In addition to the basic access mode, the Whitelist can be used to grant access to specific users by inputting their [https://wiki.secondlife.com/wiki/Category:LSL_Legacy_Name Legacy Name]. You DO NOT need to add yourself.
##* To add multiple users, separate the names with a comma (CSV format).
##* Those with access will be able to enable/disable the system, control lights, and silence any active alarms for any network that the Control Panel is managing. For example: <pre>WHITELIST = Johnny Nexen, Shymus Roffo</pre>
##; The remaining sections are only applicable if you would like to receive Pager and/or Discord alerts* for each time an alarm is triggered
##; * To receive Pager alerts, you must own the [https://marketplace.secondlife.com/p/Nexus-Pager-System-V3/4593342 Nexus Pager System]
##; * To receive Discord alerts, you must have a valid Discord Webhook
## PAGER KEY
##* Input your Pager Network Key
##* Can't find your Network Key? The Network Key is located in the description field of your "Nexus Computer Terminal" object, if you've created a Pager network. For example:<pre>PAGER KEY = #BACEECBE-5F9F-4322-B79E-7414C818BEB5</pre>
## PAGER CHANNEL
##* Input the name of the channel that you would like to have alerts sent to.
##* Note: Channel names are case-sensitive.
##* Can't find your channel name? Click on your Computer Terminal and select <kbd>Channels</kbd> / <kbd>List</kbd> for a full readout of your registered channels. For example:<pre>PAGER CHANNEL = YOUR_CHANNEL_NAME</pre>
## TONE OUT
##* Set the type of alert that you would like to receive: <code style="color:#E38A2B">Pager</code>, <code style="color:#E38A2B">Speaker</code>, or <code style="color:#E38A2B">Both</code>. For example:<pre>TONE OUT = Both</pre>
## PAGER DEBUG
##* Enable this feature temporarily if you are not receiving Pager alerts properly, as it will output any error messages to help you troubleshoot the problem. For example:<pre>PAGER DEBUG = FALSE</pre>
## DISCORD WEBHOOK
##* Input your Discord Webhook URL. For example:<pre>DISCORD WEBHOOK = https://discord.com/api/webhooks/747191624765014036/IrMD-_jTlSTxUlliwmIk3aXYpAv7E4561pFI90kKSSE7o35BeRvyiYAORSuvucS869j1</pre>
## OUTPUT MESSAGE
##* This is the alert message that will be relayed to your Pagers and/or your Discord Server. To include alarm details in your message dynamically, you may include the following keywords:
##** <code style="color:#E38A2B">((LOCATION))</code> — This will insert the "LOCATION" value that has been set in the Home Panel configuration
##** <code style="color:#E38A2B">((SENSOR))</code> — This will insert the "SENSOR NAME" value that has been set in the Home Panel configuration
##** <code style="color:#E38A2B">((INTRUDER))</code> — This will insert the name of the user that was detected by a sensor, that caused the alarm to trigger
##** <code style="color:#E38A2B">((TIME))</code> — This will insert the time of the alarm (Second Life time).
##* If left blank, a default alert will be set. For example:<pre>OUTPUT MESSAGE = BURGLAR ALARM ACTIVATED - [Location: ((LOCATION))] - [Sensor: ((SENSOR))] - [Triggered By: ((INTRUDER))] - [Time: ((TIME))]</pre>
# Your Control Panel is Ready!

== Home Panel ==
# Rez the "Nexus Burglar Alarm - Home Panel".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Home Panel:
## ALARM ID
##* Input the name of your alarm network (aka: alarm ID) that you previously set in your Control Panel configuration. This will allow the Home Panel to sync to your Control Panel. For example: <pre>ALARM ID = Home</pre>
## MASTER PANEL
##* With each alarm network, you must have one Home Panel act as the "Master Panel"; this will effectively make it so additional Home Panels that are rezzed, if needed, to act as relays and will refer to the "Masters" configuration instead of it's own.
##** For instance: If you were setting up an alarm system in a home and wanted a Home Panel located in each room, you would only need to set one of them as the "Master Panel" and have it fully configured. All other Home Panels would simply require just the shared "Alarm ID".
##* Set to <code style="color:#E38A2B">TRUE</code> to make it the primary Home Panel in your setup. For example: <pre>MASTER PANEL = TRUE</pre>
## TIMEOUT
##* Input the amount of <code style="color:#E38A2B">seconds</code> the alarm should sound for, before it is silenced automatically if no users are around to silence it themselves. For example: <pre>TIMEOUT = 300</pre>
## REMAIN ARMED AFTER TIMEOUT
##* If <code style="color:#E38A2B">TRUE</code>, after an alarm has timed-out, the sensors will re-enable automatically and continue to monitor for intruders.
##* Otherwise if <code style="color:#E38A2B">FALSE</code>, the system will require manual user intervention to re-arm the system. For example: <pre>REMAIN ARMED AFTER TIMEOUT = TRUE</pre>
## ACCESS
##* Set the basic access mode for this panel. You can either set it to: <code style="color:#E38A2B">Owner</code>, <code style="color:#E38A2B">Group</code>, or <code style="color:#E38A2B">Anyone</code>.
##* Those with access will be able to arm/disarm the system. For example: <pre>ACCESS = Owner</pre>
## WHITELIST
##* Input the name of user(s) that should NOT trigger an alarm. Including yourself, if you do not want to trigger the alarm when in presence of a sensor.
##* To add multiple users, separate the names with a comma (CSV format). For example: <pre>WHITELIST = Johnny Nexen, Shymus Roffo</pre>
##; The remaining section is only applicable for Pager and/or Discord alerts
## LOCATION
##* Set a location description for this Home Panel. The location value you set will be replaced with <code style="color:#E38A2B">((LOCATION))</code> if set in your "output message". For example: <pre>LOCATION = Nexus Corporate Tower</pre>
# Your Home Panel is Ready!

== Sensors ==
# Rez your preferred style of sensor:
#* "Nexus Burglar Alarm - Straight Sensor".
#* "Nexus Burglar Alarm - Angled Sensor".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Sensor:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## RANGE
##* Input the range for this sensor, you can set the range between <code style="color:#E38A2B">0</code> - <code style="color:#E38A2B">96</code> meters.
##* Unsure what range to set? Use the included "Sensor Range HUD". Simply move your Sensor into it's permanent position and equip the HUD to find the range. For example: <pre>RANGE = 15</pre>
##; The remaining section is only applicable for Pager and/or Discord alerts
## SENSOR NAME
##* Set a name description for this Sensor. The name value you set will be replaced with <code style="color:#E38A2B">((SENSOR))</code> if set in your "output message". For example: <pre>SENSOR = Front Entrance</pre>
# Your Sensor is Ready!

== Speaker ==
This is an optional component
# Rez the "Nexus Burglar Alarm - Speaker".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Alarm:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## ALARM SOUND
##* If you wish to change the default alarm sound, input the UUID for the sound you wish to set.
##* Unsure where to find the UUID? Open your inventory, locate the sound you would like to use, then right-click and select "Copy Asset UUID". For example: <pre>ALARM SOUND = 6e37a900-816a-753e-514c-258eb8e90f85</pre>
# Your Speaker is Ready!

== Emergency Light ==
This is an optional component
# Rez the "Nexus Burglar Alarm - Emergency Light".
# Right-click & Edit.
# Go to the Contents tab and open the "_config" notecard.
# Go through each section to configure your Emergency Light:
## ALARM ID
##* Input the name of your alarm network that you previously set in your Control Panel configuration. For example: <pre>ALARM ID = Home</pre>
## TURN ON WHEN ALARM
##* If set to <code style="color:#E38A2B">TRUE</code>, the light will automatically turn on when an alarm is triggered. For example: <pre>TURN ON WHEN ALARM = TRUE</pre>
# Your Emergency Light is Ready!

File:ObjectSetGroup.png

2023-10-08T20:23:18Z

Johnny:

RolePay Store Expansion

2023-09-07T14:21:47Z

Johnny:

RolePay Toll System Expansion

2022-05-24T20:29:17Z

Johnny: reflects changes for v1.1

Rolepay Money System/Documentation

2022-04-29T07:33:52Z

Johnny:

[[Rolepay Money System|← Rolepay Money System]]
{|align=right
|__TOC__
|}
= '''Product Documentation''' =
This documentation is relevant to the most recent version. Anything outdated will not work with this documentation.
For information on what has been added in recent versions or if there have been any updates, please view the [[Rolepay Money System/Version History|version history]] for the RolePay System.

= '''RolePay Server''' =
All information in this article is regarding the most recent server to run a network.The server is used to start a network, with it you are able to distribute cards and access the web interface. It also gives support staff members access to your network information and web dashboard.

== '''Server Features''' ==
Your server is used as a gateway to your web dashboard, without it you will not be able to distribute cards or access features that would require you to be online.
One of the first things you will get asked when you rez the server is if you would like to Register a network. This will create a new network with nothing on it. After creation you will get an error saying that you are missing a card. This error will happen until you place the RolePay Credit Card into the inventory of the server. Please remember that it must be configured.

== '''Server Dialog''' ==
Don't know what the buttons do on your server, refer to this simple reference.
* '''Dashboard''' will take you to the web interface. It will require you to go to your browser.
* '''Reset''' will reset the server to factory removing all the network information off the server. (''This is not recommended unless your network is broken. Please contact support before resetting.'')
* '''Re-Obtain''' will reset the server, except it will keep all network settings. It is good to refresh it once a week.
* '''Exit''' will exit the dialog.

= '''RolePay Registration Terminal''' =
The registration terminal allows users to get registered into your network and possibly adding funds into their account.

== '''Terminal Features''' ==
:<table border="0" cellpadding="5px" cellspacing="0" style="width:75%;border:dashed 2px #008BBA;"><tr style="color:#008BBA;"><td style="font-size:50px;position:relative;top:-12px;"> ⚠</td><td style="font-weight:bold;">Due to an update in Linden Lab's Gaming Policy. We are not allowed to sell virtual currency. This means that the '''Add Funds''' feature will no longer work. You may still be prompted sometimes to allow it if using an older version, however it will not do anything.</td></tr></table>
The follow things can be done using the terminal.
* Register into a network.
* Receive a new credit card.

== '''Terminal Dialog''' ==
Don't know what the buttons do on your terminal, refer to this simple reference.
* '''Register''' will register the user into the network and send them a card if they are not registered.
* '''New Card''' will send them a card from the server.

= '''RolePay Credit Card''' =
The card is the most important tool that you can use for the RolePay Money System.Without this tool you will not be able to transfer money. You will also be able to view how much money you're carrying.

== '''Transfering Money''' ==
Looking to transfer money to other users? Before these steps can be taken, please make sure that there is someone within 10 meters of you and registered into the same network.
* Open the tab on the right side of your card.
* Select "Transfer Funds" on the menu.
* Select a person from the list.
* Enter the amount of money to transfer.
* Press Confirm.
You did it! You just transferred money. Please remember, you will actually have to have the money in the account to transfer it.

== '''Card Settings''' ==
As you might have guessed, there are a lot of settings on the card HUD. A lot of them are not explained well. But that's what this documentation is for isn't it.Any settings changed on the current card will be loaded onto other cards you have in that network. If you turn off sounds on one card, and you get a new card. The settings will be loaded and sounds will be turned off after loading the settings.

=== '''Sound''' ===
This button is used to turn off the sounds that you receive when ever someone gives you money.The feature is simply Enable / Disable. All you have to do is click it once and it will be saved.

=== '''Animation''' ===
When ever you send money to someone that is within 10 meters of you, you will have the option to have an animation show.This animation will only show how ever if you are wearing the attachment which can be retrieved by clicking Settings -> Attachment and wearing it.If you send money and have this feature enabled. Your arm will hold a dollar bill out showing the transfer of money.

=== '''Background''' ===
This will allow for you to change the background of the card.To change your background please follow these steps below.
* Touch Settings -> Background
* Get a texture UUID
* Paste the UUID into the box.
* Press submit and the texture is changed.
This feature will not sync across all cards you own in the network. It will only work on this single card.If you change a card the background will never change back. Meaning if you are the owner of a network and change the texture, when you distribute the card. The texture will be the same for everyone unless they are to change the texture.

= '''The Web Interface''' =
The web interface is where you manage all settings and features for your network.You can also view all transaction logs, and edit user account settings.There are multiple pages, each page will be explained here.

== '''Home Page''' ==
The main page is where you can view the network settings, and statistics.It also has a place to view what support members are online to get help for the system. But remember, we also have a group of active customers that are willing to help you.

=== '''Server Options''' ===
The server options displays all important information for the server including errors, users registered, how much network funds you have, and the tax.There is also a feature called notifications. This will give a little popup whenever someone makes a transaction in your network. You will need to be logged in the Web Interface for the notification to show up. You must also have a browser that is up to date. We recommend the internet browser [https://www.google.com/intl/en/chrome/browser/ Google Chrome].

=== '''Support (Need Help?)''' ===
This is a simple way to see what staff members are online.These staff members will be able to help you with the system. This also allows you to figure out when they are online and links to the wiki.Please view the wiki first before contacting them.

=== '''Banned Users''' ===
Do you have a user that has been abusing your system? Use this as a way to ban them from your network.
They will not be able to do anything within the network. This includes register, transfer funds, and receive funds.
'''How to Ban Someone'''
* Click the button "Add To Ban List"
* Enter their Username (not display name)
* If their name is found they will be added on the list.
 '''How to Un-Ban Someone'''
* Locate their name in the ban list.
* Click remove next to their name.
* Poof, their off the list free to continue what ever they want in your network. (''Well, not whatever...'')

== '''Users Page''' ==
This page will show all account information for every user registered in your network.
You will also be able to remove users and give them money.

=== '''Deleting a User''' ===
''Please remember once this is done, you cannot undo it.''
To delete a user, simply navigate to their name and select the "Manage" button. A dialog will appear, then simply touch the button "Delete", and their information and account will be deleted from your network.

=== '''Deleting Multiple Users''' ===
''Please remember once this is done, you cannot undo it.''

To delete a bulk amount of users, simply click on the row of each user that you would like to have deleted from your network — selected rows will become highlighted — once you've finished making your selections, simply click the "Remove Selected Users" button at the top of the table, and select "Yes" when the dialog confirmation appears; the selected users will then be removed permanently.

To undo a selection, click on the desired row and it will no longer be highlighted.

Note: You can only delete users that are currently in view. If you have a lot of users, you cannot jump between pages and make selections. Instead, increase the entries from the default "10" to "100" and go through one page at a time.

=== '''Giving / Removing a User's Money''' ===
When ever you give/take their money. All funds will be placed into the network funds. Since the money has to go somewhere, the only other destination would be the network owner. That would require the user to give/take to the other user.
Follow these steps to give money.
* Navigate to their name.
* Select "Manage"
* Enter a new amount in "Amount of Money".
* Press the button "Update".
* Bam, their money has been changed.

== '''Transactions Page''' ==
The transactions page will display all information regarding transactions. The latest transaction will be displayed at the top of the list.All information regarding the transaction will be displayed. You are not able to delete the logs.

== '''Settings Page''' ==
The settings page let's you change all the network settings.These settings include the Tax and Starting Funds. You are also able to view the network key.Your network key is the key that our staff members use to access your network when you are having troubles.

=== '''Changing the Tax''' ===
To change the tax, simple navigate to the "Tax Percentage box", change the number and hit the "Update" button.

=== '''Changing the Start Amount''' ===
To change the start amount, simple navigate to the Start "Amount" box, change the number and hit the "Update" button.

== '''API Keys Page''' ==
This page will display all your API keys.The API keys are used for expansions or add-ons made by scripters to access your network.For information on what an API is and what ours is capable, please visit our [[Rolepay Money System/API|API Documentation]]


=== '''Warning!''' ===
When ever you give an API key out, the user with the key will be able to access other account information.The user will be able to allocate funds without permission of the account holder.'''Use caution when distributing API keys!'''


=== '''Creating API Keys''' ===
Creating API keys is very simple, all you have to do is press the "Create API Key" button.

=== '''Deleting API Keys''' ===
Deleting API keys is just as simple as creating them.
Navigate to the Key you would like to delete. Press the "Delete" button and it's gone.
Any devices that are using that key will have the error "API Keys does not exist" when ever they try to make calls to our servers.

= '''RolePay Rebate''' =
'''What is RolePay Rebate?''' The rebate is money you get back from purchasing the newer system if you purchased the older version. Sadly due to the extreme amount of changes and addons we are unable to provide the free update to the product. If we gave the product away free we would not be able to pay for our servers to keep the system running.
If you recently purchased one of the older versions of the money you are eligible to receive the rebate if the following applies to you.
* If you purchased the system at our inworld store, PrimBay, or Second Life Marketplace.
* If you purchased the system from a another person with Affiliate vendor.
* If you participated on the beta for the product.
You '''will not''' receive the rebate if these terms apply.
Have any more questions about the rebate, please contact one of the support members from Nexus.
* Someone purchased the system for you as a gift. (''They are eligible for the rebate not you.'')
* It was given to you and you did not pay L$.
* You purchased the newer version v2.0.0+

Nexus Moonshine/Documentation

2022-04-10T21:10:39Z

Johnny:

[[Nexus Moonshine|← Nexus Moonshine]]
{|align=right
|__TOC__
|}
= '''Nexus Moonshine Documentation''' =

This documentation is to better help you with the product to help you efficiently work with the product and make use of all of it's features properly.
Having trouble using a feature? Consult the documentation below.

Need help navigating this manual better? Please use the table of contents to the right of this page.

Before we get started on using the Moonshine, we would like to thank you on choosing us! If you have any questions please ask in our Second Life Group.
If your questions are not answered, please file a ticket here on our [http://tickets.nexus-sl.net/ Support Site].
 

= '''Getting Started''' =
Before starting to brew the Moonshine, you will need to take a few steps to set up your still.

It is a very complex system that will take time, it has some challenge to the system and does not have a high return without effort. 
=== '''What's Inside?''' ===
Once you have got everything unpacked, you will notice a lot of tools inside and other items. 
These are the tools and what they are used for.
* Nexus Moonshine - Water Spout
* Nexus Moonshine - Cornmeal Pallet
* Nexus Moonshine - Equipment Crate
* Nexus Moonshine HUD v1.0.0
* Nexus Moonshine Hand Attachments
 
= '''Setting Up Your Cooking Area''' =
Decide where you're going to be cooking your moonshine at? Well, it's time to get that grill set up. 

== How To Get An Area Set up ==
# Attach The "Nexus Moonshine HUD v1.0.0"
# Attach the "Nexus Moonshine Hand Attachments"
# Rez out the "Nexus Moonshine - Water Spout"
# Rez out the "Nexus Moonshine - Cornmeal Pallet"
# Rez out the "Nexus Moonshine - Equipment Crate"

== How To Set Up The Propane Burner ==
Before picking up items from the HUD, please remember that you will need to be standing near Equipment crate.
#Click Stove Items -> Propane Burner on the HUD.
#Go into Mouselook and click where you would like to place the propane burner.
#Click Stove Items -> Propane Tank and touch the burner.
#Click Stove Items -> Metal Pot then touch the burner.
#Click Tools -> Thermometer then touch the burner.

'''Congratulations, you've got your area all set up! Now time to get cooking.'''
 
= '''Preparing The Corn Mash''' =
This step is very safe, but can't be a waste of time if not done correctly. Follow instructions carefully to avoid burning the mash and having to redo this process over again.

== Important Notable Items ==
* Black smoke means the mash is over the temp range (Burning.)
* White smoke means the mash is in the ideal range range.
* Boiling water means the mash is ready for the next ingredients.
* The mash will cook/burn faster while the pot lid is on.
* Ingredients cannot be added while pot lid is on.
* If you are having trouble keeping the temperature under control, add the regulator to the burner.

== Cooking The Mash Pt.1 ==
# Add Cornmeal to the Pot. (Ingredients -> Corn Meal on HUD)
# Add Barley to the Pot. (Ingredients -> Barley on HUD)
# Select Water Pitcher on HUD. (Tools -> Water Pitcher)
# Walk over to the Water Spout and fill the pot.
# Repeat last 2 steps.
# Turn the gas on and light the stove with the lighter. (Touch near propane handle and turn. Tools -> Lighter on HUD)
# Maintain the temperature by turning the handle up or down.
# Keep the temperature between 175-185.
# Cook until the water begins boiling.

== Cooking The Mash Pt.2 ==
# Add 3 Packets of Alpha Amalyze.
# Keep the temperature between 140-150.
# Cooking until water begins boiling.

== Cooking The Mash Pt.3 ==
# Add 3 Spoonfuls of Beta Amalyze.
# Keep the temperature between 125-135.
# Cooking until water begins boiling.

== Cooking The Mash Pt.4 ==
# Add 1 Spoonful of Yeast Nutrient.
# Add 2 Spoonful of Dry Yeast.
# Keep the temperature between 100-110.

'''Congratulations, You've completed cooking the Corn Mash. Don't forget to turn off your burner.'''
 

= '''Distilling The Corn Mash''' =
STOP & READ This step can be very dangerous. If you do not keep track of the temperature and burn the mash. Your still will explode.

== Important Notable Items ==
* If you go over temperature and burn the moonshine, the still will explode.
* Removing the Copper head will lower the pressure in the pot and will decrease the percentage of the shine cooked.
* You will know you're at the perfect cooking temperature when the corn mash is boiling.

== Setting Up The Copper Still ==
# Set up a brand new propane burner and tank next to your current one.
# Place a Wooden Stool onto the burner.
# Place a Copper Coil onto the Wooden Stool.
# Place a Copper Pot onto the Propane Burner.
# Place a Paper Filter onto the Copper Pot.

== Filling The Copper Pot ==
# Pickup the Metal pot from the propane burner that you just cooked from.
# Pour the metal pot into the copper pot.
# Get rid of the metal pot.
# Remove the paper filter from the copper pot.
# Place a Copper Head onto the Copper Pot.

== Filling The Copper Pot ==
STOP & READ This part can cause the pot to explode. Make sure to read the Important Notable Items above.

# Light the burner, and maintain 120-130.
# When the copper pot is giving water boiling sounds, then you are at the current temperature.
# Once the copper pot begins dripping, select the Glass Jar from your HUD and click the Copper Coil.
# When the glass jar is full, click it to have the final product delivered.

You will get a total of 4 jars. 1 Methanol (This can be throw like a molotov cocktail.) and 3 Drinkable Moonshine Jars. (Attach to drink.)

RolePay Store Expansion

2022-01-03T02:55:06Z

Johnny:

2018-09-28T00:57:24Z

Johnny: Created page with "← Gridnet Radio System {|align=right |__TOC__ |} = '''Getting Started''' = :New to the system? Follow our guide h..."

[[Gridnet Radio System|← Gridnet Radio System]]
{|align=right
|__TOC__
|}
= '''Getting Started''' =
:New to the system? Follow our guide here for information on how to get started!

:This guide will help you setup a network successfully, if all steps are done properly.

:Need help and don't understand the guide? Feel free to get in touch with our support by opening a ticket: [http://tickets.nexus-sl.net/ Nexus Ticket Support]

= '''Creating a New Network''' =
:It's important to note, before you are to create your network, you will need to find a suitable place where you can rez your server and leave it. This server has to be running 100% of the time.

Follow These Steps to Create a Network
#Rez the "Nexus GridNet Server v1.0". (Remember it has to stay there for as long as you have the network.)
#Touch the server to begin registration & type the desired network name when prompted.
#Once submitting the network name, you'll receive a prompt to open the webpage. This will lead you to the GridNet Dashboard.
#Go to the webpage and enter a new password for your account. (Please note, all networks that you create will appear under this account.)
#Bam, your new network is created. Access the new network by clicking the small blue icon that appears in the upper-right hand corner of the network's box.

= '''Creating Zones & Channels''' =
:To begin creating your first zone & channel, you will need to navigate to the "Zone Editor" page.

#Select "Add Zone" and enter the desired zone name.
#Once your zone has been created, you can select "Add Channel" from within the zone and enter the desired channel name.
#Now that you have created your first zone and channel, you can now proceed to configure a radio!

= '''Configuring a Radio''' =
:STOP & READ - If you haven't created a zone & channel yet, please go back and follow the previous step before proceeding.

:Located in the "GridNet Radio System" folder are 15+ radio models to choose from. Go ahead and determine which radio model you'd like to configure to your network!

:Once you have chosen a radio model that you'd like to configure, rez the radio next to the server.

#Touch the server you want to configure the radio to.
#Touch the radio to begin configuring.
#Select the zone you would like to configure the radio to when prompted.
#Set the radio next-owner permissions to 'No Transfer'.
#Take the radio back into your inventory when it asks what channel to use.
#You can now freely distribute the radio.

Gridnet Radio System/API

2018-09-27T23:31:24Z

Johnny:

[[Gridnet Radio System|← Gridnet Radio System]]
{|align=right
|__TOC__
|}
= '''API Documentation''' =

:If you have scripting knowledge, you can take advantage of GridNet's API and begin creating your own tools & devices that control your network.

:To navigate this wiki better, please use the navigation on the right side of the screen.

=== API Actions: ===
----
* Get Network Details
* Create Zone
* Delete Zone
* Zone ID to Name
* Zone Name to ID
* Zone List
* Zone Channel List
* Create Channel
* Delete Channel
* Channel Name to ID
* Channel ID to Name

=== How to make an API Call: ===
----
Before you can make a call to the API, you must first create and obtain an API key from your GridNet dashboard.
To do this, log into your GridNet Dashboard, select the network, then navigate to "API" and select "Add API Key" to generate a new API Key.

If you aren't the owner or manager of a network and you'd like to use the API, you'll need to check with network owner about acquiring one.

=== Prerequisites:===
----
You'll need to include the following global functions & variables into your script in order to successfully call an API action:

<pre>
string network_api_key = "YOUR-NETWORK-API-KEY-GOES-HERE";
key req_id;

string GenerateHash(string api_key, string data) {
return llSHA1String(api_key+""+llStringToBase64(data));
}

SendToServer(string json_data) {
string hash = GenerateHash(network_api_key, json_data);
req_id = llHTTPRequest("https://gridnet.nexus-sl.net/api/index.php?",[
HTTP_METHOD,"POST",
HTTP_MIMETYPE,"application/x-www-form-urlencoded"
],"hash="+hash+"&api_key="+network_api_key+"&data="+llStringToBase64(json_data));
}
</pre>

All API Calls are sent to our server in JSON format. Each function listed below contains the list of requirments that you must first set in your JSON string prior to executing the <code>SendToServer(string json_data)</code> function.

= '''Get Network Details:''' =

This function will return the following details pertaining to the specified network:
* Network ID
* Network Owner
* Server Location
* Devices Connected
* Channel Count
* Zone Count
* Transmission Count

=== Required JSON data for API Call: ===
* "action" : "get_network_details"

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"get_network_details");
json = llJsonSetValue(json,["network_id"],network_api_key);
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"network_id" : "12",
"network_owner" : "Johnny Nexen",
"server_location" : "Silesia",
"devices_connected" : "12",
"channel_count" : "2",
"zone_count" : "3",
"transmission_count" : "50"
}
</pre>

= '''Create Zone:''' =

This function allows you to create a new zone that is associated with the supplied API Key.

=== Required JSON data for API Call: ===
* "action" : "create_zone"
* "zone_name" : "The Name of Your New Zone"

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"create_zone");
json = llJsonSetValue(json,["zone_name"],"Fire Dept");
SendToServer(json);
</pre>

=== Example Response: ===
zone_id is returned upon successful zone creation.
<pre>
{
"zone_id" : 20
}
</pre>

= '''Delete Zone:''' =

This function allows you to delete a zone that is associated with the supplied API Key.

=== Required JSON data for API Call: ===
* "action" : "delete_zone"
* "zone_id" : The 'zone_id' number

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"delete_zone");
json = llJsonSetValue(json,["zone_id"],"12");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"success" : TRUE
}
</pre>

= '''Zone ID to Name:''' =

This function will fetch the zone name by providing the zone ID.

=== Required JSON data for API Call: ===
* "action" : "zone_id_to_name"
* "zone_id" : The 'zone_id' number

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"zone_id_to_name");
json = llJsonSetValue(json,["zone_id"],"12");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"zone_name" : "Fire Dept"
}
</pre>

= '''Zone Name to ID:''' =

This function will fetch the zone ID by providing the zone name.

=== Required JSON data for API Call: ===
* "action" : "zone_name_to_id"
* "zone_name" : The name of the zone

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"zone_name_to_id");
json = llJsonSetValue(json,["zone_name"],"Fire Dept");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"zone_id" : 20
}
</pre>

= '''Zone List:''' =

This function will return a list of all your created zones.

=== Required JSON data for API Call: ===
* "action" : "zone_list"

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"zone_list");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"zone_list" : ["Fire Dept","Poice Dept","Medical","DOT"]
}
</pre>

= '''Zone Channel List:''' =

This function will return a list of all the channels within the specified zone.

=== Required JSON data for API Call: ===
* "action" : "zone_channel_list"
* "zone_id" : "20"

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"zone_channel_list");
json = llJsonSetValue(json,["zone_id"],"20");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"channel_list" : ["Engine - 22","Ladder-21","Engine - 21","Tanker - 21","Chief"]
}
</pre>

= '''Create Channel:''' =

This function will create a channel within the specified zone.

=== Required JSON data for API Call: ===
* "action" : "create_channel"
* "zone_id" : The 'zone_id' number you'd like to create the channel under

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"create_channel");
json = llJsonSetValue(json,["zone_id"],"20");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"channel_id" : 30
}
</pre>

= '''Delete Channel:''' =

This function will delete the channel within the specified zone.

=== Required JSON data for API Call: ===
* "action" : "delete_channel"
* "zone_id" : The 'zone_id' number
* "channel_name" : The name of the channel you'd like to delete

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"delete_channel");
json = llJsonSetValue(json,["zone_id"],"20");
json = llJsonSetValue(json,["channel_name"],"Fire Dept");
SendToServer(json);
</pre>

= '''Channel Name to ID:''' =

This function will return the channel ID of the provided channel name that is in the specified zone.

=== Required JSON data for API Call: ===
* "action" : "channel_name_to_id"
* "zone_id" : The 'zone_id' number that the channel is linked to
* "channel_name" : The name of the channel that you'd like the ID for

Unsure how to obtain the "zone_id"? View the API function: [[#Zone Name to ID:]]

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"channel_name_to_id");
json = llJsonSetValue(json,["zone_id"],"20");
json = llJsonSetValue(json,["channel_name"],"Fire Dept");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"channel_id" : 30
}
</pre>

= '''Channel ID to Name:''' =

This function will return the channel name of the provided channel ID.

=== Required JSON data for API Call: ===
* "action" : "channel_id_to_name"
* "channel_id" : The channel ID that you'd like the name for

=== API Call Example: ===
<pre>
json = llJsonSetValue("",["action"],"channel_id_to_name");
json = llJsonSetValue(json,["channel_id"],"30");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"channel_name" : "Fire Dept"
}
</pre>

= '''Complete API Examples''' =

We've put together a couple of examples demonstrating how to use the GridNet API in your own scripts.

=== Example One - Get Network Details ===
<pre>
string network_api_key = "INSERT-API-KEY-HERE";
key req_id;

string GenerateHash(string api_key, string data)
{
return llSHA1String(api_key+""+llStringToBase64(data));
}

SendToServer(string json_data)
{
string hash = GenerateHash(network_api_key, json_data);
req_id = llHTTPRequest("http://gridnet.nexus-sl.net/api/index.php?",[
HTTP_METHOD,"POST",
HTTP_MIMETYPE,"application/x-www-form-urlencoded"
],"hash="+hash+"&api_key="+network_api_key+"&data="+llStringToBase64(json_data));
}

default
{
touch_start(integer n) {
if(llDetectedKey(0) == llGetOwner()) {
string json = llJsonSetValue("",["action"],"get_network_details");
SendToServer(json);
}
}
http_response(key i, integer s, list m, string b) {
if(i == req_id)
llOwnerSay(b);
}
}
</pre>

=== Example Two - Create a New Zone ===
<pre>
string network_api_key = "INSERT-API-KEY-HERE";
string json;
key req_id;
integer chan;
integer handle;

string GenerateHash(string api_key, string data) {
return llSHA1String(api_key+""+llStringToBase64(data));
}

SendToServer(string json_data) {
string hash = GenerateHash(network_api_key, json_data);
req_id = llHTTPRequest("https://gridnet.nexus-sl.net/api/index.php?",[
HTTP_METHOD,"POST",
HTTP_MIMETYPE,"application/x-www-form-urlencoded"
],"hash="+hash+"&api_key="+network_api_key+"&data="+llStringToBase64(json_data));
}

default
{
touch_start(integer n) {
if (llDetectedKey(0) == llGetOwner()) {
json = "";
llListenRemove(handle);
chan = (integer)(llFrand(1000000000.0) - 1000000000.0);
handle = llListen(chan, "", llGetOwner(), "");
llTextBox(llGetOwner(),"Create a New Zone\n\nPlease enter a zone name you'd like to create",chan);
}
}

listen(integer channel, string name, key id, string message) {
if (channel == chan && id == llGetOwner()) {
message = llStringTrim(message,STRING_TRIM);
if (message == "") return;
else {
json = llJsonSetValue("",["action"],"create_zone");
json = llJsonSetValue(json,["zone_name"],message);
SendToServer(json);
}
}
}

http_response(key i, integer s, list m, string b) {
if (i == req_id) {
if (llJsonValueType(b,["zone_id"]) == JSON_NUMBER) {
string zone_id = llJsonGetValue(b,["zone_id"]);
llOwnerSay("The zone (\""+llJsonGetValue(json,["zone_name"])+"\" - Zone ID: "+zone_id+") has successfully been created!");
}
else llOwnerSay("ERROR >> " + b);
}
}
}
</pre>

Gridnet Radio System/API

2018-09-27T22:08:03Z

Johnny: Created page with "← Gridnet Radio System {|align=right |__TOC__ |} = '''API Documentation''' = :If you have scripting knowledge, y..."

RolePay Time Clock Expansion

2018-06-09T19:24:20Z

Johnny:

[[Rolepay Money System/Expansions|← Rolepay Money System Expansion Packs]]
{|align=right
|__TOC__
|}

= '''Using Expansion Packs''' =
In order to use any expansion pack, you must have an API key only obtained from the Web Interface from the RolePay Server. You can also obtain an API key from the network owner or someone who has access to the Web Interface. 

= '''Making Expansion Packs''' =
Want to learn how to make expansion packs? All expansion packs are made using the [[Rolepay Money System/API|RolePay Money System API]]. All you will need is basic knowledge of HTTP and LSL. 

= '''Setting Up The Time Clock Expansion''' =
These steps assume that you already have an API key. Follow these steps to configure your device:
#Locate the Time Clock in your inventory and rez into place
#Left-click the Time Clock to receive the dialog menu & select "Setup"
#A URL dialog will be presented, offering you a link to the online device registration page
#Once on the registration page, input a RolePay API key and select "Validate"
#If successfully validated, you can then select the funding source which will be the funding used to complete payouts. You can either input a credit card number belonging to the RolePay network that you're connecting to or use network funds (please ensure you have permission from the network owner)
#Once funding has been validated, you will be directed to the Time Clock dashboard and your Time Clock is ready for use!
 

== '''User Registration & User Options''' ==
To add users to the Time Clock, you will need to visit the Time Clock's online dashboard. To do this, left-click the Time Clock & select "Dashboard" from the menu. Once you've accessed the dashboard, navigate to the "Users" tab. On the left, enter the Second Life username and the hourly wage for the user you'd like to register and select "Add User". The users name will then appear to the right of the registration box if the user was successfully registered. Selecting a registered user from the Registered Users list will display the users unpaid/paid earnings and allow you to edit the following settings:
*Rate/HR: Set the $ amount that the user will earn per hour clocked in
*Auto Clockout: Check the box if you wish to enable the Auto Clockout feature; this feature will monitor the status of clocked in users & will automatically clock out those that go offline.
** Please Note: This feature requires additional configuration to the Time Clock in-world. More instructions will become available on the interface once you've enabled Auto Clockout for one or more users
*Work Days: Allows you to check the boxes of the week days the user is permitted to work. Note: The system conducts midnight checks; if the user is not permitted to work the new day, they'll be clocked out automatically
 

= '''Clocking In''' =
Once a user has been registered to the Time Clock, they'll have access to the Time Clock. When left-clicked, a menu will be provided which will give them the option to view their stats and option to clock-in/out. 

= '''Clocking Out Users''' =
On the "Home" dashboard page, any users that are currently clocked in will be listed there. You will be able to see when each person started with the option to clock out the user. When a user is clocked out, the system will calculate their total earnings and add it to the users unpaid earnings. Note: Regardless if the user has been clocked out manually or automatically by the system (ex. Auto clockout) - The users clocked time will always be added to their unpaid earnings which then allows those unpaid earnings to be paid out. 

= '''Payouts & Records''' =
There are two payout options available:
#Manual Payouts by Owner: If you would like to manually payout time for each user, you can do so by visitng the "Users" page on the Time Clock dashboard. Simply select the user, followed by "Payout". If the Payout option is not clickable, the user has no unpaid earnings to payout.
#Manual Payouts by User: To allow users the ability to request payouts themsevles, navigate to the "Settings" page on the Time Clock dashboard & enable "Allow Manual Payout"; users will then be able to request payouts for their unpaid earnings via the Time Clock menu.
Each time a payout has been completed, a new record will be made on the "Payouts" page. Each record consists of the following details: Date & Time, Payee, Funding Source, and the Amount paid. 

= '''Updating Time Clock Configuration''' =
Navigate to the "Settings" page on the online Time Clock dashboard. There you are able to change the RolePay API key & funding source details. 

= '''API Documentation''' =
In order to use the Time Clock API, you must first get an API key from the Time Clock Dashboard, "API Keys" page. 

== '''API Features''' ==
*Check Key (Checks to make sure an API key is valid and exists)
*Register User (Registers user into the Time Clock network)
*Clock-in User (Clocks in specified user into the Time Clock network)
*Clock-out User (Clocks out specified user from the Time Clock network)
 

== '''Check API Key''' ==
This function will check to see if the specified API Key exists and is valid.

=== Information required for API call ===
* action (check_key)
* api_key

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/check_key/api_key/{API_KEY} GET</pre>

=== Example Response ===
<pre>
{
"success": "api_key found"
}
</pre>

== '''Register User''' ==
This function will register the specified user to the Time Clock network.

=== Information required for API call ===
* action (register_user)
* api_key
* user_uuid (The user to register)
* wage (The users hourly wage)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/register_user/api_key/{API_KEY}/user_uuid/{USER_UUID}/wage/{USER_WAGE} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been registered!"
}
</pre>

== '''Clock-In User''' ==
This function will clock-in the specified user.

=== Information required for API call ===
* action (clock-in_user)
* api_key
* user_uuid (The user to clock-in)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-in_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked in."
}
</pre>

== '''Clock-Out User''' ==
This function will clock-out the specified user.

=== Information required for API call ===
* action (clock-out_user)
* api_key
* user_uuid (The user to clock-out)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-out_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked out."
}
</pre>

= '''Changelog''' =
* Version: 1.2:
** PLEASE READ BEFORE YOU UPDATE **
If you already have a Time Clock set up and would like to continue using that network, you'll have to copy the network key located in the description field of your old time clock. (The Network Key begins with an '@' character, followed by 36 characters) Once you have copied the network key, you can paste the key into the description field of the new time clock. Once set, left-click the time clock and it should automatically connect to your network.

* Fixed: Fixed security issue with URLs

* Version 1.1:

* New Feature: Admin login; you can now assign admins and allow them access to the dashboard.
* New Feature: Time Conditions; set specific working hours a person can work for each day of the week.
* Fixed: Auto-Clockout; users with 'auto-clockout' enabled should now be properly clocked out when they go offline.

Nexus Light System/Documentation

2017-04-05T04:23:34Z

Johnny:

RolePay Store Expansion

2017-04-05T04:18:56Z

Johnny:

RolePay Time Clock Expansion

2017-02-15T23:40:37Z

Johnny:

[[Rolepay Money System/Expansions|← Rolepay Money System Expansion Packs]]
{|align=right
|__TOC__
|}

= '''Using Expansion Packs''' =
In order to use any expansion pack, you must have an API key only obtained from the Web Interface from the RolePay Server. You can also obtain an API key from the network owner or someone who has access to the Web Interface. 

= '''Making Expansion Packs''' =
Want to learn how to make expansion packs? All expansion packs are made using the [[Rolepay Money System/API|RolePay Money System API]]. All you will need is basic knowledge of HTTP and LSL. 

= '''Setting Up The Time Clock Expansion''' =
These steps assume that you already have an API key. Follow these steps to configure your device:
#Locate the Time Clock in your inventory and rez into place
#Set the Time Clock to a specific group; this will allow your registered users to access the Time Clock
#Left-click the Time Clock to receive the dialog menu & select "Setup"
#A URL dialog will be presented, offering you a link to the online device registration page
#Once on the registration page, input a RolePay API key and select "Validate"
#If successfully validated, you can then select the funding source which will be the funding used to complete payouts. You can either input a credit card number belonging to the RolePay network that you're connecting to or use network funds (please ensure you have permission from the network owner)
#Once funding has been validated, you will be directed to the Time Clock dashboard and your Time Clock is ready for use!
 

== '''User Registration & User Options''' ==
To add users to the Time Clock, you will need to visit the Time Clock's online dashboard. To do this, left-click the Time Clock & select "Dashboard" from the menu. Once you've accessed the dashboard, navigate to the "Users" tab. On the left, enter the Second Life username and the hourly wage for the user you'd like to register and select "Add User". The users name will then appear to the right of the registration box if the user was successfully registered. Selecting a registered user from the Registered Users list will display the users unpaid/paid earnings and allow you to edit the following settings:
*Rate/HR: Set the $ amount that the user will earn per hour clocked in
*Auto Clockout: Check the box if you wish to enable the Auto Clockout feature; this feature will monitor the status of clocked in users & will automatically clock out those that go offline.
** Please Note: This feature requires additional configuration to the Time Clock in-world. More instructions will become available on the interface once you've enabled Auto Clockout for one or more users
*Work Days: Allows you to check the boxes of the week days the user is permitted to work. Note: The system conducts midnight checks; if the user is not permitted to work the new day, they'll be clocked out automatically
 

= '''Clocking Out Users''' =
On the "Home" dashboard page, any users that are currently clocked in will be listed there. You will be able to see when each person started with the option to clock out the user. When a user is clocked out, the system will calculate their total earnings and add it to the users unpaid earnings. Note: Regardless if the user has been clocked out manually or automatically by the system (ex. Auto clockout) - The users clocked time will always be added to their unpaid earnings which then allows those unpaid earnings to be paid out. 

= '''Payouts & Records''' =
There are two payout options available:
#Manual Payouts by Owner: If you would like to manually payout time for each user, you can do so by visitng the "Users" page on the Time Clock dashboard. Simply select the user, followed by "Payout". If the Payout option is not clickable, the user has no unpaid earnings to payout.
#Manual Payouts by User: To allow users the ability to request payouts themsevles, navigate to the "Settings" page on the Time Clock dashboard & enable "Allow Manual Payout"; users will then be able to request payouts for their unpaid earnings via the Time Clock menu.
Each time a payout has been completed, a new record will be made on the "Payouts" page. Each record consists of the following details: Date & Time, Payee, Funding Source, and the Amount paid. 

= '''Updating Time Clock Configuration''' =
Navigate to the "Settings" page on the online Time Clock dashboard. There you are able to change the RolePay API key & funding source details. 

= '''API Documentation''' =
In order to use the Time Clock API, you must first get an API key from the Time Clock Dashboard, "API Keys" page. 

== '''API Features''' ==
*Check Key (Checks to make sure an API key is valid and exists)
*Register User (Registers user into the Time Clock network)
*Clock-in User (Clocks in specified user into the Time Clock network)
*Clock-out User (Clocks out specified user from the Time Clock network)
 

== '''Check API Key''' ==
This function will check to see if the specified API Key exists and is valid.

=== Information required for API call ===
* action (check_key)
* api_key

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/check_key/api_key/{API_KEY} GET</pre>

=== Example Response ===
<pre>
{
"success": "api_key found"
}
</pre>

== '''Register User''' ==
This function will register the specified user to the Time Clock network.

=== Information required for API call ===
* action (register_user)
* api_key
* user_uuid (The user to register)
* wage (The users hourly wage)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/register_user/api_key/{API_KEY}/user_uuid/{USER_UUID}/wage/{USER_WAGE} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been registered!"
}
</pre>

== '''Clock-In User''' ==
This function will clock-in the specified user.

=== Information required for API call ===
* action (clock-in_user)
* api_key
* user_uuid (The user to clock-in)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-in_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked in."
}
</pre>

== '''Clock-Out User''' ==
This function will clock-out the specified user.

=== Information required for API call ===
* action (clock-out_user)
* api_key
* user_uuid (The user to clock-out)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-out_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked out."
}
</pre>

RolePay Time Clock Expansion

2017-02-15T19:51:57Z

Johnny:

[[Rolepay Money System/Expansions|← Rolepay Money System Expansion Packs]]
{|align=right
|__TOC__
|}

= '''Using Expansion Packs''' =
In order to use any expansion pack, you must have an API key only obtained from the Web Interface from the RolePay Server. You can also obtain an API key from the network owner or someone who has access to the Web Interface. 

= '''Making Expansion Packs''' =
Want to learn how to make expansion packs? All expansion packs are made using the [[Rolepay Money System/API|RolePay Money System API]]. All you will need is basic knowledge of HTTP and LSL. 

= '''Setting Up The Time Clock Expansion''' =
These steps assume that you already have an API key. Follow these steps to configure your device:
#Locate the Time Clock in your inventory and rez into place
#Left-click the Time Clock to receive the dialog menu & select "Setup"
#A URL dialog will be presented, offering you a link to the online device registration page
#Once on the registration page, input a RolePay API key and select "Validate"
#If successfully validated, you can then select the funding source which will be the funding used to complete payouts. You can either input a credit card number belonging to the RolePay network that you're connecting to or use network funds (please ensure you have permission from the network owner)
#Once funding has been validated, you will be directed to the Time Clock dashboard and your Time Clock is ready for use!
 

== '''User Registration & User Options''' ==
To add users to the Time Clock, you will need to visit the Time Clock's online dashboard. To do this, left-click the Time Clock & select "Dashboard" from the menu. Once you've accessed the dashboard, navigate to the "Users" tab. On the left, enter the Second Life username and the hourly wage for the user you'd like to register and select "Add User". The users name will then appear to the right of the registration box if the user was successfully registered. Selecting a registered user from the Registered Users list will display the users unpaid/paid earnings and allow you to edit the following settings:
*Rate/HR: Set the $ amount that the user will earn per hour clocked in
*Auto Clockout: Check the box if you wish to enable the Auto Clockout feature; this feature will monitor the status of clocked in users & will automatically clock out those that go offline.
** Please Note: This feature requires additional configuration to the Time Clock in-world. More instructions will become available on the interface once you've enabled Auto Clockout for one or more users
*Work Days: Allows you to check the boxes of the week days the user is permitted to work. Note: The system conducts midnight checks; if the user is not permitted to work the new day, they'll be clocked out automatically
 

= '''Clocking Out Users''' =
On the "Home" dashboard page, any users that are currently clocked in will be listed there. You will be able to see when each person started with the option to clock out the user. When a user is clocked out, the system will calculate their total earnings and add it to the users unpaid earnings. Note: Regardless if the user has been clocked out manually or automatically by the system (ex. Auto clockout) - The users clocked time will always be added to their unpaid earnings which then allows those unpaid earnings to be paid out. 

= '''Payouts & Records''' =
There are two payout options available:
#Manual Payouts by Owner: If you would like to manually payout time for each user, you can do so by visitng the "Users" page on the Time Clock dashboard. Simply select the user, followed by "Payout". If the Payout option is not clickable, the user has no unpaid earnings to payout.
#Manual Payouts by User: To allow users the ability to request payouts themsevles, navigate to the "Settings" page on the Time Clock dashboard & enable "Allow Manual Payout"; users will then be able to request payouts for their unpaid earnings via the Time Clock menu.
Each time a payout has been completed, a new record will be made on the "Payouts" page. Each record consists of the following details: Date & Time, Payee, Funding Source, and the Amount paid. 

= '''Updating Time Clock Configuration''' =
Navigate to the "Settings" page on the online Time Clock dashboard. There you are able to change the RolePay API key & funding source details. 

= '''API Documentation''' =
In order to use the Time Clock API, you must first get an API key from the Time Clock Dashboard, "API Keys" page. 

== '''API Features''' ==
*Check Key (Checks to make sure an API key is valid and exists)
*Register User (Registers user into the Time Clock network)
*Clock-in User (Clocks in specified user into the Time Clock network)
*Clock-out User (Clocks out specified user from the Time Clock network)
 

== '''Check API Key''' ==
This function will check to see if the specified API Key exists and is valid.

=== Information required for API call ===
* action (check_key)
* api_key

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/check_key/api_key/{API_KEY} GET</pre>

=== Example Response ===
<pre>
{
"success": "api_key found"
}
</pre>

== '''Register User''' ==
This function will register the specified user to the Time Clock network.

=== Information required for API call ===
* action (register_user)
* api_key
* user_uuid (The user to register)
* wage (The users hourly wage)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/register_user/api_key/{API_KEY}/user_uuid/{USER_UUID}/wage/{USER_WAGE} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been registered!"
}
</pre>

== '''Clock-In User''' ==
This function will clock-in the specified user.

=== Information required for API call ===
* action (clock-in_user)
* api_key
* user_uuid (The user to clock-in)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-in_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked in."
}
</pre>

== '''Clock-Out User''' ==
This function will clock-out the specified user.

=== Information required for API call ===
* action (clock-out_user)
* api_key
* user_uuid (The user to clock-out)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-out_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success": "User has successfully been clocked out."
}
</pre>