About
This got slightly out of hand.
Polymodus started as a simulation-game mechanics project. The scope expanded to real systems, real data, browser execution, and a visual editor.
Scope creep
- Simulation games
- Reusable mechanics
- General simulation engine
- Real systems and data
- Visual workbench
- Browser runtime
The origin
It started with trying to create better game mechanics.
Polymodus began as a simulation engine, because i hated the Geo-Political Simulator line of games for their horrible depth.
Then the models needed to interact with real data. Then i wanted a visual editor so that it was easier for me to manipulate. Then i... and so on, you get the drill.
At some point, building the simulation engine replaced playing simulation games. Dunno how i feel about that.
Logo tidbit
A P, an O, and an accidental dam.
The Polymodus mark began as an exploration of the P and O in the name. But then i added a dam to it, and now it looks like an R.
Design priorities
How Polymodus is built
Runs in the browser
Build and run supported models without installing a desktop application.
Shows the working parts
Inspect queues, resources, routing, parameters, data bindings, and results in the same workspace.
Grows with the model
Add experiments, agents, spatial behavior, and external data to the same project.
Example model