Skip to main content
All guides

Adventure Book Guide: 149 Entries, Five Sections, and the Rewards

The Adventure Book turns exploration into completion. Learn the five sections, the entry types, and the reward thresholds that make the collection worth the detours.

Current Orbis version

Adventure Book Guide: 149 Entries, Five Sections, and the Rewards

What the Adventure Book actually tracks

The Adventure Book organizes Orbis completion into five sections: Named Monsters, Field Bosses, Treasure Chests, Familiars, and Viewpoints. The current catalog contains 149 entries across those sections, and each entry records its location, its mission type, how many times it must be done, the points it grants, and any power recommendation. The Adventure Book /adventure-book shows the full list with every field, which makes the book a planning tool rather than a mystery counter.

The entry mix is heavily weighted toward exploration: Treasure Chests and Viewpoints together make up most of the entries, while Named Monsters and Field Bosses are the combat section, and Familiars connect the collection system to the book. That weighting is the practical hint—most of the book is finished by routing, and the combat entries are finished by repeat clears.

Read the mission type and requirement before traveling

Every entry has a mission type and a requirement, and they differ by section. A Named Monster entry asks for a defeat count; a Field Boss entry asks for a boss clear; a chest entry asks for opening the chest; a viewpoint asks for visiting the spot; a Familiar entry asks for registering the Familiar. The Adventure Book /adventure-book shows the exact requirement per entry, so a route never wastes a trip on the wrong action.

The recommended power field is the safety check. An entry that recommends more power than the team has can be marked and returned to later, while the map route focuses on the entries the team can clear now. Combining the book with the Orbis map /map layers keeps both the locations and the readiness visible.

Use the reward thresholds as the milestone

The book grants rewards at point thresholds, and the total catalog adds up to a published points pool. Each entry contributes its points, so the milestone is a point target rather than a raw entry count. The reward ladder starts early—the first thresholds pay gold and progression items—and the Adventure Book /adventure-book shows the full ladder. Picking the next threshold and counting the entries needed to reach it turns the book into a concrete plan.

Because chests and viewpoints dominate the entry list, the fastest threshold progress comes from routing the exploration sections first, then filling the combat sections with repeat clears during the normal loop. The book, the map, and the quest database /quests can be read together so story travel and book travel share the same route.

Combine the book with the collection systems

The Familiar section ties the book to the Familiar roster, and the Field Boss section ties it to the boss encounters. Registering a Familiar you already obtained completes its entry for free, and clearing a field boss during the weekly loop completes its entry with the same trip. The Familiar database /familiars and the boss database /bosses show what exists, and the show what exists, and the Adventure Book /adventure-book shows what is still missing, so the systems reinforce each other instead of duplicating work.

The same overlap applies to quests: story steps pass through regions full of chests and viewpoints, so completing the story with the book open finishes the exploration entries along the way. The quest database /quests shows the story route, and the map shows what sits on it.

Track completion without a spreadsheet

The book is its own tracker: the Adventure Book /adventure-book page marks what is done and what is missing, with the locations and requirements for every remaining entry. A session plan is three lines: the next point threshold, the entries that reach it, and the map route that visits them. When the threshold is reached, the reward is banked and the next threshold becomes the plan. The book, the Orbis map /map, and the , and the quest database /quests together replace memory with a checklist, and the completion percentage stops being a rumor.

Review the book once a week rather than every session, because most entries complete themselves during normal play. The weekly review scans for three things: entries that finished silently, thresholds that are now reachable with the entries already done, and combat entries the team can now clear thanks to new power. The progress database /progress shows the achievements alongside, and the boss database /bosses lists the field bosses the book's combat section needs, so the review fits into the standing weekly loop instead of adding a separate chore.