Run your AION 2 guild without spreadsheet chaos.

Start with the community you can support

Before recruiting, write down the activities you intend to organize, the hours you can reliably host and the sort of atmosphere you want. A small community with two dependable sessions can make a clearer promise than a new guild advertising every activity at every hour. Let the profile describe the group you can support today.

Separate membership from event selection. Somebody may be welcome in the social community without having a permanent place in every progression run. Explaining that early prevents an accepted application from becoming an accidental promise of a weekly seat. Publish the attendance and preparation expectations for each type of session rather than relying on a vague casual or hardcore label.

Write an AION 2 recruitment profile with useful details

The guild form collects region, server, faction, languages, playstyle, timezone, prime time and requested roles. Use the description to explain the information those fields cannot capture: normal event days, learning expectations, communication preferences and the kind of player who would enjoy the group. Avoid repeating the guild name several times while leaving the actual schedule unclear.

Descriptions accept 80–3,000 characters. A concise, specific profile fits that space well. Start with the most useful facts, add a short account of the group’s purpose and finish with what applicants should send. Public profiles go through content review before directory inclusion. Editing a reviewed profile returns it to review, so keep updates accurate and deliberate.

Review applications consistently

Read availability before judging an applicant’s class. A skilled player who cannot attend your schedule is not a solution to an empty weekly seat. Then discuss the requested role, relevant experience and preparation. Ask the same core questions across applicants so a friendly conversation does not hide different expectations about commitment.

Applications are reviewed in the private dashboard queue. Keep questions relevant to participation and use character-level information rather than asking for game credentials. If a player is not a match, a short explanation about schedule, roster availability or the run’s objective is more useful than silence or a broad judgment about their ability.

• Which of our scheduled sessions can you attend from start to finish?
• What role can your current setup cover, and what are you still learning?
• Are you looking for a community place, a trial session or a regular event slot?
• Which communication method can you comfortably use during an encounter?
• How much notice can you normally give if your availability changes?

Give an officer a clear responsibility

The current workspace supports one owner and one additional manager. Invite somebody you trust to help with a defined task, such as applications or the next event. Explain the decisions they can make and where you want a handover. Access to a website dashboard does not establish their authority over an in-game legion.

Agree on who handles cancellations, replacement decisions and reports from applicants. A small amount of written process prevents two officers from offering the same seat to different people. Keep private signup-management links and account sessions private; event links and applicant messages belong in the channels appropriate to their visibility.

Create an event with a complete invitation

Choose the destination and objective before setting capacities. NC’s current Global product description includes five-player party content and ten-player group dungeons, but the specific encounter determines its current entry conditions. Confirm those in the client, then configure the roles your group has agreed to use. The event form allows manual capacities; it does not certify a composition.

Enter the start date in the selected timezone and give the session a realistic duration. Decide whether the displayed time is assembly or actual start, then state the other time in the notes. A named timezone and a dated event link are clearer than an undated UTC offset, especially when your members live in places with different daylight saving rules.

Choose visibility intentionally. Public events can appear in the community calendar. Unlisted events stay out of the feed but remain accessible to people with the link. Guild-only events require an account and membership. Select the audience you can support, rather than using an open event as a substitute for discussing readiness with new players.

Reference: NC · AION 2 on Steam · IANA · Time Zone Database

Manage confirmed players and the waitlist fairly

Confirmed signups fill the configured role capacities; full roles send additional signups to the waitlist. Players declare class and role separately. Review the actual responsibility each person has offered before treating the roster as ready. If a player needs to switch role, have them update their signup and recheck capacity rather than counting both the old and new commitment.

Write the selection process before the event fills. You might prioritize agreed roles, full-session availability and a clear learning objective, but tell applicants what matters. If you need a substitute, contact an eligible player, confirm they can attend and manually promote them when the relevant seat is available. The current product does not automatically promote a player when someone cancels.

Do not ask backups to hold an entire evening without a decision time. Explain whether they should stay available and what they can do if they are not chosen. When an organizer must change capacity after signups, existing confirmed seats constrain the edit: resolve those commitments with the players before trying to remove the seats they occupy.

Run the session, then close the loop

Before the first pull, confirm attendance, the meeting point, the current encounter and the group’s responsibility split. Give one person the main calling role and agree on a simple way to request a pause. For learning runs, make space for a brief explanation and one actionable observation after a failed attempt rather than several competing instructions.

If you cancel, update the event status and send a message through your existing community channel. A stale event link wastes people’s time even if the cancellation was mentioned elsewhere. When the session is over, mark it complete and note what would improve the next invitation. The dashboard does not currently generate historical attendance reports, so do not promise automated records.

What you can use today

Guild discovery, a basic guild profile, applications, manual party planning and one-time event signups are available now. Public and unlisted event guests can join without an account, then use their private management link or the same browser to update or cancel. Guild-only events require membership. Event pages also offer timezone display and a calendar download.

Recurring events, automatic Discord messages, extended attendance reporting and extra management permissions are proposed Pro features. There is no live subscription checkout. Plan your current workflow around the tools that are available: one event, one shared URL, declared roles and a deliberate manager review of the roster.

Common questions