Familiar Guide: Compare Travel Abilities, Sources, and Collection Goals

Start with the question you need to answer, not with a copied endgame build. The useful route is the one that matches your unlocked roster, current inventory, and next playable objective. The current catalog contains 29 Familiars with published categories, movement values, abilities, and source text; a collection goal should start from the ability the route needs. Familiars.

The Orbis map is for location questions: where is a named place, chest, resource, monster, NPC, dungeon, waypoint, or field boss, and which nearby points can be combined into one route? Start with official locations and treasure chests, then enable gathering, mining, monsters, or NPCs only when needed. Dense layers cluster at lower zoom so the terrain remains readable. Search can find records from a hidden layer, which is useful when the player knows a name but not the category.

Choose a search result or map marker and inspect its player-facing details before moving the view. Multiple selected results can remain visible for route comparison, while zooming separates clustered locations into individual points. Marking a treasure as found stores progress locally; Hide found turns the same map into a cleanup route. Copy link preserves the selected point and map view for another player. These controls answer different questions, so a found marker should never be treated as removed game content or a shared account state. World map.

Results are ranked against localized names, descriptions, roles, effects, sources, locations, missions, categories, and useful keywords. Arrow keys move the active result, Enter opens it, and Escape clears the current query. Each result keeps up to a few verified connections visible, such as an exclusive Karma, recommended hero, item source, map position, or system route. These links let the player continue the same question without retyping it. A map query loads the published map index only when needed, so other searches remain responsive.

Treat names, requirements, relationships, counts, and displayed values as evidence. Treat live timing, random outcomes, account-specific availability, and unlisted triggers as checks that still belong in the game. Map evidence comes from the published Orbis layers and the exact coordinates shown for their locations. Details may include coordinates, elevation, quantity, durability, or recommended power only when that value is available. A generic label remains until a public localized name is confirmed; it is safer than guessing a translation. Treasure grades and monster groups are filters, not rankings of route value. Search multiplicity indicates several known positions, not a guarantee that every spawn is simultaneously active.

A result’s category label explains what kind of page will open; the summary supplies context but does not replace the detail page. Multiple map locations are grouped with a count rather than duplicated as indistinguishable cards. The index uses public localized names and player-facing relationships. Unavailable areas do not appear, Belos material is kept separate from Orbis content, and unresolved rewards remain identified on the relevant system page. Familiars.

Compare one constraint at a time. Keeping the same target while changing only the route, hero, slot, or milestone makes the cost of that decision visible and prevents several assumptions from being mixed together. Orbis is the released world and therefore the default decision space. Belos remains clearly separated as a preview, while unavailable areas do not appear in normal map choices. Plan travel by grouping nearby verified points, checking waypoint access, and deciding whether completion or resource density matters more. A visually short path can still be impractical if it crosses locked content or ignores elevation. The map supplies geography and known labels, but it does not infer quest order, live respawn timing, or an account’s unlocked travel state.

When no result appears, shorten the query to the official name, clear only the current scope, and remove descriptive words one at a time. Search by the effect when an item name is forgotten, by the source when the target item is unknown, or by the location when several entities share a name. Do not treat the first high-ranked card as a recommendation; ranking measures text relevance, not combat power, farming efficiency, rarity, or account suitability. Open the detail record before making a resource decision. Items.

For a missing point, clear the narrowest filter, search its current localized name, and check whether the relevant layer is enabled before assuming the data is absent. For a completed treasure route, mark only points actually found and keep a copied link for anything that needs a second visit. Continue from a field boss to the encounter page, from a material to its item page, or from a quest location to the quest workspace. Recheck shared links after map data changes; coordinates remain evidence, while live availability and hidden conditions must be confirmed in game. World map.

Use global search as a router, then complete the decision in the specialized workspace. Move from a material result to its sources or planner, from a boss to exact phases and rewards, from a quest to its prerequisites, or from a map result to the selected location. If a localized query fails while the English official name works, keep the verified page and report the localization gap rather than inventing a synonym. Recheck results after a page update because available results and links can change with the published version. Finish by writing down one next action that can be verified: open a named page, test a rotation, visit a mapped point, confirm an unlock, or update the local plan after spending materials.