WvW Alliance Verification

WvW Alliance Verification automatically assigns Discord roles based on a member's Guild Wars 2 World vs. World (WvW) team and their guild membership. It is built for WvW alliances: give everyone in the alliance a shared role, and optionally a separate role for each guild that is part of it.

Aleeva reads each member's WvW team and guild membership from their linked Guild Wars 2 API key, so members need a valid key stored with Aleeva. One part (pre-assignment) also needs the key to have the WvW permission.

Running a big community?

If the built-in options do not cover how your alliance is organised, we are happy to build custom role mappings that match your use case. Tell us what you need on the support server.

The pieces

Alliance role

The alliance role is the single Discord role that everyone in the alliance receives. How a member qualifies for it depends on the verification mode below. Aleeva keeps it in sync: if a member no longer qualifies, the role is removed again.

Verification mode

You choose one of two modes for who gets the alliance role:

• Guild only (default). A member gets the alliance role if their account is in at least one of the guilds you added to the alliance. Their WvW team is not considered.
• Team based. A member gets the alliance role if their account is on the same WvW team as the alliance's follower guild. Guild membership is not required. This mode needs a follower guild (see below).

Mode	Alliance role granted when	Requires
Guild only (default)	The member is in at least one listed guild	At least one guild and the alliance role
Team based	The member is on the follower guild's WvW team	A follower guild and the alliance role

Guilds and per-guild roles

You add the guilds that belong to your alliance. For each guild you can also set a separate Discord role that its members receive.

Per-guild roles work the same way in both modes: a member gets a guild's role when their account is in that guild, independent of the alliance role. So in team-based mode a member who is in a listed guild but on the wrong team can still get that guild's role without the alliance role.

You can add, edit and remove guilds at any time. Free servers can link up to 5 guilds.

Premium

Link an unlimited number of guilds. Alliances that outgrow the 5 guild limit can list every guild they contain, each with its own Discord role, without dropping one guild to make room for another.

Follower guild (team based)

The follower guild defines which WvW team the alliance is on. In team-based mode Aleeva compares each member's team to the follower guild's team. Team-based mode cannot be enabled without a follower guild. In the settings, each listed guild shows a marker for whether it is currently on the same team as the follower guild.

Role for members in the wrong team (team based)

Optionally you can set a role for alliance members who are in one of your guilds (or the alliance) but on the wrong WvW team, which helps you spot members who still need to transfer. This feature is currently in beta.

Premium

Setting a wrong-team role requires Premium. Team-based mode works without it, but members on the wrong team are only visible by the alliance role they are missing, so you have to spot them yourself instead of having Aleeva mark them for you.

Pre-assignment (team based)

WvW teams change at the weekly reset. With pre-assignment Aleeva can grant the alliance role early, before reset, based on the member's selected alliance guild's upcoming team. You choose how far in advance, from 1 up to 24 hours. Because Aleeva has to read the member's selected alliance guild, pre-assignment only works for members whose API key has the WvW permission.

How it all fits together

When Aleeva verifies a member, she assigns every role in a single evaluation.

Guild only

• Member is in at least one listed guild: they get the alliance role.
• For each listed guild the member is in, they also get that guild's role (if one is set).
• Member in no listed guild: neither.

Team based

• Member is on the follower guild's team: they get the alliance role (guild membership does not matter).
• For each listed guild the member is in, they also get that guild's role (if one is set), even if they are on the wrong team.
• Member in a listed guild but on the wrong team: the guild role and, if configured, the wrong-team role, but not the alliance role.
• With pre-assignment on, a member whose selected alliance guild moves to the follower guild's team gets the alliance role early, during the window before reset.

Alliance roles are evaluated together with your other Aleeva role mappings, such as Guild Rank Mapping, so everything stays in sync in one pass. If you also use custom role mappings, they can interfere with alliance verification; Aleeva shows a warning in the settings if it detects them.

When roles are updated

Aleeva rechecks a member's alliance roles:

• when they join the server,
• when they link or change their API key, or their account data changes,
• at the weekly WvW reset,
• during the pre-assignment window before reset,
• on a regular background recheck,
• when an admin uses Recheck roles of all members in the settings (available once per hour).

Setup

WvW Alliance Verification is server-based, so you configure it with the command. Open the Guild Wars 2 Feature Setup and select WvW Alliance Verification, then:

1. Set the alliance role.
2. Choose the verification mode. For team based, set the follower guild first.
3. Add the guilds in your alliance, and give each a role if you want one.
4. Optionally enable pre-assignment (team based) and set a wrong-team role (team based). Premium
5. Activate the feature.

Members are matched through their own linked Guild Wars 2 API key. Removing the last guild turns the feature off again.