Last Asylum Alliance Guide: Ranks, Officer Titles and Auto Rally

For Last Asylum: Plague R5s and R4s who want to know how alliance roles really work, what each officer title does, how auto rally works and which habits separate alliances that win events from alliances that react to them.

The gap between a competitive Last Asylum: Plague alliance and a messy one is almost never about the power scores on the roster. It is about coordination.

Fifteen Doctors working as one unit will beat a stronger alliance with no system, in every event that matters: Alliance Duel, Hunt Battle, Elixir Scramble and Kingdom War.

This guide covers how ranks and roles work, what each officer title means and when to give it, how auto rally works and when to use it, the systems that keep 50 to 100 members aligned across time zones, and the rules top alliances enforce.

Alliance ranks

Last Asylum: Plague alliances hold up to 100 members across five ranks. Each rank has its own permissions.

R5 (Leader): full control. Sets the alliance direction, handles diplomacy with other alliances on the server, appoints and demotes R4s, assigns officer titles and makes the biggest calls. Only the R5 can promote or demote an R4, disband the alliance or reassign officer titles. The R5 should be the most consistently active player in the alliance. An R5 who disappears for days during war windows leaves a gap no R4 can fully cover.

R4 (Officer): the working backbone. R4s can accept and kick members within their tier, start rallies, manage territory and hold officer titles. An alliance can have several R4s. The best-run alliances give each R4 a clear job instead of having every officer do the same loose work. Once the roster passes 40 to 50 active members, clear roles become critical, and generalist R4s become bottlenecks.

R3 (Elder): trusted senior members, often reliable event players and rally contributors. R4 and above can promote and demote them. R3 works best as recognition for steady participation, not as a near-leadership seat. Handing R3 to new members to keep them around makes the rank mean less.

R2 (Member): established regulars and standard event contributors.

R1 (Recruit): new or probationary members, with limited permissions until they show activity.

The four officer titles

On top of ranks, the game has named officer titles. The R5 gives them to R4s. The four titles are God of War, Diplomat, Recruiter and Inspector. Each one maps to one lane of alliance work. In competitive alliances, titles should show who actually does that work, not who spends the most or has been around longest.

God of War

The combat title. The God of War owns offense: rally targets, march timing, war day assignments and attacks during Alliance Duel Kill phases, Elixir Scramble and Kingdom War. Give it to the R4 who is most reliably online during war windows and whose target calls members follow without debate. A God of War who is offline on Kill Day is a gap you cannot fix mid-event.

Diplomat

The server relations title. The Diplomat handles NAP (Non-Aggression Pact) agreements with nearby alliances, tracks who is hostile and who is neutral, talks to other alliance leaders and watches the map for threats before members get hit. It is the least visible R4 job and the easiest to neglect. Alliances that skip it tend to lose members the moment a stronger neighbor tests them, because nobody saw it coming.

Recruiter

The membership title. The Recruiter finds new members, runs screening, watches activity levels and flags members slipping below standard before they become a roster problem. The Recruiter should track the difference between members who contribute and members with high power but low event participation. Power score and real value to the alliance are not the same thing.

Inspector

The internal standards title. The Inspector checks that members follow alliance rules, tracks event participation, confirms pre-event prep (defense squads set, troop training running, resource stockpiles ready) and gives the R5 what they need to make roster calls. It saves the R5 from personally watching 80 members.

One rule covers all four titles: give them to players who are reliably online when that job matters, not to whoever has been around longest or spends the most. A Diplomat who is not tracking NAPs is not doing diplomacy. A God of War who is missing on Kill Day is not running war. Titles are working decisions, not rewards.

Auto rally and auto join rally

Auto rally lets members join rallies started by R4 or R5 officers without confirming each one. When it is on, the game sends the member's squad to the rally as soon as leadership starts it, within the member's settings.

Why it matters: in time-sensitive events like Elixir Scramble and Kill Day phases in Alliance Duel, the time between a rally starting and filling decides whether it lands full or fires short. Members with auto rally on help fill rallies without watching the game. In a 30-minute Elixir Scramble, a 15-member rally and a 20-member rally are very different.

How to set it up: auto rally should join R5 and R4 rallies only, not every rally from every rank. Members set to join anything can get their squads pulled into low-value targets that R3 members start without coordination. Auto-join officer rallies and confirm everything else by hand.

When to turn it off: before any event where your squad needs to stay home to defend. A member who reaches Kill Day with auto rally on and their squad out in a far rally cannot defend their base if it gets hit. The R5 or the God of War should remind members to turn auto rally off before every event where defense matters.

Coordination habits of competitive alliances

Brief before the event, not during it

The most damaging mistake is giving instructions during the event. By the time the message lands, the members who needed it have already decided. Send every critical instruction at least 24 hours before the event opens. For Kingdom War, start the briefing 48 to 72 hours ahead.

Coordinate spending

Before each major event, the God of War or R5 should tell members which packs give the best return for that event. One message stops 50 members from making 50 separate buying decisions that do not match what the alliance needs that week.

Standardize hero builds

When members build overlapping heroes, the alliance ends up with too many tanks and no supports, or too much damage and no frontline. The R5 should keep a recommended hero build priority so the roster has variety instead of duplicates.

Cover your territory

The territory that gets raided first is always the one with gaps during known offline hours. Plan online hours openly and spread coverage across time zones when your roster allows it. Do not try to hold ground in every direction at once. Expand along lines you can defend, where the alliance can respond together instead of being too thin to answer any single hit.

Set minimum participation standards

Define what active means before it becomes a problem. Active is not a power score. A big account that misses every Alliance Duel phase without notice costs the alliance more event score than a smaller account that shows up every time. Set standards you can see (event score thresholds, response times, troop training participation) and enforce them on patterns, not single incidents.

Use an alliance Discord

The most competitive alliances do not run events from in-game chat alone. Alliance announcements have character limits, and chat moves too fast during events for key instructions to stay visible.

An alliance Discord with a channel for each event (Alliance Duel, Hunt Battle, Elixir Scramble, Kingdom War), a leadership channel for R4s and R5 and an announcements channel for pre-event briefings is what makes keeping 50 to 100 members aligned actually possible.

Rules that hold and rules that fail

Rules that work are visible and have consistent consequences. Rules that cannot be checked, or that leadership enforces unevenly, stop working within days, however clearly they are written.

Rules that hold:

• Minimum event score per phase (visible in the event log)
• Auto rally on before offensive events (visible in rally fill rates)
• Defense squads set before defensive events (checked by screenshot)
• Stockpile check before major event windows (members report resource levels)

Rules that fail:

• "Spend efficiently" with no clear definition
• "Be active" with no defined minimum
• Rules that apply differently depending on how much a member spends

The rule that drives away your strongest members fastest: rewards the whole alliance won piling up with leadership instead of going to the members who contributed.

Doctors who invest big and show up for every event will leave an alliance where shared rewards flow to the R5 or get hoarded. Protecting the members who carry your results matters more than any single event.

Where Packsify fits

Packsify buys the Last Asylum packs you and your members pick through the official Apple or Google store, usually with 10 to 30% more pack value for the same budget. If you have not used it before, start with the Last Asylum top up guide and how we keep accounts safe.