paulagrata.com View on GitHub

06 / Games

Sims 4 Modding

Small experiments in how a familiar game can look, feel, and play differently.

  • Python
  • The Sims 4 Runtime
  • TS4 Package Files

01 / The idea

Give my Sims a few more things to do.

I started modding The Sims 4 because I kept running into little things I wished my Sims could do. That turned into a collection of experiments with custom interactions, traits, object behavior, console cheats, and interface changes. I wanted those additions to feel like something players could discover naturally while playing.

02 / The architecture

Extend the simulation from inside the game.

I wrote Python script mods that run inside The Sims 4 rather than as standalone programs. The project keeps Python modules in src and reserves a separate assets directory for tuning files and .package files. The build configuration keeps those source paths separate from the output directory and the game's Mods folder.

03 / The challenge

Make a new behavior feel native to the game.

In my own game, I can decide when an interaction appears and what happens when the player selects it. In The Sims 4, a new interaction has to make sense alongside the rules and menus that already exist. A command working in the cheat console is one thing. An action appearing on the right object, in the right context, is a different problem.

04 / The build

Take a Python change from source to an in-game build.

I used a community modding template credited to junebug12851 as the starting point for my build workflow. I used decompile.py to inspect the game's Python modules as a reference, then wrote my gameplay scripts separately in src. The compile.py entry point calls compile_src() and runs sync_packages.py to copy .package assets into the build output and the game's Mods folder. A final bundling step creates a ZIP of the build, so I can rebuild after a change without assembling the files by hand.