WEAPON / RECIPE LOOKUP

LOOK UP REQUIREMENTS WITHOUT INVENTING FACTS

Damage, drops, quantities and market values stay unknown unless the source package supports them.

Review lookup rows REPORT A CORRECTION

EARLY ACCESS DETAILS CAN CHANGE. EACH FACTUAL ROW SHOULD SHOW SOURCE, LAST VERIFIED DATE AND CONFIDENCE.

Text-first review surface

SRCDATECONF

Unknowns stay visibleNo unsupported art

review-before-action

Facts stay provisional

EARLY ACCESS DETAILS CAN CHANGE. EACH FACTUAL ROW SHOULD SHOW SOURCE, LAST VERIFIED DATE AND CONFIDENCE.

correction path

Source-backed edits only

Corrections require a source, a last-verified date and a confidence note before any future publication.

production boundary

Source-first public guide

This public page stays source-first: unknown game facts remain visibly unverified until a source/date/confidence label supports them.

support table

WEAPON AND RECIPE REVIEW TABLE

This production route preserves source-first table behavior across non-/keys routes.

ITEM	CATEGORY	KNOWN REQUIREMENT	KNOWN OUTPUT	SOURCE	LAST VERIFIED	CONFIDENCE	CORRECTION
Unverified item row	Unknown until verified	Unknown until verified	Unknown until verified	SOURCE NEEDED UNTIL VERIFIED	--	LOW CONFIDENCE — CHECK SOURCE BEFORE ACTING	REPORT A CORRECTION

FAQ accordion

OPERATIONAL FAQ

ARE DROP RATES INCLUDED?

Only if verified source evidence exists; otherwise the field remains unknown.

CAN RECIPES BE ADDED?

Yes, with source, date and confidence labels.

CURRENT QUEUE STATUS [ACTIVE]

REPORT A CORRECTION

Found a stale key note or unsafe claim? Send a correction with a source/date/confidence note. Reports stay in the review queue and are not published automatically.