Township

Overview

Franchise

Unknown

Release date

• Windows — 2015
• macOS — 2014
• iOS — 2013
• Android — 2013

Developer

• Playrix Entertainment

Publisher

Unknown

Age rating

• ESRB E — Everyone · IGDB mirror
• App Store 12+ — age 12+ · App Store
• Google Play Everyone · Google Play

Content warnings

Not specified by the storefront

Interaction modes

Multiplayer

Session capacity

Unknown

Access model

• Free to play

Monetization

Unknown

Storefront price

Unknown

Store contents

Unknown

Languages

EnglishRussianGermanFrenchSpanishPortugueseItalianTurkishJapaneseKorean +2 more

Classification

Genres

Casual and puzzlePuzzle

Evidence:Casual and puzzle — 2 excerptsPuzzle — 2 excerpts

Setting and subject matter

Modern day

Evidence:Modern day — 1 excerpt

Camera

Isometric

Evidence:Isometric — 2 excerpts

Visual style

Stylized

Evidence:Stylized — 1 excerpt

Combat system type

Absent

Scale

Ratings

• players93.8% · 12.9MGoogle Play, worldwide · Google Play
• players67.6%Global · IGDB mirror

Last update

• September 24, 2026 · Google Play

Mechanics

Key game systems from the Mechanics Catalog. Assessment axes are independent and are not combined into a single score. An unassessed mechanic is unknown, not absent.

• Clan system

  Present View implementation

  A persistent player organization created or recognized by the game itself, with a stable membership, a life beyond one session, a shared identity, functions, and goals.

  Assessment scope: iOS

  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.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Participants:

  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.

  Participation format:

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

  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 scores (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.

  research draft · methodology 0.4 · September 2, 2026

• Player economy

  Unknown View implementation

  An in-game system where player decisions materially influence at least part of the production, supply, distribution, or price of in-game value.

  Assessment scope: iOS

  The current official Team page confirms member-to-member exchange of resources, lives, and collection cards, but it does not establish regular price formation or explicitly establish that prices are absent. The complete methodology section 12.11 minimum is therefore not met.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Depth:

  Unknown

  Core experience relevance:

  Unknown

  Observed adoption:

  Unknown— No adoption, relevance, structural-expectation, or dependency conclusion is derived while Presence remains Unknown for this exact boundary.

  Structural expectation:

  Unknown

  Player dependency:

  Unknown

  Change direction:

  Not assessed

  Assessment type:

  Unknown

  Confidence:

  Insufficient data— Player transfer is directly documented, but price formation, supply sources, restrictions, binding, sinks, and the external layer are not established as a complete current contour. Silence was not treated as proof of a transfer-only market.

  research draft · methodology 0.2 · September 2, 2026

• Territory control

  Unknown View implementation

  A system where players or organizations capture, hold, and use parts of the game world with lasting consequences.

  Assessment scope: iOS

  Official-source search did not resolve transferable, contestable ownership that persists beyond one session for this product boundary. Silence was not treated as absence.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Depth:

  Unknown

  Core experience relevance:

  Unknown

  Observed adoption:

  Unknown— Adoption reach is unmeasured: primary sources provide neither unique participants nor a compatible active-audience denominator.

  Structural expectation:

  Unknown

  Player dependency:

  Unknown

  Change direction:

  Unknown

  Assessment type:

  Unknown

  Confidence:

  Insufficient data— On 2026-09-02, official-domain mechanic-specific searches for Township did not yield indexed primary evidence resolving Presence. Secondary sources were excluded.

  research draft · methodology 0.3 · September 2, 2026

• Competitive PvP

  Unknown View implementation

  Structured competition between players with rules and a measurable outcome, usually including skill-based matchmaking.

  Assessment scope: iOS

  Official-source search did not resolve a built-in PvP contest with formal rules and a recorded cross-match result for this product boundary. Silence was not treated as absence.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Depth:

  Unknown

  Core experience relevance:

  Unknown

  Observed adoption:

  Unknown— Adoption reach is unmeasured: primary sources provide neither unique participants nor a compatible active-audience denominator.

  Structural expectation:

  Unknown

  Player dependency:

  Unknown

  Change direction:

  Unknown

  Assessment type:

  Unknown

  Confidence:

  Insufficient data— On 2026-09-02, official-domain mechanic-specific searches for Township did not yield indexed primary evidence resolving Presence. Secondary sources were excluded.

  research draft · methodology 0.3 · September 2, 2026

• Live service and updates

  Unknown View implementation

  A regular rhythm of meaningful updates, including seasons, patches, events, and a roadmap that supports a long product life.

  Assessment scope: iOS

  The retained primary item identifies a release-related fact, but the package does not contain the complete dated release series, cadence observations, support-team boundary, and persistence evidence required by section 15.13. A positive live-service result is therefore not published.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Depth:

  Unknown

  Core experience relevance:

  Unknown

  Observed adoption:

  Unknown— No compatible participation numerator and eligible-audience denominator were assembled for this exact boundary.

  Structural expectation:

  Unknown

  Player dependency:

  Unknown

  Change direction:

  Not assessed

  Assessment type:

  Unknown

  Confidence:

  Insufficient data— The checked source is insufficient for a positive result because the minimum evidence set in section 15.13 is incomplete.

  Component scores (0–4):

  • Release cadenceNot assessed
  • Release announcementsNot assessed
  • Content scope and typeNot assessed
  • Seasonal structureNot assessed
  • Event calendarNot assessed
  • Roadmap transparencyNot assessed
  • Response to playersNot assessed
  • Game integrationNot assessed

  research draft · methodology 0.3 · September 2, 2026

• Character progression

  Unknown View implementation

  A system for long-term character or account development through levels, skills, equipment, and specializations.

  Assessment scope: iOS

  The targeted source check did not establish persistent cross-session progression that changes gameplay capabilities in Township. Silence was not classified as absence.

  Access cost:

  Unknown

  Product horizon:

  Unknown

  Depth:

  Unknown

  Encounter mode (record 1):

  Unknown— The checked source does not establish a specific player encounter contour.

  Progression role dimension in an encounter (record 1):

  Unknown— The source does not establish progression effects for either gear-and-stats or roster-and-roles.

  Progression role in an encounter (record 1):

  Unknown— Normalization, advantage, or a horizontal progression role in an encounter is not established.

  Core experience relevance:

  Unknown

  Observed adoption:

  Unknown— The checked mechanic-specific material provides neither a compatible participant numerator, an active-audience denominator, nor source coverage sufficient to estimate adoption.

  Structural expectation:

  Unknown

  Player dependency:

  Unknown

  Change direction:

  Not assessed

  Assessment type:

  Unknown

  Confidence:

  Insufficient data— A mechanic-specific primary source was checked, but it did not establish both required criteria or an explicit negative statement.

  Component scores (0–4):

  • Path length and structureNot assessed
  • Progression axesNot assessed
  • Specialization choiceNot assessed
  • Role of equipmentNot assessed
  • Progression sourcesNot assessed
  • Progress persistence and carry-overNot assessed
  • Game integrationNot assessed

  research draft · methodology 0.3 · September 2, 2026