Bahkruums does not currently expose a verified public landmark dictionary, so players need callouts that describe what is actually visible. A good landmark can be recognized during movement, approached from both directions, and separated from repeated corridor geometry. A player nickname is useful when clearly labeled unofficial.
Choose strong visual cues
Prefer lighting transitions, unusually wide or narrow openings, room proportions, distinctive wall breaks, or stable prop clusters. Use color only with a second cue because lighting and device settings can change it. Avoid naming a landmark after a nextbot that may move.
The official media shows a yellow-lit interior with openings and distant geometry. That supports lighting and opening-based callouts, but the scene’s official name is unknown.
Two-part callout format
Combine a feature and a position: “bright split,” “wide opening,” “dark corner,” or “chair room.” These examples describe a method, not verified official Bahkruums labels. Keep them lowercase in notes unless the game publishes a name.
Add direction when calling to a group: “bright split, left branch.” A landmark without an action may arrive too late during a chase.
Validate from both directions
Walk toward the landmark and record what appears first. Continue past it, turn around, and approach from the reverse route. If the visual disappears or becomes indistinguishable, add a second cue.
Repeat after rejoining a current server. Dynamic props or lighting should not be the only identifier. If the feature changes, downgrade confidence and keep the route attached to more stable geometry.
Avoid duplicate landmarks
Repeated interiors can produce several “bright corners.” Add the connected opening count, nearby prop, or route relationship. Compare screenshots with full context rather than cropped walls.
If two records describe the same geometry, merge them under the clearest neutral name and preserve aliases only in notes. Do not create duplicate pages for misspellings or group slang.
Use landmarks in route cards
Every route needs a start and end landmark. Record turns from the traveler’s perspective and the visible cue before each decision. Reverse the route and write the reverse sequence separately.
Mark one recovery landmark that can be reached from multiple known continuations. That does not make it safe; it makes it useful for orientation. Use the Routes guide for the full card.
Group callouts
Agree on labels before pressure. Keep the callout short, then add threat direction. Q Scream and T Speak are official actions, but their range and AI effects are unknown; the group protocol is voluntary.
Avoid callouts based on “where I died” or another temporary event. Use geometry someone else can recognize independently.
Landmark confidence
- Official: current UI or OrbitWave Creations names the location.
- In-game verified: the cue is directly observed and reproducible in a dated current server.
- Community corroborated: two independent current sources show the same cue and label.
- Player callout: a useful neutral label without official status.
- Needs retest: geometry, access, or visibility changed after an update.
Confidence applies to the label and cue, not to safety. A perfectly recognizable landmark can still be dangerous.
Common failures
- Using only color in repeated lighting.
- Naming after a moving entity.
- Recording only one approach direction.
- Cropping away connected openings.
- Treating group slang as official.
- Calling a landmark safe without pathing tests.
Report a landmark
Include date, Place ID, full-scene image or description, entry direction, two stable cues, connected routes, and label status. Avoid unauthorized copied screenshots when a text description is sufficient.
After an update, retest visibility and access. A landmark can remain while one route changes, so update the relationship rather than deleting all notes.
Landmark FAQ
Are these official names?
Not unless marked Official. Most early labels are transparent player callouts.
What makes a landmark good?
It is visible while moving, distinct from nearby geometry, stable, and recognizable from both directions.
Can a nextbot be a landmark?
No. Moving entities are encounter cues, not stable map positions.
Does a regroup landmark need to be safe?
No. It needs to be recognizable and connected; the group still needs an exit.
Evidence checked 2026-08-07 UTC: official media visual context and current Bahkruums navigation demand. Exact location names remain in-game test items.