Spy Antagonist Design Doc#603
Conversation
|
The concept sounds interesting, but there's one thing I don't like: using a single code for every PDA. It sounds... kind of weird? |
|
This would add a bit more logic to the process: Syndicate agents already spawn with hacked PDAs, whereas spies would have to obtain the malware themselves. |
|
|
I could envision a system where the spy gets visual cues on how to tamper correctly. Every PDA then can be made random for it's tamper per department, if we wanted to feature creep a little. Failed attempts to tamper could result in a broken PDA; where the PDA would occasionally spark, spit out it's pen, or spit out its ID card to prevent non-spies from obtaining Black Market access. Once a PDA is broken, even a correct series of inputs would still fail, forcing the player who did the wrong thing to go seek out a replacement. Just needs to then be complex enough not to brute-force. |
|
Thief but good |
I would look at it from this perspective. |
The idea's good, but if both a wire sequence and a code is required then what's the gameplay reason for needing both? I think it'd be better off with either-or, instead of having 2 codes but each is useless without the other. Also keep in mind that the wires adds an arbitrary requirement for the spy to use their main tool, meaning if you aren't in a role with access to a lathe, you'll have to run to cargo or get lucky in the tools room to get a multitool every time. |
Code with no wires: Someone could say the code over chat (especially since code can be learned just from someone else looking at the PDA), now everyone has a spy PDA Wires with no code: Spies have no way to lock the PDA without also destroying it. Could be desirable for a "This message will explode in 5 seconds" texture to the RP, but also inconvenient. Code and wires: Spy PDAs can be captured in functional state, but only if a spy is caught off guard, and capturing them only results in at most one PDA in the hands of the spy's enemies. Effect on TOTs - likely negligible, as the limiting factor to PDA uplink use is access to telecrystals, not just access to uplinks. I forget if tots have personalized codes, but if not, you could theoretically have sec opening uplinks using a code they busted off a different TOT? But I've never seen that happen, so I assume it's either not possible, or so powergamey that even the shittest of secs haven't dared try it. |
|
I had some thoughts on how the unlocking/locking could work: PDAs now have easily accessible wire terminals, which can be accessed with a barehanded, somewhat lengthy doafter. Wires are then revealed. PDAs are low voltage, and do not require insuls to tamper with. Certain wires interacted with in a particular order make contact with your spy network / black market trader for a limited time. Spies get visual cues on this workflow -- non-spies do not. Incorrect tampering by anyone, spy or not, would result in a broken PDA, the effect could be that the pen auto-ejects, or that the screen is cracked, whatever you like, but the intent would be that a tamper would be impossible, and that PDA would need to be replaced. |
They would use the same system as uplinks where inputting the code doesn't actually save the code as the ringtone so you can't just read it even if the spylinks open. You can only get the code from a spy telling you.
Alternatively, wire pulsing unlocks the PDA but locking is still just done through a "lock spylink" button in the PDA UI, same as locking an uplink. Only unlocking would need to be wire based. Also, this wouldn't touch anything about how tot uplinks work, they'd be exactly the same. The only extra feature, assuming it works the way it does in the current design doc, is that a PDA can have both an uplink and a spylink unlocked at the same time on it, which just displays both buttons. |
Whats the reason for making the PDA only unlocked for a limited time, and making spies have to be selective about when to open it? I can't think of any gameplay justification for subtley punishing a spy for checking their spylink. Besides that, I'm not against PDAs having an easy-remove wire cover so you can open it without unscrewing. When I heard the original wire idea I had it in my head that the PDA would have a power wire but the code would deliberately avoid ever selecting that wire for the code, so while you could still shock yourself as usual while messing with wires, you would never need insuls to input your code |
5 participants
Started working on this, and figured I should follow guidelines and write a doc before anything is set in stone. Meet the spy.
Never wrote a design doc before, hopefully this is acceptable. Please let me know if any parts need to be rewritten for conciseness because I feel like it gets a little wordy at parts. If you want to discuss on discord, ping me in a development channel @ livelaughlord, or just tell me why it sucks in github comments.
Initial implementation of the bounty board UI, just for examples sake. Subject to change of course.