DragonSword: Awakening Beginner’s Guide: Your First Hours in Orbis

Begin with “1. To the Orbis Kingdom” and keep the main quest selected. The opening route introduces movement, combat, companions, and the first mercenary jobs in a useful order. Pick up obvious items on the path, but do not stop to clear every icon or farm levels before the game asks you to. If an objective is unclear, find its exact ordered steps in the Quests.

Complete the tutorial prompts as they appear—especially Signal Skills, Team Setup, Hero Level Up, Equipment, Karma, and Familiars. These are unlocks and lessons, not a list of systems you must master immediately. If a menu or activity mentioned elsewhere is still unavailable, the usual next move is to continue the main story, not search for a hidden grind.

A Signal Skill is a response to a combat condition. One hero uses a skill that applies a status such as Airborne or Knockdown; when another hero’s matching Signal becomes available, tag that hero in. Practice this two-hero handoff before worrying about a perfect three-character rotation. You can inspect which skill applies and which skill answers each status in the Team Builder.

If the Signal never appears, check three things: the first skill must actually apply the required status, the receiving Signal must be unlocked, and the target must not interrupt or resist the setup. Seeing the same status word on two skills is not enough—the direction matters. Once one handoff works reliably, add a third hero whose skill continues from the second hero’s status.

Use three jobs when choosing from the heroes you actually have: an opener who applies a status, a connector who can answer that status and create the next one, and a finisher who answers the connector. The middle slot is the important part because it must support both sides of the chain. Check each hero’s current skills and unlock requirements in Heroes.

Do not bench a favorite just because a ranking uses different assumptions. First see whether changing the order or one partner creates a valid route, then test that route against ordinary enemies until you can recognize the Signal prompt without staring at the skill bar. When only one edge is broken, keep the working pair and compare replacements for the missing slot in the Team Builder.

Keep your active trio close enough in level to survive the same story fights, and prioritize the skills that make their Tag route work. Avoid upgrading every newly unlocked hero just because a notification appears. When several upgrades compete for the same items, plan one reachable milestone at a time with the Hero Upgrade Materials.

Equip compatible drops as you receive them and use small upgrades only when the story starts to push back. Early on, correct body slots and usable stats matter more than a perfect five-piece plan. Save expensive enhancement, reroll locks, set chasing, and Rune optimization for equipment you expect to keep. Use the Build Planner when you are ready to compare a real loadout instead of filling every slot on day one.

Lost objective: reopen the active quest, read the next ordered step, and follow its named location or prerequisite. Use the World map only after you know what you are looking for; map completion, distant chests, and optional gathering are easier to return to after waypoints and movement options open.

Combat wall: confirm that all three heroes are equipped and leveled for the same point in the story, reproduce one working status-to-Signal handoff, and then decide whether the problem is damage, survival, or a broken chain. Change one thing at a time. If equipment is the weak link, compare only compatible replacements in the Equipment database before spending more materials.

A good first-session stopping point is simple: you advanced the main quest, completed every tutorial that appeared, tested one Tag handoff, invested only in the trio you are playing, and left optional map cleanup for later. There is no reroll target or mandatory opening team in this guide. Your next step should come from the story objective or from one clearly identified problem—not from trying to finish every system at once.