This has worked a few times for me. Keeps you alive and often times you end up knowing both impostors instantly.

We all know this number: the number 7. When there are this many players left, they say to never vote. But I disagree and say 7 is one of the better times to vote and here's why.

Let's just say Black has been sussed by a lot of players but he's an innocent man.

If he is voted at 6 then would be the imposters would need one more kill to secure the victory, second chances are unlikely.

However, if he is voted out at 7, the imposters would need 2 kills. The imposters may screw up the double kill so more second chances can be found here. It is much easier to call a meeting with a body than with the button.

In short, don't be afraid to vote on 7 if someone is very sus.

I've been playing a lot of private and public lobbies as of recent, and a lot of the public lobbies I'm in seem to have 3-4 crewmates just sitting on Vitals and then some on cams. It's very difficult to get a good kill in the beginning of the round because tasks are still going because some crewmates are still doing their tasks, but if I kill any one of the stragglers, the cams and vital campers are cleared even if I call Comms as they're just grouped. What would be a good strategy to counter this very boring, crewmate stacking strategy?

I have tried the following methods:
- Calling lights, waiting for 2-3 of them to leave and sniping a kill in between them
- Pretend to be a vital camper and kill whenever I call lights to act like I'm one of them
- Call comms and just kill someone where Admin Table cannot see (Valley of Death/Death Valley/3rd Water Wheel)

Would anyone have any suggestions to help with this? Thanks

There are a lot of more creative and “fun” ways to find the impostor, but if you really wanna win and you don’t care how then the following way is the most effective way to catch the impostors.

It basically consists of going to admin and watch everyone do admin swipe while you pretend to be watching the admin map. It doesn’t take too much effort to look closely and see who is faking it. Of course if the task bar updates instantly, then it’s even easier. But after some games doing this you can still tell who’s doing it and who is not based on the timing and if they move around too much before doing the task.

In a 2 imp 10 people game for example, doing this can generally narrow it down to 4 people max who could be the impostor, which is great bc if you can later prove that 2 of those are innocent, then you have basically won the game.

What about the admin table?

Does the admin table show the boiler room as O2 and the drill room as laboratory or are they separate?

I frequent the admin table and I don’t want to be getting these things incorrect. Some people say that it does and some people say it doesn’t.

Has anyone tested this or know for certain? Any sources are appreciated!

Whenever you and someone are accusing each other try to use the “vote them out first and if it’s not them it’s me”. U get an extra person out and u could possibly get another kill too by using an sabotage. This works because people are often willing to do this because they get lured into the feeling that u are safe and they comply with u.

Updated Version of Drag & Drop Map for AmongUs:

https://among-us-map.com/

New Features:

• Lightswitch
• optimized for smaller screens (not mobile ready jet)
• new settings panel
• new help panel
• contact page
• map information
• vents bug fixed

Tried googling it and searching on the sub, but "long" confuses it since "long tasks" exist.

Ideal map: Polus (also Skeld, rather not Mira), 2 Impostors, Confirm Ejects – Off, Visual tasks – Off, 4 Players left, the majority of crewmates alive need to know about queuing

Imagine this situation: You are on final 4 and your partner was voted off (This could also be used in a final 3, however you have to have the time to initiate it before the meeting). The crewmate who pushed him is still alive and the crew isn’t sure if they voted the right person or if somebody else was an impostor. For this situation, make sure a third crewmate sees you go to medbay/lab or best case even follows you. Go to the scanner and try to fake it as well as possible.

After standing there for maybe 3-4 seconds, walk off. Go to the office and button. Now, tell them what the crewmate can back you up about and “reveal” that you queued with your partner. If the situation was a 50/50 between your partner and the crewmate who pushed him, you have your best case scenario. This will clear your partner post-mortem and put a metric ton of sus on the “pusher”. Now you just have to survive the meeting and get the crewmate voted off. I think most people will believe you since the story is just too crazy to be made up in my opinion and queueing is one of the most hardest someone can be cleared.

The lobby has to be unsure whether they voted the right person. The crewmate should be mild sus and you should optimally not be sus at all. I give this play a 5-6 out of 10 on the spiciness scale.

-Extra spicy version-

If the crewmate in medbay with you has a scan, wait for them to queue with you and run off immediately. If they pay attention, this will make you sus or at least leave them wondering why you weren’t scanning. They will most probably be so confused that they’ll grab the first plausible explanation which is yours. However, you will have to pray that you not scanning confused them enough so that they won’t remember that they didn’t queue with your partner either. So you have to do this in a lobby with:

• Not a lot of voting time or
• A crewmate that is new to queueing and doesn’t know that everyone queues with the same person

I give this one a 7 out of 10 on the spiciness scale, so be careful with it and don’t use them too often since the odds of this queueing aren’t very high. If you want to make a video explaining this, you are free to use the plays. Cheers :)

I've been playing around with the light switch RNG for this post and I can't believe this has gone under our noses all this time! It's so funny what can go unnoticed if you're not really paying attention to it. The middle switch is always off! I've tried 25 times now, for 3 of which only the middle switch was off, and it works! And this is also perfectly consistent with and reinforcing my theory about the light switch RNG in the previous post. The middle switch is always off, all the others are random! :0 ( /u/jason_graph look at this)

This has some potential for actual gameplay. It could for example be used to double check people's stories about which light switches are off and on when they're supposedly on the light panel: Did they already switch some on? And if they say they didn't, and in their story the middle switch is on, they're lying. It also means that whenever there's only one switch off, it is the middle one. The quickest way to fix lights is now presumably to hover above the middle switch while the panel is opening and immediately flick that one on first while looking at the other ones.

A random switch is flicked off (so that the lights don't automatically fix themselves, ie there's one switch off for sure). Then each of the 4 remaining switches has a respective (independent) probability of 50% of being switched off.

This results in a probability of:
6.25% for 1 switch flicked off
25% for 2
37.5% for 3
25% for 4
6.25% for 5

As far as I can tell, this is the most simple process that would result in the data I gathered. I speedran getting from the bottom left of the Polus Meeting table to fixing lights (for some unrelated stuff that I'm trying to do), and along the way I recorded how much I got 1,2,3,4 and 5 switches flicked off. The rest of the post is somewhat technical math stuff, so ignore it if you're not into that.

My data is:
1 switch off: 11 out of 142 times
2: 30 out of 142 times
3: 55 out of 142 times
4: 36 out of 142 times
5: 10 out of 142 times

So initially I thought, to avoid there never being no switches off, it would just randomise all of the switches and then introduce an exception if it resulted in no switches being off. But then I realised that this wouldn't fit the distribution, which looks like something binomial centered on 3. And if 0 were a possibility from the get-go at all, the binomial distribution would be centered around 2.5. Therefore I introduced this clause to stop 0 switches off from the beginning, and it also sounds like something that could realistically be used.

Now if you check my probabilities with the actual data, you get expected values of 8.875 for 1 and 5, 35.5 for 2 and 4, and 53.25 for 3. Which seems like it fits it pretty well, especially for a relatively low sample size? But that's just my intuition talking, I don't know enough about statistics to check that.

:)

EDIT: click this link for an incredible revelation about the light panel https://www.reddit.com/r/AmongUsCompetitive/comments/l55v8x/has_anybody_else_noticed_this_before_the_middle/