Start with the support you need for the next fight. Write down the effect, who should get it and whether it needs to be refreshed during the run. For example, a caster who runs out of MP and a caster who needs faster casting have two different jobs for support.
Choose a support skill and its recipient
These examples come from pinned L2J Mobius CT0 Interlude class trees and skill records. Check the rank you have learned and the server’s current rules before planning around a skill.
| Support class | Example skills | What to check |
|---|---|---|
| Prophet | Haste and Acumen | Haste affects physical attack speed and Acumen affects casting speed. Check the buff icon on the character you targeted. |
| Elven Elder | Recharge | Check that the intended recipient can receive MP, then compare their MP before and after the cast. |
| Shillien Elder | Empower and Recharge | Empower affects magic attack. Record its buff icon separately from the MP change after Recharge. |
| Warcryer | Chant of Battle | This physical attack buff uses PARTY. Ask intended party recipients nearby to confirm the icon. |
| Overlord | The Glory of Pa’agrio | This magic defense buff uses PARTY_CLAN. Use the recipient check below. |
The same Prophet tree lists Blessed Body and Blessed Soul, and their skill records affect maximum HP and maximum MP respectively. Check the resource limit on the intended character.
Check who actually received the effect
Test one effect at a safe spot. For The Glory of Pa’agrio, the PARTY_CLAN handler checks nearby players for the same party or clan along with other eligibility rules. Check recipients when your group changes or spreads out.
- 1Write down the skill, the caster and the intended recipients. For a single-target cast, select the right character.
- 2Record each recipient’s buff icon, remaining time or current MP as appropriate. Ask teammates what their own client shows.
- 3Cast once and recheck. If someone missed the effect, confirm the target, party or clan membership where relevant, and position. Check the client message before trying again.
| Test | Before and after | If the effect is missing |
|---|---|---|
| Acumen on the caster | Buff icon and remaining time on the selected character. | Check whom you selected and whether the cast completed. |
| Recharge on the damage dealer | MP on the damage dealer and remaining MP on the support. | Check eligibility and range, then use the client message to decide what to try next. |
| Your support skill | Write the intended recipients and what they observed. | Change one condition and check again. |
Practice example. Your caster has Acumen, but the party keeps waiting for that caster’s MP. Keep the buff setup the same and ask an Elder to test Recharge on the intended damage dealer between pulls. Record whether MP increased and whether the Elder can still support the next pull.
Questions before the next run
Why did Recharge fail on another support character?
The Recharge record and its target condition show that in this implementation it targets one character and excludes a recipient who has learned Recharge. Check the recipient’s skills and the server’s own rule.
How many buffs can I plan around?
Check the limit and durations on the server where you play. This implementation’s shipped configuration has separate settings for ordinary buffs and songs or dances. Use the dances and songs guide to plan those effects and their refresh cost.
Can I use a second client or a buff NPC?
Check whether your server allows an extra client and what any buff NPC actually offers. Confirm that the intended character received each effect, then decide which active healing or MP support the group still needs. The PvE party guide helps assign those jobs.


