Unofficial Fan Wiki

Last checked: Sep 23, 2026

100 Days At Sea Companions Guide

Chapter 4 - Playstyle and Helpers. A companion and helper-unit chapter for 100 Days At Sea covering companion leads, NPC/pet/team support differences, testing behavior and team play.

Field notes

How to use this chapter

Read this before the table. It is the decision the cards and rows are there to support.

A companion is a behavior, not a poster

Players use companion to mean a pet, a tame, an NPC, a class summon, or a teammate. Those are different systems. This chapter keeps the word narrow: something you can obtain or prompt, that follows or helps, and that you can describe after a test. A character standing on an island is not a companion until the interaction does something. Zookeeper is the class lead to test first, because community notes tie that row to tamed animals or extra companion effects. Read the row on Classes and then try the prompt somewhere safe. If nothing prompts, say so. An empty test is still a result.

The four behaviors worth logging

Follow, fight, heal or buff, and carry or utility. Add whether the helper has an icon, a name, and a slot, and whether it is still there after death, a server change, or a new run. Those fields are the roster. A list of cute names without them cannot tell a solo player whether the helper replaces a teammate. Healing behavior is easy to confuse with the revive prompt, so test it separately from the revive drill. Combat behavior belongs in a cheap fight before you trust it beside a badge boss on Bosses. If the helper only exists while a class is equipped, that belongs in the note too.

How this page should grow

Add a card when the obtain method and at least one behavior are visible. Keep community articles as the reason to look, not as the finished stats. The walkthrough can mention a helper only after this checklist has a real example from a run. Until then, play as if you do not have a companion: raft safety, a tested weapon, and your own healing plan. A surprise follower is a research event. Record it, finish the trip you already planned, and turn it into a row afterward.

Chapter intro

Quick survival answer

Quick answer

Treat companions as a support-system lead: useful enough to track, but only real once you can show how a companion is obtained, follows, fights, heals or persists.

Companion test rule

If something follows you, helps you or appears recruitable, record the prompt before naming it a companion.

Companions can be pets, NPCs, teammates, class summons or tamed units. The behavior matters more than the label.

Player use

Use this chapter during a real run

Pick the card that matches why you opened the page. It gives you the next safe move without asking you to trust untested drops, stats or route claims.

If you are starting now

Do the first safe move

Separate companions, NPCs, pets, teammates and class effects in your notes.

If you are stuck

Calling every NPC a companion

Record interaction and behavior first.

If you are comparing advice

Zookeeper class link

Extra tamed animal slot / companion effect Bring or check: Could change team utility and animal strategy

If you want the next chapter

Classes

Compare companion-related class leads.

Guide

What to do first

Do these before chasing rare drops, region mysteries or long routes.

Move 1

Separate companions, NPCs, pets, teammates and class effects in your notes.

Move 2

Check whether a companion has an interaction prompt, icon, inventory slot or follow behavior.

Move 3

Record whether it fights, heals, carries, scouts or simply follows.

Move 4

Check whether it persists after death, server change or run reset.

Move 5

Use Zookeeper and companion-related class leads as the first test targets.

Guide

Strategy path

Read this like a route page in a guidebook: order matters.

Step 1

watch for NPCs or animals during early exploration and island trips.

Do: Step 1: watch for NPCs or animals during early exploration and island trips.

Avoid: Skipping the setup step because the next clue looks more exciting.

Next: Classes

Step 2

test interaction prompts only when the area is safe.

Do: Step 2: test interaction prompts only when the area is safe.

Avoid: Treating a lead as a shortcut before your run is stable.

Next: Healing / Revive

Step 3

record behavior in four categories: follow, fight, heal, carry/utility.

Do: Step 3: record behavior in four categories: follow, fight, heal, carry/utility.

Avoid: Treating a lead as a shortcut before your run is stable.

Next: Full Walkthrough

Step 4

compare companion behavior with class effects such as Zookeeper.

Do: Step 4: compare companion behavior with class effects such as Zookeeper.

Avoid: Treating a lead as a shortcut before your run is stable.

Next: Bosses and Raids

Step 5

add companion rows only after obtain method and behavior are visible.

Do: Step 5: add companion rows only after obtain method and behavior are visible.

Avoid: Treating a lead as a shortcut before your run is stable.

Role: Whether helper acts differently from a teammate

Use it: Important for solo players

Beginner tip: Manual needed

Read route note

Guide

Guidebook table

Use the table to scan roles, risks, prep and evidence without turning leads into fake facts.

Companion lead	What to test	Why players care	Evidence
Zookeeper class link	Extra tamed animal slot / companion effect	Could change team utility and animal strategy	Editorial class lead
NPC helper	Prompt, dialogue, rescue or follow behavior	May support quests or survival	Community lead
Pet / animal	Taming, follow, attack or persistence	Could support exploration or combat	Companion article lead
Support companion	Healing, revive or buff behavior	Could change low-health survival	Manual needed
Team substitute	Whether helper acts differently from a teammate	Important for solo players	Manual needed

Guide

What to record in your next run

Use this during play so you know what worked, what was risky, and what is worth repeating on the next run.

Check 1

Prompt, icon, name and how the helper was obtained

Check 2

Behavior: follow, fight, heal, carry, scout, buff or disappear

Check 3

Whether it persists after death, reset, server change or a new run

Guide

Danger cards

These are the mistakes or encounters most likely to wreck a run.

beginner trap

Calling every NPC a companion

Why it matters: A character can exist without being recruitable or useful.

Prepare: Record interaction and behavior first.

Common trap: Calling every NPC a companion

beginner trap

Assuming companions persist

Why it matters: Some helpers may be run-only or disappear after death.

Prepare: Test reset, death and server behavior.

Common trap: Assuming companions persist

beginner trap

Skipping behavior notes

Why it matters: A name without behavior does not help players.

Prepare: Track follow, fight, heal, carry and UI icon.

Common trap: Skipping behavior notes

Guide

Common mistakes

These are the traps that make a run feel unfair even when the route was avoidable.

Calling every NPC a companion

Why it hurts: A character can exist without being recruitable or useful.

Better move: Record interaction and behavior first.

Assuming companions persist

Why it hurts: Some helpers may be run-only or disappear after death.

Better move: Test reset, death and server behavior.

Skipping behavior notes

Why it hurts: A name without behavior does not help players.

Better move: Track follow, fight, heal, carry and UI icon.

Ignoring class links

Why it hurts: Some companion behavior may be locked behind a class like Zookeeper.

Better move: Check class menu and companion UI together.

Writing a roster from one source

Why it hurts: A list can be incomplete or outdated.

Better move: Cross-check with gameplay before final cards.

Guide

Mystery board

These are public/community leads worth watching. They are framed as clues, not official facts.

editorial lead

Zookeeper

How to read this chapter

Treat this like a field notebook: use the route advice now, then double-check exact stats, coordinates, drop rates and hidden mechanics in-game before betting a run on them.

Guidebook status

Readable chapter

Built for players to use from internal guide links

Search status

Public guide

Included with the mature player-guide pages

Safety

Clean play / verified codes

No risky shortcut content or fake working-code claims