Nexus - New pages [en]

Nexus MARS System/Documentation

2022-01-11T00:08:27Z

Shymus:

[[Nexus MARS System|← Nexus MARS System]]
{|align=right
|__TOC__
|}
= '''Nexus MARS System 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 its 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 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 here on our [http://tickets.nexus-sl.net/ Support Site].

= '''Installing The Ramp''' =
: This MARS System was built for the 4 Door Medium Paladin. While it can be removed and attempted to be put onto other vehicles, it was made for that model specifically. No promises it will work for other models or vehicles.

== Instructions to link to Paladin ==
# Ensure that the vehicle is turned off, including any lighting or other components that may change any attributes while installing the modification.
# Take a copy of your vehicle as-is. Modifications may cause damage or unlink prims accidentally. Save a copy now in case this happens!
# Rez the modification near your vehicle.
# Right click the modification and select "Edit".
# With the Edit window open, hold your SHIFT key and left click the vehicle. This should select both objects at once. Make sure you select the vehicle last.
# Press your CTRL + L keys, or click the "Link" button in the Edit window.
# If prompted, confirm that you want to link the two objects together.
# When linked, the modification should automatically position itself to the recommended position and resize if necessary.
# If prompted, grant link permissions. This may unlink some prims. Make sure to delete them after.
# If desired, you may usually move the equipment once linked.

== Adding A Rappel Bar ==
: This repel bar allows for deployment of the rappel rope to get over large fences/walls. This is perfect for rapid deployment.
# Ensure that the vehicle is turned off, including any lighting or other components that may change any attributes while installing the modification.
# Take a copy of your vehicle as-is. Modifications may cause damage or unlink prims accidentally. Save a copy now in case this happens!
# Rez the Rappel Bars near your vehicle.
# Right click the modification and select "Edit".
# With the Edit window open, hold your SHIFT key and left click the vehicle. This should select both objects at once. Make sure you select the vehicle last.
# Press your CTRL + L keys, or click the "Link" button in the Edit window.
# Once the item is linked, the Rappel bar will automatically position itself once the scripts have updated.

= '''Operating The Ramp''' =
: Operating of the ramp is very straight forward. This can be done through the transferable HUD supplied in the box.

== Syncing the HUD ==
: To sync the HUD, simply sit in the vehicle passenger or driver seat, then press the sync button on the HUD.
: The vehicle will then listen for commands from the HUD.

: '''When the HUD is synced, there can be two operators. A Passenger and a Driver can both operate the MARS System at the same time.'''

== Moving The Ramps ==
: The ramps are moved with the arrows. Simply select the side you would like to operate and use the buttons to move the ramps.

= '''Using The Rappel Bar''' =
: The Rappel Bar is a special add-on used for getting over large walls.
: The Rappel Bar can be activated by simply getting close to the rappel bar and clicking it to deploy it.
: Once the rappel bar is deploy, you can touch the carabiner to deploy the rope and fast rope down.

: To fold the bar, simply touch the support structure of the Rappel Bar to fold.

: '''If the Rappel Bar does not deploy when touched, stand closer and try again.'''

= '''Using The Side Steps''' =
: The Side steps allow for SWAT members to hold onto the side of the vehicle for bigger groups to use it for breaching.
: Before the steps can be used, they will need to be deployed. Simply touch the side step and the step will deploy.

: '''If the step does not deploy when touched, stand closer and make sure you're on the vehicle's access list.'''

Nexus MARS System/Version History

2022-01-10T23:41:28Z

Shymus: Created page with "← Nexus MARS System {|align=right |__TOC__ |} = '''How to get updates''' = : When a newer version comes out, our ser..."

[[Nexus MARS System|← Nexus MARS 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.

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

Nexus MARS System

2022-01-10T23:40:32Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus MARS System is a perfect tool for breachin..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus MARS System is a perfect tool for breaching compounds and high areas quickly. This system is perfect for 2-3 story buildings, airplanes, and high walls.</div> 
<div style="font-size:1.3em;">Need help with your MARS System? Look at the documentation below!</div>

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

</div>

Nexus Moonshine/Documentation

2021-11-03T20:59:13Z

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.)

Nexus Moonshine/Version History

2021-11-03T20:51:59Z

Shymus: Created page with "← Nexus_Moonshine {|align=right |__TOC__ |} = '''How to get updates''' = : When a newer version comes out, our servers..."

[[Nexus_Moonshine|← Nexus_Moonshine]]
{|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 redelivery from the terminals in any of the stores.

: Looking for the 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.

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

Nexus Moonshine

2021-11-03T20:51:11Z

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 Shroom Growing/Documentation

2019-12-23T06:24:37Z

Shymus: /* Nexus Shroom Growing Documentation */

[[Nexus Shroom Growing|← Nexus Shroom Growing]]
{|align=right
|__TOC__
|}
= '''Nexus Shroom Growing 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 its 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 Shroom Growing, 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 here on our [http://tickets.nexus-sl.net/ Support Site]. 

= '''Getting Started''' =
Before starting to grow shrooms, you will need to take a few steps in growing your shrooms. 
It is a very complex system that will take time, it does not grow within an hour. Plants take at least 12 hours to grow. 
== '''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 Microwave (Used to dry shrooms after they have grown.)
*Nexus Shrooms HUD (Right Click -> Add)
*Nexus Metal Table (Used to place jars on.)
*Nexus - Bar Surface Script (Place inside a prim to allow for jars to be placed on the prim.)
*Nexus Shroom L Hand Attachment (The Left-hand attachment for the HUD.)
*Nexus Shroom R Hand Attachment (The Right-hand attachment for the HUD.)

== '''Setting Up Your Growhouse''' ==
Obviously, you will need everything set up before you start growing your shrooms. 
These items are required for your grow hose.
* Microwave
* Metal Table or Prim with Nexus - Bar Surface Script in contents.
 
Once you have those items placed out, go ahead and move on towards your next steps. 

== '''How To Use The HUD''' ==
The HUD works very simply. It uses a simple combination method. To use items together, wear both in your hands and select Combine. 
If you have nothing selected in one hand, that will be considered an empty hand and will remove items from jars or etc.
 
== '''Filling Jars''' ==
Once you are ready to place the jars, follow these steps. 
These steps assume you're wearing all the attachments for making shrooms. (HUD and Both Hands)
# Select Glass Jar and Spray Bottle, then Combine.
# Deselect Spray Bottle
# Select Dirt Trowel, then Combine.
# Deselect Dirt Trowel.
# Select Seeds, then Combine. (This will remove the seeds automatically)
# Select Jar Lid, then Combine.
'''Once you have sealed the jar, the growth process will start. You can either place the jar on a table or carry the jar around.''' 
'''If you carry the jar around, it is not recommended to log out with the jar or your HUD will reset.'''
 

== '''Opening The Jar''' ==
Once you Shrooms have started peaking the top of the jar lid, you will need to open the jar to help the growing process. 
''These steps will not work if the shrooms are not ready.''
# Place the jar in your hand. (Click it from the table)
# Combine the sealed jar with an empty hand.
# Place the jar back down.
# Remove the Jar Lid from your hand.

== '''Harvesting The Shrooms''' ==
If your shrooms have completed growing, you can finally harvest them and process them for packaging. 
''These steps will not work if the shrooms are not ready.''
# Pickup the jar from the table.
# Combine the shrooms with the empty hand.
# Throw away the empty jar. (Press the X)
# Select Metal Tray, Then Combine.
# Place Metal Tray into the Microwave.
# Wait 3 Minutes for the shrooms to dry.
# Open the microwave and take the metal tray.
# Combine the shrooms with an empty hand.
# Throw the metal tray away and select plastic bag.
# Combine the Plastic Bag with the Dry Shrooms.
You have completed the steps to growing, harvesting, and processing your own Psilocybin Shrooms. Once you hit '''Deliver Drugs''', you will be delivered the drugs for consumption.
 

= '''Distribution''' =
All the drugs are transferable! That means you can sell them, give them away, or maybe consume them yourself. 
When consuming the drugs, you will need to attach the baggie and touch it. 
After you ingest the drugs, it will no longer be able to be used! 
Good luck with your major drug creation/manufacturing/growing/dealing/usage!

= '''Disclaimer''' =
This system is not 100% accurate, it is not intended to be used as a guide to producing real-world Psilocybin. Doing so can cause harm to self or others. 
We do not support the use of illegal substance in the real world. If you use this as a guide for real-world production, we will not be responsible for any harm you inflict upon yourself. We warned you.

Nexus Shroom Growing/Version History

2019-12-21T19:20:55Z

Shymus: Created page with "← Nexus Shroom Growing {|align=right |__TOC__ |} = '''How to get updates''' = : When a newer version comes out, o..."

[[Nexus Shroom Growing|← Nexus Shroom Growing]]
{|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 redelivery from the terminals in any of the stores.

: Looking for the 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.

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

Nexus Shroom Growing

2019-12-21T19:18:53Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Shroom Growing is Second Life's first shro..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Shroom Growing is Second Life's first shroom growing system that allows for 100% growable psilocybin. You can manage your shroms to get Psilocybin for distribution and consumption.</div> 
<div style="font-size:1.3em;">Need help with your Shroom System? Look at the documentation below!</div>

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

</div>

GridNet Radio System/Documentation

2018-09-28T14:40:24Z

Johnny:

[[Gridnet Radio System|← Gridnet Radio System]]
{|align=right
|__TOC__
|}
= '''Getting Started''' =
:New to the system? Follow our ''[http://wiki.nexus-sl.net/wiki/index.php?title=GridNet_Radio_System/Getting_Started Getting Started]'' guide for information on how to get started!

:This guide will help you set up a network successfully if all steps are done properly. '''It is highly recommended to read that guide before reading this.'''

: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]

= '''How To Use This Documentation''' =
: The documentation is built into three parts. Server, Radio, and Web Interface.
: Every feature on here is sorted to help you find what you're looking for.
: If you are unable to find something, please refer to the table of contents on the right side of the page. If you are still unable to find what you're looking for, you can try messaging in our group chat ''Nexus Roleplay System'' or file a ticket here: [http://tickets.nexus-sl.net/ Nexus Ticket Support]

= '''GridNet Server''' =
: The GridNet Server is an item that is rezzed in-world. This item is used to keep the network in your name, handle distribution servers, and prevent others from stealing your network name.
: When you create a network, the server will need to remain rezzed. If it is not rezzed, someone will have the ability to steal your network name. The server prevents that until you delete the network.
== Configuring The Server ==
#Rez the "Nexus GridNet Server v1.11". (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.
== What Is The Server For? ==
: The server is used for large purposes. There are multiple reasons that a network's server needs to be rezzed.
'''Here are some of the reasons'''
* The Server acts as an interface to the web dashboard.
* The Server allows you configure items to the network.
* The Server creates distribution servers and manages their load.
* The Server manages the radio network's repeater.
== What Is The Network Repeater? ==
: In the real world, a radio repeater is used to get a radio signal and repeat it over a larger distance.
: For us, the radio repeater is used as a way to verify with the server that there are active and connected devices.
: The repeater plays an important role in keeping the network stable. It keeps everything synced across the radios.
=== How Do I Know The Repeater Is Working? ===
: Every hour you will hear morse code giving off the repeater code. This is the repeater re-syncing with the server making sure that all the radios are on the same page.
: If there are no radios connected the repeater will not fire off its repeater code until a new device connects.
=== How Do I Disable The Repeater Noise? ===
: The repeater morse code can easily be turned off on the web interface.
'''Follow These Steps To Disable It'''
#Navigate to your network dashboard.
#Go to the Settings page.
#Turn the "Enable Repeater" checkmark off.
:Please remember, this does not turn the repeater permanently off, it does not affect performance with the servers. It will just turn off the noise that the repeater makes when it syncs to the server.

== Server Updates ==
:When your server is outdated, it will be clearly visible and will inform you via floating text.
:The server will not stop working just because the server is outdated. __You will not be able to configure anything to the server while in this mode.__
:Worried about losing your network or data? Don't worry, Network data is NOT lost when updating.
=== How To Update Your Server ===
#When your server gets outdated. (Visible from the floating text.)
#Touch the server to request an ''Update USB''. (Will be sent directly from our servers.)
#Rez the USB next to the server.
#Touch the USB then Touch the server.
#It will then start updating. (Do Not Touch or Delete Anything! If that is done, you're risking data corruption and a lost network.)
#Once the update is complete, the server will turn itself back on and work just like new!

= '''GridNet Radios''' =
:This section applies to all radio models. All radios function exactly the same except models that are animated.
== Configuring Items/Radios ==
: Configuring an item to work with your network is very simple. If you have an official item we have created, the configuration is quick and simple.
:STOP & READ - There are steps recommended before configuring the radio. You will need to create zones and channels before configuring.
:For more information on setting up the network, please follow the ''[http://wiki.nexus-sl.net/wiki/index.php?title=GridNet_Radio_System/Getting_Started Getting Started]'' guide.
=== Radio Configuration ===
#Touch the server you want to configure the radio too.
#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.
== Using The Radios ==
:Now that you have your radio set up, using the radios is very easy.
:When you first pull up the radio and attach it, you will need to give it a second to load. If it is your first time wearing the radio, it will configure and reset.

=== What Happens When Attached? ===
:When the radio is attached to a person, there are a few steps that happen before the radio is usable.
:Here is what happens once a radio is attached.
#If this is your first time attaching the radio, it will clear all the settings and variables from the old owner.
#The radio will then check if you are banned from the network. If you are; the radio will not move any further.
#The radio will then check to see if group access is enabled and determine if you are in the correct group.
#The radio will load all the channels for the zone the radio is configured in and prompt for you to pick one.
#Once you have picked your channel, your radio will then register with the network and show it online. Your radio is now usable!

=== Radio Operations ===
:Once operational, the radio will work in a structure of radios. The structure is very important as to who you can talk too.
:This structure is very simple. Transmissions are as followed:
==== Global ====
:When you send a message on the global, your message will be transmitted to every radio that is on the radio network. This includes all zones and all channels.
==== Zone ====
:When you send a message on a zone, your message is sent to all radios configured to the matching zone. If your radio is configured to zone ''Fire Dept'', then your message will go to every radio in that same zone.
==== Channel ====
:When you send a message on a channel, the message will be sent to every radio in that channel only.
=== Radio Settings & Dialog ===
:There are multiple settings that can be changed within the radios. This can be accessed by simply typing __/1 menu__ or touching the radio.
:These settings are as defined.
*'''Change Chan''' This will change the channel that the radio is set too. For example, if you are on Tac-1 then you can switch to another channel like Tac-2.
*'''Settings''' This will allow you to change some of the settings for the radio in the dialog.
**'''Verbose''' This setting will allow you to set how the message is received/transmitted to you.
***'''rOwner/tOwner''' Sets the radio to __OwnerSay Messages__ that are received/transmitted.
***'''rSay/tSay''' Sets the radio to __Say Messages__ that are received/transmitted.
***'''rWhisper/tWhisper''' Sets the radio to __Whisper Messages__ that are received/transmitted.
**'''Transmit Channels''' This will allow you to change the chat channels to other channels. Example; change /5 to /12 or other.
***'''Global''' Sets the chat channel for Global transmissions.
***'''Zone''' Sets the chat channel for Zone transmissions.
***'''Channel''' Sets the chat channel for Channel transmissions.
**'''Animations''' If your radio allows for animations, this is how to enable/disable them.
***'''Enable Anim''' This will __Enable__ the animations.
***'''Disable Anim''' This will __Disable__ the animations.
**'''Sounds''' This will allow you to change the sounds used by the radio. (''You will need to enter a UUID'')
***'''Transmit''' This will change the sound that goes off when you __Transmit__ a message.
***'''Receive''' This will change the sound that goes off when you __Receive__ a message.
*'''Call Sign''' Your callsign is how your name is displayed on the radios when a message is sent across Global/Zone/Channel.
= '''Web Interface''' =
: The web interface is where most of the work happens on your network. A large majority of your network will be managed here.
== Logging In ==
: When logging in, you will be met with two options Network Manager and Network Owner.
: '''If this is your first time logging in, you will be forced to change your password.'''
: If you are the Network Owner; you will need to log in through this method.
: If you are the Network Manager; this is your way. Please remember that the password is specific to that network. You can have two different passwords per network.
== Forgotten Password ==
: If you have forgotten your password, these are the steps that you take to reset your password.
=== Network Owners ===
# Select [https://gridnet.nexus-sl.net/forgot-password Forgot Password] on the home page.
# Enter your Second Life Username and Captcha.
# You will be IMed by one of our bots supplying you a link to change your password.
# Once you have navigated to that link, you will be able to change your password.
# After you have changed your password, you will be able to access your account like normal.
: If you are still unable to access your account, please file a ticket at our [http://tickets.nexus-sl.net Support Site] and we will manually reset your account.
=== Network Managers ===
: If you are a network manager, you will need to contact another Manager in the network or the network owner.
: They will need to manually reset your password for you through the network manager page.
: If your network owner will not reset your password, DO NOT CONTACT SUPPORT. We do not reset the Network Manager's passwords. That is solely up to the Network Owner. They could have changed it to lock you out, so we will not manage it for you.
: If you're a Network Owner and you're having trouble resetting a Network Manager's password, then you can contact support at our [http://tickets.nexus-sl.net Support Site] and we will gladly help you.
== Network Selection ==
: The Network Selection page will list all the networks that you are an Owner of. If you do not own the network, it will not appear.
: __If you are a Network Manager; you will not see this page, you will be logged straight into the network your Manager account is registered too.__
== Logging In To Your Network ==
: Logging in to your network is extremely simple and completed in a very simple step.
# Locate the network you'd like to manage.
# Click the blue arrow on the right upper corner of the network box.
== Deleting A Network ==
: DISCLAIMER Once you delete a network, the effects are permanent. Please __do not contact support__ asking us to undo the mistake. We cannot undo the mistake.
: If you have decided that you no longer need the network or you have made errors and want to start over. Deleting your network is extremely simple.
: '''Follow These Steps To Delete Your Network'''
# Delete your network server in-world. (This will make the server show up red on the network dashboard.)
# Once deleted, navigate back to the web dashboard and select the Trash can in the top-right corner of the network.
# You will then need to enter the Network Name exactly and confirm you're not a bot.
# This will then delete the Network Permanently.
=== Why Is My Network Showing Red? ===
: If your network is showing up on the dashboard red, then our servers are not able to communicate with your Network Server In-World.
: There are Two reasons why this can happen.
==== Server Still Loading ====
: If you have just created the network server, then it will take a few seconds for the network server to finish setting itself up and register itself on the dashboard.
: Most of the time this is caused because you loaded the web dashboard before the In-World finished it's loading.
: '''To fix it, simply refresh your web browser.'''
==== Poor Region Performance ====
: The second reason is your Region that your server is in is not able to be contacted or our servers cannot send messages to the server in that region.
: This is caused by poor performance in the region.
: To check if there are performance issues in the region, simply use your Second Life Browser.
: '''Firestorm''' : In your toolbar, navigate to Advanced -> Performance Tools -> Statistics ''CTRL+SHIFT+1''
: You will need to verify that the Region's FPS is above 40, the Scripts Run is below 90%
==== No Free URLs ====
: The region has no available Free URLS. This can easily be checked with your Second Life Viewer.
: This can easily be checked with a script placed into a prim. This script can easily be found on the [http://wiki.secondlife.com/wiki/LlGetFreeURLs Second Life Wiki].
==== Scripting Disabled In Parcel/Region ====
: Scripts may be disabled for the land.
: If you have scripts disabled for everything except the land group, the server may be set to the wrong group.
: This can be fixed by either enabling scripts in the parcel or setting the server to the land group.
== Nexus I.T. Services ==
: If you are wanting a stable environment to store your server, Nexus has a wonderful place to store the servers.
: Nexus I.T. Services allows you to pay monthly for a 15LI Server Rack that can allow you to store your servers for a long period.
: All Nexus customers receive a free month if they purchase 3 months. Each rack costs 99L$ a month.
== Network Dashboard ==
: The ''Network Dashboard'' is the home base of operation. Here you can see basic statistics of your network and the latest messages in your network.
: Although there is nothing that can be changed, you can easily navigate around the website.
=== Navigating Around ===
:[[File:Server-Select.png|50px|none]] '''Change Network''' This can easily be accessed at the top by clicking the three server's icon.
:[[File:Logout.png|50px|none]] '''Log-Out''' This will log you out of GridNet.
: '''Settings''' This page is made to let you change the basic settings of the network, adjust the ban list, and set the group access.
: '''Managers''' This page will allow you to add, remove, and edit Manager's privileges.
: '''Zone Editor''' This page will let you edit the channels and zones for the network.
: '''Transmissions''' This page will allow you to view transmissions specific to the zone.
: '''Radio List''' The radio list will let you view information about the radios that are currently connected to the network and actively worn by users.
: '''API''' The API is where you can go to manage your API keys used for the network.
: '''Distribution''' This page will allow you to manage your distribution network and servers. Information can also be viewed from the servers.
== Settings ==
: Here you are able to adjust your network settings to better fit your network's needs.
: Along with the settings, you can also manage your ban list and set the groups that can use the radio system.
=== Discord Support ===
: Discord is a very good tool used by Gamers to better help communicate. Discord can be found at the [http://discordapp.com/ Discord Website]
: Discord is not affiliated with Nexus in anyway and solely managed by separate entities. Nexus does not endorse/promote/discourage Discord in any way.
: ''Please note, although Discord is there, it does '''not currently''' have the ability to send messages via discord. It is currently just used to receive messages. We are looking for methods or ways to send messages in Discord.''
==== How To Add The Discord Bot ====
: Discord is very simple to link to your Network.
: '''Follow these steps'''
# Click the __Connect Discord Server__ Button.
# You will get sent to the Discord website. You may need to Log-In.
# Select a server you would like to use.
# Select the server -> channel you are going to create a webhook for the bot to use.
# Hit Authorize. This will put the bot into the server.
: Now that you have the Discord bot in your server, you will need to configure everything inside your server.
==== Configure Discord Bot ====
# Once the bot is in the server, type /help (This will give a step by step guide.
# If you do not have the text channel created, go ahead and create it.
# Make sure the bot has the correct privileges to send messages on the channel.
# Once the channel is set correctly, simply type /setup in the channel.
# If everything is set up correctly, you can send a quick message from your radio and see it in Discord.
=== Enable Repeater ===
: The repeater, as explained above is used to keep the in-world server synced with the Nexus servers.
: This checkbox will disable the noise that the repeater makes when the repeater fires.
=== Enable EMAS (Emergency Mutual Aid Station) ===
: EMAS is a global station that connects all radio networks using GridNet into one channel.
: This channel is separate from your network. Other networks can only post into EMAS and can only see what you post into EMAS. It is a good way to broadcast the need for assistance and get help from other departments.
: To enable it, simply check the box and all radios in your network will load the new network settings.
=== Show Channel Join ===
: This setting will enable Join Messages when a user joins a channel.
: If a user attaches a radio on the channel that you are currently on, you will see the message when they join.
=== Group Restrictions ===
: The group restrictions allows you to enable the network radios to only be used by a certain group.
: The turn this feature on, simply turn on the checkmark.
==== Adding A Group ====
: Once you have the group restrictions enabled, you can simply add the group by pressing ''Add Group'' button on the right.
: You will get a pop-up, simply place the Group's UUID (Example: 45fd6037-2cf2-0a42-cfc5-938303add5f2) inside the pop-up.
: Then it will add the group and all radios in the network will be reset.
==== Removing A Group ====
: To remove a group, simply go to the group you would like to remove and click the trash can to the right of the name.
=== Ban List ===
: If you have a person that has caused a large disturbance in your network and you would like to ban them, this feature works great.
: To ban someone, simple press the ''Ban User'' button and enter their name.
: Once you ban them, it will forcibly remove their radio and they will be banned from the network.

== Managers ==
: If you would like other users to be able to manage your system while you are away, simply add them as a manager.
: If you only want them to have certain permissions, that can easily be done right after you have registered them.
=== Adding A New Manager ===
: Adding a new manager is very easy. Follow these steps.
# Press the ''Add Manager'' button in the top.
# Type in their name in the Pop-Up.
: Once they're registered in your manager list, they will be sent a link to set up a password.
=== Changing Manager Permissions ===
: To modify a new Manager's permissions and restrict him to certain pages, simply open their box on the page.
: Inside there you will be able to find the pages they are able to access. If you would like to adjust that, select the pages you want and hit ''Update''.
=== Change Manager's Password ===
: If a manager is having difficulties logging in to the network, you can change their password by clicking the ''Change Password'' button.
: Once you have entered and confirmed the password, you will need to send them their new password.
=== Delete A Manager ===
: If you no longer need a manager on your network and would like to get rid of them. This can easily be done by deleting their account.
: To delete their account, simply find their account in the window, and select ''Delete'' from the buttons.
== Zone Editor ==
: The zone editor is where you edit all the channel and zones within your network.
: If you are starting a network for the first time and need help setting up your channels, please follow our [http://wiki.nexus-sl.net/wiki/index.php?title=GridNet_Radio_System/Getting_Started Getting Started] guide.
=== What Are Zones? ===
: Zones are like networks within your networks. Radios are configured to the zone and can communicate privately to the other radios configured in the network.
: However, they can not communicate to other radios in other zones unless they are using the global frequency.
: They also can only connect to other channels in that network only. If you have a police department and fire department zone with Tac-1 in PD and Eng-1 in FD. A radio from PD cannot send messages into Eng-1.
=== Creating A Zone ===
: To create a zone, simply click ''Add Zone'', then when pop-up shows, give it a name.
=== Deleting A Zone ===
: If you made a spelling error or just need to get rid of a zone that you had created. You can easily delete the channel.
: To delete the zone, simply touch the trash can in the Top-Right of the Zone Box.
=== Creating A Channel ===
: '''Brefore creating a channel, you must have a zone created.'''
: To create a channel, simply click the ''Create Channel'' button inside the Zone Box. Give the channel a name, and you have a channel.
=== Deleting A Channel ===
: If you are sick of the channels, you can easily delete them by clicking the trash can next to the channel's name inside the Zone Box for the channel that was created.
== Transmissions ==
: DISCLAIMER This is '''NOT''' used track public/local chat. It is only used to gather '''RADIO TRANSMISSIONS ONLY'''.
: This page will allow you to see and track the transmissions from your zones. This is a detailed way of seeing what's going on without being online.
: '''Want to see the whole network transmissions? Go to the Home Dashboard.'''
=== Viewing Transmissions ===
: In order you view the transmissions, you will first need to figure out which Zone you would like to view. After that, you can simply click the zone, and watch the transmissions flow in.
== Radio List ==
: The radio list allows you to see who is wearing a radio.
: If they are wearing a radio, you can see basic information about their radio. Such as, Region they are in, Call Sign, Channel, Zone, and Username.
: If needed, you can detach their radio. (Used if you ban them or make changes to the network.)
== Radio API ==
: The radio API is very complex, please view our API documentation here : [http://wiki.nexus-sl.net/wiki/index.php?title=Gridnet_Radio_System/API GridNet Developer API]
: There are examples, and more information pertaining to the API and how it works.
: Please remember this is an advanced API. You will need a good deal of scripting knowledge to make stuff work with it.
== Distribution Networks ==
: Your distribution networks are used to allow distribution of your radios without having to give a radio out to any of your Generals, Chiefs, or Admins.
: This will make one central location where you can track the distribution and make sure that certain servers only carry certain radios.
=== Setting Up A Distribution Server ===
: Setting up a distribution server will require space under the server's location. We highly recommend that you get a rack and leave it at the top of the rack if you intend on having multiple distribution servers.
: '''To set up your rack, follow these steps.'''
# Select ''Create Distribution Server'' from the buttons on top.
# Wait for the server to load in world and everything to set itself up. This will take less than 15 seconds.
# Once the page has automatically refreshed, you will see the server in-world and on the web interface.
# Go in-world and add the radios you would like sent from this server. '''DO NOT REMOVE WHAT'S ALREADY INSIDE IT (Scripts and Giver object)'''
# Rename your server in-world to something appropriate.
# Once you have added all your radios. Go back to the Web Interface and confirm they show all the contents of the server.
# On the web interface under the server, select ''Create Giver'' from the buttons. (This will create a giver in front of the server in-world.)
# Simply take the giver into your inventory.
: You are now ready to distribute radios from this server with ease.
=== How Does The Giver Work? ===
: The giver works very easily, simply rez it somewhere you would like to give out radios, set the group, and it will work.
: Whenever someone with the matching group touches it, they will be able to select an item from the distribution server's inventory.
: Once they have selected their item, the item will be sent to them.
=== Can I Send Stuff Other Than Radios? ===
: Yes, you can send whatever kind of items you want.
: The server is made to fit as much shit as you can fit inside it.
=== Deleting A Distribution Server ===
: If you no longer need a distribution server, '''DO NOT''' delete the server in-world.
: Delete the server from the web interface correctly. This will remove it from the stack of server and will free up the space. It will also remove it from the web interface.

GridNet Radio System/Getting Started

2018-09-28T00:57:24Z

Johnny:

[[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''' =
== '''Server Placement''' ==
:We highly suggest that you place the server in an area that meets the following criteria:
:*A location where the server can remain rezzed & running 100% of the time.
:*A location where you're permitted to rez objects. The server has a rezzing feature built-in that will automatically rez a distribution server underneath the main server when requested.
:**You should leave about 0.2100m of clearance underneath the server in case you do intend to setup a distribution server to prevent it from merging into another object.

== '''Setting up Your Server''' ==
#Rez the "Nexus GridNet Server v1.11". (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 your network has been created, you'll receive a dialog prompt to visit a webpage; this will lead you to your 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/Rebate Policy

2018-09-27T23:37:52Z

Shymus:

[[Gridnet Radio System|← Gridnet Radio System]]
{|align=right
|__TOC__
|}
= '''Rebate Policy''' =
: The rebate policy is a discount that is given to users who have purchased the "Nexus Gridwide Radio System".
== How To Get Rebate ==
: '''The rebate is sent automatically from our servers every 15 minutes after the purchase of the new system.''' These are the requirements for getting a rebate.
: When you purchase the GridNet Radio System, you will automatically be registered into our servers. When our in-world servers poll from our transaction servers, they will check to see if you qualify for a rebate.
== Qualifications ==
: If one of these applies, you qualify for the rebate.
* Purchase Nexus Radio System before Oct 1st, 2018.
* Had a friend purchase Nexus Radio System before Oct 1st, 2018.
* Participate in the GridNet Radio System Beta.
== F.A.Q. ==
=== My Friend Purchased The '''OLD''' System For Me, Do I Get Rebate? ===
: If you had a friend purchase the system for you in the past, you will get the rebate if you are the one to purchase the new system.

=== I Own the old system, My Friend Bought Me The '''NEW''' System, Where's My Money? ===
: If your friend had purchased you the new GridNet Radio System, they will receive the rebate.

=== How Much Money Is The Rebate? ===
: The rebate percentage is 20%. We feel that is more than generous for the amount of work that was put into the system. Please remember that the system was 100% remade. Nothing was carried over except one headset model.
=== I did not participate in the beta, do I get the rebate? ===
: As long as you purchased the old radio system, and purchase the new system, then you get the rebate.

Gridnet Radio System/API

2018-09-27T22:08:03Z

Shymus: /* Optional JSON data for API Call: */

[[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
* Transmit Message

=== 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>

= '''Transmit Message''' =
This function will transmit a message globally, zone, or channel

=== Required JSON data for API Call: ===
* "action" : "transmit_message"
* "transmit_level" : "GLOBAL", "ZONE", or "CHANNEL"
* "message" : The message to be sent.
* "network_id" : This will need to be obtained via ''network_details'' (See example below.)

=== Optional JSON data for API Call: ===
* "callsign": This will display who sent the message.
* "channel_id": If you are sending a message on a channel, then you need to supply the channel_id.
* "zone_id": If you are sending a zone message, you need to supply a zone_id.
* "use_discord": If you want the message to be sent into Discord, set the value to ''TRUE''

=== API Call Example: ===
<pre>
string json = llJsonSetValue("",["action"],"transmit_message");
json = llJsonSetValue(json,["message"],"Hello World!");
json = llJsonSetValue(json,["transmit_level"],"global");
json = llJsonSetValue(json,["network_id"],(string)network_id);
json = llJsonSetValue(json,["callsign"],"Shymus Roffo");
SendToServer(json);
</pre>

=== Example Response: ===
<pre>
{
"success" : TRUE
}
</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("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()) {
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>
=== Example Three - Transmit Message On Global ===
<pre>
string network_api_key = "INSERT-API-KEY-HERE";
key req_id;
integer network_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));
}

default {
state_entry() {
string json = llJsonSetValue("",["action"],"get_network_details");
SendToServer(json);
}
http_response(key i, integer s, list m, string b) {
if(i == req_id) {
network_id = (integer)llJsonGetValue(b,["network_id"]);
state transmit_on_touch;
}
}
}

state transmit_on_touch {
touch_start(integer n) {
if(llDetectedKey(0) == llGetOwner()) {
string json = llJsonSetValue("",["action"],"transmit_message");
json = llJsonSetValue(json,["message"],"Hello World!");
json = llJsonSetValue(json,["transmit_level"],"global");
json = llJsonSetValue(json,["network_id"],(string)network_id);
json = llJsonSetValue(json,["callsign"],"Shymus Roffo");
SendToServer(json);
}
}
http_response(key i, integer s, list m, string b) {
if(i == req_id) {
llOwnerSay(b);
}
}
}
</pre>

GridNet Radio System/Version History

2018-09-27T21:53:20Z

Shymus: /* Version 1.11.5 (5/6/2021) */

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

: Want to update your network without losing data from the last network?
: We give you a tool that will help with upgrading your servers, we do all the work for you.
= '''How updating works?''' =
: When a newer version comes out, we will give you an upgrade tool if there is an update for the network servers. This will prevent you from losing your network.
: If there is no update for the in-world servers, then you do not have to worry about updating.

= '''Version 1.11.5 (5/25/2021)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #990000;"><tr style="color:#990000;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;position:relative;left:-4%;">This update requires you to upgrade your radios. </td></tr></table>
* Fixes issues with Callsign not setting correctly.

= '''Version 1.11.4 (5/6/2021)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #990000;"><tr style="color:#990000;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;position:relative;left:-4%;">This update requires you to upgrade your radios. </td></tr></table>
* Fixed Stack Heap Collisions caused when messages are received. This repairs the memory leak that occurred when a message was received.

= '''Version 1.11.3 (5/5/2021)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #990000;"><tr style="color:#990000;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;position:relative;left:-4%;">This update requires you to upgrade your radios. </td></tr></table>
* Added 'GridNet API - Receiver' to allow for receiving messages through a script.
* Added 'GridNet API Receive Config Example' to show an example of API Receiver script.
* Fixed Stack Heap Collisions caused when send a long message. (Long messages will be sent in chunks and handled on a separate script.)
* Fixed Animation Permissions being overwritten when radio is configured.
* Fixed Radios from not being deleting when they were not attached or worn. (Radios were still showing as connected, but were not listed on the website.)

= '''Version 1.11.1 (10/06/2020)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #008BBA;"><tr style="color:#008BBA;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;">This update does not require you to upgrade your server. You can continue using the same server as before.</td></tr></table>
* Added ability to enable/disable sounds when a radio transmits or receives messages.
* Adjusted animation handling in scripts to not interfere with scripts when the script is attempting to request attach permissions.

= '''Version 1.11 (06/15/2020)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #990000;"><tr style="color:#990000;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;position:relative;left:-4%;">This update requires you to upgrade your server. </td></tr></table>
* Radio Repeaters are now on a seperate script to free up memory in main radio script.
* Adds access for support to set the servers to an existing network that no longer has an in-world server.
* Adds Emergency Mutual Aid Station. A public radio station that is a linked network to all those who have it enabled. Allows for talking to other networks that have the feature enabled.

= '''Version 1.0.5 (10/15/2018)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #008BBA;"><tr style="color:#008BBA;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;">This update does not require you to upgrade your server. You can continue using the same server as before.</td></tr></table>
* Updated the radios message handling to help prevent 'stack-heap collision' errors.
** NOTE: If really long messages are transmitted, you risk encountering this error at which point you will need to re-attach the radio to resume normal operations.

= '''Version 1.0.4 (10/06/2018)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #008BBA;"><tr style="color:#008BBA;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;">This update does not require you to upgrade your server. You can continue using the same server as before.</td></tr></table>
* Fixed Issue with Managers and API Keys. Fixed data only being submitted correctly for the first accordion.
* Fixed Issue on dashboard with API Calls and Transmission Count displaying a large amount of zeros when the number became >9999
* Fixed Issue with repeater still making noise when the noise is turned off.
* Fixed Issue with Forgot Password not catching any of the errors when the captcha is not ticked.

= '''Version 1.0.3 (10/04/2018)''' =
:<table border="0" cellpadding="0px" cellspacing="0" style="width:50%;border:dashed 2px #008BBA;"><tr style="color:#008BBA;"><td style="font-size:30px;position:relative;left:7px;top:-10px;"> ⚠</td><td style="font-weight:bold;">This update does not require you to upgrade your server. You can continue using the same server as before.</td></tr></table>
* Added Transmit Messages to the API.
* Added Redirection to Forgot Password.
* Added Support to Aileron for GridNet.
* Fixed Managers from being added to networks when they were a manager in another network.
* Fixed Name2Key Service from showing invalid keys on newer users.
* Fixed Detach Radios on the Radio Page.
* Fixed Detach Radios on the in-world radio and should no longer give a script error.
* Fixed issue with API giving server error on the Transmit_Message action.
* Fixed issue with radio networks not checking all groups on the access list and only checking for the first group on the list.
* Fixed Issue with API calls not incrementing when an API Call is made.

= '''Version 1.0.0 (10/01/2018)''' =
* Initial Release

Gridnet Radio System

2018-09-27T21:38:43Z

Johnny:

[[File:GridNetRadioSystem.png|center|350px]] 

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

<div style="color:#4D5A93;font-size:1.5em;">GridNet Radio System is one of the best radio systems used by every sim around the grid. One of the best ways to communicate.</div> 
<div style="font-size:1.3em;">Need help with your system? Look at the documentation below!</div>

{| border="0" cellpadding="35" cellspacing="0"
|[[File:Question_mark.png|link=GridNet Radio System/Getting Started|32px]]
[[GridNet Radio System/Getting Started|Getting Started]]
|[[File:Book.png|link=GridNet Radio System/Documentation|32px]]
[[GridNet Radio System/Documentation|Product Documentation]]
|[[File:Structure.png|link=Gridnet Radio System/API|32px]]
[[Gridnet Radio System/API|API]]
|-
|[[File:Calendar.png|link=GridNet Radio System/Version History|32px]]
[[GridNet Radio System/Version History|Version History]]
|[[File:MoneySymbol.png|link=GridNet Radio System/Rebate Policy|32px]]
[[GridNet Radio System/Rebate Policy|Rebate Policy ]]
|[[File:Bug.png|link=Bugs|32px]]
[[Bugs|Bugs ]]
|}

</div>

Nexus Light System/Documentation

2018-05-04T20:29:27Z

Johnny:

[[Nexus Light System|← Nexus Light System]]
{|align=right
|__TOC__
|}
= '''Nexus Light System 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 its 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 Light 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 here on our [http://tickets.nexus-sl.net/ Support Site].
 

= '''Getting Started''' =
Before using the Light System, it is reccomended that you have made sure you have all the parts required below.

== '''What's Inside?''' ==
Once you have purchased your package, you will have the basic items needed for your light system. 
These items include your switches and breakers. One thing to remember, there are multiple packs of lights, each with their own style.
* All The Lights
* Nexus Light System - Breaker Panel
* Nexus Light System - Large Breaker
* Nexus Light System - Timer Box
* Nexus Light System - Wall Switches

== '''Setting Up Your Light System''' ==
Ready to get your system setup? Lucky for you, the system is easy to set up and great to use.

=== '''Setting Up The Breakers''' ===
There are two types of breakers in your pack. The Large Breaker, or the Breaker Panel. 
The Breaker Panel is made up of 12 breakers into one box. Saves Prims and is slightly more efficient. 
The Large Breaker is one single breaker on a metal box with a lever. Great for places that do not need multiple breakers. 
When using the breakers, if you do not configure a switch to the light, the breaker will act as the switch and the lights will turn on when powered.

* Rez Out Breaker Panel or Large Breaker
* Go into the Inventory and select '_config'.
* Set the BreakerID to a name or number. (We'll use 'Home' as an example)
* Set the access. Owner, Group, or Everyone.

Bam, leave your breaker sitting there and you're done.

=== '''Setting Up The Wall Switches''' ===
This step is completely optional. You could still have lights without the walls switches. 
The light switch will allow you to have up to four switches on one panel.
* Rez The Wall Switches onto the ground.
* Open '_config' in Switches Inventory.
* Enter your BreakerID. ('Home')
* Enter Your SwitchIDs. (We'll use 'LivingRoom'. Leave blank to keep switch invisible.)
* Set The Access. (Owner, Group, or Anyone)
* Save and place onto the wall.

=== '''Setting Up The Light''' ===
Once you have all the items set up, you are free to position your lights and set up the lights. 
It is reccomended before you shift-drag the lights, that you set up the notecard first. This will save you a lot of time when setting up your lights.

* Rez the light.
* Open '_config' in light's inventory.
* Set the BreakerID to match your breaker box. (Home)
* Set the SwitchID to match your switch. (LivingRoom)
* Position the light and finish.

=== '''Setting Up The Timer Box''' ===
The Timer Box is used for turning the lights on at certain times on the day(SLT). 
Along with specific times, there is also a DAY/NIGHT feature. 
If you are using street lights, or outdoor lights. This feature is great to turn your lights on in the nighttime. 
This box, acts as a switch. When entering the SwitchID. IT will need to match on the lights.
* Rez The Timer Box.
* Open '_config' in timer's inventory.
* Set the BreakerID.
* Set the SwitchID.
* Set the Timer's Mode.
''If using TIMER Mode.''
* Set TurnOnTime and TurnOffTime. (Uses SLT time.)

= '''How To Create Your Own Lights''' =
Creating your own lights is a breeze! Simply create your light object and insert the following items into the contents:
A.) _light   
B.) _light-cnf   
C.) _config   
D.) Light Configurer
Can't find items A-C? You can acquire these items by rezzing a light that was included in your Nexus Light System pack; edit the contents of the light and drag the items to your inventory.

== '''Step One - Light Appearance''' ==
To start, you will want to edit the light parameters/values as the light would appear in an on-state. To do this, right-click the object and open the 'edit'/build window and navigate to the Texture tab and edit the following parameters for each face of the object that is considered a light:
*Glow
*Fullbright

Then navigate to the Features tab and check-mark the "Light" box and edit the light values:
*Set the light color
*Set light image/texture (optional)
*Set "Intensity" value
*Set "Radius" value
*Set "Falloff" value
*Set "FOV" value (optional)
*Set "Focus" value (optional)
*Set "Ambiance" value (optional)

== '''Step Two - Applying Light Configuration''' ==
The "Light Configurer" script should be in the contents of your light before continuing.

Once you're satisfied with the appearance of your lights, left-click your object and select "Proceed" from the menu. You will then be prompted to select the faces of your object that are considered lights. Selected faces will appear in floating text above the object - if you select the wrong face, simply select it again to undo the selection. If you closed the dialog menu by accident, type '/88 menu' and it will re-appear.

Once the face(s) have been selected and you're ready to continue, select "Finalize" and your light configuration will be generated and displayed in main chat, which will look similar to this:
<pre>{"color":{"blue":0.000,"green":0.000,"red":1.000},"faces":0,"falloff":0.750000,"fullbright":1,"glow":0.101961,"intensity":1.000000,"radius":10.000000}</pre>

Copy & paste the configuration that was generated into the "_light-cnf" notecard and save.

== '''Step Three - Configure Your Light to a Switch/Breaker''' ==
Open the "_config" notecard and edit the values to assign the light to a breaker and switch that you've setup previously:
*BreakerID
*SwitchID

Save the notecard when finished.

== '''Your Light is Ready!''' ==
Your light should now be functional!

= '''Credits''' =
A lot of people helped make lights. Here are some of the people!
* Scripting: Shymus Roffo and Johnny Nexen.
* Modeling & Texture: Shymus Roffo, Kira Alena, and Johnny Nexen.
* Testing & Ideas: Yurii Velinov and Antaeus.

Nexus Light System/Version History

2018-05-04T20:25:50Z

Shymus: Created page with "← Nexus Light System {|align=right |__TOC__ |} = '''How to get updates''' = : When a newer version comes out, our s..."

[[Nexus Light System|← Nexus Light 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.

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

Nexus Light System

2018-05-04T20:25:03Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Light System is perfect for any sim that n..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Light System is perfect for any sim that needs lighting in Houses, Streets, Offices, and Industrial parks. With the easiest way to configure and multiple features, it is one of the best systems on the market.</div> 
<div style="font-size:1.3em;">Need help with your Light System? Look at the documentation below!</div>

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

</div>

RolePay Water Meter Expansion

2017-12-06T01:42:19Z

Johnny: Created page with "← Rolepay Money System Expansion Packs {|align=right |__TOC__ |} = '''Using Expansion Packs''' = I..."

Nexus Meth Manufacturing/Documentation

2017-09-10T12:49:04Z

Shymus:

[[Nexus Meth Manufacturing|← Nexus Meth Manufacturing]]
{|align=right
|__TOC__
|}
= '''Nexus Meth Lab 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 its 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 Meth 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 here on our [http://tickets.nexus-sl.net/ Support Site].
 

= '''Getting Started''' =
Before using the Nexus Meth System, please be aware that it is rather complicated to get the hang of. 
Please make sure to read all documentation so you are understanding of how to make the Meth! 

== '''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 Meth Tool HUD (This is a transferable tool that is used to make the meth)
* Nexus Foldable Table (Used to put shit on...)
* Nexus Standing Heater (This is your oven to cook the Meth on trays)
* Nexus Meth Filter & Funnel (Filters out the liquids)
* Nexus Pill Processor (Used to grind up certain ingredients)
* Nexus Orbital Shaker (Shakes the conical flasks)
* Nexus Chemical Storage Shelf (Stores all the chemicals)
* Nexus Trash Barrel (Gets rid of all your trash)
* Nexus Meth Trailer House (A wonderful gift from a friend to you for your wonderful cooking needs)

== '''Setting Up Your Meth Lab''' ==
Obviously, you will need everything set up before you start cooking your meth. 
These items are required for your meth lab.
* Standing Heater
* Filter & Funnel
* Pill Processor
* Orbital Shaker
* Chemical Storage Shelf
 
Once you have those items placed out, go ahead and move on towards your next steps. 

== '''Making Pseudoephedrine''' ==
Before you start, don't forget to set up your HUD! Wear the HUD and attach the items for your hands. 
'''Psuedoephedrine''' is one of the main ingredients in meth. It takes a little preparation. You will need to get it from Pill form, down to powder. 
# Grab ''Pseudoephedrine Hydrochloride Pills'' from the Chemical Storage Shelf.
# Place the ''Pseudoephedrine Hydrochloride Pills'' into the Pill Processor.
# Repeat those steps 10 times until Processor is full, then press the power button.
# Touch the Processor to pick it up.
# Select the ''Conical Flask'' under tools, then merge together.
# Grab ''Methanol'' from the Chemical Shelf and mix with Pseudoephedrine.
# Place Conical Flask onto the Orbital Shaker and allow for drugs to mix.
# Once Orbital Shaker is finished, grab the conical flask and run it through the ''Filter & Funnel''.
# Once Filtered, retrieve the filter then place all the Pseudoephedrine onto a Metal Tray(Tool).
# Place Metal Tray into the ''Standing Heater'' and allow to dry for about 2 minutes.
 
That's how you set up your Pseudoephedrine! Now you can make as many trays as you want and allow them to sit. The difficult part is now finished.

== '''Mixing The Rest''' ==
So far you have the worst chemical out of the way, not it's time to mix everything together into one batch. 
This will make one brick per tray. 
# Grab a Beaker(Tools) and add Iodine(Chemical Shelf) to it.
# Add Red Phosphorous(Chemical Shelf) to the same Beaker(Tools).
# Add Hydrochloric Acid(Chemical Shelf) to the same Beaker(Tools). (If you didn't notice, your beaker will switch hands. This will allow for you to pick up the metal tray.)
# Grab the Metal Tray with Pseudoephedrine from the Standing Heater and Mix into the Beaker. (Pseudoephedrine needs to be Dry)
# Transfer Beaker Contents into a Conical Flask(Tools)
# Place Conical Flask onto an Orbital Shaker for 3 minutes.
# Once Finished, add Sodium Hypochlorite to the same Conical Flask.
# Place Conical Flask back onto the Orbital Shaker for 3 minutes.
# Once Shaker is finished, grab the Conical Flask and pour the contents onto a Metal Tray.
# Place the Metal Tray into the Standing Heart for 2 minutes.
# Once 2 minutes pass, take the Metal Tray out and go to the Pill Processor.
# Touch the Pill Processor to add the contents of the tray.
# Once it is finished grinding, pick up the Pill Processor.
# Place the contents from the Pill Processor to Plastic Wrap(Tools).
# Remove the Pill Processor and poof! You have successfully made a brick of meth.

= '''Frequently Asked Questions''' =
A lot of questions that we seem to get quite a bit are listed here. 

'''What is the trash can for?''' 
Whenever you throw a chemical away or use it, the chemical will be thrown onto the ground. The trash can will collect that garbage if it is placed.
 
'''Why is nothing working in the standing heater?''' 
The Standing Heater will only cook the product on the trays if the door is closed. Everything cooks in 2 minutes. If it hasn't been sitting in there for that long, it will not cook. Once it is removed and placed back inside, then the tray's timer will be reset. 
'''Why won't my lab blow up?''' 
The causes for a Meth Lab explosion are due to stupidity. Most of the time it is from a cook smoking around a propane or improper ventilation of the building. Once that happens, they start smoking and Poof. Fire everywhere...

= '''Distribution''' =
All the drugs are transferable! That means you can sell them, give them away, or maybe consume them yourself. 
When consuming the drugs, you will need to attach the baggie and touch it. 
After you smoke the drugs inside, it will no longer be able to be used! 
Good luck on your major drug creation/manufacturing/growing/dealing/usage!

= '''Disclaimer''' =
This system is not 100% accurate, it is not intended to be used as a guide to producing real world methamphetamine. Doing so can cause harm to self or others. We do not support the use of illegal substance in the real world. If you use this as a guide for real world production, we will not be responsible for any harm you inflict upon yourself. We warned you.

Nexus Meth Manufacturing/Version History

2017-09-10T11:46:13Z

Shymus:

[[Nexus Meth Manufacturing|← Nexus Meth Manufacturing]]
{|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.

= '''Version 1.0.02''' =
* Fixed Pill Processor (Fixed Pills Color not being red.)
* Fixed Pill Processor (Was only able to be filled once.)
* Fixed Meth Baggies (Not registering in Drug Test Database)

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

Nexus Meth Manufacturing

2017-09-10T11:45:01Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Meth Systemis Second Life's first meth man..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Meth Systemis Second Life's first meth manufacturing system that allows for 100% craftable meth. You can easily create your product to get the best meth for distribution and consumption.</div> 
<div style="font-size:1.3em;">Need help with your Meth System? Look at the documentation below!</div>

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

</div>

Nexus Phone Entry/Documentation

2017-03-27T07:18:00Z

Shymus: /* Setting Up Gate */

[[Nexus Phone Entry|← Nexus Phone Entry System]]
{|align=right
|__TOC__
|}
= '''Nexus Phone Entry System 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 its 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 Phone Entry 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 here on our [http://tickets.nexus-sl.net/ Support Site].

= '''Who Is The System For?''' =
: This system is made for gated houses or gated communities.
: Houses and Communities that use this system are able to regulate and create access to their homeowners easily by configuring the directories.

= '''Getting Started''' =
: This guide will help you get the basic set up ready for your community gates.

== To Setup ==
# First Rez out 'Nexus Entry Gate' and 'Nexus Telephone Entry Keypad'
# Right Click -> Edit 'Nexus Telephone Entry Keypad', Go to Contents and 'CONFIGURATION' notecard.
# Under '[SETTINGS]', you will need to change the 'CommunityName' to whatever you want to name your community. (Does not change functionality.
# Under '[SETTINGS]', you need to set a 'GateID', this GateID will need to be used for the Gate to be opened. (Take note of what you use).
: We will change the directory later.

== Setting Up Gate ==
# Right Click -> Edit 'Nexus Entry Gate', go to Contents and 'CONFIGURATION' notecard.
# Set 'GateID' to match the GateID of your 'Nexus Telephone Entry Keypad' GateID.
# If you want to reverse the direction of rotation, Set 'Reverse=TRUE'
: If you are looking to set up double gates, simply rez two gates next to each other and reverse one. Match their GateIDs and you will be golden.
: If using the sliding gate variant, you will need to set a speed in the gate.

== Setting Up Your Keypad Directory ==
: When using the system, you have the option to add key codes without adding a name to the directory, if a name is added to the directory, then they will be able to be called from this keypad to the assigned phone.
# Right Click -> Edit 'Nexus Telephone Entry Keypad', Go to Contents and 'CONFIGURATION' notecard.
# Under '[DIRECTORY]' Enter the label of the person who you would like to add into the directory.
# Example, "S. Roffo", then assign them a key code.
# To add their keycode, follow their name with the code separated by an = sign.
# Example, "S. Roffo=1234".
: This will add "S. Roffo" into the directory and anyone can use his pin of "1234".

== Setting Up Phones ==
: The phones are used to open the gate and receive phone calls from the keypad.
# Rez out 'Nexus Gate Access Phone'.
# Right Click -> Edit, go to the description.
# Enter "S. Roffo". This will allow someone to be able to select "S. Roffo" off your keypad and dial the phone.
# Touch the phone and add the person who will own the phone, Enter their Username not Display Name.
: Once a user is added to the phone, they are now able to access the phone and open the gate.
: To open the gate, simply touch the phone and select "Open Gate".

== Setting Up Sensors ==
: The sensors are optional add-ons for the gate that will allow the gate to open or close based on the position of the vehicle.
=== When are these useful? ===
# For an exit Gate. (Open Mode)
# Close the gate once a vehicle enters the gate (Close Mode)
# House Entry & Exit (BOTH Mode)
=== Configuring ===
# Rez out 'Nexus Gate Sensor'.
# Right Click -> Edit Linked Parts.
# Position both sensors at the side of each road where you want them to sense cars.
# Right Click -> Edit -> Contents -> "CONFIGURATION" notecard.
# Set the Mode you would like the sensor work in. "OPEN" will open the gate when a car is sensed, and so on.

= '''Emergency Access''' =
: If you have a 100% gated community and no one is able to get access except for the people who live there and their houses catch on fire, it will be very difficult for Emergency Services to get access.
: You will need to set up a Key Box for use with the keypad.

== Setting Up Key Storage Box ==
# Rez Out 'Nexus Access Key Storage'
# Touch it and give it a name.
# Take a copy to your inventory, then position it in your Police, Fire or EMS station.
# Set to the proper emergency service group.
# Have your members touch and take keys.
: When using this, once it is configured you are able to place unlimited copies of it.
: People who have the same group as the key are able to take keys.
:
: If you feel that someone has should no longer be on the key list, you can reset the box and remove everyone from the box. Then they will need to touch and take keys again.

== Setting Up Emergency Access Box ==
: This will be the device that the fire department uses to access the gate.
# Rez Out 'Nexus Emergency Access Box' next to the "Access Key Storage".
# Touch it to configure.
# Take it to your inventory and then rez out copies next to your keypads.
: The group that it is set too will not matter, as long as they have access to an "Access Key Storage" box, they will be able to get keys for this device.
: When a person uses this device to open the gate, the gate will open and remain locked open until used again.

Nexus Phone Entry/Version History

2017-03-27T07:02:42Z

Shymus:

[[Nexus Phone Entry|← Nexus Phone Entry 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.
= '''Version 10/19/2023''' =
* Fixed issue with 'Nexus Gate Access Phone' clearing the access list on the phone after calls were received.
* Fixed issue with all gates, physics were set to convex hull when they were supposed to be prim.

= '''Version 9/1/2023 ''' =
* Fixed issue with 'Nexus Telephone Entry Keypad' not correctly interpreting the sensor's messages.
* Fixed issue with all sliding gates. Fixed so they don't slide one direction.

= '''Version 7/20/2023 ''' =
* Fixed issue with 'Nexus Telephone Entry Keypad' not correctly interpreting messages
* Fixed issue with 'Nexus Gate Access Phone' not allowing for the GateID to be set

= '''Version 4/18/2022 ''' =
* Fixed sensor issues not communicating correctly with certain characters in the configuration notecard.
* Added sliding variants.
* Added MoreThanPixels double steel gate.

= '''Version 3/14/2022 ''' =
* Fixed issue with the gate sensor closing the gates when the emergency lock is open.

= '''Version 1.0.2''' =
* Added llName2Key as a fallback for current Name2Key service.

= '''Version 1.0.1''' =
* Added GateID to Sensors

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

Nexus Phone Entry

2017-03-27T07:01:43Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Phone Entry System is the Grid's number on..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Phone Entry System is the Grid's number one gate system used for gated communities.</div> 
<div style="font-size:1.3em;">Need help with your Phone Entry System? Look at the documentation below!</div>

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

</div>

Nexus Burglar Alarm/Version History

2017-02-27T04:49:49Z

Johnny:

[[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.

= '''Version 2.0.1 [2024-03-02]''' =
{{Information|This update consists of minor changes. If you have an existing [2023-10-13] system already in place, you can simply replace your Home Panel(s) with the updated version. There is no need to replace all the components.}}
* Added an "Alarm Delay" option to the Home Panel; this prevents the alarm system from triggering immediately, allowing those with panel access to have enough time to disarm the system.

= '''Version 2.0.0 [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

2017-02-24T22:55:11Z

Johnny:

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

This documentation is intended for version: v2.0.0 or greater - Reference version history [[Nexus Burglar Alarm/Version History]]. If you have an outdated 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>
## ALARM DELAY
##* Input the amount of <code style="color:#E38A2B">seconds</code> you would like to delay the alarm for when a non-whitelisted user is detected. This delay setting allows for users with panel access to disarm the system before the alarm sounds. For example: <pre>ALARM DELAY = 20</pre>
## ALARM DELAY VOLUME
##* Input the volume level for the delayed alarm sound, you can set the range between <code style="color:#E38A2B">0.0 - 1.0</code>; where 0.0 = off and 1.0 = max volume. For example: <pre>ALARM DELAY VOLUME = 0.1</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 Alarms

2017-02-24T21:54:18Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Burglar Alarm System is the Grid's number..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Burglar Alarm System is the Grid's number one police information technology.</div> 
<div style="font-size:1.3em;">Need help with your Burglar Alarm System? Look at the documentation below!</div>

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

</div>

RolePay Time Clock Expansion

2017-02-14T06:55:21Z

Johnny: Added "clocked_in_count" API action

[[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.mtp.onl/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.mtp.onl/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.mtp.onl/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.mtp.onl/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>

== '''Mass Payout''' ==
This function will payout all users that are eligible for a payout.

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

=== HTTP API Call ===
<pre>http://rolepay.timeclock.mtp.onl/api/action/payout_everyone/api_key/{API_KEY} GET</pre>

=== Example Response ===
<pre>
{
"success": [{"paid":"johnny nexen"}]
}
</pre>

== '''Payout User''' ==
This function will payout the specified user.

=== Information required for API call ===
* action (payout_user)
* api_key
* user_uuid (The user you're wanting to pay out)

=== HTTP API Call ===
<pre>http://rolepay.timeclock.mtp.onl/api/action/payout_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>

=== Example Response ===
<pre>
{
"success":"johnny nexen was successfully paid $27."
}
</pre>

== '''Clocked-in Count''' ==
This function will fetch the number of users currently clocked-in.

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

=== HTTP API Call ===
<pre>http://rolepay.timeclock.mtp.onl/api/action/clocked_in_count/api_key/{API_KEY} GET</pre>

=== Example Response ===
<pre>
{
"success":"There are currently 6 users clocked-in.", "total":"6"
}
</pre>

= '''Changelog''' =

** UPGRADE INSTRUCTIONS **
If you already have a Timeclock 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 timeclock. (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 timeclock. Once set, left-click the timeclock and it should automatically connect to your network.

* Version: 1.4:
* Fixed: An issue preventing Dashboard access.

* Version: 1.3:
* New: Moved to new server

* Version: 1.2:
* 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.

Aileron Dispatch System/Dispatcher

2016-12-09T05:51:10Z

Shymus:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Dispatcher Module allows for dispatchers and emergency responders to actively respond to phone calls within their network. This will allow for them to make 911 calls without having to use a group chat. 911 calls can be made from Cell Phones or Call boxes.

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Setting Up Your Dispatch System''' ==
To set up your dispatch system, you will need to first configure it for your network. Simply do this by rezzing it next to your Aileron server, then touching the Cell Tower.
Once that has been completed, you can then take it into your inventory and rez at the regions you would like to receive calls in for your network.
'''When you remove a tower from your region, someone else will be able to place a tower and then it will go to their network and not yours.'''

== '''Dispatch Desk''' ==
In order to use the system, you will need the dispatch desk. This will allow for Phone Calls to be received.
With this device, you will need to have it rezzed out and configured next to your server.

=== How To Add Dispatchers ===
Luckily, you don't have to add dispatchers. Anyone who is in the same group as the desk can answer a phone call. So if they are in a fire departement group and the desk is set for the fire department; they can answer calls.

=== Receiving Calls ===
When someone makes a 911 call, the phone calls go into your network cell tower, then are sent to every dispatch desk that's configured to your network.
If you have a cell tower in region "Mayfield", but your call center is in a different region, you will still receive all the calls from that sim.

=== Answering Calls ===
Once someone has made a 911 call from either the Emergency Box or Cell phone, the lights on the desks will start flashing red.
''''Any desk configured to your network will flash red.'''' Once the call is answered, the flashing on all the desks and the desk that answered the call will have a green light.

Once the light is green, you will now be connected to the caller and will be able to talk to them on the channel.

== '''Emergency Call Box''' ==
The Emergency Call Box is able to be placed on the ground and can be used to make calls into the dispatch center.
Once a dispatcher picks up the phone, then the call can be initiated.

== '''Emergency Cell Phone''' ==
The Emergency Cell Phone is an item that can be given out to anyone to allow them to make 911 calls without having to use the emergency call box.

=== Making a 911 Call ===
To make a 911 call, simply wear the HUD and select "Dial 911".
If there is no cell tower in your region, then you will not be able to get service and the cell phone will not connect to a dispatch desk.

Nexus Weed Growing/Version History

2016-09-18T19:17:24Z

Shymus:

[[Nexus Weed Growing|← Nexus Weed Growing]]
{|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 redelivery from the terminals in any of the stores.

: Looking for the 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.

= '''Version 1.2''' =
* Fixed issue with the plant being stuck in an endless loop waiting for the dirt patch to collect water.
* Fixed issue with dirt plant not properly syncing with the plant after it's planted.
* Added ''Soil Moisture Probe'' that will show the output of dirt's statistics. (If it has light, if it has water, and how much water)
* Added red water valve to the barrel. (Click to force sprinkler's to turn on for one cycle.)
* Changed color of weed plant to make it darker.

= '''Version 1.1.01''' =
* Fixed issue with dirt patch not working with the new plant and killing the plant every time.

= '''Version 1.1''' =
* Added Aluminum Foil Tarp Walls. Used for decoration.
* Updated Weed Plant model. Made to look better and have lower Land Impact.

= '''Version 1.0.9''' =
* Fixed issue with Trowel not removing plant after it is harvested.
* Added Long Light.

= '''Version 1.0.8''' =
* Changed Plant, now able to be by TPF or HD fires.
* Fixed Irrigation Barrel Event Scheduling. This fixes the draining issues.
* Changed Irrigation Barrel. Can no longer place a water pump within 10 meters.

= '''Version 1.0.5''' =
* Fixed Irrigation Barrel draining extremely fast. (Apparently Not...)

= '''Version 1.0.4''' =
* Fixed Irrigation Barrel not linking. (Corrected the permissions.)
* Fixed Irrigation Barrel doing nothing after water level went to 0.
* Changed Irrigation Barrel's water level from 500 to 1000. This will allow you to fill it once in a plant's life cycle.
* Added Water Pump. This will help users who have no linden water.

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

Nexus Weed Growing/Documentation

2016-09-06T23:16:02Z

Shymus:

[[Nexus Weed Growing|← Nexus Weed Growing]]
{|align=right
|__TOC__
|}
= '''Nexus Weed Growing 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 Weed Growing, 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 grow weed, you will need to take a few steps in growing your weed. 
It is a very complex system that will take time, it does not grow within an hour. Plants take at least 8 hours to grow. 
== '''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 Irrigation Water Barrel (This is used to water your plants and place sprinklers.)
* Nexus Irrigation Pipes (This is used lay the pipes for the Irrigation Barrel.)
* Nexus LED Light (This is used to give your plants the light they need to grow.)
* Nexus Cannabis Seed Patch (Where you plant your seeds.)
* Nexus Cannabis Seeds (Your seeds....)
* Nexus Cannabis Scissors (Used to harvest the plants once they have grown.)
* Nexus Cannabis Trowel (Used to dig up dead plants.)
* Nexus Water Can (Allows you to get water from LL Water and put it into the barrel.)
* Nexus Soil Moisture Probe. (Will show you the statistics of the plant's soil.)

== '''Setting Up Water Irrigation''' ==
Now that you know what everything is used for and what it does, you will need to understand how to set up your water for your plants. This will allow the plants to grow. 
* Rez out Irrigation Water Barrel and position it where you're growing.
* Wear the Irrigation Pipes, and allow the HUD to attach.
* Once the HUD is attached, select your Pipe Type and start laying pipes.

The Pipe HUD is a very simple tool that will allow you to place pipes without having to rez anything. 
All the work is done for you in a simple matter. All the positioning and rotations.

* After you have placed your pipes, select ''Finish Building''.
* When you select ''Finish Building'', it will ask you to link everything. This will reduce the amount of prims used up by the Irrigation System.

Now that you have set up your pipes, it is recommended that you get your Water Can and start filling up your barrel.

You now have a wonderful Irrigation System ready to use with your plants.

'''Are your sprinklers not turning on? Touch the red valve on the barrel's pipe. This will turn them on.'''

== '''Setting Up Plant Patches''' ==
Browse your inventory and look for your ''Seed Patch''. 
The seed patch is where your plant will be growing from. Setting it up is extremely simple.

* Rez out Seed Patch and position around a water sprinkler.
* Attach the ''Cannabis Seeds''. Touch the patch.
* Your little seedling will now be growing from the patch. Partially.
* To complete the growth process, you need to position an LED Light above the plant.

Your plants should now be growing. Now just time to wait about 8 hours for them to grow.

== '''Probing Your Plants''' ==
If you are unsure if your plants are growing or getting light/water, then you can check with the moisture probe.

To use the moisture probe, simply attach the moisture probe and touch the dirt patch.

Using the moisture probe will tell you three things.
# If the plant has light.
# If the plant has water. (Moisture Level above 0%)
# How much percentage of moisture is in the dirt.

== '''Harvesting Your Plants''' ==
Have the patience for them to finally grow? Now time for the rewards!

* Attach your ''Cannabis Scissors'' and allow the ''Harvest HUD'' to attach.
* Find a plant and touch it.
* If you have your ''Harvest HUD'' attached, you will notice the number update at the top. This is how much drugs you are carrying.

Once you are done harvesting your drugs, you will be able to get either a baggie or a brick.
1 Brick = 10 Baggies.
1 Baggie = 1 Joint.

'''If you choose to get a brick when harvesting, you will need to rez it and click it to get the baggies from it.'''

== '''Removing Plants''' ==
If your plant has died or you just harvested it, you are able to use the trowel to remove the plants.

* Attach ''Trowel''
* Click the plant to remove. (Cannot be undone)
* Poof, out goes the plant.

'''To remove, you click the plant and not the patch of soil.'''

== '''Distribution''' ==
All the drugs are transferable! That means you can sell them, give them away, or maybe consume them yourself. 
When consuming the drugs, you will need to attach the baggie and touch it. 
After you smoke the drugs inside, it will no longer be able to be used! 
Good luck on your major drug growing/dealing/usage!

Nexus Weed Growing

2016-09-06T23:07:07Z

Shymus: Created page with "<div class="center" style="width:auto; margin-left:auto; margin-right:auto;"> <div style="color:#4D5A93;font-size:1.5em;">The Nexus Weed Growing is Second Life's first weed g..."

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

<div style="color:#4D5A93;font-size:1.5em;">The Nexus Weed Growing is Second Life's first weed growing system that allows for 100% growable plants and weed. You can manage your plants to get Marijuana for distribution and consumption.</div> 
<div style="font-size:1.3em;">Need help with your Weed Growing? Look at the documentation below!</div>

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

</div>

Aileron Dispatch System/Vehicle Database

2016-08-20T04:15:34Z

Shymus:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Vehicle Database module is for registering vehicles of all types and displays warnings if citations have been linked to a vehicle, as well as any added notes for future use.

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Aileron License Plate Press''' ==
The License Plate Press is used to receive the commands from the "Vehicle Database" program used on the Aileron Interface.
Once it's configured, it can print plates for a vehicle owner.

=== Configuring License Plate Press ===
In order to use this device, you will need to configure it. It can be configured very easily.
# Rez "Aileron License Plate Press" next to your network server and Touch the License Plate Press.
# Your device is now configured!

=== How It Works ===
Once a plate has been printed and dispensed, the person that intends to upload the License Plate texture can Touch the plate that is visible on the press which will provide an Aileron web link where the newly "printed" plate texture can be downloaded and uploaded into Second Life. You can save the image by right-clicking on the image and saving to your desktop.

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.
This module will add the '''Vehicle Database''' to your list of programs.

== '''Vehicle Database''' ==

=== Register A Vehicle ===
To '''Register''' a vehicle you will need to open the Vehicle Database program, you will find the button to register a vehicle in the top left as normal. Once you have the View Vehicle window open, you can begin entering the details.

# Assign a plate number (Custom or randomly generated)
# Specify registration type
# Enter vehicle details (Year, Manufacture, Model, Color, and Type)
# Enter Vehicle Owner User Name
# Create Vehicle

=== Printing a Plate ===
The license plates allows for you to upload background textures from our [http://aileron.nexus-sl.net/r/license_plate/License-Plate-Template.zip License Plate Template]. In their are a few examples of how the cards will look, different styles and examples.
# Select the registered vehicle you wish to print a plate for
# Choose '''Stamp License Plate'''
# The License Plate will now be stamped and available to pick up at your License Plate Press!

=== Citations ===
Indicates the number of citations that reference a registered vehicle. If "CLEAR" is indicated, no citations have been recorded.

=== Notes ===
Additional notes can be attached to the vehicle registration by selecting the record and choosing '''Change Comment'''.

Aileron Dispatch System/Civilian Database

2016-08-20T03:36:57Z

Johnny:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Civilian Database module let's you manage citizens and give them licensing. You will be able to place civilians into the database and store important information about themselves. Along with that you will be able to issue identification cards that you create within the network. You will be able to create whatever kind of identification cards you can think of. From Concealed Carry, Drivers, and even Fishing Licenses. The world is your oyster.

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Aileron License Card Printer''' ==
The License Card Printer is used to print out the license cards for people. When a civilian is created on the network, you will be able to give them a license, select their license, then print it. '''To Setup the the printer, rez it next to your network server and touch it.''' Once you have configured it, take it into your inventory and place it where it will be needed, like your DMV building.

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.
This module will add the '''Civilian Database''' and '''License Cards''' to your list of programs.

== '''Civilian Database''' ==
The Civilian Database will allow you to store civilians in your network and keep track of their information. Along with their information is their Licenses.

=== Change Comment ===
This just allows you to change the comments on a civilian's record. It provides no benefit except for notes.

=== Creating Civilians ===
When a new person joins your city, you may be wanting them to register to be a civilian in your network. This will give them the choice to get new licenses and store their roleplay character information privately in your database. '''To create a civilian, simply go to the Civilian Database and hit "Add Civilian" in the top left'''. Once you have done this, you will need to enter their information and then they will show up in the database.

=== Deleting Civilians ===
To delete civilians, all you will need to do is find the civilian you are looking to delete in your database. Once done, click on their name and select "Delete Civilian" at the top.

=== Change Civilian's Picture ===
Changing the civilian's picture will allow for their image to show up on their driver's license when it is printed and given to them. '''Follow These Steps To Change A Civilian's Picture'''
# Find Your Civilian and Open Their Record.
# Select "Change Picture" at the top.
# Select Browse on the form and look for a picture to use. (.png format)
# Confirm their name matches the person in the picture.
# Hit the button, "Upload Civilian Image"
# Bam, they now have a new picture! It will display with pride on their licenses.

== '''License Cards''' ==
The license cards allows for you to upload background textures from our [http://aileron.nexus-sl.net/r/license_card/License-Card-Template.zip ID Card Template]. In their are a few examples of how the cards will look, different styles and examples.
=== Creating License Cards ===
Before you create a license card, you will need to create your background in Photoshop or GIMP. We provide a template for use with Photoshop that can be used. Please remember that this will not come out perfect the first time.
'''Follow Instructions To Create License'''
# It is assumed you already have your background made.
# Select your ID Card Background from your computer for upload. (.png format)
# Select colors you would like to use for your text. (View color reference: https://gyazo.com/c9fd389cd0688a8135bde59403996899)
# Give your License a name.
# Poof, you now have a license.
Now that you created your license card, make sure that you test print it. You may not be happy with the way that the card's lettering or some positioning is. You want to make sure that you have everything set before you start distributing it.

Aileron Dispatch System/Citations

2016-08-20T02:48:05Z

Johnny:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Citations module allows you to manage & oversee all citations that have been issued. Once officers have created a citation, they may obtain a signature and print the ticket to hand to the intended recipient which then prompts the user to view their ticket online.

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Aileron Ticket Writer''' ==
The Ticket Writer is used to receive the commands from the "Citations" program used on the Aileron Interface. Once citations have been created through the program, the Ticket Writer can accept hand signatures from the civilian that is being cited and can then print the final ticket which can be handed to the user. Once the ticket has been accepted by the user, they will be directed to an online Aileron page where they can view their ticket.

==== Using Ticket Writer ====
The Ticket Writer is an in-hand attachment & only functions through Aileron Interface actions: '''Print Citation''' and '''Get Signature'''.

'''Printing a Citation'''
# Select '''Print Citation''' from the Aileron Interface for the intended citation.
# The Ticket Writer will then being printing the ticket.
# Once printed and in-hand, the civilian being cited can obtain the ticket by clicking it; this will provide a link to an online Aileron page where the ticket can be viewed.

'''Obtaining a Signature'''
# Select '''Get Signature''' from the Aileron Interface for the intended citation.
# The ticket writer will then allow the civilian to submit a signature via textbox by clicking the Ticket Writer.
# Once a signature has been received, it will be applied to the citation.

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.
This module will add the '''Citation''' to your list of programs.

== '''Citations''' ==
The Citations program will allow you to create & oversee/manage citations.

=== Creating Citations ===
To '''Create''' a citation you will need to open the Citation program, you will find the button to create a citation in the top left as normal. Once you have the Create Citation window open, you will need to fill out each of the 5 forms. '''You will not be able to proceed until all forms have been completed'''.
'''Driver Information'''
# You must enter a '''registered''' User Name OR Operator License.
# A successful match will display "User Successfully Found!" and their information will be displayed. - if not found, ensure the name/license ID has been entered correctly '''and''' that the user is registered in the Civilian Database.
# '''Submit Information'''

'''Vehicle Information'''
# You must enter a registered vehicle license plate number and check.
# A successful match will display "Vehicle Plate Number Successfully Found!". - if not found, ensure the vehicle is registered in the Vehicle Database program.
# Submit Information

'''Citation Information'''
# Select Defendant Actions
# Choose or enter a vehicle type
# Enter location
# Submit Information

'''Citation Charges/Offenses'''
# Select the type of charge to issue
# Complete the form
# Add Charge

'''Driving Conditions'''
# Complete Form
# Submit Information

Once all forms have been completed, select '''Create Citation'''. The citation will then be listed under the 'Citations' section in the program.

=== Deleting Citations ===
To '''Delete''' a citation, you will need to open the Citation program. Select the citation you wish to delete and select "Delete Citation" and it will be removed.

=== Marking Citation As Paid ===
NOTE: Prior to marking a citation as paid, the citation must have a user signature on file. To '''Mark Paid''' on a citation, you will need to open the Citation program. Select the citation you wish to Mark Paid and select "Mark Paid".

=== Viewing a Citation ===
To view an existing citation, you will need to open the Citation program. Select the citation you wish to view and select "View Citation"; this will open the citation in a new window tab.

Aileron Dispatch System/Unit Manager

2016-08-20T00:27:47Z

Coolburnsy: /* Change Unit Status */

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Unit Manager module allows for you to keep track of vehicles and their whereabouts. When this is active a person can assign themselves to a unit. Once that is done, then they can post updates and other information about their vehicle. This will make it easier than using a radio as long as a dispatcher is in use. If a user is dispatched to a call, instead of the user making a radio call, they can press the button on the Unit HUD and it will update on the Interface.

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Unit HUD''' ==
 This item is used to give out and can be placed in your delivery server. It's uses are very simple. 
=== Assigning a Unit ===
Before you can use the HUD you will need to assign yourself a unit. This can be done by getting a unit number off the Aileron Website. A unit number can look like E-0001 or maybe U-1044. They must be entered exactly the same way when entering them into the HUD.

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.
This module will add the '''Unit Manager''' to your list of programs.

== '''Unit Manager''' ==
The unit manager will allow for you to keep track of your units activities and who is using the vehicle or assigned to that unit. If you are wanting to make a vehicle 'In-Service' or 'Out-Of-Service' all you need to do is select the vehicle and click and arrow button.
=== Creating & Deleting Units ===
To '''Create''' a unit you will need to open up the "Unit Manager" program, you will find the button to create a unit in the top left as normal. Once you have the "Create Unit" window open, you will need to select what type of Unit you would like to have put in, then enter a number from 1-9999. After this is complete, everything will show up on the "Unit Manager".
To Delete a unit, all you need to do is select the unit in the "Unit Manager" module. Then hit the "Delete Unit" button. Once this is done, it can not be undone. Only administrators can do this.

=== Change Unit Status ===
 Changing a unit's status will display next to the unit on the list when some text is entered. The status will also be changed when someone using the HUD presses one of the buttons. There are many statuses that programmed into the interface that will change colors. Those can be entered manually.
'''Programmed Statuses'''
# Transporting
# On-Scene
# Dispatched
# Patrolling
# En-route To Scene
# Clearing Scene

=== Dispatch To Incident ===
'''If You Have a Radio Network Configured and Incident Manager Module''' you will be able to use Dispatch To Incident. When Dispatching a unit to an incident, you will need to get the Incident's "Event Num" from the list of incidents. Once you have the number, simply enter it into the input box and it will send a message on the radio and the unit's status will be updated.

Aileron Dispatch System/Garage Manager

2016-08-19T23:54:24Z

Shymus:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Module Information''' =
All modules require the Base System. If it does not have the base system, you will not be able to use them. 

= '''What's This Module For?''' =
The Incident Manager module is used to track incidents and keep logs of the incident on your dashboard in real time. Just like real dispatchers, you are able to manage the priorities of the incident and determine how important a call can be. 

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Aileron Garage Control Panel''' ==
The Garage Control Panel is used to receive the commands from the "Garage Manager" program used on the Aileron Interface. Once it's configured, it can open any device including HD and Gentek doors. With the proper knowledge, it can open other items like Nexus Hydraulic Barriers or even your own scripted device.
=== Configuring Panel ===
In order to use this device, you will need to configure it. It can be configured very easily.
# Rez "Aileron Garage Control Panel" next to your network server and Touch the Panel.
# Go onto the Aileron Interface, navigate to Garage Manager and create a Garage Door.
# Once the door is created and has a label, find the access key and copy it.
# Touch the Control Panel and enter in your access key.
# Your device is now configured!

==== Using Gentek Doors ====
If you are using Gentek Doors, please follow this guide to open them using the Aileron Garage Manager. This will not explain how to set up the door. '''It is assumed that you already have the DoorID'''
'''Adding To Panel'''
# As example, we will use the ID "Garage". (Change in Garage Door's Notecard)
# Touch the Control Panel, and select "Add ID".
# Enter the ID you are using for the door. (Garage)
You are now able to operate the doors from the Aileron Interface. '''You can have as many DoorIDs at once.'''
'''Removing From Panel'''
# Once again, we will use the ID "Garage".
# Touch the Control Panel, and select "Remove ID".
# Enter the ID you are wanting to remove from the panel.
If the DoorID is enter exactly as entered, it will remove it.

==== Using HD Doors ====
If you are using HD Doors, please follow this guide to open them using the Aileron Garage Manager. This will not explain how to set up the door. '''It is assumed that you already have the DoorID and API Key'''
'''Adding To Panel'''
# As example, we will use the ID "Garage". (Change in Garage Door's Notecard)
# Touch the Control Panel, and select "Add ID".
# Enter the ID you are using for the door. (Garage)
# Touch the Control Panel, and select "API Channel".
# Enter the API channel matching the HD doors.
# Link the HD Door and the Control Panel to a prim. (Allows them to communicate.)
You are now able to operate the doors from the Aileron Interface. '''You can have as many DoorIDs at once. But they must have the same API Channel.'''
'''Removing From Panel'''
# Once again, we will use the ID "Garage".
# Touch the Control Panel, and select "Remove ID".
# Enter the ID you are wanting to remove from the panel.
# Unlink the Control Panel from the doors.
If the DoorID is enter exactly as entered, it will remove it.

==== Using Other Doors ====
If you are using other doors that you might have created, you can see what commands from the control look like by listening to the API Channel set in the control. It is recommended that you have a door ID for your doors, it will also send all the door IDs in the commands.
Looking for an example script? http://pastebin.com/cQZy7w9Z

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.
This module will add the '''Garage Manager''' to your list of programs.
== '''Garage Manager''' ==
The Garage Manager will allow for you to Open and Close your garage doors as long as they are configured to a panel. If the user access the Garage Manager is an administrator, they will be able to delete some of the labels. When a label is deleted, it will not delete the control panel in world.

Aileron Dispatch System/Incident Manager

2016-08-19T22:59:31Z

Coolburnsy: /* Updating Incidents */

Aileron Dispatch System/Documentation

2016-08-19T22:08:31Z

Shymus:

[[Aileron Dispatch System|← Aileron Dispatch System]]
{|align=right
|__TOC__
|}

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

= '''Item Information''' =
This will list all items that are included with the base system and their features. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Aileron Network Server''' ==
The Aileron Network Server is used as a contact from the Aileron Interface into Second Life. This does not include delivery items. When a user is created on the Interface, it will send them their credentials and information on how to log-in to the network that it is configured for. 
''' Item Uses '''
# Network Creation
# Interface <-> Second Life
# Distributes Log-In Information To Created Users.

== '''Aileron Delivery Server''' ==
The Aileron Delivery Server is used for a simple way to send items from your network interface to people who request the items from the "Get Equipment" program. Any type of item can be placed inside the server to be distributed.'''All items being sent out must be copy-able.'''
''' Item Uses '''
# Sends Out Items.

= '''Interface Information''' =
This will list all interface features that are included with the base system. It will also include the uses and descriptions of all the items. This will help you better in using the items to their greatest potential.

== '''Settings Tab''' ==
The settings tab allows you to access settings that will modify your account. You can change your password and Log-Out of the interface.

== '''Administration Tab''' ==
The administration tab on the top navigation bar is used to manage all things. A user must be assigned as an administrator before he will be able to access anything on the admin tab.
To make a person an administrator, you will need to go into the "Network Users" dashboard and select "Edit Users" button next to their name. Then just check the Administrator checkbox.

== '''Network Settings''' ==
This feature can be found under the navigation tab "Admin". It is used to change your network settings. At this time, it can only change the Radio and Pager Network Keys, along with the default permissions.
The default permissions are used to change what permissions and modules a person can access when their account is created. This does not include administrator modules. Modules will appear on there as they are purchased.

== '''City Settings''' ==
The City Settings allow you to change details about your city. This feature is mostly for the aesthetics and used by modules. This is not a huge requirement if you are not using modules such as the Civilian Database, Vehicle Database, and Citations. Those are examples that use items such as a ID Card printer that needs access to the city name for the card.

== '''Network Users''' ==
The Network Users allows for people to be registered on your network. If they are on there and have a password, they will be able to log into your network.
=== Adding Users ===
To add a user to your network, you can go into Network Users and select "Add User". Simply enter their Second Life Username. It is very case sensitive, if they don't have a last name; you will need to put "Resident" at the end. The User role is not required, it just lets you know what they do in your network.
Once you create their account, they will get messaged in-world with their new password and information to log-in to your network.
=== Removing Users ===
If you are wanting to remove someone from your network, you can access the interface, find their name, and hit "Delete User". After you confirm, their name will be removed.
=== Changing Passwords ===
This feature will allow for you to change a user's password. If someone in your network has forgotten their password, you can simply change it by clicking the button next to their name.
=== Edit Users ===
The Edit Users will allow you to change a few things with a user. If you spelled their name incorrectly, Need to change their role, or make them an administrator. This will easily allow for it.
=== Change Permissions ===
If you have purchase other modules and would people to access them or remove access, you can simply check the boxes on what modules you want them to access.

== '''Get Equipment''' ==
If you have set up your Network Delivery Server and have equipment inside it, this is how user's on your network will be able to request for those items from the server.

Aileron Dispatch System/Getting Started

2016-08-19T21:19:51Z

Lowtide:

[[Aileron Dispatch System|← Aileron Dispatch 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 set up a network successfully if all steps are done properly.
: If all instructions are read correctly, you will be able to navigate the interface and make good use of all the features included.
: Need help and don't understand the guide? Feel free to contact support with a ticket. [http://tickets.nexus-sl.net/ Nexus Ticket Support]

= '''Setting Up Your Network''' =
: Before you are to create your network, you will need to find a place to put your server and leave it. This server has to be running 100% of the time. If it is not running, people will not get their passwords to login to your network.
'''Follow These Steps to Create a Network'''
# Rez 'Aileron Network Server' out. ''(Remember it has to stay there for as long as you have the network.)''
# Select "Yes" when it asks you to create a network.
# Enter a name for your network. ''Save the name, you need it to login to Aileron.''
# Let it go through it's set-up process. It can take about a minute.
# Once it has completed the steps, look in chat for your password.
# Navigate to http://aileron.nexus-sl.net/ and use your credentials.
# There you go! Your network is set up!
: ''One of the first things you will want to do is '''change your password'''.''
: You will notice that there is nothing in your interface except for the "Get Equipment". That is because you will need to purchase modules.

= '''Setting Up Your Delivery Server''' =
: The delivery server will allow you to deliver items such as the Unit HUDs, Radios, Ticket Printers, Uniforms, and anything else that you will need for your network.
'''Follow These Step to Setup a Delivery Server'''
# Rez 'Aileron Delivery Server' near your network server.
# Touch the delivery server to configure it to your network.
# Once everything is configured, start placing items inside.
# After the items are inside, it will automatically upload them to Aileron.
# If a user uses the Get Equipment on Aileron, they will be able to request what is in the Delivery Server.

: If your network does not have anything listed on the interface, you can wait a bit then click the delivery server. That will sync it back up with the server.

= '''City Settings''' =
: Every city has a name! You will need to set up your city settings for most items to work.
# Go to your Aileron Interface.
# Go to the top bar that says "Admin" and look for "City Settings"
# Enter a City Name, County Name, State Name, Court House Address, and a City Type.
# Once all this information is set, just hit the button "Change City Settings".
: Congratulations, you're done! Moving on.

= '''Network Settings''' =
: Your network settings allow you to control your pager, radios, and permissions. Obviously more things will be added as life goes on.
: If you have a radio or pager network, you can add the keys from the network. They can be found in the descriptions of their servers.
: The permissions allows you to set what people are able to access when they are first registered into the network.

= '''What's Next?''' =
: Completed this guide and wondering what else you can do with the system? Have a look at the [[Aileron_Dispatch_System/Documentation|product documentation]]. You will be able to read about every feature about the dispatch system. These features do not include documentation for the modules after programs. You will need to consult the documentation separately. 
: We are glad you decided to choose us! Need to contact support, please file a ticket at our [http://tickets.nexus-sl.net/ support site].

Aileron Dispatch System/Version History

2016-08-19T20:56:51Z

Coolburnsy: /* How updating works? */

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

: Want to update your network without losing data from the last network?
: We give you a tool that will help with upgrading your servers, we do all the work for you.
= '''How updating works?''' =
: When a newer version comes out, we will give you a upgrade tool if there is an update for the network servers.

: If there is no update for the in-world servers, then you do not have to worry about updating.

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

Aileron Dispatch System

2016-08-19T20:06:31Z

Shymus:

[[File:Aileron-Logo.png|center|350px]] 

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

<div style="color:#BE202D;font-size:1.5em;">Aileron Dispatch System is a CAD used by First Responders looking to enhance their department productivity.</div> 
<div style="font-size:1.3em;">Need help with your system? Look at the documentation below!</div>
 


<table border="0" cellpadding="0" cellspacing="25" style="vertical-align:top;">
<tr>
<td>
<div style="color:#BE202D;font-size:2.0em;">Aileron Base System</div> 
<div style="font-size:1.3em;">Lists all instructions for the interface, this does not include any modules.</div>
{| border="0" cellpadding="35" cellspacing="0"
|[[File:Question_mark.png|link=Aileron Dispatch System/Getting Started|32px]]
[[Aileron Dispatch System/Getting Started|Getting Started]]
|[[File:Book.png|link=Aileron Dispatch System/Documentation|32px]]
[[Aileron Dispatch System/Documentation|Product Documentation]]
|[[File:Calendar.png|link=Aileron Dispatch System/Version History|32px]]
[[Aileron Dispatch System/Version History|Version History]]
|-
| 
|}
</td>
<td width="10%"> </td>
<td>
<div style="color:#BE202D;font-size:2.0em;">Aileron Modules</div> 
<div style="font-size:1.3em;">This will list all the documentation for every module.</div>

{| border="0" cellpadding="35" cellspacing="0"
|[[File:Civilian-Database.png|link=Aileron Dispatch System/Civilian Database|40px]]
[[Aileron Dispatch System/Civilian Database|Civilian Database]]
|[[File:Vehicle-Database.png|link=Aileron Dispatch System/Vehicle Database|40px]]
[[Aileron Dispatch System/Vehicle Database|Vehicle Database]]
|[[File:Citations.png|link=Aileron Dispatch System/Citations|40px]]
[[Aileron Dispatch System/Citations|Citations  ]]
|-
|[[File:Incident-Manager.png|link=Aileron Dispatch System/Incident Manager|40px]]
[[Aileron Dispatch System/Incident Manager|Incident Manager]]
|[[File:Garage-Manager.png|link=Aileron Dispatch System/Garage Manager|40px]]
[[Aileron Dispatch System/Garage Manager|Garage Manager]]
|[[File:Unit-Manager.png|link=Aileron Dispatch System/Unit Manager|40px]]
[[Aileron Dispatch System/Unit Manager|Unit Manager]]
|-
|[[File:Dispatcher.png|link=Aileron Dispatch System/Dispatcher|40px]]
[[Aileron Dispatch System/Dispatcher|Dispatcher]]
</td>
</tr>
</table>
</div>

RolePay Parking Meter Expansion

2016-08-16T18:57:49Z

Johnny: