Accepted Own-Team Disguise Card Changes

This suggestion has been accepted for future development.
Status
Not open for further replies.
What does this suggestion change/add/remove:
This is basically two separate suggestions about the own-team disguise card. I'd do them separately, but they'd be guaranteed to be rejected if I did that because one is pointless without the other and one would cause issues without the other.

First, when holding an own-team disguise card in your hand, it should appear and act like your disguise's regular access card would. E.g. if you had Engineer Timmy Malone's disguise, it would appear like a CL1 access card with their title/name on it. It would also work on keypads as if it were that access card.

Each own-team disguise card would individually have a whitelist of jobs that could "see through it", meaning those jobs would see it as the person's actual ID or would see it as the fake access card with an additional line that said their actual role (e.g. line one says "Engineer Timmy", line two says "Agent John Johnson"). This would be configurable, so e.g. all IA, ISD, etc. could see through an IA Agent's disguise, but only ISD, SC, etc. would be able to see through an ISD's disguise.

The second feature, which would prevent the issue introduced here of being able to e.g. take a CL4 disguise as an IA Agent and get CL4 access, is to also allow disguise cards to be configured to not be able to target specific jobs. E.g. an IA Agent shouldn't be able to disguise as an Ambassador, or a Site Advisor.

Has something similar been suggested before? If so, why is your suggestion different?:
Not that I could find.

Possible Positives of the suggestion (At least 2):
  • Allows IA and ISD to actually disguise and blend in properly without having to show site admin ID or undisguise every five minutes when ID checked. As it is, it's very difficult for either to actually blend in and do their jobs, as any time they're ID checked their only option is to out themselves.
    • Deep Covers can actually blend in better than they can, because they can just steal somebody's keycard and kill them. IA and ISD can't do that for obvious reasons.
  • Allows IA and ISD to use a keycard to open doors while in disguise and not out themselves/get questioned about having the wrong keycard.
  • The second part of the suggestion also prevents people from disguising as people they aren't meant to, which doesn't happen too often or too severely, but it is just an additional benefit.
  • EDIT: With the disguise role whitelisting, it will also prevent the common issue of accidentally taking the disguise of somebody else that is in disguise.
Possible Negatives of the suggestion:
  • Dev time
  • Can potentially cause confusion.
  • If somebody does something wrong in somebody's disguise, the original person is also more likely to e.g. get arrested by IA for it - though they often already do due to metagaming.
  • Somebody could more easily deliberately get somebody else in trouble, but they already mostly could by just having their name above their head.

Based on the Positives & Negatives, why should this suggestion be accepted:
It makes own-team disguises much more useful, as currently you get outed every time you get ID checked, which makes going undercover basically pointless.

This makes IA and ISD much more useful and allows them to do a lot more. With them being able to blend in much better, it would make them be able to do a lot more e.g. in investigations.

This is not the same as site admin ID (or the planned SWEP for that). This is in addition to that, and basically does the opposite - it allows you to pretend you are that role/person, rather than reveal that you're not.

If SL wants a role to be configured to be able to disguise but not also have the fake ID, they could with this just configure that role's card to be seen through by all other roles.

All of this would also only apply to own-team disguise card, for obvious reasons.
 
Last edited:
Some parts of this suggestion are good however it's quite problematic, under little to no circumstances should ISD ever be able to see through IA disguises, furthermore allowing the disguise card to function as the disguisees ID is not needed, IA have interrogation tools for a reason, they can just kidnap their target, take ID and then amnesticate, also the disguise card should be able to disguise as anyone as taking CL4 disguises and such is against in character policy for IA, however there's no real ooc issue with people taking unauthorised disguises and sometimes we must take these disguises for the purposes of blending in im certain scenarios
 
bro suggestions have been up for 2 minutes
+Support
update: I just remembered the ID Card (Spy) (Same Team) can also take enemy disguises. How would it work with e.g. ISD taking a CI disguise? Would they also have their keycard? You could say "oh well they could just strip them" but what if this is on somewhere like surface?
 
update: I just remembered the ID Card (Spy) (Same Team) can also take enemy disguises. How would it work with e.g. ISD taking a CI disguise? Would they also have their keycard? You could say "oh well they could just strip them" but what if this is on somewhere like surface?
That's a bug and as far as I know is intended to be fixed at some point.
 
Then the fact that this suggestion includes preventing it from targeting set jobs could be used to stop that.
If its set job, wouldn't that prevent all people with disguise cards from taking a specific disguise?
(E.G. A1 can't take a CI disguise anymore, but a CI can no longer take a CI disguise)
Or would it just be independent (E.G. A1 can't take a CI disguise, but CI can still take a CI disguise)
 
If its set job, wouldn't that prevent all people with disguise cards from taking a specific disguise?
(E.G. A1 can't take a CI disguise anymore, but a CI can no longer take a CI disguise)
Or would it just be independent (E.G. A1 can't take a CI disguise, but CI can still take a CI disguise)
It'd be configurable, so different jobs' cards could target different people, etc. Also, for ISD taking CI disguise and the like, they'd just have both this updated own-team card and the enemy one to allow the card disguise and the like without allowing it for enemy disguises.
 
  • Like
Reactions: Niox
Some parts of this suggestion are good however it's quite problematic, under little to no circumstances should ISD ever be able to see through IA disguises, furthermore allowing the disguise card to function as the disguisees ID is not needed, IA have interrogation tools for a reason, they can just kidnap their target, take ID and then amnesticate, also the disguise card should be able to disguise as anyone as taking CL4 disguises and such is against in character policy for IA, however there's no real ooc issue with people taking unauthorised disguises and sometimes we must take these disguises for the purposes of blending in im certain scenarios
Hm. For interro tooling and amnestication, that's just a hassle for you and the person you're grabbing it off when you as IA or ISD should have the tools already on you to make your disguise work within Foundation. You also are very likely to be caught and I think are probably liable to get shot or something for it.

For ISD being able to see through it, this was just an example, it'd be configurable by SL, so if they should they can see through it, if not then they can't.

For allowing higher clearance disguises, I'm unsure where OOC policy lands on this. Possibly, either:
  • The updated disguise card can also be configured to only be able to copy certain ID cards, ideally job-based.
  • The updated version would be a separate SWEP. You can get the basic own-team that just does disguise and can target anyone, and a separate one that does the card and the like but is limited on who it can target.
 
Status
Not open for further replies.