Everything you need to write about Simulation Baseball.

One line

A browser-based baseball franchise simulator where you run the entire front office and the engine plays out every pitch.

Short, about 50 words

Simulation Baseball is a browser-based baseball management game. You handle scouting, the draft, trades, free agency and the farm system, and a purpose-built engine resolves every game one pitch at a time to a full box score. Play solo against AI front offices or in a league of up to 30 human general managers.

Long, about 150 words

Simulation Baseball is a browser-based baseball franchise simulator built for people who have played this genre for decades and want it to move again. You run an entire front office: scouting, the draft, trades, free agency, player development and the farm system. Every game resolves one pitch at a time on an engine where thirty-three separate inputs decide a single pitch, twelve pitch types carry their own velocity and break across the thirteen zones Statcast uses, and every ball in play gets an exit velocity, launch angle and spray angle calibrated against roughly 1.1 million real batted balls. Players carry sixty-six named ratings including eight personality traits, morale runs off seven drivers, scouting is fogged so nobody sees true ratings, and each ballpark carries its own dimensions and twelve months of real climate. It runs in a browser, on desktop and phone, with nothing to install.

On why it exists

Twenty years is a long time to love something that stopped changing.

I have spent more hours playing simulation baseball than doing any other single thing in my life. Somewhere in the last decade the genre quietly agreed it was finished. Each year brought a roster update and a redesigned panel and nothing that changed how you actually play. We got tired of describing the game we wanted to each other and started building it.

On the engine

Most sims roll a number against a rating. This one plays out the confrontation.

Thirty-three separate things decide one pitch. Eighteen of them choose which pitch gets thrown, thirteen decide what it physically does, and then the catcher can steal a strike and the ballpark has an opinion. That is not a marketing number, it is the actual call path, and we publish where every one of them lives in the code.

On trust

If you are going to spend a thousand hours inside a simulation, you deserve to know what it thinks a slider is.

The loudest complaint in this entire category is that players cannot trust what they cannot inspect. So we publish the method. Not a whitepaper nobody reads, a plain-language explanation of what actually decides an outcome, with the file it lives in.

On the design choice

We are not optimizing for one exciting afternoon. We are optimizing for season sixty.

This is a career game first. That decision is why everything else looks the way it does. If the state of your league at the end of a season is not coherent, nothing else we build matters, so that is the bar we hold ourselves to before anything ships.