Editorial Policy

A sentence is published when a player could act on it without being lied to about the source. That is a higher bar than filling a template. The public Hooked badge says to grab an object with the harpoon. That sentence can stand as a milestone, because Roblox badge text is the source and the page says so. A community beginner route that names a Sawmill, a Crab Trap, and a Map Radar can be discussed as a lead. It cannot be printed as the required craft order, and it cannot grow ingredient counts the menu has not shown this wiki.

Class rows are the clearest test. Reported Pearl costs and starter tools help a player know which button to read. They are not a price list. If the guide says "about 50 Pearls" it must also say the figure is community-reported and unverified until the class menu matches it. A best-class ranking fails this policy even when the prose is long. The editor's job is the tradeoff: solo sustain versus a duo split, cheap row versus a specialist you have not earned, and the decision to stay on the starter until the raft feeds itself.

Codes fail closed. No working value is listed until an official post or a recorded in-game reward confirms the exact string, the reward text, and the date. A passed community window is a lead that died. It is not revived because a new page needs a code block to look complete. Boss health, drop rates, coordinates, and death penalties stay off the page for the same reason. Badge names of fights are allowed. Invented fight math is not.

Updates follow reviewed when public sources materially change. The checked date is the review stamp, not a claim that every route was replayed that day. A correction replaces the sentence players would follow and keeps the label. Padding a thin chapter until a word counter is happy, without a new decision or a new source boundary, is not an update this policy recognizes.