Esta é a versão em português do Brasil do guia de Bahkruums. Ela preserva os fatos, identificadores, links e limites de evidência do corpus aprovado em inglês; nomes oficiais, teclas e valores em código permanecem sem tradução. Use os links internos desta versão para continuar no mesmo idioma.
Identify a Bahkruums nextbot by a combination of cues, not by a single resemblance. The official description confirms nextbot-game inspiration but provides no roster. First-party media shows stylized subjects in the game’s visual language without naming them. A reliable cue card lets players recognize danger and communicate before the final name is known.
The four-part cue card
Appearance: note the dominant colors, outline, facial features, cropping, animation, and whether the image changes at different distances. Avoid claiming the subject is a real person or copyrighted character based on resemblance.
Audio: record when the cue begins, whether it loops, how it changes as the threat approaches, and what other sounds were present. A teammate or another nextbot can contaminate the observation.
Motion: describe turns, pauses, direction changes, and qualitative pace. Do not publish a speed number without a controlled route and method.
Context: include the date, server, landmark, player positions, current action, and how the encounter ended. Context prevents one target switch from becoming a false AI rule.
Recognition under pressure
Use the earliest cue you can identify reliably. If an audio pattern has matched the same visual several times, it can warn you before contact. Face a known continuation first, then use a short camera check to confirm. Recognition should support route choice, not turn the chase into prolonged observation.
If you cannot identify the cue, call the location and direction. “Unknown threat behind the wide opening” tells teammates what to do. A fake name adds less value than a clear landmark.
Neutral labels
Create a temporary label from visible, non-speculative traits: “red portrait,” “tall dark figure,” or “glasses image.” Keep it inside notes until a reliable source connects an in-game name. Do not create separate articles, lore, or tier rankings for neutral labels.
When two players use different labels, compare cue cards. If appearance and audio match, merge the records. If only the visual resembles another entry, keep them separate until the current game shows they are the same.
Audio testing
Choose a familiar route and reduce unrelated group noise where practical. Record the cue at first notice, at closer contact, and after turning away. Do not state an exact range unless distance is measured consistently.
Test Q Scream and T Speak separately from identification. Their official labels are known, but AI or audio-masking effects are not. If your own action obscures the cue, record that as an observation about audibility, not nextbot behavior.
Visual testing
Use the current official server and keep enough of the scene visible to establish Bahkruums. A cropped face can remove the route and game context. Compare with approved official media only as visual reference; its alt text does not supply names.
Lighting and distance can change colors. Use shape, recurring facial features, and animation alongside color. A video thumbnail may be edited, so prefer current gameplay frames.
Confidence labels
- Official: creator-owned text or current UI names the entity.
- In-game verified: a dated direct observation visibly connects the name and cue.
- Community corroborated: two independent current sources match name and cue.
- Community reported: one relevant source connects them.
- Needs in-game testing: the cue is observed but identity or behavior remains unsupported.
Confidence belongs to each claim. A name can be corroborated while speed remains unverified.
Common identification errors
- Naming from a thumbnail without gameplay context.
- Treating a resemblance as official identity.
- Mixing two audio sources in a crowded chase.
- Assuming every visual change is a separate entity.
- Copying a roster from another nextbot game because the inspiration is similar.
- Inferring behavior from the name rather than observing it.
Turn identification into action
Attach each cue card to a route response you understand: nearest known continuation, common failure point, and regrouping landmark. Do not call that response a universal counter until it survives repeated current tests.
Read the Map Routes guide to record geometry and the Behavior guide to test what happens after recognition. The Nextbot List tracks which identities are ready for publication.
Identification FAQ
Can I name an entry from the official media image?
Not unless creator text or current UI supplies the name. The media image is official visual evidence, not a roster label.
What if only one video uses a name?
It may be Community reported if the video clearly connects current in-game cue and name. Otherwise keep a neutral label.
Which cue is best?
The earliest repeatable combination is best. Audio may warn early; visual confirmation prevents mismatching similar sounds.
Why record the map landmark?
Geometry and nearby players affect what you observe. Without context, behavior and targeting conclusions become unreliable.
Sources checked 2026-08-07 UTC: official Bahkruums description and media API plus recent game-specific walkthrough context. No authoritative cue/name catalog was available.