Repository navigation
Home
Player- and contributor-facing documentation for NeroSecurity, part of the Neroland ecosystem. Built on Neroland Core.
NeroSecurity lets you protect a base. A Security Hub controls an installation: who its owners and members are, which devices answer to it, and whether it is in lockdown. Doors, chests, keycards, laser grids, cameras, alarms and force fields all ask the hub's installation the same question: is this player allowed here? The server answers it every time, and any refusal wins.
Bases stay raidable. Anyone can break every device except the hub, force fields overload under fire, and nothing makes a door unbreakable. Owners are never locked out of their own base.
Status: version
0.5.0-beta.1, a beta. Some textures are still simple placeholders.
- Getting Started — hub, Linking Tool and your first door in five steps
- Access Levels — PUBLIC, MEMBER, OFFICER, OWNER, and how a decision is made
- Keycards — writing, copying, wiping and revoking cards
- Doors and Chests — security doors, blast doors, secure chests and automation
- Sensors and Alarms — laser grids, cameras, alarms, the monitor and the log
- Lockdown — sealing a whole installation, and alarm lockdowns
- Force Fields — emitters, power, overload and the raid-server preset
- NeroLink App and Notifications — the companion app and phone notifications
- Blocks and Screens — every block, item, recipe, tooltip and screen
-
Commands — every
/nerosecuritycommand -
Config — every setting in
config/nerosecurity.properties - Privacy — what a server can see about you, and how to export, opt out or be erased
- NeroEconomy integration — what changes when NeroEconomy is installed
- NeroQuests integration — the Access Granted quest chapter