QUICK START
Before registering
Choose a clear alliance name, a short tag, a theme, trusted leaders, simple internal rules, a public description, and honest recruitment messages. Do not use fake members, fake proof, alt abuse, impersonation, or spam.
ALLIANCE LEADERSHIP GUIDE
Alliance Handbook
Alliance leadership reference for approved Thrones of Aether alliances.
READ THIS FIRST
What this handbook is
This handbook is a practical guide for creating, launching, and running a Thrones of Aether alliance. It helps new founders prepare a name, tag, theme, leadership team, public description, recruitment plan, opening event, map strategy, and basic internal rules.
This is not the legal Terms of Service. The Terms of Service remains the legal document. This handbook explains how alliance leadership should work in normal play.
READINESS
Decide if you are ready
Alliance leaders need activity, patience, rule knowledge, fair recruitment, and the ability to handle losses without rage quitting. Leading is not just picking a cool name; you manage people, events, diplomacy, wars, and reputation.
IDENTITY
Name, tag, and theme
Good names are recognizable, not offensive, not too similar to existing alliances, and connected to the theme. Good tags are short, easy to type, and not already used by another official alliance.
BRANDING
Logo and banner
A logo or banner helps recruitment and public posts. It should be readable, original or properly allowed, safe for the community, and not pretending to be official TOA staff.
LEADERSHIP
Start small
A good starter structure is one Leader, one Co-Leader if needed, one to three trusted senior helpers, and regular members. A new alliance does not need twenty leaders on day one.
LEADER DUTIES
Final responsibility
The Leader keeps the alliance active, handles major decisions, talks with staff when needed, approves diplomacy and wars, stops fake attendance, prevents rule abuse, and keeps members informed.
CO-LEADERS
Trusted backup
Co-Leaders help run events, recruit, manage members, handle diplomacy, and keep the alliance alive when the Leader is busy. Do not give major power to someone only because they ask for it.
INTERNAL RULES
Keep them simple
Internal rules should require members to follow TOA rules, respect each other, avoid fake attendance, avoid troop stealing by only counting players who actually agreed to join, protect private plans, avoid scams, listen during events, and never use alts to cheat. Internal rules cannot override TOA rules.
REGISTRATION
What to prepare
Before registering, prepare the alliance name, tag, leader username, leadership list if needed, public description, logo or banner if available, contact method, proof you are not impersonating another group, and agreement to follow TOA rules.
OFFICIAL STATUS
Recognition matters
Posting about an alliance does not automatically make it official. An alliance becomes official when the TOA system or authorized staff recognizes it.
OPENING EVENT
First public proof
An Opening Event is a first public gathering used to confirm that the alliance is real, has leadership, and has starting activity. Leaders should post the Opening Event submission in the official TOA Discord server using the required format. It is not meant to be a war, invasion, or serious competitive event.
MINIMUM REQUIREMENT
Attendance and points
For an Opening Event to count toward official registration, the alliance should reach at least 2 attendees and at least 10 event points through official event point options.
STAFF REVIEW
Approval checks
Staff may review the name, tag, leader account, impersonation risk, rule history, fake member risk, banned user involvement, and whether the alliance exists to abuse gameplay. Staff may approve, deny, or ask for fixes.
DENIALS
Fix and resubmit
If an alliance is denied, stay calm and ask what needs to be fixed. Common fixes include renaming, changing tags, replacing unsafe art, clarifying leadership, proving activity, or waiting for restrictions to end.
LAUNCH POST
Public announcement
After approval, make a launch announcement with the alliance name, tag, theme, leader, recruitment status, goals, how to join, and first event if planned.
RECRUITMENT
Real members only
Recruit honest members. Do not use alts, inactive placeholders, fake accounts, users who never agreed to join, banned users, copied member lists, or roster entries made without the player's consent. Fake numbers and non-consensual roster moves can lead to punishment.
MEMBER CARE
Welcome people properly
Explain what TOA is, what the alliance does, who the leaders are, where announcements happen, how events work, and how members can help. Confused new members usually become inactive fast.
EVENTS
Start simple
After the Opening Event, begin with training, recruitment, meet-the-alliance events, practice battles, or basic strategy meetings. Do not make the first normal event overly complicated.
ATTENDANCE
Track honestly
Track who attended, screenshots, judge notes, bot records, event results, and rewards. Do not count people who were not there, do not count alts, and do not fake screenshots.
GOALS
Grow with direction
Good early goals include recruiting five real members, hosting three events, making a logo, writing a description, creating one treaty, preparing for a first invasion, and building stable leadership.
DIPLOMACY
Go slowly
Begin with friendly relations, visitor agreements, non-aggression pacts, training partnerships, and event cooperation. Do not sign complicated treaties if you do not understand them.
TREATIES
Write clear terms
A treaty should include involved alliances, start date, end condition, exact terms, who approved it, what happens if broken, and whether staff validation is needed.
MAP GAMEPLAY
Prepare before war
Before serious map gameplay, understand land ownership, capitals, invasions, freeland, adjacency, cooldowns, attendance requirements, War Terms, and staff validation.
FIRST INVASION
Check the basics
Make sure the target is invadable, the time is valid, attendance is realistic, staff approval is handled, leaders understand the risk, every listed participant actually agreed to be there, and all required invasion details are included.
STABILITY
Avoid common mistakes
New alliances often fail by creating too many ranks, starting wars too early, faking attendance, relying on alts, spamming recruitment, changing names constantly, writing unclear treaties, or ignoring staff instructions.
DRAMA
Handle it early
Talk calmly, check proof, avoid instant punishments, keep private issues private, and involve staff only when official TOA systems, safety, land, wars, rewards, or records are affected.
MEMBER SAFETY
No leader abuse
Leaders must not threaten, dox, scam, blackmail, pressure, force users to stay, punish honest reports, or demand private information from members.
HIATUS
Pause honestly
If leadership is busy, announce why the alliance is pausing, whether recruitment stays open, what happens to land and events, whether the alliance plans to return, and who to contact. Do not use hiatus to dodge consequences.
TEMPLATES
Useful formats
Alliance registration: Alliance Name, Alliance Tag, Theme, Leader, Co-Leader, High Command, Public Description, Logo/Banner, Discord or contact if allowed, and agreement to follow TOA rules.
Opening Event Discord submission:
Event Name: [Alliance Name] Opening Event
Alliance Name:
Alliance Tag:
Leader:
Timestamp:
Discord server + alliance website link, if one exists:Normal event announcement: Event Name, Alliance, Date, Time, Location, Goal, Rewards if any, Visitors Allowed, and Notes.
Treaty: Treaty Name, Alliances Involved, Start Date, End Date or Ending Condition, Terms, Allowed Actions, Banned Actions, What Happens If Broken, Approved By, and Staff Validation Needed.
War declaration: Declaring Alliance, Target Alliance, Start Date, Reason if required, War Terms, Raiding Allowed, Multi-Logging Allowed, Staff Validation Needed, and Proof or Links.
Troop stealing review: Reporting Alliance, Accused Alliance or User, Player Added Without Consent, Event or System Affected, What Happened, Screenshots or Logs, Player Statement if available, and Requested Staff Action.
Leadership transfer: Alliance Name, Old Leader, New Leader, Effective Date, Reason, Old Leader Approval, New Leader Confirmation, Staff Validation Needed, and Proof or Links.
FINAL RULE
Use common sense
Staff may review alliance creation, leadership, names, tags, public posts, member lists, event proof, treaties, wars, invasions, and transfers when they affect official TOA systems.
An alliance may be denied or punished for fake members, adding players without consent, alt abuse, fake attendance, fake proof, impersonation, unsafe names or logos, scams, harassment, map abuse, API abuse, using the alliance to dodge punishments, or refusing staff decisions.
Alliance creation questions, registration issues, leadership changes, treaty proof, map questions, and appeals should go through official TOA support channels. © 2026 Thrones of Aether. All rights reserved.