POIs
Points of interest are one of the cleanest ways to turn scattered public data into a practical field guide.
CrabCodex already exposes a recognizable POI roster with names, images, biome placements, and many of the available choices. That makes this one of the best next sections to build as a searchable archive instead of waiting for full late-game firsthand verification.
Quick Facts
Fast read before the full guide
Tracked Roster
12 CrabCodex POIs currently mirrored into the site with local images.
Current Scope
Name, biome placement, and publicly documented choice summaries.
Source Layer
Community-documented CrabCodex material, kept clearly separate from official confirmation.
Best Use
Route planning, survival pivots, and spotting value spikes inside a biome.
POI Answer
Use POIs when the map itself is giving you the decision
Short answer
ConfirmedThis page works best when a landmark, interaction site, or recovery object is changing the direction of the run.
Best for
ConfirmedRoute planning, value checks, and deciding whether a visible POI is worth detouring for.
Avoid if
Community-testedYou really need a full biome overview or a build diagnosis instead of a point-of-interest lookup.
Fast route
Community-testedConfirm the POI here, then go to Biomes or pivot-related pages if the route choice still is not obvious.
How To Read This Page
- These entries are real POIs from CrabCodex, not invented filler.
- Some POIs already have detailed choice text, while others still have incomplete public documentation.
- A missing exact effect should not block a POI from being indexed if the name, image, and biome are already stable.
Why POIs Matter More Than They First Look
POIs are often where a run stops being theoretical.
A build can look fine on paper, then a recovery point, stat object, or high-variance interaction appears and suddenly the correct route is different. That is why this archive matters. It keeps map objects from getting buried inside unrelated guide paragraphs.
Common POI Reading Mistakes
- Looking at the reward and ignoring the detour cost.
- Treating every POI as pure upside when some only matter in the right state.
- Waiting for perfect public documentation before indexing something that is already stable enough to recognize and route around.
Index Layer
POI Archive
Use this as the first searchable layer for route-relevant landmarks, temporary stat spikes, recovery points, and high-variance interaction sites. Each card now leads to its own archive page for deeper detail.
12 entries
Algae Reef
A water-biome POI that currently offers one max-HP growth option and one AD increase option.
Calendar Stone
A Sand and Snow POI whose documented choices alter the day-night balance rather than directly buffing combat stats.
Carved Tree
A broadly distributed POI that currently offers either a full level of Progress or a +1 PD increase.
Chaos Tree
A multi-biome POI built around a high-variance choice between a large random stat spike and a mutagen payout.
Unattended Nest
A Sand and Snow POI with unusually swingy outcomes tied to eggs, social stats, and possible land-boss interaction.
Frozen Specimen
A Snow-only POI whose current public page clearly confirms ally gain, but still leaves some other reward text unresolved.
Giant Mushroom
A Grass POI focused on mushroom systems, poison scaling, and spawn-rate knowledge rather than raw body stats.
Growing Tree
A Grass and Snow POI that currently maps to modest PD or AD boosts, plus a random-stat option.
Healing Pond
A Grass and Snow recovery POI with one large HP refill option and one health-regeneration increase.
Lotus Plant
A Water POI whose documented choices currently split between progression gain and cooldown reduction.
Mud Pond
A Grass and Sand POI with a notably practical set of defensive, adaptation, and social bonuses.
Oasis
A Sand POI whose public CrabCodex page currently confirms the location and image, but does not yet list choices data.
Best Next Page By Intent
- Use
How Biomes Workif the POI only makes sense inside wider terrain pressure. - Use
How To Tell When You Should Pivotif the landmark is offering a real correction or escape route. - Use
Codexif you are still mapping terms and systems before making the route call.