侠云录 — the three boards, the two gatekeepers, and what a rank pays

The 侠云录 is one list of sixty names. The game shows it as three boards (天榜 for places 1 to 10, 地榜 for 11 to 30, 人榜 for 31 to 60), but XiaYunLuManager.m_XiaYunLuBang holds a single ordered list. A "人榜 29" is place 59 on it, and everything the board pays is keyed to that full-list place.

What the board is made of

RefreshXiaYunBang rebuilds the list every time the board is opened and after every sanctioned fight:

1. Every active, named human character who is either flagged notable (gender attribute bit 16) or procedurally generated is collected and sorted by 战力, highest first, and the top sixty are taken.
2. The characters the table npc_rank fixes to a place (NpcRankProptype.rank, 1 to 60) are then forced into that place (独孤飞鸿 at 1, 无暇子 at 11, 朱孔明 at 31, one for each board) unless they are dead. A table row with a name and rank 0 is a character the board must never show; that is why companions and story figures such as 小龙女 or 东方不败 are absent however strong they are.
3. A fixed character you have beaten is removed, and the first unlisted character the game comes across whose 战力 does not exceed theirs is slotted in at the same place (InsertDeadNpc, kept in buWeiNpcDir).
4. You are inserted at your own place, m_ForcePlayerRank, which starts at −1, off the board.

So the sixty are mostly fixed by the table, and the sort by 战力 only decides who fills the gaps. The table comes in three per-mode copies (npc_rank, npc_rank_xianejianghu, npc_rank_zhenshijianghu) that differ only in the stipend column.

战力 (NpcEntity.GetZhanLi) is a weighted sum of the sheet: 气血上限 + 3×内力上限 + 8×(外攻 + 内攻) + 7.2×(外防 + 内防) + 10×(命中 + 闪避 + 诛心 + 御心 + 要害 + 化解) + 4×(阴 + 阳 + 刚 + 柔 + 毒) + 10×轻功上限. Notable characters have their 气血 term deflated by their spawn-time percentage bonus first. The player's own figure (GetPlayerZhanLi) divides the two pools by 100 and is otherwise the same sum.

How you get on, and how you move

The one way onto the board and up it is 挑战侠云录, the interaction on a listed character. A plain 切磋, a bounty fight or a kill in the open does nothing for your place, because the manager only listens for the character named in m_curXiaYunLuID, and only Handle_IT_TIAOZHANXIAYUNLU sets it.

• The option shows (CanNpcBeTiaoZhanInXiaYunBang) on any listed character while you are unlisted, and once you are listed only on characters placed above you.
• A 人榜 name always accepts (IsCanTiaoZhan). A 地榜 or 天榜 name accepts only if the gate below is open, and a refusal costs nothing.
• A win gives you their place if it is better than yours. They are removed, a replacement is slotted in, and the board is rebuilt.
• A knockout and a kill are not the same move. Beating them runs OnNpcDefeatNpc, which hands over the place only if your progress up the ladder reaches that far: with shoubangId at 1 you may take places past 10, at 2 any place at all, and at 0 only places past 30. Killing them runs OnNpcDead, which has no such tier — it takes the place outright. So a rank a knockout will not give you yet can be had by killing the character you challenged.
• Your recorded 战力 is raised to one more than theirs, which only affects where the sort puts you if the forced place ever fails to apply.

Killing a listed character outside a challenge

Mostly you cannot, and that is the short answer to "why not just 劫杀 them". All 100 npc_rank rows name a real character (NpcType 1 — 独孤飞鸿, 圆寂, 古元 and the rest), and Handle_IT_ROB refuses a named character outright unless they carry their own IT_ROB row:

bool flag = !npcEntity.IsRandomNpc();                  // true for a named character
if (flag && num == 0 && !npcEntity.m_MastCanJueDou)    // and no IT_ROB row of their own
{ ShowNpcTalk(5000119); return; }                      // a line, and nothing else

So 劫杀 is not a shortcut past 挑战侠云录; it is not offered on the people it would matter for. What follows is what happens if a listed character dies some other way — a bounty, a sect war, a script.

• You get nothing. OnNpcDead returns at the m_curXiaYunLuID guard before any rank is read.
• They fall off the board. NpcController.Dead leaves the entity in place with IsDead() set, and RefreshXiaYunBang inserts a fixed-rank name only if (!(GetEntity(npcId) is NpcEntity e) || !e.IsDead()). Opening the 侠云录 panel is enough to trigger the rebuild.
• Nobody below is promoted. It is tempting to picture the list closing up, and it does not. The rebuild starts from the 战力-sorted live characters and then inserts each fixed-rank name at its own index, in ascending order — so rank 21 is placed at index 20 whether or not rank 20 was skipped, and rank 22 at 21, and so on. Kill the rank-20 holder and the board reads:

Everyone keeps their number. The vacated one goes to the 战力-sorted filler pool, which is where the unnamed places on the board come from anyway.

That filler is challengeable — CanNpcBeTiaoZhanInXiaYunBang asks only that the character is on the board and placed above you — but beating them moves you nowhere. Both win handlers look the place up with NpcRankProptype where npcId == the victim's prototype id, and a filler has no row, so npcRankProptype comes back null and m_ForcePlayerRank is never touched.

So what a stray kill destroys is not the place. It is one of the fifty-odd named characters who can actually hand a place over. The number remains on screen, occupied by a body you can beat all day without moving. If a listed character is on your route, challenge them before you fight them.

The fight itself is the ordinary 切磋 flow, ceremony included, and the trainer's FastQieCuo option strips the ceremony here as anywhere else.

The two gates

Movement is tiered, and the tier is a saved number, shoubangId, 0 to 2:

A kill is the way past this table. The tiers above are read by OnNpcDefeatNpc and by nothing else, so they bind a knockout only. Kill the character you challenged and OnNpcDead gives you their place with no tier consulted — which means a 天榜 place can be taken before either gatekeeper has been beaten, provided you challenged that character properly first.

The gatekeepers are not on the board. Each has a challenge of his own, 挑战人榜守榜人 on 段天涯 and 挑战地榜守榜人 on 庆丘 (rows 93005001 and 93006001 in npc_interact), and each carries a rank condition, ECT_CheckPlayerRank == 31 for 段天涯 and == 11 for 庆丘. The board's own sign, 成为人榜第一方可挑战定榜人, says the same thing. The option exists only while you hold the top place of the lower board. Beat the gatekeeper and m_WinedNpc records it, and from then on the next board's names accept.

The two "already placed" clauses cannot fire on their own, since getting to 30 requires beating a 地榜 name, which requires the level. They exist for saves that reached those places another way.

The whole ladder, then, is to beat any 人榜 name to get on, climb the 人榜 to 31, beat 段天涯, climb the 地榜 to 11, beat 庆丘, and climb the 天榜 to 1. At place 1 the board's title changes to 天下第一.

What it pays

Once, on the way up. Passing certain places sends a letter from 侠云帮礼物使 (character 34866) with the row's addItem, and m_GetedJiangLiRanks makes sure each fires once per save:

Every 720 seconds of play, for as long as you hold a place. MailManager.UpdateXiaYunLu counts m_GamePlayedSecond, which advances by Time.deltaTime only while the game runs, and for every full 720 seconds since the last payout calls FeiGeTongZhiPlayerFengLu. Each call is one letter, body 190015, carrying the rankItem of the row for your current place. Several periods that elapse before the check arrive as a batch. The clock is the only trigger.

In the 真实江湖 column no two of the sixty rows are the same: the first item changes at every place, the second item after places 10, 20, 30, 40 and 45, and the stone every five places from 21 to 55, alternating between two kinds at 1–10, 11–16 and 56–60. 真实江湖 is the first column; the other two modes pay an 经脉详解 volume and a 玄脉丹 of the band's grade in place of the herb and the book, and only the default mode adds a 神照经残卷. Read your row by the place on the full list.

The stones are the part that changes least, seven at 1–10 and six below: 金珀锻石 and 玄兵铸石 alternating at 1–10, 苍月锻石 and 紫霜铸石 alternating then 血鸣锻石 at 11–20, 苍岩铸石 and 刚玉锻石 at 21–30, 龙魄铸石 and 剑心锻石 at 31–40, 天地铸石 and 剑心锻石 at 41–50, 天地铸石 then 凝炼铸石 and 斩剑锻石 alternating at 51–60. The money sits in the middle item, 神秘钱袋 ×3 at 11–20 and ×2 at 31–40, with a 修为 book everywhere else (宝册 at the top, 密卷 at 21–30 and 41–45, 典籍 from 46 down). The herb cycles, so the 天榜 ten are the 地榜 ten, the 21–30 herbs return at 41–50, and the 31–40 insects return at 51–60. A 人榜 29 (place 59) and a 人榜 21 (place 51) therefore differ in that single herb and in the stone.

The two paid buttons

Both sit on the board beside each name and charge 铜钱 up front:

• 查看资料 opens the character's information page, priced by place (XiaYunLuView.GetCostMoney), 5,000 at 1, 4,000 at 2, 3,000 at 3, 2,500 for 4 to 10, 2,000 for 11 to 30, 1,500 for 31 to 50, 1,000 for 51 to 70 and 500 below.
• 查看位置 costs the row's chaKanWeiZhiCostMoney, 3,000 for every row in the table, and sends a letter from 侠云帮礼物使 naming the character's board, place, title, area and last saved x and z. For a character who is not currently spawned it says so and gives the last position anyway.

Where this was read

• XiaYunLuManager (RefreshXiaYunBang, IsCanTiaoZhan, OnNpcDefeatNpc, OnNpcDead, InsertDeadNpc, CanNpcBeTiaoZhanInXiaYunBang, FeiGeTongZhiPlayerFengLu, GetNameByIndex)
• InteractSlot.Handle_IT_TIAOZHANXIAYUNLU, the only writer of m_curXiaYunLuID
• MailManager.UpdateXiaYunLu, the 720-second clock, and AppGame.GetRealGamePassTime, which returns m_GamePlayedSecond, advanced by Time.deltaTime in AppGame.Update
• NpcRankProptype and the tables npc_rank, npc_rank_xianejianghu, npc_rank_zhenshijianghu (id, npcId, addItem, rank, mailDesId, chaKanWeiZhiCostMoney, rankItem)
• npc_interact rows 93005001 and 93006001, the gatekeepers' challenges and their rank conditions
• XiaYunLuView, in RefreshOSAWuShuang (the 0/10/30 splits), GetCostMoney and OnClickChaKanWeiZhi
• NpcEntity.GetZhanLi and GetPlayerZhanLi
• Strings 190010, 190015, 160000 and LocalString.bangtip

What the community says, and what survives