Managing Inactive Members in Your Evony Alliance

TL;DR: Inactivity is normal. How you handle it determines whether your alliance stays healthy or slowly decays. Define activity clearly, enforce a consistent 14-day policy, have polite conversations before kicking, and learn which retention patterns actually keep members engaged.

Defining activity: last-seen vs. participation

“Inactive” means different things to different alliances. You need a clear definition before you can enforce anything.

Last-seen activity measures when a member last logged into the game. This is the minimum bar — if someone has not logged in for 7 days, they are clearly not contributing.

Participation activity measures whether a member is doing alliance-relevant things: filling rallies, showing up for BoC or BoG when selected, donating to alliance tech, responding in Discord. A member who logs in daily to collect resources but never fills a rally or participates in events is “active” by one definition and dead weight by another.

The recommended approach: Track both, but weight participation more heavily. A member who logs in 5 days per week and fills rallies when called is contributing. A member who logs in daily but has not donated or attended an event in 3 weeks is not.

Metrics that matter:

• Login frequency (days per week)
• Event participation (available for BoC/BoG selection, filled rallies during kill events)
• Donation consistency (met alliance tech quota this period: yes/no)
• Discord responsiveness (responded to direct pings within 48 hours: yes/no)

The 14-day inactive queue

Every alliance needs a clear, documented inactivity policy. Here is the standard framework:

Day 7: friendly check-in

When a member has not logged in for 7 days or has not participated in any alliance activity for 7 days:

• An R4 sends a friendly DM: “Hey [name], noticed you’ve been quiet this week. Everything okay? We have BoC coming up on Saturday if you’re available.”
• Tone: concerned, not accusatory
• Record that the outreach was sent and when

Day 14: direct conversation

If there is no response to the day-7 message or the member has still not been active:

• R5 or senior R4 sends a direct message: “We need to hear from you by [specific date, 3 days from now]. If we don’t hear back, we’ll need to free up the slot for an active member.”
• Be specific about the deadline
• Be clear about the consequence
• Record the message and deadline

Day 17-21: removal

If the deadline passes with no response:

• Remove the member from the alliance
• Send a final message: “We’ve removed you from the alliance roster due to inactivity. You’re welcome to reapply when you’re ready to play actively again.”
• No public announcement, no drama
• Update the roster and open the slot for recruitment

Exceptions

• Members who informed leadership about planned absences (vacation, exams, military deployment) before going inactive are exempt from the timeline. Set a return date and check in on that date instead.
• Members in good standing who have a single week of inactivity during an otherwise consistent track record deserve more patience than chronic low-activity members.

The polite kick conversation

Kicking a member is uncomfortable. It is also necessary for a healthy roster. Here is how to handle it well.

What to say:

• Be direct but kind: “Your activity has been below our minimum for [specific period]. We need every slot filled with active members, so we need to make a change.”
• Acknowledge their past contribution if applicable: “You were solid during SvS last month. We appreciated that.”
• Leave the door open: “If your schedule changes and you want to come back, reach out.”

What NOT to say:

• “You’re being kicked for inactivity” (too blunt, sounds punitive)
• “The alliance voted to remove you” (creates a mob dynamic)
• “We found someone better” (disrespectful)
• Nothing at all (ghosting someone out of the alliance is the worst option)

Where to have the conversation:

• Private DM, never in a public channel
• If the member is not responsive on Discord, use in-game alliance mail
• If they are completely unreachable, the removal speaks for itself — just send the courtesy message

When to farm-alliance someone instead

Not every inactive member should be kicked outright. Sometimes the right move is to move them to a farm or sister alliance.

When a farm alliance move is appropriate:

• The member is a long-time contributor who is taking a break but plans to return
• The member has very high power and their presence in a sister alliance still benefits the server coalition during SvS
• The member explicitly asked for a temporary move rather than a full kick

When it is NOT appropriate:

• The member simply stopped playing and has not communicated
• You are using the farm alliance as a dumping ground to avoid hard conversations
• The farm alliance is already full of inactive members (that defeats the purpose)

Farm alliance rules:

• Set a maximum duration (e.g., 60 days) after which the member either returns to the main alliance or is fully removed
• Check in with farm-alliance members monthly
• Do not promise to hold their main-alliance slot unless you actually will

Retention patterns that work

The best way to handle inactivity is to prevent it. Here are the patterns that keep members engaged.

Consistent event rhythm

Members are most likely to stay active when they know what is happening and when. Post the weekly schedule every Monday — BoG on Wednesday, BoC on Saturday, boss rally windows daily. Never go more than a few days without an alliance-wide activity.

Public recognition

People stay where they feel valued. Recognize contributions publicly:

• Rally fill leaderboard posted weekly
• Shoutouts for consistent performers after BoC or BoG matches
• Role promotions announced in the general channel with a reason (“Promoted to R3 for consistent rally fills and donation record”)

Meaningful communication

A dead Discord kills alliances faster than anything else. Keep the channels active:

• Daily or every-other-day posts from leadership (event reminders, tips, questions)
• Encourage casual conversation in off-topic channels
• Respond to member questions within 24 hours

Clear growth path

Members who feel stuck leave. Show them what is next:

• Published promotion criteria (R1 to R2, R2 to R3, R3 to R4)
• Skills development (teach members about rally mechanics, general setups, sub-city optimization)
• Leadership opportunities (let R3s call boss rallies or run practice sessions)

Feedback loops

Ask members what they want and act on it:

• Monthly quick survey (3 questions max): “What’s going well? What should change? What events or activities do you want more of?”
• Actually implement at least one piece of feedback per month
• Close the loop: “Based on your feedback, we’re adding a Wednesday boss rally practice session”

Tracking inactivity at scale

For alliances with a large roster, manual inactivity tracking becomes a full-time job for an R4. Here is how to scale it.

Manual approach (functional but tedious):

• Spreadsheet with member names, last login date, last event participation, last donation
• R4 updates weekly by manually checking each member’s profile
• Conditional formatting highlights anyone past the 7-day or 14-day threshold

Semi-automated approach:

• Use game data or screenshots to populate the spreadsheet
• Set calendar reminders for the R4 to run the weekly review
• Template the day-7 and day-14 messages so the R4 can send them quickly

Alliance Studio’s inactive member queue automatically flags members who cross the threshold and tracks outreach attempts so R4s know exactly who needs attention and what was already said.

The 80/20 of inactivity management

Most of your inactivity management time will be spent on 20% of your roster — the chronically borderline members who hover around the activity threshold. For these members:

• Be consistent. Apply the same standards every time.
• Do not make exceptions for high-power members. If they are inactive, they are inactive regardless of their keep level or troop count.
• Track patterns. A member who goes inactive for 7 days every other month has a pattern — address the pattern, not each individual absence.

The other 80% of your roster will either be consistently active (no intervention needed) or clearly gone (simple removal). Spend your energy on the borderline cases, and your roster will stay healthy.

For how inactivity management fits into the bigger picture of running an alliance, see the complete R5 playbook. For the front end of the member lifecycle — recruiting the right people in the first place — see the recruitment guide.