Official game and APIs
Roblox game identity, public description, media, activity, votes, badges, and passes are checked against Roblox-hosted pages or public endpoints.
Independent editorial identity
Forgotten Stories Field Guide Editorial Team
The Forgotten Stories Field Guide Editorial Team maintains this independent player resource. The team turns scattered public evidence into practical pages while preserving the source, check date, uncertainty, and difference between published work-in-progress records and confirmed game behavior.
VerifiedEditorial policy checked 2026-08-31Who maintains this guide
Independent, source-linked player help
This site is not the game developer, Roblox, Discord, or Trello. It is an independent field guide that organizes public information around player questions.
The editorial team does not claim private developer access. When a value is missing, removed, inaccessible, or only discussed by players, the page says so instead of filling the gap. Dated negative findings—such as finding no verified code—remain dated and can be replaced when an official source publishes new evidence.
Start with the verified wiki directory, follow the beginner survival route, compare the boss database, or inspect the current codes verification.
Source hierarchy
How evidence is ranked
Higher levels establish identity and facts. Lower levels can reveal questions or context but cannot silently replace an official source.
Official public Discord
Staff announcements, FAQ answers, server notices, and creator links are used only when the public message can be preserved with its channel, message URL, and check date.
Official public Trello
Cards support WIP records for bosses, enemies, equipment, spells, Books, items, and locations. A Trello value is not described as deployed gameplay unless another official source confirms it.
Community material
Community videos or discussion can identify a question, but they do not become official facts. Community evidence is labeled and kept separate from primary-source claims.
Review process
From source to published page
Every substantive page follows the same evidence route before it is released or refreshed.
- 01
Identify the player question
The page starts from a concrete decision such as a control, stat cap, boss record, update, or redemption claim.
- 02
Collect the strongest public evidence
The team checks Roblox, official public Discord messages, and the public Trello, keeping direct links and dates wherever the source allows.
- 03
Mark the evidence boundary
Verified, Partial, Unknown, WIP, and community labels prevent a source gap from becoming a fabricated answer.
- 04
Review links and freshness
Pages are connected to related answers and refreshed when a dated official update or source change materially affects the published record.
Corrections and updates
What happens when evidence changes
The team rechecks the affected primary record, updates the page, changes its check date, and keeps uncertainty visible when sources conflict. A Trello edit alone is described as a documentation change unless an official announcement or current game evidence confirms deployment.
Readers can verify recent changes through the official update timeline, the Discord source guide, and the public Trello guide. The live source remains the final check for volatile values.