Use your current game values. Numeric cases below are illustrative; exact game rates and prices have not been independently tested.
Join when you need a team; create when you can run one
Joining is usually the more practical editorial starting point when your immediate goal is to learn group play or find people active at the same time. Creating a family makes sense when you already have willing participants and someone prepared to coordinate them. A memorable name alone does not supply a roster.
Confirm the current join or creation requirements inside the Family interface before committing cash or resources. This guide does not claim a verified creation fee, level gate, member limit or leadership permission list.
Compare the work, not just the label
| Decision | Joining | Creating |
|---|---|---|
| First task | Find a compatible group | Find committed participants |
| Schedule | Fit existing activity | Establish overlap yourself |
| Coordination | Understand expectations | Set and maintain expectations |
| After a failed session | Give useful feedback | Organize the next plan |
These are social tradeoffs, not game-enforced permissions. Inspect the actual role controls before promising other players what a leader or member can do.
Five useful questions before joining
- At what dated times are people usually available?
- Is participation casual, scheduled or expected every session?
- Who chooses the objective and tells members when it changes?
- What resources are members expected to commit?
- What happens if someone misses a planned session?
Ask for concrete examples rather than accepting “very active.” A large roster with little overlap may be less useful to you than a small group whose schedule matches yours. Use the time-zone converter to compare actual dates; daylight-saving changes can shift local times.
A minimum plan before creating
Agree on a first objective with the people who intend to join. Name a coordinator and someone who can follow up afterward. Establish how a target change will be communicated and how participants can say they are unavailable. Keep the first commitment small enough to evaluate.
An illustrative first-session brief might say: “Review one district together, confirm its current requirements, then decide whether to act.” This is more useful than promising immediate map control. If no one can attend the same session, recruitment or scheduling is the current bottleneck; another equipment purchase will not solve it.
Review fit after a few shared sessions
Keep a small record of planned versus actual attendance, whether objectives were clear and whether costs matched expectations. This is a way to assess fit, not a score of individual worth. If coordination repeatedly breaks down, discuss a smaller objective or a different schedule before assuming the game requires more grinding.
Before leaving or transferring responsibility, read the current game’s consequences and role controls. Do not assume territories, benefits or permissions transfer in a particular way. Once the group works for you, use the territory reading guide and war preparation checklist to plan concrete actions.
Sources & scope
Core systems are described by the developer. Strategy is editorial guidance unless a specific test is cited. Exact prices, unlocks and rewards should be checked in your current game.
Report a discrepancy