Jump to content

(WIP) Devices / Security / Surveillance - Expansion Framework


-Vagrant-

Recommended Posts

A lot of stuff to add - so the full command list and item list is incomplete and a total works in progress, but wanted to let people chime in on this as I update it and clean it up. Let me know what you think!

Short description:
An expansion to the current device system in game that offers a wide variety of legal devices to be used and purchased by businesses and to be manufactured by approved businesses and organizations.

Detailed description:

This is an overhaul to the current device system in game that will add a series of objects, and provide customizable surveillance options to enhance security features for security based businesses, as well as offer some small security options for all businesses.

Commands to add:
 

/deployterminal <inventoryID> <serverID> <serverpassword>

This command checks three points of reference. It is asking for a relevant inventory ID object that will successfully allow the creation of a terminal (inventory item is called terminal, go figure)

It then searches the server array of active server objects in world for the unique ID. This is what links your terminal to your server you have placed in world. <server password> is the password that you created or have currently assigned to the server object. It checks the serverID (unique server identifier) for its password property and makes sure that the command you entered in here has the correct password. If the string for server password entered in this command does not match the string for serverPassword assigned to the Unique Server ID, then deploying the terminal will fail.... or, if its not much work, it will succeed, but linking to the server will fail.

 

This deploys a new persistent marker in world and can only be deployed if the prerequisite required item is found in the player's inventory. This marker represents a physical object, and thusly this marker can be seen by all players. It is recommended that this marker be placed by a relevant furniture object in a player's property (a PC, laptop, tablet, etc. Some type of user interface device that is capable of accessing a server/network.)

Terminal commands that can be used at the location of the terminal marker.

/tdevicelist <terminalID> <serverpassword> - Lists the device IDs linked to the attached server along with their description parameters. Calling this command runs a conditional check on whether the player is within 5 meters of the relevant terminal world object, if not - returns error:

You are not in range of this terminal.


Ex:

/tdevicelist 121 P@ssw0rd

case - password does not match password of the server that is linked to this terminal -
You entered the incorrect password and are unable to sign in to the terminal.

case - password matches the password of the linked server.

You have successfully logged in to the terminal.

The following devices are synced to the server:

Device Type: <camera> - Camera ID <ID: 423> - Device Description (created when player deploys device): Restaraunt Name - Lobby Entrance.
Device Type: <alarm> - Alarm ID <ID:13> - Device Description (created when player deploys device): Restaurant Name - Anti-Burglary Alarm
Device Type: <wire> - Wire ID <ID: 131> - Device Description: Brandon's Wire - Undercover
Device Type: < camera> - Camera ID <ID: 177> - Device Description: Restaurant Name - Alley Entrance

 

/deployserver <password> (The password section of this command can be anything you like within 16 characters. When you use the deployserver command, you are actually creating a password for the newly deployed server in tandem with creating the server object in world.)
 

This deploys a new persistent marker in world and acts as a 'large' container, or an array of linked device IDs. A device object, such as a bug, wire, or any of the new surveillance objects mentioned in this suggestion thread can now be linked to a single server or several servers. It extends the accessibility of these device's functions to any terminal or device that is connected to the server.

Each server object in game consists of the following properties:

ID: This is a unique SERVER ID, every in world server is provided the lowest ID available - these IDs become available if the server is destroyed. The relevant inventory object is required in order to place a server marker in world.
Linked: This is an array of terminal unique IDs that have been successfully linked to this server. Terminals can be unlinked from the server (Master) by entering the following command at any attached server terminal

/unlinkterminal <server ID> <terminal ID> <server Password>

Or, if in immediate proximity of the server (within 5 meters of the server marker) using the /resetserver command:

WARNING: ANYONE CAN USE THE RESET SERVER COMMAND! STORE YOUR SERVERS IN SECURE LOCATIONS WITH LIMITED ACCESS!

THE RESET SERVER COMMAND WILL DO THE FOLLOWING:
Unlink ALL TERMINALS and remove them from the TERMINALs array of the Server OBJECT, as well as Unlink ALL DEVICES and remove them from the Devices array of the Server Object. It essentially makes it so no terminals are now connected to the server and no devices are connected in the event that a server is hacked.


 

 

 

Items to add:

How would your suggestion improve the server?

Additional information:

Link to comment

Alright so, let me see if I've gotten this idea straight:

  1. Devices that currently exist are to be linked to a terminal.

How exactly is the terminal used? Are you meant to "see" the cameras and listen to the wires, et cetera?

 

Also, why would the marker be on the map for all players? Wouldn't this encourage people to metagame all locations? Shouldn't they be either visible only to the deploying player, or through the terminal?

Link to comment
  • Wuhtah locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...