Spy

Mechanics

 * You will receive the amount of and/or  who visit certain people each night. The order is randomized.
 * You will not be able to see who the  and/or  visit if you are jailed.
 * You are able to "bug" a person each night, which reveals any direct actions against them, such as attacks, roleblocks, transportations, ect. Investigative actions are not shown, such as from a or.
 * will trigger the 's trap if they bug the trapped person. Bear this in mind when weighing the pros and cons of bugging.
 * If you are controlled, you will still receive the visits, but you will instead bug the controller's target.
 * Your bug sticks to the original player targeted. It is not swapped by a transportation once the bug has been placed.
 * The bug will fail if your target is jailed. You will know that your target was jailed.

Bugging Messages
When a uses their night ability to bug someone, they'll see messages from the following list for appropriate events:

Strategy

 * When the has a, you should try to figure out why the  is trying to keep the blackmailed person quiet. Maybe they blamed the , and you don't have to reveal yourself as a  to point out that someone is blackmailed since you can just say that the person is being quiet and ask them to vote for you if they are blackmailed. Then tell everyone what they said before they were blackmailed.
 * If a is lynched, you may know off the chance if a member of the / voted guilty, innocent, or abstained.
 * Always keep a detailed will, noting down every night's and  visits. While this is true for any role, the significance of a night's visits often aren't obvious until later in the game. It might be tempting to summarize it into a list of who has / hasn't been visited or a possible number of, but knowing the precise visits and what night they occurred on can be valuable for catching a  or , or for interpreting the wills of other players.

Revealing

 * If you are unable to gather a lot of information but still have some information to contribute, a good time to reveal yourself as a is when you know there are a lot of targets as lots of other roles at this point are a higher priority to kill than the . Otherwise, you should reveal yourself when you have some good information to contribute with, for example, if you know who one of the members of the / is.
 * You should try to counter an unlikely  claim, as they could be a . is a common claim for members of the  and  as it is easy to fake for them.

/ Visits

 * Make sure to keep track of who the and  visit at night, in most cases the visited target will not be a member of the /. You can use this information to narrow down who could be a member of the /. However, a / or a  can make a member of the  visit another (if this happens, members of the  will often point out that they were visited by the, which could give you a lot of information on who the  are.) A  could also be healing a member of the  so watch out for this. If an  remembers that they were a member of the /, they might be among the targets too.
 * If no targets are visited at all, it is very likely that the or  was in jail or role blocked. In modes where the number of  can vary significantly, such as All Any, it can also indicate that the  are all dead.
 * If a target is visited repeatedly but is not blackmailed or roleblocked, the might have a  or.
 * If none of the targets die, it is possible that one of the targets was attacked and either had a higher Defense value than said attacker's Attack value or was healed by a . This is especially true if a target was visited by multiple members of the (the second being a  or ).
 * Bear in mind, however, that a common mistake among novice is to make broad assumptions based on visitations, such as assuming one or more of the targets visited has a naturally high defense, or assuming that a  member visited a  based on the change in the number of visits.
 * Calling these out early on can be detrimental for two reasons: if they actually did visit a, the is less likely to be believed and may end up providing valuable distraction for the  or . On the other hand, if the target was innocent and merely protected, it would expose both that innocent player and their protector.
 * Furthermore, now that is easy for any  or  member to fake, these call outs can cast suspicion upon the  themself. This can be exacerbated if the  doesn't have a proper, or just calls out someone without giving the full story. This can result in a  or  killing the , dealing a huge blow to  in the process.
 * Keep track of who the visit at night and use the process of elimination to find who the members of the  are. Be aware, however, that  and  may make the  visit themselves.
 * You can distinguish between and  claims by checking to see if the people who were role-blocked were visited by the  on those nights.  cannot easily lie about their visits, since each one produces a message; but they can easily claim  if you're not there to catch them.
 * Your list of visits can be extremely effective in combination with a or, allowing you to narrow down possible  and  members even further:
 * If the or  didn't visit the 's target or whoever the 's target visited, then those visitors cannot be  or, respectively.
 * If the or  did visit that target, then it puts any visitors under suspicion. However, for the, remember that there may be other visitors you didn't see who could be the actual  or.
 * You can also use the pattern of visits to figure out the role of the Random member.
 * For example, if one person is visited two times, there is likely a or  in play. If they don't die, they may be healed or have a higher Defense value than the attacker's Attack value.
 * If one person is visited and not killed, then visited and killed, this may point to the presence of a . They would have investigated the person, shared their role, and then the or  would have decided to kill them. Keep this in mind especially if they are an important Town role, such as  or, or one that could have found out members of the , such as  or.
 * If one person is being visited repeatedly, this could indicate a, , or possibly a who is intent on disguising/framing/role blocking one person. If the victim is claiming role-blocked, it is most likely.
 * If someone is visited once by and did not die, they could be a,  or.

Bugging
(NOTE: this article needs a fix, there are conflicting reports in the article: some say that your target is switched by a transporter, some say that your bug stays on the original person, meaning you will see what truly happened to them(but, of course, they weren't targeted for, and what was meant to happen to the other target).
 * With the 'bug' ability, you can now know if someone is lying about what happened to them. You can also find out if someone is immune.
 * Generally speaking, you should bug people who you suspect will lie about or conceal what happened to them at night - in other words, potentially evil roles. There's usually little point in bugging a confirmed role, who will reveal what happened to them at night anyway.
 * However, one benefit to bugging is that you can use what you see to confirm yourself. For this reason, it's sometimes useful to choose targets the way a  would, and visit whoever you think is most likely to be visited and have an 'exciting' night in general; that will give you information you can later use to confirm that you're a.
 * Remember that some of the information you can gather with bugging is redundant with the information you get from your ability to see and  visits:
 * If someone is repeatedly acting blackmailed, you could theoretically use your bugging to confirm this; however, most of the time you will already know they're telling the truth due to the visits.
 * There are a few specific messages you can see that are much more important than others and worth actively looking for by targeting people who are likely to get them. These are:
 * The unique messages an, , or gets when killed by a  or (for the  only) a  they targeted; this will tell you with certainty whether the person they targeted was a  or not if they get killed by one. For this reason, it's worthwhile to focus on bugging anyone who claims those roles. Remember, if you're watching them and do not see the unique message when they die to a , that means their target was not a ; you will probably have to speak up to save them.
 * If you target a who gets role-blocked, you'll get a special message telling you that they attacked their role-blocker (which instantly outs them as an .) For this reason, it can be useful to watch possible.
 * If your target has night immunity, you'll get a message when they're attacked telling you that. For this reason, it's worth watching people you suspect of having night immunity.
 * Note that while you can make some deductions about immunity with by watching your and  visit reports on a night when they fail to kill, actually bugging a target lets you distinguish between bulletproof vests, healing, and persistent immunity.
 * If you watch an who cleans themselves, you'll get a message saying so. This is fairly rare and typically only happens in games with multiple, but it's a reason to watch potential  in any game that seems to have more than one.
 * The "Control Immunity" message is seen by . Remember that if you see it and the transportation message, an actual probably transported your target with themselves.
 * You can tell if the target was transported. This can be vital to preventing mislynches. Remember that if you see that message, it means that your target was changed by the, too; for instance, if you see that message and an immunity message, it means the 's other target is immune, not the person you intended to target.
 * If you manage to catch the message of: "Someone role blocked your target so they stayed at home." then it means your target is a, as this is a specific message. However, you will die due to visiting them, unless you are protected in any way.
 * The "role-block immunity" message is only seen by a few roles:, , , , , , , , and . If you see it, your target is one of the roles on that list. Of course, if it was , you will die.
 * While your bugging can be valuable, it is generally less powerful than your ability to see and  visits; additionally, it exposes you to getting killed by a, , , or (but not a ). For this reason, you might consider staying home when those roles are active, especially if you don't have any clear plan in terms of what you're checking for with your bugging.

Trivia

 * Prior to Version 2.0.0.6537, the  and the could read whispers. Now, only the  can read whispers.

Шпион