BloxNote How to Find Kira: Evidence Channels and Decision Guide

Watch who gets close to other players without a task reason — the notebook only works once Kira has stolen a target's ID at close range, so proximity is the most reliable tell, especially when it happens repeatedly around players who later die. Leave a task early? Note it. Consistently skipping votes? Note it. Report those facts in meetings by name and let the lobby test them against other accounts. Treat every unexplained close approach as a potential ID steal in progress; backing away costs nothing, and a player who keeps shadowing you without a task nearby should be reported by name in the next meeting. Before accusing anyone, ask what a cautious Kira would have done in the same situation — genuine Kira behaviour tends to be cautious and unremarkable rather than dramatic, which filters out most false positives. Also count notebook holders, not just Kira: because the Death Note can be passed to the Kira Follower, ejecting the obvious suspect does not necessarily remove the threat.

Using tasks and the task meter as evidence

The shared task meter is simultaneously a win condition, an information source, and a bluffing surface, and reading which players are genuinely contributing is a core skill. The killing team can stand at task markers and appear to work, but this does not help their win condition — the purpose is purely social, faking progress to build an alibi. That is why task claims matter less than what the meter shows: watch whether the shared meter actually rises when someone says they finished a task, because a bluffer's story rarely matches the bar. In meetings, cross-reference the meter's jump between meetings with each alibi — if a suspect's stated landmark is close to the kill but the meter barely moved, their task defense collapses. Community strategy guides also treat task avoidance as an accusation chain: in one writeup, task avoidance combined with a body-trail ping becomes a workable accusation chain in the second half of the round, though this is player inference, not a confirmed mechanic. Visible task completion works the other way — a player who has been visibly completing tasks all round is dramatically harder to eject than one who has been drifting around the map, even when the drifter is innocent. Note that only two task mini-games (upload and wires) are confirmed by players; Kira can also fake tasks to look aligned with the Investigator side, so task behavior is inference, not proof.

How L tools can contribute to identifying Kira

L is the investigation side's dedicated information role, but the described toolkit is currently inconsistent across player reports, so treat the specific ability names as unconfirmed and check your in-game role card. The reported versions include:

• Forensic Sweep, Deduction Board, and Wiretap — a short-radius scan that tags players recently near Death Note activity with a visible marker, a persistent log of names, alibis, and vote records that transfers to an L successor when L dies, and a passive that logs who voted for whom during meetings (useful for catching a Kira Follower voting in lockstep with Kira). The recommended play is to cross-reference sweep tags with the Wiretap log, scanning early, logging often, and broadcasting findings publicly to lock in a primary suspect.
• A single camera command card — shows a fixed room for a few seconds, revealing movement but not names. A player standing still near the notebook glow is a much stronger signal than a player simply walking through a room.
• A proximity ID check — L walks near players in sequence, triggers an ID check on each, and uses the overlapping results to narrow the suspect pool.
• An Investigator proximity scanner — lights up when close to Kira, with a two-person accusation plus matching scan data as the minimum threshold for a confident vote.

Across all versions, the shared principles hold: L's information should be released in small testable pieces, used to confirm (not just filter) suspects, and converted into votes at meetings.

Reading notebook writes, the kill feed, and body evidence

Because the Death Note has a distinctive glow and writing requires standing still, an observed write is the strongest single signal available. Field checklist for investigators during a public write:

If three of five line up, there is enough to call a public meeting; if only one or two line up, keep patrolling and let the next write add a data point. A meeting-ready call from community strategy guides names the player and a timestamped sighting — for example, "Saw Player C holding the notebook at 3:42 near the south stairs." The kill feed entry names only the victim, never the holder, so the holder must be inferred from location and timing — record the name, move away, and reconvene. Body evidence is hard data: walk to the body immediately, note the exact position and time, and cross-reference with who else was nearby, who defended who during the accusation phase, and who deflected with a weak alibi. Two cautions: the most common investigation-side loss is a premature accusation — calling a meeting on a pass animation and getting the wrong player voted out; let the write resolve, then use the kill feed. And Shinigami Eyes (roughly 15% of the task meter per community data, not official documentation) can let the holder write names they never saw in line of sight, so kills that seem impossible to read by sight suggest Eyes are active rather than a different suspect.

Turning observations into meeting decisions

Meetings are where observations become votes, and they should be run as evidence collection rather than argument:

• Budget the meeting: roughly the first 20 seconds for a tight alibi pass (one verifiable fact per player), the middle 20 for cross-checks, the final 20 for the vote lock. Over-explained alibis are a data point — real players answer in under five seconds.
• Report only what you actually saw: who was near the last victim, who left a task early, who has been following players instead of working the meter. A single testable claim is worth more than three vague suspicions.
• Cross-check alibis: if two players' accounts of the same moment contradict, flag it on the record even if you cannot resolve it this meeting — the notebook moves between meetings, but a recorded contradiction stays.
• Track vote patterns across meetings, not just one: a mirror voter who always copies a specific player, or two names voting together meeting after meeting, is a stack worth calling out by name because the notebook usually moves through a known pair of hands.
• When there is no real proof, a skip vote is often correct — accusations without support split the vote and hand Kira an easy round. Track habitual skippers, though, because a consistent pattern of avoiding every ejection while contributing nothing is a recognised Kira-side pattern.
• Do not push for a vote before the second meeting unless the case is overwhelming; the first meeting is for alibis, the second for contradictions.

Remember that meetings cut both ways: every meeting is also an information window for the killing side, which reads reactions, watches who defends whom, and pivots their defense — avoid revealing L's full picture at once.

Common evidence gaps and uncertainty

• Most tells are behavioral inference, not mechanical confirmation. A Kira can fake movement, fake tasks, and vote like the majority; the only near-hard signals are an observed glowing write, the notebook pass/pickup animation, and (in one account) server-authoritative L ID checks.
• The notebook pass animation is reported inconsistently — as indistinguishable from simply putting it away in one account, and as unmistakable when watched directly in another. Either way, do not accuse on a pass alone.
• The kill feed never names the killer, so the holder must always be triangulated from location, timing, and who else was nearby.
• L-collected information persists even if L is removed, since L's board transfers to a successor, so the investigation can continue without losing data — but L's exact kit is currently inconsistent across player reports, so verify your tools in-game after each update.
• Meeting mechanics themselves (timers, thresholds, ties) are not settled and are out of scope here; treat voting and meeting rules as a separate topic.

BloxNote updates frequently, so recheck investigation tools and meeting behavior after balance changes.