A duel is a better practice setup than trading unannounced hits outside town. It gives both sides an explicit challenge and a defined end. Agree on what you are testing before sending it: a short damage comparison, a defensive response, or party target calls.
This guide covers the original Interlude duel system. A private server can change its checks or arena setup. If its published rules differ, use those rules rather than treating another server's duel settings as proof of a bug.
Start a one-on-one duel
- 1Find your practice partner and agree on the test.
- 2Finish any existing combat and choose a suitable, quiet location.
- 3Select your partner and use the Duel action, or enter
/duel. - 4Have the other player accept the challenge. Start only when the duel begins.
The original Interlude patch notes introduce /duel, the Duel action, and /partyduel. The normal one-on-one result is reached when an opponent has 1 HP left, rather than by deliberately killing them.
Start a party duel
The challenging party's leader uses Party Duel or /partyduel against a member of the opposing party. Both sides need to be ready; one unavailable teammate can prevent the request.
After acceptance, the original system moves the parties to a party-duel arena. Check that everyone has arrived before your shot caller starts the exercise. The Interlude request handler in L2J Brasil separately checks leadership, opposing-party membership, distance and each party member's eligibility. That is an open-source implementation cross-check, not a guarantee of every private server's configuration.
If you target a member of the other party and they see no prompt, ask their leader to check. In this L2J Brasil implementation the prompt goes to that leader, who must finish any other open request first. The original notes also describe the leader’s Decline Duel setting. Check those two things before resending.
Do a readiness call before each attempt: “ready” should mean the player has finished shopping, recovered and closed other requests. It is quicker than having the leader repeatedly send a challenge while everyone guesses who is blocking it.
Why the challenge will not start
Use the system message as your first clue. Check your own character, then the recipient and, for a party duel, the remaining teammates.
| Message or situation | What to check |
|---|---|
| Already fighting or dueling | Finish that activity, then retry. |
| HP or MP too low | Recover both; the reference implementation rejects values below half. |
| Private store or manufacture open | Close the shop before trying again. |
| Invalid location | Move away from peace, siege and PvP zones. |
| Riding or fishing | End that activity before the next request. |
| Opponent too far away | Bring the challenger and the selected opponent closer together. |
| Opponent busy | Let them finish the other request first. |
| No challenge is received | Check the client's Decline Duel option as well as the server message. |
The activity and resource checks above are visible in the Interlude character eligibility code. The original notes also list Olympiad participation among the restrictions. For party duels, a teammate can have a restriction even when both leaders look ready.
Make the practice round useful
Change one condition at a time. If you swap a weapon, armor set and buffs together, the result will not tell you which change helped.
For a damage comparison, record each participant's equipment and buffs before the first round. Keep positioning and the chosen attack consistent. Write down what happened rather than relying on the winner announcement alone. Several comparable attempts are more informative than one unusually strong hit.
For party practice, pick one task: everyone assisting the same target, protecting a healer, or responding to a target change. Stop the exercise if the group loses track of the task. Discuss the missed call before trying again; immediately repeating a chaotic round usually produces the same confusion.
End the test cleanly
Use /withdraw if you need to end the duel early. The original system normally restores the participants' pre-duel HP, MP and CP, but the original notes exempt a one-on-one duel interrupted by attacking an NPC or being attacked by one. Practice away from wandering monsters and do not assume every abnormal ending provides a reset. The distinction between ordinary and abnormal endings is also present in the reference duel implementation.
Afterward, check your actual bars, equipment and buffs before returning to farming. A duel result is useful feedback on that controlled test, not a universal ranking of two classes.
For coordinated party practice, set up a short target-assist macro before the first round. You can also browse Interlude servers and check each operator's duel rules before joining.


