`5kernel`.`2panic` I got bored one day, and dreamt of an alternate BINMAT-like loc defense system. I'm posting it here so that others can comment on it; I don't actually expect anything to come of this. `1--------------------------------------------------------------------------------------------------------` `TTHE GOAL:` `1--------------------------------------------------------------------------------------------------------` When installed on your system, it will act as a last-resort measure, much as BINMAT does now. It will serve as a method of active defense, while also providing real stakes for both users involved. `1--------------------------------------------------------------------------------------------------------` `THOW WILL IT WORK?` `1--------------------------------------------------------------------------------------------------------` The experience is different for the attacking player (`Vattacker`) and the defending player (`Ndefender`). The minigame is asymmetrical, taking inspiration from BINMAT. `1Starting the minigame:` When a loc is breached with `5kernel`.`2panic` installed, the `Ndefender` has 15s to respond to the threat. They will recieve a popup with the text `D:::LOCKDOWN INITIATED - <USER>:::`, as a warning. (A new `Dlockdown` parameter in `5sys`.`2status` will allow cron-bots to respond to the threat.) During this lockdown, the `Ndefender` is unable to: - Transfer GC from the breached user to other users. - Transfer upgrades from the breached user to other users. - `5kernel`.`2hardline` on any user account. This is to prevent the 15s being used as an escape mechanism. Please note that GC and upgrades can be transfered to a user under `Dlockdown`. During this time, the `Ndefender` can either accept or deny this minigame. If they deny the minigame, or 15s pass, their system is breached as normal. On the other hand, the attacker, when breaching a loc with `5kernel`.`2panic` installed, will see: `D:::` `5kernel`.`2panic` `Dinstalled on this system. :::` Please pass the argument { `Nconfirm`: `Vtrue` } to trigger defender lockdown sequence. If they pass { `Nconfirm`: `Vtrue` }, their hardline counter will count down 15s. If the `Ndefender` accepts the minigame, the `5kernel`.`2panic` minigame starts. `1The game loop:` - Neither account, once `5kernel`.`2panic` has initalised, can xfer GC or upgrades out of their user. - This lasts for the duration of the minigame. - The `Ndefender` creates a chain of "shell" NPC accounts. - Shell NPCs do not pop, and will remain until the end of the minigame. - These NPC accounts cost the `Ndefender` GC to create. - The amount of GC depends on the amount and tier of the locks put on the shell. - A shell NPC *must* have a lock. - The `Ndefender` wins if their loc rotates. - The `Vattacker` is trying to breach these shell accounts faster than the `Ndefender` can make them. - Their hardline has no connection limit; this continues until `Ndefender` lock rotation. - Once they breach an NPC, they can find the next in its transaction/access logs. - As the shells require GC to form, the `Vattacker` can use `5sys`.`2xfer_gc_from` to gain that GC. - The `Vattacker` loses if: - Their hardline ends, either through a disconnect or running out of time. - They take longer than 60s to breach a shell NPC. - The `Vattacker` wins if they outpace the `Ndefender`'s shells. - Both users will connect to other user accounts owned by the same user. - These connections will show up with logs in their respective access logs, with locs. - This serves as a prize to the winner; the longer the game goes, the more infra might be unveiled. - The winner breaches the other user automatically, whether attacking or defending. - This is so that the defender can win back the GC they lost. With, hopefully, interest. - Furthermore, the loser is subject to the following restrictions on their account: - They cannot `5kernel`.`2panic` on any user account until their next lock rotation. - They cannot hardline on any user account until their next lock rotation. - They cannot xfer GC or upgrades to accounts not owned by the same user until the lock rotation. `1Necessary limitations:` - You cannot initialise `5kernel`.`2panic` against one of your own users. - Other users cannot hack either the defender or attacker. `1--------------------------------------------------------------------------------------------------------` `TCONCLUSION` `1--------------------------------------------------------------------------------------------------------` Thanks for reading this far! :P If you have any feedback, please share. I don't really know how it could spread, besides the BINMAT win-and-you-get-it-now system. (yes, I see l0ckbox, l0ckjaw, and l0g_writer being concerns ^^)