Lol, everybody just be gawking

You're making arguments that even silence could disprove.

Driving through iwo road on a Saturday noon while listening to radio

looking good Yeah, having knowledge of game design (physics, animations, integrations, tranforms, etc) will indeed make a huge difference

The interesting problems in simulation development aren't always the ones that get the most attention. It's not just about making more NPCs, adding more mechanics, or building bigger worlds. It's about making complex systems easier to compose, understand, test, and change without breaking everything else. That's an engineering problem in its own right. And I think there's still a lot of room to explore better ways of solving it.

Namecheap

I've been thinking about what the fundamental unit of a simulation actually is. I don't think it's state. It's an action. "₦5,000 was removed from the player's balance" tells you what happened. But it's missing the important part: Why? Maybe they bought food. Maybe they paid rent. Maybe they transferred money. Maybe an event increased transport prices. The state change is the result. The action is the cause. A useful simulation should be able to represent: Actor → Action → Requirements → Effects → Consequences → Events And importantly, an action that fails shouldn't partially mutate the world. If you're too tired to work, you shouldn't lose energy and get paid and have the work action fail. The simulation should reject the action, tell you why, and leave the state untouched. This seems obvious until your world has hundreds of interacting systems. Then "just update the state" becomes a recipe for bugs that are incredibly difficult to reproduce. The more systemic the world becomes, the more important it is to treat actions as first-class objects rather than scattered state mutations.

One thing I find fascinating about simulations is that the core loop is surprisingly simple. You start with a state. Then something happens. An actor takes an action. The system checks the rules. The state changes. That produces consequences. Those consequences create new events. Then time moves forward. And you do it again. State → Action → Rules → State Change → Events → Time → Repeat That's basically the heartbeat of a simulated world. The complexity doesn't come from the loop. It comes from how many systems are connected to it. A job changes income. Income changes spending. Spending affects businesses. Businesses affect employment. Employment affects income. Suddenly a simple action can ripple through an entire world. That's where simulations get really interesting.