Intended game design · Not live gameplay

Chapter 01

A persistent world
mapped onto ours.

NFTerra is planned as a mobile MMORPG in which real streets, parks, waterfronts, districts, and verified venues provide the geography for a separate dark-fantasy game layer.

Android & iOSGoogle Maps foundationServer-authoritative world

Map below. Game above.

Geography would shape the opportunity—not expose the player.

The proposed client would use Google Maps SDK for geographic context and render NFTerra's original characters, enemies, resources, structures, effects, and interface as a separate game layer.

  • Roads and paths could shape traversal routes and encounter boundaries.
  • Parks, waterfronts, commercial areas, and districts could influence biome and resource tables.
  • Time, weather, regional history, live events, and world state could modify what is available.
  • Exact player coordinates would remain private server data and would never be written to the public chain.

Location is an input, not authority.

A phone-reported coordinate would be treated as untrusted evidence. The backend would decide movement validity, encounter eligibility, rewards, and cooldowns.

A planned NFTerra encounter over the road geometry of a dark coastal city
World-layer concept artIllustrative · not a gameplay capture

A map of the intended game context

Routes, resources, encounters, venues, and territory can share one geographic layer.

This conceptual map separates the readable real-world foundation from server-controlled game opportunities. It is an explanatory diagram—not a proposed GPS interface.

A conceptual coastal-city map marks a safe route, server encounter, regional resource, verified venue, and contested clan cell
Geographic gameplay context mapConcept diagram · precise player location stays private

From location signal to persistent reward

The map would propose context. The server would construct the encounter.

Generated content would pass through safety, eligibility, regional, timing, and economy rules before a player could see or resolve it.

A five-stage dark fantasy diagram showing map context, safety validation, regional modifiers, a live dockside dragon encounter, and reconciled rewards
Location-to-event authority pipelineIllustrative · open full-size image for detail
  1. 01 · ContextRoads, coastlines, districts, public venues, and bounded cells establish possible space.
  2. 02 · ValidateSafety, access, presence, spoofing, speed, cooldown, and account rules filter eligibility.
  3. 03 · ModifyRegion, terrain, time, authored history, world state, and campaigns shape content tables.
  4. 04 · ResolveThe authoritative server runs the encounter, cooperation, conflict, objectives, and contribution.
  5. 05 · ReconcileExperience, resources, currency, quests, and sealed loot settle into their canonical ledgers.

A possible play session

From a nearby signal to a lasting consequence.

A short walk could begin an encounter, but the wider game would connect that moment to skills, crafting, markets, clans, and persistent item histories.

  1. 01

    Scan

    The client would request safe, eligible content for the player's validated game area.

  2. 02

    Travel

    The player could move toward a resource, breach, boss, event, service, or contested boundary.

  3. 03

    Engage

    The server would resolve combat, gathering, cooperation, or another approved interaction.

  4. 04

    Recover

    Rewards could include materials, currency, quest rewards, or sealed unidentified bases.

  5. 05

    Decide

    The player could use, hold, trade, craft with, or eventually mint the recovered value.

Persistent MMORPG systems

The map would be the stage, not the entire game.

NFTerra's planned depth comes from systems that continue beyond the moment of movement.

Encounters

Regional threats

Mobs, elites, bosses, breaches, resources, and world events could be generated from geography, time, state, and authored content rules.

Progression

Independent skills

Combat, gathering, production, construction, and utility skills are planned to progress through use, creating distinct professions.

Social world

Players create demand

Specialists, traders, clans, service providers, explorers, and fighters would depend on one another rather than share one optimal path.

Persistence

Consequences remain

Created relics, trade history, clan history, settlement structures, territory upkeep, and specialist reputation could survive beyond one session.

Recovered from the legacy Miro board · Candidate systems

The original board describes a reactive local world—not a static map of markers.

These mechanics are not yet confirmed, but they reveal important product intent that was missing from the public explanation.

Regional identity

Terrain, country, city history, landmarks, and authored local context could influence enemies, appearances, loot, and events without stereotyping real cultures.

Real-time cycles

Local time and day/night state could change available creatures, bosses, gathering conditions, hazards, and encounter rules.

Event alerts

A nearby breach—such as a dragon attacking docks—could notify eligible players within a safe, capacity-limited radius.

Proximity encounters

Nearby players could trade, communicate, cooperate, negotiate, flee, pursue, sabotage, or betray under explicit visibility and consent rules.

Contextual PvP

PvP could be enabled only in designated states or zones, with safe areas and protected services remaining non-combat spaces.

Contribution rewards

Experience and party rewards could recognize meaningful participation while limiting effortless carrying by much stronger players.

Safety before reward

No game objective should encourage unsafe movement.

A geolocation MMORPG needs stricter rules than an ordinary map interface.

The intended design would exclude dangerous, private, restricted, inaccessible, or inappropriate destinations; discourage interaction while driving; respect closure and capacity; provide emergency controls; and avoid exposing another player's exact location.

Movement

Validated server-side

Speed, timing, route plausibility, device integrity, and replay signals would inform eligibility.

Privacy

Minimum necessary data

Precise and historical coordinates would be limited, retained deliberately, and kept out of public records.

Access

Safe public places

Content rules would consider operating hours, accessibility, crowd risk, boundaries, and incident response.

Still to be decided.

  • Physical-only movement versus bounded remote play
  • Combat model, party size, and encounter duration
  • PvP availability and safe-zone policy
  • Initial launch region and minimum age
  • Day/night and weather influence
  • Nearby-player visibility and communication
  • Map camera, sprite scale, and readability
  • Accessibility alternatives to physical movement

Next chapter

The map creates opportunity. Skills determine what a player can do with it.

Review the planned character identities, starter loadouts, independent disciplines, specialist professions, and boundaries around purchased progression.