AION 2 raid & party composition planner.

AION 2 Global party and raid sizes

NC’s current Global Steam description distinguishes solo challenges, five-player party content and ten-player group dungeons. Start with the destination you intend to enter, then check that encounter’s current entry conditions in the client. A general format does not establish the level, equipment requirement, reward eligibility or exact role distribution for every encounter.

Older reveal articles describe four-player and eight-player formats. A guide can be official and still describe an earlier design. Check the region and publication date before copying its roster. LegionBoard starts a fresh manual plan with five seats; you can change every role capacity for the activity you have agreed to run.

Reference: NC · AION 2 on Steam

How to use the party composition planner

The planner above is available without an account. It records the party name, activity, role capacities and players you enter. It counts confirmed seats, displays gaps and marks additions beyond a role’s capacity as waitlisted. It does not inspect characters or validate the game’s entry requirements. Ask each player to check those separately.

Start with the responsibilities your group needs rather than a list of class names you hope to recruit. A useful plan explains both who is coming and what they have agreed to do. When a friend can cover several jobs, choose one responsibility for this run so they are not accidentally counted twice.

1. Give the plan a recognizable name and choose an activity. Include the dungeon or practice objective in the name if that helps your group.
2. Set Tank, Healer, DPS, Support and Any capacities. Check the total before adding players; every category contributes seats to that total.
3. Add a character name, class and declared role for each player. Use names your group recognizes and confirm availability outside the planner.
4. Read the role gaps and waitlist together. A full damage category does not fill an empty healing category.
5. Copy the summary or share a plan link. For actual attendance collection, create a separate event and let players RSVP there.

What Tank, Healer, DPS, Support and Any mean

These five labels are organizer-controlled responsibilities. Class and role are independent fields in LegionBoard. A Templar selecting DPS is not automatically moved to Tank; a Chanter selecting Support does not also fill a Healer seat. Confirm the player’s actual setup and the encounter’s needs before relying on them for a job.

Support is especially easy to misunderstand. Write down what you expect: a particular form of assistance, an agreed backup task or simply a flexible contribution. Any means the organizer has left a seat without a fixed role requirement. It does not mean that one player can cover every missing responsibility simultaneously.

A five-player planning example

For a first practice session, one possible starting point is one Tank, one Healer and three DPS seats. This creates five clear commitments and is easy to explain in a recruitment message. It is an editorial example, not a statement that every AION 2 dungeon requires that split or that it produces the best performance.

If your group wants a dedicated Support seat, discuss the tradeoff and change a capacity while keeping the intended total. For example, one Tank, one Healer, two DPS and one Support still makes five. Do not add support on top of an already full five-player plan and discover the extra seat only at entry.

A teaching run also needs a learning agreement. Decide whether the group will explain each encounter, how long the session lasts and whether mistakes are expected. An accurate five-person roster can still fail socially if one player expects a fast clear while four expect to practice. State the objective before inviting replacements.

Planning a ten-player group

A ten-player plan needs assignments as well as totals. Begin with the encounter’s current requirements, ask who can cover each responsibility and only then set capacities. Ten names in a spreadsheet do not show whether an assignment is uncovered, whether two people expect to lead or whether a backup can attend for the full session.

If your group chooses to work as two five-person teams, write the team assignments in the event notes or your shared discussion. LegionBoard’s planner counts one combined roster; it does not automatically allocate subgroups, distribute support effects or check whether a split is legal in the current encounter. Review each team manually when a split matters.

For a learning session, an illustrative draft is two Tank, two Healer and six DPS seats, but the encounter and your players may call for something different. Agree on the plan with the group before using it. Avoid treating a convenient template as proof that two tanks or two healers are mandatory.

Role gaps, substitutes and the waitlist

An open role and a waiting player are different pieces of information. If a Healer seat is empty and a DPS player is waiting, ask whether that player can actually change responsibilities. Changing their label to make the display look complete does not prepare them to heal. If they agree to switch, update the roster and tell the rest of the group.

Set expectations for substitutes before asking them to keep an evening free. Explain when you will make a decision, whether they need to remain online and what happens if nobody drops out. A waitlisted signup is not a promise of a seat. Avoid asking several backups to arrive with no explanation of how you will choose between them.

In the browser-local planner, changing capacities recalculates seats in the existing player order. Removing someone leaves their seat open until you adjust the plan; it does not automatically promote another person. Event RSVPs have a separate live roster, where managers manually confirm an eligible waiting player when capacity is available.

The check before the first pull

Use the final few minutes to check things the planner cannot know: attendance, destination, eligibility, equipment readiness and the group’s agreed communication method. A filled roster represents headcounts, not an assessment of skill or a guarantee of a clear. Ask short questions that produce useful answers rather than asking whether everybody is ready in general.

Choose one caller for time-sensitive decisions, agree on how to request a pause and tell new players where to meet. If a player arrives late, confirm their responsibility rather than restarting the whole conversation. After the session, record one practical improvement for the next invitation, such as an earlier check-in or clearer target instructions.

• Everyone is entering the same region, server context and encounter difficulty.
• Each player has checked current entry and reward conditions in the game.
• The planned role matches what each person can and wants to provide today.
• The start time, finish time, meeting place and communication channel are understood.
• The organizer has explained learning, replacement and cancellation expectations.

Share the composition and collect real signups

Copy summary produces text you can paste into your existing group chat. Share plan creates a link containing a snapshot of the plan, including the character names you entered. Recipients can open that snapshot without signing in. Changes they make are local to their own browser; this is not a shared document that everyone edits in real time.

Local plans are saved in this browser. They are not an account backup, and clearing browser storage can remove them. Keep a copied summary when the plan matters. Share only character names and other information you are comfortable sending to link recipients; avoid putting private contact details in a party title or player field.

When you need attendance decisions, create an event from the dashboard, enter the date and timezone, configure its capacities and share its RSVP URL. The event roster is separate from the planner and must be configured separately. Guests can join public and unlisted events; guild-only events require an account and membership. A copied plan does not silently create an event or reserve anyone’s seat.

Common questions