All Lumpinou Sims 4 Mods: Complete List

Lumpinou’s Sims 4 catalog is best understood as one shared library — Mood Pack — sitting underneath three functional families: the Relationship & Pregnancy Overhaul (RPO) modules, the LGBTQIA+ identity and orientation suite, and a handful of smaller standalone gameplay mods. The practical rule is to install Mood Pack and the RPO core first, then add only the optional modules whose behaviour you actually want, because every extra module is another script file that has to be re-downloaded and re-checked after each game patch. Everything below is organised by what the mod does in play, not by the order it appears on a download page.

Quick comparison: the Lumpinou mod families

Sizes are order-of-magnitude figures for script-based Sims 4 mods of this type; treat them as a way to sanity-check that a download is complete, not as a spec printed on a box. Exact module names and counts shift between versions — per Lumpinou’s own module documentation, the framework is deliberately modular so pieces can be added, split or retired without rewriting the whole thing.

Layer 1: Mood Pack, the file everything else leans on

Mood Pack is not a gameplay mod in the usual sense. It is a library of moodlets — emotional buffs — that other mods call on instead of each one inventing its own. If a Lumpinou mod references an emotion your game doesn’t have, the moodlet either fails silently or throws a script error, which is why Mood Pack appears in the requirements list of most of the catalog rather than being an optional extra.

Practical consequence: install it once, in the same folder as the mods that depend on it, and keep it updated when it is updated — not every patch. It is one of the smaller downloads here and one of the least disruptive to update.

Layer 2: RPO — the pregnancy and family modules

The Relationship & Pregnancy Overhaul is the flagship. It replaces the base game’s single pregnancy roll with a system you configure, and it does so through separate modules so you can keep the parts you like and ignore the parts you don’t. Functionally they fall into four groups.

Conception and prevention

• Fertility and cycle tracking — gives Sims a fertility window so conception odds vary by day rather than being a flat percentage.
• Birth control and protection — adds contraceptives and condoms as inventory items Sims can buy and use, which changes conception chance rather than blocking it outright.
• Conception tuning — lets you set how likely pregnancy is overall, useful if you want pregnancy to be rare and meaningful rather than constant.

Outcomes and testing

• Paternity testing — establishes who the other parent is through an in-game test rather than the game simply knowing.
• Miscarriage and loss — makes pregnancy failure possible; this is the module most people either want badly or switch off immediately, and it is worth deciding before you install rather than after.
• Infertility — Sims can struggle to conceive, with treatments available.
• Teen pregnancy — extends the system to teen Sims, with the school and household consequences that implies.

Family building without pregnancy

• Adoption — a structured adoption process instead of instant household editing.
• Surrogacy — another Sim carries the pregnancy, with the relationship tracking that follows.

Social reactions

• Pregnancy reactions — partners, family and strangers respond differently depending on traits and relationship state.
• Woohoo reactions — moodlets attached to intimacy, which is what makes the relationship modules feel connected to the pregnancy ones.

Layer 2b: RPO — romance and relationship structure

The same framework covers how relationships are allowed to work, not just how pregnancies start. The modules here handle open relationships and polyamory as recognised states rather than affairs, reactions to cheating that vary by Sim, and breakups that can be negotiated rather than instant. If you install these alongside the pregnancy modules you get a coherent system; if you install them alone you get a relationship overhaul with the base game’s pregnancy rules untouched.

Layer 3: the LGBTQIA+ identity suite

This family handles gender identity, sexual orientation, pronouns, coming out and transition as separate but linked systems. The design point worth knowing before you install: orientation and identity are tracked as data the game reads, so other mods — including RPO’s relationship modules — can respond to them. That is why the suite lists Mood Pack as a dependency and why installing it after RPO Core tends to produce fewer odd moodlets than the reverse.

Smaller standalone mods

Outside the two big families there are smaller additions, most notably a first-impressions system that gives Sims an initial reaction to a new acquaintance based on traits, and woohoo-focused mods that decouple physical intimacy from romantic relationship state. These are usually .package files, they rarely depend on Mood Pack, and they are the first things to survive a patch without an update — which also means they are the safest place to start if you are new to script mods.

Installation: the order that avoids a broken save

• Step 1 — Enable script mods first. Game Options → Other → tick “Enable Custom Content and Mods” and “Script Mods Allowed”, then restart. Reason: .ts4script files are ignored entirely until this is on, and people routinely install a script mod, see nothing happen, and start deleting files that were fine.
• Step 2 — Place files no more than one folder deep. The game reads Mods\Lumpinou\MoodPack.package but not Mods\Mods\Lumpinou\MoodPack.package. Reason: nesting is the single most common cause of “the mod is installed but nothing happens”.
• Step 3 — Install in dependency order: Mood Pack → RPO Core → optional modules → LGBTQIA+ suite → standalones. Reason: it makes it obvious which file to suspect when something misbehaves.
• Step 4 — Delete the old version before adding the new one. Reason: two copies of the same script in the Mods folder is a guaranteed conflict, and it looks like a broken update rather than a duplicate.
• Step 5 — Delete localthumbcache.package from the Sims 4 folder. Reason: stale cache makes removed mod data linger in the save and can produce moodlets that no longer exist.
• Step 6 — Back up your save folder before the first launch. Reason: script mods are removable, but the moodlets and relationship flags they wrote into a save are not, and rolling back is far easier than repairing.

Update and compatibility realities

The honest ownership picture: script mods are the most fragile category of Sims 4 content. Per EA’s patch notes, patches frequently change the internal tuning and Python APIs that script mods call on, so a patch day usually means at least one Lumpinou file needs replacing before your save behaves normally again. Package-only files often keep working for weeks. That difference is why the standalone mods and the Mood Pack library are low-maintenance while RPO Core is high-maintenance.

Three compatibility rules worth memorising. First, run only one pregnancy overhaul at a time — two systems rolling the same outcome produce double pregnancies and stuck moodlets. Second, MC Command Center can coexist, but its own pregnancy settings overlap with RPO’s; leave the pregnancy side of MCCC at default rather than tuning both. Third, mods that edit the same interactions as RPO — relationship, woohoo or family interactions — are the likeliest conflicts, and the usual symptom is a missing pie-menu option rather than a crash.

Which setup fits your play style

One more trade-off to weigh up front: mods disable in-game achievements on that save. If you are chasing them, install these on a separate save rather than your main one.

Frequently Asked Questions

Do I need Mood Pack to use Lumpinou’s mods?

Not for all of them, but for most of the larger ones. Mood Pack supplies the custom moodlets that the RPO framework and the LGBTQIA+ suite call on, and it is listed as a dependency on those mods’ release pages. Standalone .package mods usually run without it. If you are installing anything in the two main families, install Mood Pack in the same step.

Can I use these mods with MC Command Center?

Yes, they coexist, but you should avoid tuning the same system in both. MCCC has its own pregnancy and relationship settings that overlap with RPO’s, and running both at once is a common cause of double pregnancies or moodlets that never clear. Leave MCCC’s pregnancy options at default and let RPO handle that side.

Will installing RPO break my existing save?

It will not corrupt the file, but it does write new data — moodlets, relationship flags, pregnancy states — that persists after you remove the mod. Removing it later can leave Sims with buffs that no longer have a source. Back up the save folder before the first launch, and if you want to test, do it on a copy of the save rather than the original.

How often do these mods need updating?

Expect an update check after every game patch, and treat RPO Core as the priority. Script files are the ones that break; package-only files and the smaller standalones often keep working for weeks. A useful habit is to note the game patch version each mod’s release page states it targets, then match it against your own.

Can I install just one RPO module instead of everything?

Yes — that is the point of the modular design. RPO Core is the framework and is required, but every optional module is a separate download you can skip. Many players install only the conception and testing modules and deliberately leave out miscarriage and teen pregnancy, which is a perfectly supported configuration.

Where exactly do the files go?

Into Documents\Electronic Arts\The Sims 4\Mods, in a single subfolder such as Mods\Lumpinou, with script mods enabled in Game Options and the game restarted afterwards. Files nested two or more folders deep are not read. After any change, delete localthumbcache.package from the Sims 4 folder so the game rebuilds its cache from the current file set.