Your first dungeon: prepare your build and party

Choose the exact instance and difficulty

NC Japan’s official Global page lists Krao Cave, Urugugu Canyon, Fire Temple and Draupnir as Expeditions for up to five players. A dungeon name alone does not establish level requirements, gear requirements or reward rules. Read those in the current entry window.

A short check before entering

Do this check before assembling the party. It separates access problems from character-strength problems. If the entry window is unclear, use the game’s own message instead of borrowing a number from an old video.

• The region, instance name and selected difficulty match the guide.
• I meet the current entry requirements shown in the client.
• I understand when rewards are claimed and which resource they use.
• My build is saved and I know which parts are still targets.

Agree on three things before combat

Tell the group this is your first attempt. Agree who starts the encounter, who watches the important mechanic and what signal means to stop attacking. Do not assume everyone understands the same abbreviations.

A short message is enough: “First time here. Who starts, and what should I do when the mechanic appears?” When someone explains the boss, ask for the most important response first. The remaining details are easier to organize after seeing the fight.

Simplify your setup for the first attempt

Place basic attacks together and keep a defensive action easy to reach. Check skill descriptions, conditions and resource requirements. A plan to use everything immediately makes it harder to identify why a crucial action was unavailable.

Record your opener separately from your emergency response in the combo notes. The first attempt should show whether you can resume fighting after movement or a mistake. Do not choose a longer sequence merely because it contains more icons.

Watch the cause, not just the outcome

If you die, record the last thing you noticed: a ground area, a target change, missing resources or an unavailable action. Do not invent a mechanic you did not observe. Check the observation on the next attempt or in a current recording of the same instance variant.

If the group survives but the fight is slow, first look at gaps in attacking and time spent out of range. That is a different diagnosis from having the wrong equipment. One attempt cannot establish a universal stat priority.

Turn the run into a better build

After the run, note one thing that worked and one problem. Change only something related to that problem, then compare a similar attempt. Keep the earlier draft so you can return to the previous setup.

When publishing the build, include the instance, difficulty, region and test date. Separate your observations from recommendations borrowed from another guide. Readers should know what was actually tested and what remains a suggestion to try.