The 100 Days At Sea source policy is simple: publish claims only when they can be checked against official Roblox pages, Roblox API data, official media, high-trust trackers, or clearly labeled hands-on evidence.
Source hierarchy
The 100 Days At Sea source policy starts with official Roblox material: the public experience page, Roblox game API, Roblox badge API, and official trailer media. High-trust tracking pages such as Rolimon’s and OP.GG can support context, but they do not override official data.
Community videos and social clips can be useful leads, but they are not enough by themselves for exact routes, maps, codes, boss strategy, item drop rates, or best-build claims.
How pages are published
Each published page needs a player question, a direct answer, and visible source boundaries. That is why this launch build publishes release, platforms, gameplay, trailer, news, FAQ, source policy, beginner guide, systems, multiplayer, and badges pages.
The 100 Days At Sea source policy also explains why some tempting pages are missing. A codes page needs a verified code system. A map page needs reliable route or area evidence. A boss page needs enemy details and strategy evidence. A tier list needs hands-on comparison criteria.
What this site will not publish
- Fake active codes or reward claims.
- Full maps copied from clips without verification.
- Exact boss routes, item spawn tables, or best weapons without evidence.
- Private Discord claims that cannot be checked by normal players.
- Pages that only repeat the game name without answering a player task.
Update method
When a source-backed fact changes, the affected page, related links, sitemap date, news log, and source list should change together. The goal is a useful 100 Days At Sea source policy that keeps the guide helpful without turning guesses into facts.