Clan system

research draft · methodology 0.4 · September 2, 2026 · The assessment uses the existing iOS boundary; the cited mechanic evidence does not independently establish App Store availability or current store state on 2026-09-02.

Township Teams are persistent player groups with join and chat functions, Leader and Co-leader permissions, resource assistance, and team Regatta tasks and leaderboards. The retained evidence supports a utility layer but not shared progression or managed shared assets.

Who participates:

A player at level 12 with a restored Teams Center may join a Team; the exact account-versus-character mapping is not stated. A Team can have up to 50 members.

Group structure:

Mixed: members exchange resources and complete Regatta tasks for a team total; synchronous coordination was not established.

Assessment scope

Access cost:

Unknown

Product horizon:

Unknown

Independent dimensions

Depth:

at most 2 of 5 — Utility layer

What limits the result:

Shared progression: Level 2 is an upper bound because the current official sources do not establish shared progression; a stronger level was not inferred.

Core experience relevance:

Unknown

Observed adoption:

Unknown— No compatible count of unique Team participants and active eligible players was found for the same observation window.

Structural expectation:

Unknown

Player dependency:

Unknown

Change direction:

Not assessed

Assessment type:

Unknown

Confidence:

High— Current official Help Center pages directly support Team membership, chat, roles, requests, Regatta tasks, and leaderboards. Unstated adoption, dependency, and higher-level criteria remain unknown.

Component profile (0–4)

• Identity and communication2 of 4 — The current official source supports Team creation or joining and in-game chat; criteria for a higher score were not inferred.
• Governance and permissions2 of 4 — The current official source supports Leader and Co-leader control over membership requests; broader distributed governance was not inferred.
• Shared progressionNot assessed — The current official-source review did not establish shared progression; source silence was not converted to score 0.
• Shared assets and economyNot assessed — Member-to-member resource assistance does not by itself establish a shared organizational asset; the value remains Unknown.
• Collective goals and content2 of 4 — The current official source supports team Regatta tasks and a team total; longer-term strategic goals were not inferred.
• Competition, territory, and politics1 of 4 — The current official source supports team names and emblems in leaderboards; deeper inter-team systems or territory were not inferred.
• Game integration2 of 4 — Resource assistance speeds town development and Regatta tasks contribute to the Team, supporting a utility-level integration score.

Evidence

• component · collective_goals

  Qualifies · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  Regatta tasks the team completes. […] up to 50 players can participate in Regatta.

  The excerpt supports collective-goals score 2 through recurring Team tasks; higher strategic coordination was not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16614-what-changed-in-teams-and-the-regatta-1765959232/
• component · competition_territory

  Qualifies · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  Team emblems and names now appear in leaderboards.

  The excerpt supports score 1 for symbolic leaderboard competition; events between organizations or territory were not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16614-what-changed-in-teams-and-the-regatta-1765959232/
• component · game_integration

  Confirms · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  Team members exchange resources, lives, and collection cards to speed up town development.

  The excerpt supports game-integration score 2 through resource assistance tied to town development; dependence was not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16615-teams-1765959235/
• component · governance

  Confirms · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  Closed – players must send a request, which the Leader or Co-leader can accept or decline.

  The excerpt supports governance score 2 through named roles and membership-request permissions; broader management was not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16614-what-changed-in-teams-and-the-regatta-1765959232/
• component · identity_communication

  Confirms · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  A team is a group of players who join together to help each other and chat in the game.

  The excerpt supports identity and communication score 2 through a persistent group, joining, and in-game chat; higher coordination functions were not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16615-teams-1765959235/
• depth

  Qualifies · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  Regatta tasks the team completes. […] up to 50 players can participate in Regatta. […] Team emblems and names now appear in leaderboards.

  The excerpt supports a level 2 utility layer through recurring team tasks and a team leaderboard. Shared progression and managed shared assets remain unknown, so a stronger level was not inferred.

  https://playrix.helpshift.com/hc/en/3-township/faq/16614-what-changed-in-teams-and-the-regatta-1765959232/
• presence

  Confirms · Catalog mechanics research · Publisher: Playrix · Accessed September 2, 2026

  A team is a group of players who join together to help each other and chat in the game.

  The current official Help Center page directly establishes the persistent Team group, join function, mutual help, and in-game chat.

  https://playrix.helpshift.com/hc/en/3-township/faq/16615-teams-1765959235/