これは Bahkruums ガイドの日本語版です。英語の承認済みソースにある事実、識別子、リンク、証拠の限界を保ち、公式名称・キー・コード表記の値は変更しません。同じ言語のページへはこの版の内部リンクを使ってください。
A useful Bahkruums route is one you can walk in both directions and describe under pressure. No complete official map or universal escape route is public, so route quality is measured by reproducibility, visible continuation, recovery options, and current-version evidence—not by an unsupported “best route” label.
Build the first route
Choose two strong landmarks. Walk from A to B through no more than two meaningful junctions. Write each turn from the traveler’s perspective and note what visual cue appears before it. Turn around and record B to A separately.
Repeat without reading the notes. If you miss a turn while calm, shorten the route or strengthen the landmark. Only add a third landmark after the loop is reliable.
Route-card format
Use: checked date | start | outbound turns | end | reverse turns | visible continuations | dead ends | common failure | confidence. Keep threat behavior in a separate field because a route can remain correct while AI observations change.
Do not write “safe” as a route property. Record tested refuge candidates and exit plans through the Safe Spots guide.
Compare route choices
Count meaningful junctions, not every wall bend. Compare how early the next opening becomes visible, whether another branch remains available, and where players are likely to collide. A shorter route is not better if it ends in unknown geometry.
For solo play, precise reversibility may matter most. For a group, wider openings and clear callouts may reduce blocking. These are choice criteria, not fixed map mechanics.
Chase execution
At the first cue, face the known continuation and choose before reaching the junction. Use Shift Sprint after committing. Keep the next opening centered and use short rear camera checks.
If the route is blocked, use the nearest branch whose continuation you can see. Do not switch repeatedly between branches. When every option is unknown, preserve visibility and turning room rather than diving into an unseen dead end.
Use bhop only where you can reproduce control. The feature is official, but its benefit and surface behavior are not published. Tight turns may favor controlled sprinting.
Group routes
Assign a start landmark, branch callout, and regroup landmark. Split only along walked routes. Q and T can support a voluntary group protocol, but no AI or distance effect is assumed.
Avoid following a crowd without knowing the reverse path. A player ahead may be improvising. If a collision causes failure, record it as a group-route weakness rather than nextbot behavior.
Failure and recovery
Mark the exact junction where the route failed. Was the opening hard to see, the label ambiguous, the branch blocked, or the next segment unknown? Fix one weakness and rerun calmly.
If threat behavior contradicted the plan, move the claim to Behavior and preserve an alternate continuation. Do not redesign the entire map from one encounter.
Version checks
Date every route. After an update, walk A to B and B to A before restoring verified status. Check landmark visibility, opening access, dead ends, and any claimed refuge.
The official August 6 update timestamp does not itself prove a route changed. It tells you when a retest is sensible.
Route mistakes
- Writing directions for only one travel direction.
- Depending on a moving nextbot as a marker.
- Hiding an unknown dead end behind “shortcut.”
- Calling a route fastest without a repeatable comparison.
- Treating a group collision as universal geometry failure.
- Keeping an old safe label after a beta update.
Routes FAQ
What is the best Bahkruums route?
No universal best route is verified. Use one you can reverse with clear landmarks and continuations.
How many junctions should a beginner learn?
Begin with one or two between two landmarks. Add complexity only after the reverse route works.
Should I bhop on routes?
Only on segments where you keep control. Sprint through tight or unknown turns.
How often should routes be checked?
After a relevant update or when geometry/access disagrees with the record.
Evidence checked 2026-08-07 UTC: official Survival, controls, beta, and media context. Exact routes remain player-recorded current-build evidence.