You repair a bridge before logging off. Three days later, the merchant who could not cross the river has a stall in town. The stall changes what the baker can buy. The baker’s bread gets the village through a storm. You missed the whole chain of events, but the village remembers your first move.
That village is a Dream Project, not a game you can play today. We imagine a world whose small systems continue to interact while its players are away. Weather changes crops. Crops change trade. Characters make limited decisions using the resources around them.
Make the surprise understandable
Begin with one village, ten characters and three systems: crops, trade and weather. A repair to a road alters a merchant’s route. A rainstorm changes the harvest. Players should be able to enjoy the surprise when they return and, if curious, trace how it happened.
The graphics, sound and immediate controls belong in an ordinary game client. The shared rules and consequential state are candidates for Vara. Its programs can retain state and exchange messages, while deferred messages offer a possible way to schedule later work. That gives a builder the ingredients for interacting systems; it does not make endless simulation free or automatically produce a good game.
A small world needs limits: how often it updates, what each character is allowed to do, what happens when a component fails and how much computation the whole village can afford. Without those rules, “always on” is merely a promise to run up the bill.
The moment to aim for is coming back after a week and recognizing the consequences of something you did. The designer did not script a tribute to you. The systems kept their promises, and the village has a new story.