Case study · Active production

Building a world that stays connected in motion.

nimLandia combines an explorable island world with a production system designed to turn playtest evidence into better geography, movement, vehicles, and missions.

This is an active-development case study. A signed local macOS alpha and unsigned iOS developer export exist; public store availability still depends on the real release gates for each platform.

Illustrated nimLandia island with a city, bridge, runway, helicopter and ship at sunrise.
nimLandia world key art · active production
World

A continuous geography

Cities, medical campuses, airports, coasts, islands, and open sea share one coordinate system.

Movement

Vehicle to on foot

The design joins aircraft, cars, boats, swimming, and walking rather than isolating each mode.

Economy

Progress must be earned

The economy caps cash, rejects pay-to-win design, and makes friendship and activity the primary path forward.

Development evidence

Views from the working world.

These are approved in-game beauty captures with exact source hashes retained—not invented marketing screenshots.

01

Holy Land mission family

Travel, stop, and learn without turning Scripture into spectacle.

Ararat, Ark, Exodus, Tabernacle, and era-separated Jerusalem work is governed by source ledgers, sacred boundaries, and a visible distinction between Scripture and adventure fiction.

Read the Holy Land architecture

02

Player economy

A deliberately closed wallet and an open path to earning.

The $19.99 base-game model, $1 transaction ceiling, $10 monthly funding cap, and earn-only mode ladder are one product promise.

Read the economy law

03

Multiplayer engineering

Nearby play with honest transport boundaries.

Desktop ENet over LAN/Wi-Fi is implemented. Bluetooth controllers are input; Bluetooth gameplay networking is not implemented. Cross-platform and Apple-native discovery remain active gates.

Read the multiplayer state

04

Production system

Models, playtests, evidence, and release receipts.

Deterministic Blender specifications, nimCyclopedia reviews, waypoint captures, TAP gates, migrations, and reversible releases keep the build inspectable.

See the production loop

Keep exploring

The next useful conversation starts with the work.