The Judge can settle a meeting without winning the argument. That makes the quality of your evidence more important, not less. A loud accusation, a vent sighting and a picture from a ghost can all point toward a suspect while leaving a different explanation open.
This guide covers ordinary Classic Among Us with official roles. Its worked meetings are hypothetical. Use them to decide what to report, which question to ask and whether your case is strong enough to spend Overrule. Among Us 3D, VR and modded roles are outside this guide.
Know what your button commits you to
Overrule replaces the meeting's voting outcome with your choice. Target an Impostor and they are ejected; target someone innocent and you are ejected instead. You get one use per game, unlocked by completing the host's configured number of tasks. The decision resolves after voting ends, rather than immediately ending discussion when activated.
If several Judges activate it, the first takes priority; the others receive their use back for another meeting. You cannot rely on a second Judge to repair your choice in that same meeting.
Before building a case, open Match Info to establish which roles and settings this lobby uses. An enabled role is a possible explanation, not proof that a particular player received it.
Separate the event from the accusation
A useful report gives the group something to test. “Blue is bad” supplies a conclusion without the observation that produced it. “I saw Blue enter the vent after leaving Electrical” gives a location, action and sequence that another witness might support or contradict.
Use three parts when describing a suspicious event:
- Observation: what you directly saw, including the displayed player appearance and location.
- Limit: where your view began or ended. Say if you arrived after the action or lost sight of someone.
- Question: one detail that would distinguish the explanations still possible.
For example: “I entered after the body was already there. Yellow was leaving toward Storage. Did anyone see who entered before me?” That report does not clear Yellow, but it avoids turning proximity into a witnessed kill.
Keep reports from different witnesses separate. Three people repeating the reporter's accusation are still relying on one observation. A second player who independently saw the earlier entry supplies something new. Ask what each person actually saw before counting agreement as corroboration.
Case one: a vent sighting with Engineer enabled
Engineers can use vents. In a lobby with that role enabled, venting alone does not distinguish an Engineer from an Impostor. Equally, saying “I'm Engineer” does not establish that the speaker really has that role.
Suppose you see Blue vent, report it, and Blue claims Engineer. A poor next move is to use Overrule because Blue has admitted the action: the action was never the disputed part. The unresolved question is which role explains it.
Instead, ask Blue where they entered and what they saw before venting. Then ask a relevant witness for their own account without first supplying the answer you want them to repeat. A route contradiction can strengthen suspicion; a consistent story can leave the question unresolved. Neither outcome automatically verifies a role claim.
| What happens next | Practical decision |
|---|---|
| Blue gives only a role claim | Keep the vent observation on record, but do not treat the claim or the vent as a complete case. |
| A witness independently describes an incompatible sequence | Compare exactly where the accounts conflict before choosing a target. |
| Nobody saw the approach or exit | Acknowledge the missing evidence. Repeating the accusation cannot fill it. |
If Engineer is disabled, that particular innocent explanation is unavailable. Still describe precisely what you saw rather than upgrading a partial glimpse into a complete account. Lobby settings narrow the explanation; they cannot improve your line of sight retroactively.
Case two: the killer looked like Red
Shapeshifter can copy another living Crewmate's name, color and cosmetics. It appears as its original self in meetings. Whether a transformation leaves physical evidence is configurable, so an absent trace is not a universal way to rule out a disguise.
Imagine you report: “Red killed in Electrical.” Another player says they were with Red elsewhere. If Shapeshifter is enabled, those statements need not contradict each other. The first witness may have seen a Red-looking killer while the second saw the real Red.
The productive correction is: “The killer looked like Red. I didn't see them transform.” That preserves the important event without asserting an identity your observation did not establish.
Ask the second witness when their contact with Red began and ended. “We were together earlier” is weaker than an account covering the moment in question. Avoid inventing an exact simultaneous timeline if neither witness can anchor it.
There is another useful distinction: witnessing an uninterrupted transformation is different from finding someone near where a transformation may have happened. Describe the starting appearance, resulting appearance and any gap in visibility. Do not merge those into one confident story after losing sight of the character.
For the Judge, the decision is concrete: do not choose Red solely because the killer wore Red's appearance while the disguise explanation remains unresolved. Keep the kill report, investigate the competing account and look for evidence that identifies the player behind the appearance.
Case three: a ghost sends an ambiguous picture
Influencer is an official Ghost Crewmate role. It can send up to three images selected from a random offering to a living Crewmate, with limited refreshes. Those pictures can communicate an accusation, a warning or an attempt to clear someone. The developer explicitly warns that recipients may misinterpret them.
Suppose a picture reminds you of Green's outfit. One interpretation is “Green killed me.” Another is “trust Green.” A third is that you have associated the picture with the wrong feature entirely. The fact that a message arrived does not tell you which interpretation its sender intended.
Report the distinction honestly: “I received a picture that I think might refer to Green,” not “the ghost confirmed Green.” Then compare that interpretation with the observations already discussed. Does it explain a specific event, or are you attaching it to the suspect everyone already dislikes?
| Meeting situation | What to do with the hint |
|---|---|
| Nobody has observed anything relevant about Green | Treat it as a lead for a question, not a completed accusation. |
| A direct account already implicates someone else | Do not discard that account merely because your picture interpretation feels obvious. |
| Several people repeat your interpretation | Trace them back to the original message; this is not several independent confirmations. |
As an Influencer, favor an understandable message over one that needs a long chain of associations. Sending more pictures is useful only if they make the intended connection clearer. You still have tasks to complete; messaging is an additional contribution, not a replacement for them.
Decide what Overrule would actually change
Before activating it, finish this sentence: “The ordinary meeting is likely to do X, and I want to change that because I observed Y.” If Y is merely the loudest person's opinion, you have identified the weakness in your own case.
Consider three different meetings:
- The group is converging on the person your evidence also implicates. Explain your evidence and participate normally. An override that produces the same result adds little to this decision and spends an option you could retain.
- The group is targeting someone because of an ambiguous event, while your own uninterrupted observation implicates someone else. State that observation clearly first. This is the kind of disagreement where changing the result could matter, provided your observation actually distinguishes identity under the enabled roles.
- The group is undecided and your own evidence is also incomplete. An available ability does not manufacture a missing fact. Keep investigating through the discussion rather than treating the button as a requirement to choose immediately.
A player can give a convincing false account, and a truthful witness can describe an event badly. Your advantage comes from finding the specific point that can be checked, rather than judging the speaker's confidence.
When the ability is not available
If you have not met the task requirement, work toward the configured threshold between meetings while continuing to gather observations. Do not assume a task count remembered from another lobby applies here.
If you have already spent Overrule, your evidence still matters. Give the same clear account, identify unsupported leaps and use ordinary participation to help the group decide. The role's special action is limited; your ability to contribute to a meeting is not.
During a discussion, prioritize the most useful missing detail. Ask “Did you see the kill, or arrive afterward?” before requesting an entire round's movement history. Ask “Was that the appearance you saw, or did you see a transformation?” before arguing about who is lying. A short question that changes which explanation is possible is worth more than a long accusation repeated until the timer expires.
Latest comments
Log in to join the conversation
Log InNo comments yet. Be the first to share your thoughts!