Killing a Sim in The Sims 4, and every other needs, mood and death cheat

The three kill commands, and why none of them runs

All three exist in the shipped Python, and all three are declared debug-only. That is the command decorator's default, and it means the command never reaches the registration call in a build sold to players.

For the record, what the first two would have done: death.kill_many_npcs walks the household manager and calls set_death_type with a random death type on NPCs it can reach, skipping toddlers and younger. death.kill_offlot_npc does the same to one named off-lot NPC and prints "Sim {} must be an NPC" if you point it at a played Sim.

None of the three is reachable. Killing a Sim in a retail game is a gameplay outcome: you set the situation up and the game's own death interaction fires. The console's part in that is draining needs and removing the buffs that keep a Sim comfortable.

death.toggle: the one death command a player can type

The command body calls toggle_death in interactions/utils/death.py, then prints the resulting state back to the console as Toggling death, Enabled: {}. That echo is worth reading instead of assuming: it reports where the switch landed, not what you asked for.

The switch is global. is_death_enabled sits next to it in the same module as a plain module-level read, with no Sim or household parameter anywhere in either function.

Death types: what the code carries and what it does not

DeathType is a DynamicEnumLocked, and the only member declared in Python is NONE. Every real death type is added from tuning as the game loads. So the list of death types is not in the code this site extracts, and this page does not print one.

What the code does carry is the choice the game offers after a death. DeathOption has three members: PLAYER_GHOST, FREEROAMING_GHOST and REINCARNATION, mapped to the three custom buttons of the death dialog.

The death tracker's own signature is also readable: set_death_type(death_type, is_off_lot_death, remove_from_household, set_to_min_lod, process_inventory, is_reincarnation), with remove_from_household defaulting to true. Which is to say the game treats a death as a household edit as much as a state change on one Sim.

Filling needs

These two do the everyday work in this section, and neither needs an internal name typed after it.

visible_only defaults to true in both registrations, which limits the fill to the commodities the motive panel shows rather than every hidden statistic hanging off the Sim. Leave it alone unless you have a reason not to.

fillmotive fills one motive, on the active Sim only

Two things about it that other lists get wrong. It has no Sim argument at all: the body reads the active Sim off the client connection, so the Sim you are controlling is the Sim it hits. And it does not top a motive up by a bit; it writes the statistic's max_value straight in.

The stat_type it wants is a statistic's internal tuning name, and the registration does not carry the table of names it will accept. Those names live in the tuning rather than in the Python, so this page does not print a motive-name list.

It is also the strict case. The tuning lookup takes an exact_match flag, and only 23 of the 230 tuning-instance arguments in the game set it to true. fillmotive is one of them, so a fragment of a name will not do: it is the whole name or No names matched. If you want every motive filled, the two commands above do it without needing a name at all.

Moods, and the buff commands that do not work

Mood in The Sims 4 is computed from the buffs a Sim is carrying. There is no set-mood command. Four commands in the whole extraction have mood in the name (mood.show_active_mood_type and three debugvis.mood.* entries), and every one of them is debug-only.

The buff commands split cleanly, and not the way most cheat lists have it.

removeBuff and sims.remove_buff are one registration with two names, so anything true of one is true of the other. sims.add_buff is the one to notice: it is on every mood-cheat list on the web and it is automation type, which means the QA channel drives it and a player typing it gets nothing back.

The buff names the Python actually spells out

removeBuff takes a buff's tuning name. As with motives, the catalogue lives in the tuning rather than in the code, so there is no complete list to publish. What the code does carry is the automation harness's own table of buff references in simulation/automation/constants, and ten of the twelve labels on those references are written as buff tuning names.

Two caveats, because this is evidence rather than a catalogue. These strings are the description labels attached to each reference field, not the resolved tuning instances, and the other two entries in the same table read "An Okay buff" and "PreventFearTraitAdditions", which shows the labels are not always names. They are still the only buff names on this site traceable to a file rather than copied off another cheat list, and none of them is a mood buff you would want to remove anyway.

All 47 needs, mood and death commands

Sortable, and the column to sort on is Works in retail. 12 of these 47 run for a player. The other 35 are declared across the same nine modules, 23 of them debug-only and so never registered at all, and are transcribed onto cheat lists as though that made them usable.

The split is 7 cheat, 5 live, 12 automation and 23 debug. Not one row declares a pack code, so every command here is base game as far as its own registration is concerned, including the spells.*, occult.* and sickness.* entries, whose names point at packs but whose registrations do not. The pack column on this site reports the tag in the file, not what a name hints at.

No registration in this build ships a description string, for these rows or for any of the other 1,847. A filled cell is our own sentence, written from the code the command calls; an em dash means we have not established the behaviour and will not guess at it.

Two more that are worth knowing

resetsim is one of only eleven commands that also appear in the game executable's own console help table, where the usage string reads resetsim <sim name>. If a Sim is frozen mid-interaction rather than dying, that is the command, and it needs no cheats enabled.

Enabling cheats first

Ctrl+Shift+C opens the console, and that is the same combination on Mac: Control, not Command. Command+Shift+C is a macOS shortcut, so the game never receives it, and swapping the two is a common reason a Mac player reports that cheats do not work.

On PlayStation and Xbox, EA documents the cheat box as opening when all four shoulder buttons are held together, and notes that a keyboard attached to a console still uses Ctrl+Shift+C.

EA's cheat FAQ also names the price: cheat codes that need testingcheats true disable achievements and trophies in the save you are playing, other saves keep theirs, and build mode cheats are exempt. Setting Sim needs is on EA's own list of things that require the flag.

Traits change how a Sim behaves rather than what a Sim needs, and those are traits for sims 4. Friendship and romance are the relationship cheat sims 4. If dragging a need bar sounds better than typing a statistic name, sims ui cheats covers the mod route.