View source for Project:Beta verification

This workflow turns a player observation into a reusable guide. Check [[Project:Data policy]] for the meaning of '''Source checked''', '''In-game checked''', and '''Needs review'''. A citation to an announcement alone cannot establish in-game verification.

== Record enough to reproduce the result ==
<div class="fw-query-table">
{| class="wikitable fw-data-table"
! Subject !! Evidence to capture !! What not to infer
|-
| Quest || Exact title and ID when available, starting and ending NPCs, prerequisites, objectives, coordinates, reward choices, build || A familiar Classic name does not prove identical objectives or rewards in Forever.
|-
| Dungeon || Entrance route and map, observed access requirements, party composition, boss behavior, loot source, build || A published level band does not prove an entry restriction; one run does not establish a drop percentage.
|-
| Item || Full tooltip and the loot, vendor, quest, or crafting action that produced it || An item name does not prove its slot, quality, or source.
|-
| Profession recipe || Exact recipe/output, skill requirement, materials and quantities, trainer or blueprint source, build || A named campsite object does not establish its material cost or every way to learn it.
|-
| Talent or racial || Rank, tooltip, character conditions, before/after observations, build || A preview number or a single combat event does not establish a tested formula.
|-
| Travel or map || Start and end location, route, faction, access conditions, annotated screenshot and build || Nearby map regions do not automatically have a usable path between them.
|}
</div>

== A compact observation note ==
<pre>Subject and exact title:
Game build and observation date:
Character level, class, faction, and relevant conditions:
Steps:
Observed result:
Source or screenshot:
Difference from the existing article:
Still uncertain:</pre>

Use your own screenshots or appropriately licensed material, with source and attribution on the file page. Keep character/account details out of evidence unless they are necessary for the result.

== Publish a connected record ==
# Search for the existing subject, including alternate names, before creating a page.
# Use [[Form:Item|Item]], [[Form:Quest|Quest]], [[Form:Zone|Zone]], [[Form:NPC|NPC]], or [[Form:Dungeon|Dungeon]] for structured records.
# Add citations next to the facts they support. Enter plain page titles in relationship fields and leave unknown values blank.
# Link the related location, source, and reward pages. Verify the resulting semantic lists show the correct relationship.
# If evidence disagrees, retain both versions and explain the conditions. Record a supported change at [[Beta changes]].

For a leveling build, describe its purpose and tradeoffs, then publish the tested character level, equipment assumptions, allocated points, and route. Label an untested suggestion as theorycraft rather than a recommended or best build.

[[Help:Editing]] · [[Project:Data policy]] · [[Beta changes]]