Location-heavy
Outdoor boss rows start as map-proof rows. The page should not publish a dot, route state, or trigger until the Global map screen is checked.
Bujian boss ledger
A forum-style source desk for Bujian Mountain outdoor boss searches: location-heavy rows, combat-trigger holds, new-leader watch, achievement split, and map proof before exact advice.
Maintained byHeavenskiss
The useful English page is not a copied route. It is a split board: which source row is about a location, which one is about a combat trigger, which one may be a new-leader update, and which one is an achievement overlay that needs a different proof path.
Entertainment14 source indexNo exact locations, triggers, boss names, or achievement conditions are treated as current yet.
Outdoor boss rows start as map-proof rows. The page should not publish a dot, route state, or trigger until the Global map screen is checked.
Combat notes belong here only after the location and trigger problem is separated from tells, counters, and failure states.
The source set includes a new outdoor leader row, so patch/newness claims need date labels instead of evergreen wording.
Achievement collection rows should not be mixed into boss location advice until the achievement panel and completion proof exist.
Reader use
A Bujian field-boss search can mean four different jobs. This board keeps them apart so the site can rank for the search without publishing unverified coordinates or patched triggers.
4
source rows
2
Bujian-specific boss rows
0
public coordinates
6
proof tasks
Source desk
Use as the older schema for field-boss rows: location, fight note, proof state, and map ownership.
Hold: Current Global boss names, map labels, coordinates, spawn state, combat behavior, and rewards.
Treat location and combat trigger as one proof packet, then split map proof from mechanic proof.
Hold: Exact trigger condition, coordinates, route-state prerequisite, boss name, opening behavior, and completion proof.
Keep the title searchable and mark it as an update-watch row before saying the boss is live/current.
Hold: Which boss was added, whether the Global client has the same addition, exact marker label, and spawn window.
Use as a warning that outdoor boss pages can have achievement intent separate from location intent.
Hold: Achievement names, achievement count, completion requirements, reward values, and region/version availability.
| Chinese source | Working English row | Lane | Safe public use now | Hold until proof exists |
|---|---|---|---|---|
| 野外首領位置及打法 | Outdoor Boss Location And Combat Baseline | Baseline field-boss source | Use as the older schema for field-boss rows: location, fight note, proof state, and map ownership. | Current Global boss names, map labels, coordinates, spawn state, combat behavior, and rewards. |
| 不見山野外BOSS位置及戰鬥觸發方法 | Bujian Outdoor Boss Trigger Source | Primary Bujian source | Treat location and combat trigger as one proof packet, then split map proof from mechanic proof. | Exact trigger condition, coordinates, route-state prerequisite, boss name, opening behavior, and completion proof. |
| 不見山新增野外首領位置 | Bujian Added Outdoor Leader Location | New-leader watch | Keep the title searchable and mark it as an update-watch row before saying the boss is live/current. | Which boss was added, whether the Global client has the same addition, exact marker label, and spawn window. |
| 滹沱版本新野外首領六大成就收集 | Hutuo Version Outdoor Leader Achievement Overlay | Achievement overlay | Use as a warning that outdoor boss pages can have achievement intent separate from location intent. | Achievement names, achievement count, completion requirements, reward values, and region/version availability. |
I searched a Bujian outdoor boss location.
Start with the region note. Location, route state, and no-coordinate proof rules live there first.
Open ownerI need to know how the boss fight works.
Use this after the boss is identified. Tells, counters, phase rows, and failure states belong in mechanics rows.
Open ownerThe source says the boss is new.
Newness is patch-sensitive. Keep it as a watch row until the Global client or official notes confirm it.
Open ownerI need the achievement.
Achievement names, counts, conditions, and rewards need screenshots before they become public advice.
Open ownerThis page is allowed to be useful now because it tells the reader what kind of source they found. It is not allowed to pretend the location, trigger, boss name, or achievement row is already verified.
No coordinates, marker names, or route directions until the current Global map confirms them.
No combat trigger method until the route state, object/NPC text, and boss spawn behavior are captured.
No fight advice until a boss row can name the tell, counter, failure state, and source freshness.
No achievement counts, names, or reward values until the current achievement panel is reviewed.
Use for region, route-state, Wanshizhi, encounter, boss-location, and map-proof ownership.
Open threadUse when a boss row is ready to become tell, counter, phase, and failure-state notes.
Open threadUse if a field-boss source turns into no-hit, skip, terrain, or shortcut advice.
Open threadPublish boundary
Until map, trigger, boss panel, combat, and achievement evidence exists, this is a ledger, not a route guide.