Dev Blog: Welcome to Polinaria World

A small camp under a strange sky

Polinaria World begins under the yellow-red sky of Tau Ceti 42. A command habitat comes online, nearby systems wake up, and the player starts turning rough ground into a sanctuary for people and native herds.

Project concept illustration; not a gameplay screenshot.

The challenge is keeping that little camp working when the environment pushes back. Buildings have local inventories, components, service load, reliability, maintenance, and operating modes. Routes have exposure, disturbance, capacity, and wear. Weather and incidents change the conditions around both.

First, keep the water flowing

The early loop has a survival-engineering feel:

• Solar masts provide the power budget.
• Water extractors fill local tanks; stocked watering basins draw herds before thirst becomes dangerous.
• Mines produce raw ore, and refineries turn it into refined material.
• The command habitat and storage depots buffer supplies between destinations.

When a route is missing or a destination is empty, the interface can suggest a link that would help. The machinery becomes understandable through its consequences.

The herds remember what you build

Alongside production is a quieter system. Herds remember useful places, avoid stressful areas, and form route memories around water and landmarks. Cognition tracks observations, rituals, colored route marks, and cultural notes.

flowchart TD
    Build[Build and connect infrastructure] --> Conditions[Change water, access and disturbance]
    Conditions --> Herds[Herds explore or avoid places]
    Herds --> Memory[Memories and repeated visits]
    Memory --> Choices[New questions for the keeper]

This is the relationship that makes the map interesting: infrastructure changes how living things use the space, and their behavior gives the player something new to notice.

Read the camp as a live system

The map shows buildings, routes, weather, incidents, jobs, and overlays. Route cards expose movement, stock, condition, maintenance, reliability, and shortfalls. Service panels show repair pressure and part production.

Underneath, Python domain code and an API run the simulation, with persistence and migrations for long-running worlds. A TypeScript React client presents it through Vite in development and built static assets in deployment. Tests cover simulation, API behavior, persistence, notifications, player sessions, and frontend rules; roadmaps record the direction of the work.

What I like most is the texture of care. You keep water stocked, repair stressed routes, read the weather, make room for herds, and watch memories accumulate around the things you build. The reward is seeing the camp begin to explain itself.