DragonSword : Awakening places the player on the Continent of Orbis and advertises an open world, Dungeons and Familiars. That is enough to start an exploration record, but not enough to publish a complete map or declare what every Familiar does. This guide gives you a short loop for investigating a route, testing a Familiar and preserving evidence for future updates.
Make the story objective your anchor
Before leaving the current route, read the exact objective and identify the last named landmark. Open the map and mark one nearby point that has a clear purpose. Do not choose five unexplained icons at once. Travel to the first point, inspect its interaction, and return to the objective if the game does not provide a reason to continue.
When the route is blocked, copy the requirement. A lock may mention a quest, hero, skill, item or other system. Keep that text in your notes and do not translate it into a guess. The requirement is the evidence that a later guide needs. A public map that shows a destination but not the access condition is incomplete for a new player.
Use one exploration experiment
Choose one question such as “does this Familiar change traversal?” or “does this landmark open after the current story step?” Keep the party, food and equipment stable. Perform the action once, return to the same point, and repeat. Record the visible effect, the time, the requirement and anything that changed on the map. If the result is not reproducible, mark it as an observation rather than a route rule.
This method also helps with hidden-looking objects. An icon may be a resource, a combat encounter, a story marker or a system tutorial. The purpose should come from the current game interface. Do not use a search result’s label as proof that the object is a collectible or a puzzle.
Document a Familiar correctly
Open the Familiar panel and copy the displayed name and category. Record the effect exactly, including whether it is conditional, active, passive, local to the hero or shared by the party. Note the source and requirement shown by the game. If the interface calls the Familiar a companion, mount or something else, retain that wording rather than applying a genre assumption.
Run a before-and-after test. Travel a short route without the Familiar, then repeat with it. If the difference involves combat, use the Combat hub and keep the enemy the same. If the difference is movement, use the same path and avoid changing settings. A Familiar that feels faster may be changing stamina, camera behavior or route access rather than speed itself.
Avoid “best Familiar” shortcuts
Recent independent pages create demand for best-Familiar and Familiar-unlock searches, but their rankings can hide the mode and version. A useful guide says why a Familiar helped, in which route, with what party and on what date. It also says when the effect did not help. A Familiar that assists exploration may not be the strongest combat choice, and the official store page does not publish a universal ranking.
If two Familiars solve the same route problem, compare the cost, requirement, control and repeatability. Preserve both records. The goal is to help a player choose from what they own, not to push every reader toward one unverified table.
Dungeons and return routes
The store page names Dungeons, but this audit did not verify a complete dungeon list or reset schedule. When you discover one, record its displayed name, entrance, party rule, difficulty, reward text and whether it changes the overworld. Write a separate combat note if an enemy or ailment is the reason for failure. Keep dungeon route details distinct from a global map claim.
After a dungeon run, return to the same map point and check whether a marker, reward, quest state or Familiar interaction changed. The return test can reveal whether the activity is a one-time story step or a repeatable system, but do not call it repeatable until the interface provides a clear action or you have reproduced it.
Co-op scope
Steam lists Online Co-op. In a cooperative exploration session, record who hosts, which objective appears, what each player can interact with and what reward or progression screen each player receives. Do not assume that one player’s story completion moves the other player’s account forward. The official page does not explain that rule, and a community session is not enough to generalize.
Exploration notes template
- Date and public build label, if the game shows one.
- Region or landmark name exactly as displayed.
- Current story objective and access requirement.
- Familiar name, category, effect and source.
- Route tested and whether the result repeated.
- Enemy, dungeon or co-op condition that changed the result.
- Screenshot or official link for any claim that should survive an update.
Is there an official Orbis map?
The Store page confirms the open-world setting but does not provide a complete public map. Use in-game evidence for a coordinate or access claim.
Can every Familiar be called a mount?
No. Familiars are confirmed as a feature, but each Familiar’s current category and use must come from its panel.
How do I handle an unexplained lock?
Copy the requirement, mark the location, and continue the story route until a source or in-game system explains it.