Last checked: Sep 23, 2026
Source Methodology
A plain-English source guide for codes, classes, badges and survival guides on this fan-made 100 Days At Sea wiki.
A source note tells players how much trust to put in a claim. Official and public Roblox data can support basic facts, while player videos and competitor references only tell us what to check next.
Use this page before trusting copied code posts, Discord invite claims, Trello boards, or update rumors.
Guide
One claim, three source strengths
The same play session can produce three kinds of notes, and they do not share a confidence level. First, a public badge: We Cookin says to cook your first chowder with the cooking pot. That is strong enough to tell a new player that a cooking pot exists as a goal. It is not strong enough to list ingredients. Second, a community craft order: Wood, Metal, Sawmill, Crab Trap, Map Radar. That is a hypothesis for the build menu. The page may name it, must say it is community-reported, and must tell the player to follow the menu if the names differ. Third, a code string from a forum post with a use-before date that has passed and no recorded reward. That stays off the working list entirely.
Numbers get the same split. "Burn 1,500 items in a single session" is allowed when it is the Bonfire 8 badge description, cited as badge text. "Survivor costs 50 Pearls" is allowed only with a community-reported label, because the figure lives in a player-facing class roundup, not in a screenshot kept with this wiki. "The Squid Boss has this much health" is not allowed at all until someone records the fight. Leaving the number out is the method, not a gap to apologize for.
Player videos and other wikis are used to notice what people are struggling with: early wipes, class shopping, boss retries, fake recipes, copied codes. They are not copied into tables. When two sources disagree, the stronger one wins and the weaker one is either labeled or dropped. Official Roblox pages and public badge data beat a video title. A video title beats silence when the only honest output is "this fight is being talked about, and here is what we still cannot say." A competitor code list beats nothing, because copying it would publish a claim this site has not checked.
Rejected sources never graduate. Script and executor pages, free-Robux pitches, and password forms are not "unverified leads." They are out. The feedback form can carry a correction or a privacy question. It is not a back door for those categories. Reviewed when public sources materially change. A new source does not get a page of its own until it changes a decision a player would make.
Guide
Source types
Official source
Roblox game pages or developer-owned public pages.Public platform data
Public Roblox badge data, public game metadata, public thumbnail or platform data.Player reports and public videos
Videos, articles, guides, or public posts that can help players compare ideas but should not become final gameplay facts by themselves.Competitor reference
Used only to understand search gaps and claims that need verification. Never copied as verified facts.Rejected source
Scripts, exploits, cheats, executor pages, pastebin dumps, free Robux pages, or unsafe download pages.Guide
How each source type is used
| Source type | Used for | Not used for | Example topic | Player takeaway |
|---|---|---|---|---|
| Official source | High-level gameplay framing and official public links | Unlisted codes, hidden mechanics or private claims | Roblox game page | Strong for basics |
| Public platform data | Badge names, badge icons, public counts and metadata | Exact routes, boss strategy or recipe steps by itself | Roblox badge API | Useful for public data |
| Player reports and public videos | Route ideas and topics to compare | Final gameplay facts without another check | YouTube guide or article | Helpful, not final |
| Competitor reference | Finding risky claims to double-check | Copied prose, code lists, tables or images | Competing wiki/code page | Reference only |
| Rejected source | Nothing player-facing | Any source-backed fact | Scripts, exploits, free Robux pages | Rejected |
Guide
How this supports codes, classes, and badges
Codes
Working code values need official confirmation or an in-game reward check. Public code leads are not the same as verified working codes.Classes
Reported class rows can help players see what needs checking, but they are not final class data until the game UI confirms them.Badges
Public Roblox badge data can support badge names and milestone wording. Strategy and route advice still need gameplay evidence.Guide