Source field guide

Source Label Glossary

A compact rulebook for the labels Winds Meet Guide uses before turning source evidence into player-facing advice.

Global confirmedCN referenceCommunity leadStatic safe

Maintained byHeavenskiss

Pinned source labels

Confidence should be visible.

reader promise

A guide can be useful before every fact is perfect, but it should never hide how strong the source is. Labels tell a reader whether a claim is ready to follow, good for planning, or only a lead to verify.

5

public labels

7

review examples

482 links

author corpus

2026-07-10

checked date

Source label

Global confirmed

Use when the claim appears in global client text, official English notes, or directly checked global gameplay.

Strongest labelCurrent regionGuide-ready

Source label

CN reference

Use when CN information helps planning but has not been confirmed in global release conditions.

Planning layerLocalization riskNo hard spend

Source label

Community lead

Use when a clip, post, or player report gives a useful clue that still needs direct verification.

Useful clueNeeds checkDo not finalize

Source label

Retired or changed

Use when older advice has been superseded by a patch, localization update, or stronger reviewed source.

Old claimReasonReplacement

Source label

Static safe

Use for general guidance that avoids exact mechanics, numbers, coordinates, or unverified acquisition steps.

Low riskFrameworkNo exact claim

Review test

Ask before publishing.

Publish questions

Every claim gets a label.

Can a reviewer see where the claim came from?

Is the claim global, CN-only, community-led, or static-safe?

Could localization or patch timing change the advice?

Would a player spend scarce resources because of this claim?

If the claim changes later, can the page explain why?

Examples

Same claim, different weight.

Good label

Global confirmed advice says what was checked, where it was checked, and what page it affects.

Weak label

A community lead can be useful, but it should not tell players to commit until the route is reviewed.

Danger label

Unlabeled CN or old patch advice can look authoritative while pointing global players at the wrong choice.

Data examples

Useful does not mean guide-ready.

These rows show how the first and second data batches should be read before they become public guidance. The label decides what a player can safely do with the fact.

Global confirmed

Global 1.8 patch notes

Official English article, 2026-07-02

Can support patch timeline entries and guide-impact notes when the page keeps the date visible.

CN reference

CN 2.7.0A repair notice

Official CN article, 2026-07-07

Can support future-watch and source-comparison rows, but not global spend or build advice.

HMT reference

HMT 1.8 repair notice

Official HMT article, 2026-07-02

Can support Traditional Chinese term bridges such as 夢中不羨仙 and 奇術新悟.

Global confirmed

Steam platform facts

Steam store page, checked 2026-07-08

Can support beginner FAQ basics, while account and support caveats still need separate checks.

CN reference

Official Bilibili overseas-service caveat

Official Bilibili opus, 2025-11-15

Good for explaining that CN official posts can discuss global service, but final player instructions should still prefer global official notices.

Review source
Community lead

GameKee beginner route recommendations

GameKee beginner article, checked 2026-07-08

Good for discovering beginner questions, weapon names, and verification targets; not enough to publish exact starter-build advice.

Review source
Community lead

GameKee opening-choice UI notes

GameKee opening choices article, checked 2026-07-08

Good for finding UI terms and screenshot targets; global UI wording still needs direct global-client or official English confirmation.

Review source

Author corpus

The Chinese corpus is fuel, not a shortcut.

The Entertainment14 Where Winds Meet index is treated as owned Chinese author material. It should drive English page architecture, route ledgers, glossary work, and proof queues. It should not become silent Global instructions just because the source material is strong.

Author corpus

Entertainment14 Where Winds Meet index

482 linked guide articles, checked 2026-07-10

Treat as the project's Chinese author corpus for player problems, route logic, terminology, skill names, quest names, boss mechanics, and content routing.

CN reference

Useful material, not automatic Global advice

Owner-written CN/HMT-era guide material

Use it to build English page structure, search intent, and proof queues. Hold exact routes, rewards, coordinates, events, and build rankings until Global evidence confirms them.

Needs Global check

High-risk claims stay visibly held

Corpus placement matrix

Any row that sends a player to spend resources, follow coordinates, bind an account, use a code, or trust a current build needs stronger proof before it reads as instruction.

Static safe

Method pages can ship earlier

Section execution matrix

Framework pages, glossary rows, source desks, and routing indexes are useful now when they explain what is known and what still needs verification.

Glossary rule

Do not ask players to act on an unlabeled claim.

If a page cannot say whether a claim is Global confirmed, CN reference, community lead, retired or changed, or static safe, the page should not turn that claim into a route, build, resource, map, account, or support instruction.

Open corpus desk