Contact the wiki

100 Days At Sea Wiki does not publish a contact email. Do not send game passwords, backup codes, or payment details to an address you found on another site that claims to be this wiki. The only channel maintained with the site is the feedback form at https://100daysatsea.feedlog.ai/. Use it for a wrong route, a stale code claim, a broken link, a privacy question, or a source you think the page missed.

A useful note names the page URL and the exact sentence. Then it says what you saw in game: the menu text, the badge description, the redemption result, or the station name, plus the date. "Update the class guide" is hard to check. "The class button shows a different Pearl cost than the reported row on /classes, seen on this date" can be checked. Screenshots help when the wording is the whole dispute. Do not send a screenshot that includes a login, a wallet, or a private message.

Code reports are welcome only as evidence. If you redeemed a string and the game showed a reward or a failure, quote that result and say where the string came from. The codes page does not promote a value into the working list because several people forwarded the same post. Official posts and in-game results are the bar. An expired community window stays expired.

Route and crafting reports should distinguish a decision from a recipe. If the build menu uses a different station name than a community lead such as Crab Trap or Sawmill, that is a correction this wiki wants. If you are asking for a material count this site has refused to invent, the answer will stay "read your menu" until someone records the UI. Boss notes are the same: a wipe that shows what you lost on death is more useful than a request for a health bar we have not measured.

Privacy questions about the feedback form, analytics, or advertising belong here too, and the privacy page is the standing explanation. Editorial disagreements about whether a claim should be labeled unverified belong with the editorial policy, but you can still send the example through this form.

Do not send Roblox passwords, email login codes, payment data, or requests to recover, ban, or unban an account. This fan site cannot see Roblox support tools and will not pretend to. Billing and account access stay with Roblox. Do not ask for scripts, executors, or other ways to alter the game. Those requests are rejected, not filed for later.

Do not expect a personal reply on every note. Reviewed when public sources materially change. When a report is strong enough, the change shows up on the page, with the claim still labeled by source. Silence is not confirmation that a code works, and a slow page edit is not a studio statement. This is a fan-made guide and is not affiliated with Roblox, Stranded Devs, or any official brand.

If you are stuck in a run right now, the form will not answer before the next raid. Use the guide that matches the problem: the early decision chapter, the class split, boss recovery, crafting order, or the code status board. The form is for making those pages less wrong next time.