Goonhub
PULL REQUEST DETAILS
[BALANCE][WIP][FEATURE][INPUT WANTED]
About the PR
This PR makes three main changes:
1. Using packets to hack lockers will require netpass_security, not netpass_heads
2. Netpass_security is currently only available on the captain's disk. Now it is also available on the disk security members start with, and it's transmitted by the armory authorization computer
3. The armory authorization computer can be hacked using netpass_heads. You'll need to be within 3 tiles to do so, and it will also make a stationwide announcement, so be ready to make a hasty retreat if you plan to do this!
I think the biggest issue with this patch is that the packet emitted by the armory auth computer doesn't really do anything other than provide the netpass_security. This could probably be tied into the receive_signal triggers for lockers and doors, but there's already an area check that would be kind of awkward to replicate, and also I'm lazy. If someone else wants to add more packet integration into this PR, I would welcome it, but I think it could be acceptable without it?
Why's this needed?
Currently, hacking lockers open is trivial. This will make it more difficult while still providing multiple methods of doing so.
Changelog
PULL REQUEST DETAILS
[BALANCE][WIP][FEATURE][INPUT WANTED]
About the PR
This PR makes three main changes:
1. Using packets to hack lockers will require netpass_security, not netpass_heads
2. Netpass_security is currently only available on the captain's disk. Now it is also available on the disk security members start with, and it's transmitted by the armory authorization computer
3. The armory authorization computer can be hacked using netpass_heads. You'll need to be within 3 tiles to do so, and it will also make a stationwide announcement, so be ready to make a hasty retreat if you plan to do this!
I think the biggest issue with this patch is that the packet emitted by the armory auth computer doesn't really do anything other than provide the netpass_security. This could probably be tied into the receive_signal triggers for lockers and doors, but there's already an area check that would be kind of awkward to replicate, and also I'm lazy. If someone else wants to add more packet integration into this PR, I would welcome it, but I think it could be acceptable without it?
Why's this needed?
Currently, hacking lockers open is trivial. This will make it more difficult while still providing multiple methods of doing so.
Changelog
Code:
(u)glassofmilk:
(*)Using packets to force open lockers now requires security authorization!PULL REQUEST DETAILS