Four expansion packs in four years
High School Years, Horse Ranch, Lovestruck, Enchanted by Nature. Each one is a full product — new systems, new worlds, new art — shipped worldwide on a fixed public date across PC, Mac, PlayStation, and Xbox, into a franchise with more than 85 million players.
The constraint that shapes everything
The hard part of this job isn't the schedule. It's that every new feature has to live inside a game that has been shipping continuously for more than ten years. Nothing gets built on clean ground.
A new social system has to make sense alongside every system that came before it. It has to work with a decade of purchased content, behave identically on a console with a fraction of the memory, and not break a save file someone has been playing since 2014.
Horse Ranch
The clearest example of that constraint. Horse Ranch put a rideable quadruped into an engine built, for its entire history, around people.
That touched almost everything at once: rigging and animation for a body plan the game had never handled, coat and mane rendering, interaction systems for riding and training and care, and a creature that has to move believably through environments designed for bipeds.
I produced the 3D asset work — coordinating art, animation, and engineering through the technical problems, and making the calls about what was ready to ship and what wasn't.
Deciding what a pack is for
A lot of this job happens before anyone builds anything. Each pack has to serve a real player need without pulling the franchise somewhere it shouldn't go.
High School Years — a teen experience players had been asking about for years, built so it deepened the game rather than changing what the game is.
Horse Ranch — deliberately niche. A smaller, specific community served properly rather than broadly, which is its own kind of discipline.
Lovestruck — went deeper into relationship systems the game already had, instead of adding new ones beside them.
Enchanted by Nature — environmental and natural themes, built to hold together as gameplay rather than as messaging.
Those decisions came out of forum and community signal, mod download patterns, and player research, weighed against what the engine could actually support.
Running four packs also means watching for features that compete with each other and for the ones that compound. Teen social interactions built for High School Years made the relationship work in Lovestruck richer than it would have been on its own.
What production meant here
Milestone planning and dependency tracking across concurrent projects. Technical planning with engineering for integration into legacy systems. Platform-specific requirements and certification for console parity. Bug triage across multiple packs at once.
Working with art directors on visual themes and asset requirements, and with narrative designers on content and age-appropriate messaging. Localization and voice requirements for global markets. I wrote in-game copy, and originated costume and character concept direction with our Art Director, reviewing and approving work delivered by external partners.
Alongside that: launch timing across the four packs, coordination with marketing on community engagement and previews, and working with community managers on feedback and expectation-setting through to post-launch.
What I'd tell someone doing this next
When you're building on ten years of existing systems, the estimate is never about the feature. It's about everything the feature touches. Teams get this wrong by scoping the new thing carefully and then discovering the integration work halfway through.
And a vocal community is a real signal, but it's one signal. The players who post are not the players who play, and building only for the loudest room produces a pack that reviews well in one place and lands badly everywhere else.