Editorial Policy

How this fan-made wiki decides what belongs on player-facing pages, what stays under review and what is never accepted as a source.

This policy is written for players first. It explains why working codes require confirmation, why copied claims from other sites are not treated as facts and why unsafe shortcuts are rejected.

Use this page before trusting copied code posts, Discord invite claims, Trello boards, or update rumors.

Guide

What this wiki publishes

Official basics

High-level facts from Roblox game pages or developer-owned public pages.

Public Roblox data

Badge names, badge icons, public counts and platform metadata when available.

Player guides

Beginner routes, raft basics and crafting priorities only when the source boundary is clear.

Community leads

Classes, videos or guide leads can be listed when they are clearly labeled and not treated as official facts.

Guide

What this wiki does not publish

Unverified working codes

A code is not marked working until an official source or in-game reward check confirms it.

Copied competitor text

Competitor pages may reveal search gaps, but their wording, tables and images are not copied as facts.

Fake exact mechanics

Recipes, routes, boss stats, drops, class rankings and seed lists need visible proof before publication.

Unsafe shortcuts

Scripts, hacks, executors, free Robux claims and unsafe download pages are rejected sources.

Guide

How we handle Roblox codes

Working code values need official confirmation or an in-game reward check before they are marked as working. Public code-related leads can be tracked, but copied code lists are kept separate from verified working codes.

Guide

How we handle classes, badges, and guide topics

Classes

Class rosters and costs can be useful leads, but class rows stay clearly marked until the in-game class menu is checked.

Badges

Public Roblox badge data can support badge names, icons and milestone framing. Badge strategies still need gameplay evidence.

Guides

Beginner, raft and crafting guides use confirmed high-level basics first. Exact recipes, routes and rankings wait for proof.

Guide

Update and correction policy

Pages are updated when official public sources, public platform data, reliable community evidence or original playtest notes change. Corrections should keep the checked date, source type and player-facing explanation clear.

Guide

No scripts, exploits, or free Robux claims

This site does not publish scripts, exploits, executor links, free Robux claims or unsafe downloads. Player guides should help people understand 100 Days At Sea, not push account risk or shortcut scams.