Moonlighting gives a character access to two vocations at once, but a useful combination begins with understanding the assigned roles and the current unlocks. This guide explains what the official description establishes, how to compare a pairing and where old job guides or another Dragon Quest title can mislead.
- Separate a character level from vocation progression
- Confirm access before designing the pairing
- Read both assigned action sets
- Treat a vocational perk as its own feature
- Evaluate the pairing within the whole party
- Hold battle behavior steady during a comparison
- Keep training items and early offers distinct
- Use a Reimagined source for any detailed unlock route
1. Separate a character level from vocation progression
Character experience and vocation proficiency are separate progression measures. The producer describes configurable rewards, including proficiency, experience and gold, alongside damage settings. Check which value you intend to change before using an old battle-count rule. Increasing the proficiency reward is his suggested way to accelerate vocation training while keeping other challenge choices. The demo has progression caps; its restricted values do not describe the full adventure.
Sources: Current Steam listing / Developer practical tips / Official demo transfer conditions
2. Confirm access before designing the pairing
The developer describes vocation changes becoming available first and Moonlighting later. Build a plan using what the current game actually permits, then revisit it when the second assignment opens. This avoids presenting a late-game combination as an opening requirement. No cited source establishes one fixed hour for the unlock. A completion video may be much faster or slower than your route without changing the progression condition that the game eventually introduces.
Sources: Developer vocation explanation
3. Read both assigned action sets
Both assigned vocations supply actions and perks. The producer recommends keeping a mastered vocation assigned while training a new one. His Xbox Wire guidance also warns that skills from a mastered vocation are removed when you switch away. Do not plan around permanent access to every learned action. Check the remaining command set after a change, then confirm that the party still has the function you intended to keep.
Sources: Current Steam listing / Developer practical tips
4. Treat a vocational perk as its own feature
The revised battle system gives each vocation a distinct ability, with effects ranging from offensive actions to ally support. Keep that feature visible when comparing assignments; a list of ordinary spells alone does not describe the full choice. Read the current perk text before treating it as an automatic bonus that always applies. The overview does not give the activation condition and numerical strength for every perk, so this guide does not invent a universal trigger or ranking.
Sources: Current Steam listing
5. Evaluate the pairing within the whole party
Two offensive vocations on one character may still leave the group needing another role. Look at the other characters and the problem the encounter created, then choose an assignment that has a clear purpose. This is a comparison method rather than a fixed best team. The documented access to two sets of actions creates flexibility, but does not promise that duplicating a role is always beneficial or that every encounter asks for the same balance.
Sources: Current Steam listing
6. Hold battle behavior steady during a comparison
Tactics affect what automatic combat does with the available actions. The producer warns that Show No Mercy can spend magic points quickly, while exclusive healing can leave the party failing to fight back. He suggests Fight Wisely as a balanced starting choice and deliberate manual control for bosses. Compare the pairing under a known tactic; changing both at once makes the result harder to attribute to the vocation choice.
Sources: Current Steam listing / Developer practical tips
7. Keep training items and early offers distinct
Seeds of Proficiency appear in the launch early-purchase bonus, with the notice also saying they can be obtained through progression. The dated bonus deadline does not define the only source of the item. Check current owned rewards before building a training plan around an old offer. The demo also caps proficiency and does not expose its rewards. Do not confuse a limited sample or an expired purchase condition with the full-game possibilities available through normal progression.
Sources: Launch and dated purchase conditions / Official demo transfer conditions
8. Use a Reimagined source for any detailed unlock route
The game revises the combat and vocation systems, while the news feed also promotes another Dragon Quest title. Confirm the exact game before importing a job tree, monster synthesis rule or save transfer condition. This guide deliberately stops short of a complete unlock chart because the cited overview does not establish every prerequisite. When you need a specific intermediate vocation, use its current requirement rather than projecting an original or Nintendo 3DS rule onto the new screen.
Sources: Current Steam listing / Released April progression corrections
| Pairing check | Question to answer |
|---|---|
| Access | Has this feature actually unlocked? |
| Purpose | Which action or perk solves the observed problem? |
| Comparison | Are tactic, encounter and other changes understood? |
Keep one clear purpose for a pairing and read both current action sets. Verify detailed unlock requirements in the current game before committing to a long training route.
Related guides
Distinguish level, proficiency and story access. Use both vocation action sets deliberately, compare them within the whole party and keep old-edition rules and dated bonus offers out of a current unlock plan.
Sources checked October 14, 2026. Published facts are linked beside their explanations. Planning and practice suggestions are editorial advice rather than verified optimal builds.
Comment
No comments yet. Be the first to post one.