Sims 4 trait cheats: equipping, removing and clearing traits from the console

The two commands, and the argument that decides whether they work

Those two effect descriptions are the game's own, taken from the module that registers the commands.

The optional Sim argument defaults to the selected Sim, so with a Sim selected you type the trait and stop. The third argument on the equip side inserts the trait at a position in the personality list rather than appending it, which changes the order the trait panel shows and nothing else.

Trait names are internal IDs, and that is why the command appears to fail

trait_type is a TunableInstanceParam over the TRAIT resource type. The word you type is handed to get_tunable_instance, which asks the trait instance manager for it as an id first and then matches it against the tuning names of every loaded trait. Those names are internal identifiers, not the labels Create a Sim prints, and the two rarely look alike.

The shape of a real one is documented inside the game's own tuning. The Trait class carries an animation-parameter field whose description explains that if the field is unset the parameter is auto-generated from the instance name, and gives the example 'trait_Clumsy'.

get_tunable_instance takes a name string or an id, and it carries an exact_match flag that the caller chooses. fillmotive sets that flag to true. The trait commands do not, which is why a fragment is enough for them and is not enough for a motive name.

When a fragment matches nothing the helper raises No names matched '{}'. and when it matches several it raises Multiple names matched '{}': {} with the matches listed and sorted. That second message is the closest thing the game has to a trait-name browser: type a fragment, read the candidates back, then run the command with the one you wanted.

The other reasons a trait does not get added

Resolving the name is only the first gate. SimInfo.add_trait goes through TraitTracker.can_add_trait, which returns False and adds nothing when any of these hold.

• The Sim's age, gender or species is not in the trait's allowed set.
• The personality slots are already full. The number of slots is tuned per age rather than fixed in the code, so it is a data value, not a constant.
• A trait already equipped conflicts with this one, or a higher-weight trait in the same exclusive set rules it out.
• The trait belongs to a system that is switched off, lifestyles being the documented case.
• The entitlement check in front of the command fails. traits.equip_trait asks is_granted_or_non_account_reward_item about the trait before it calls add_trait at all.

None of those five prints an explanation. The name lookup does report its own failures, so if the console says nothing at all and the trait panel is unchanged, the name resolved and one of the five gates above turned it down.

Removing is not a clean undo

traits.remove_trait takes the trait off, but adding and removing a trait both fire tuned loot, and removing one strips the trait knowledge from every Sim who knew about it. Re-adding does not give that knowledge back. Treat a trait swap as partly one-way rather than a toggle.

All 14 trait commands in build 1.126.73.1030

7 of the 14 run in a retail game. The other 7 are registered in the same two modules and appear on trait cheat lists anyway.

Every usable row is live type, which the command table defines as registered and always callable. Not one trait command in the game is declared cheat type. Turn testingcheats true on anyway, because everything else you are likely to type in the same session needs it.

The 7 that do not work are 3 automation and 4 debug registrations. Debug commands are filtered out before register() in a shipped build; automation commands are driven through the game's QA channel rather than the console. No row in this section declares a pack code, so all fourteen are base game as far as their own registration goes.

The command that would have printed your trait names

traits.show_traits is the one you would want, and it is automation type. Its output strings are still in the file: Sim {} has {} traits equipped, {} slots left, then one Equipped: {} line per trait. A player cannot make it print any of that.

traits.show_traits_of_type and traits.show_inherited_traits are debug-only, and traits.dump_traits_with_commodities writes a TraitReport.txt that a retail build never generates because the command is debug-only too.

Clearing and bulk-equipping

The tag variant walks every trait in the instance manager, keeps the ones carrying your tag, and calls add_trait on each. It is the fastest way to hand a Sim a whole category and the fastest way to make a mess, since every add still runs its own tuned loot.

Note what is missing from the usable set. traits.clear_traits, the one that clears everything rather than only personality traits, is automation type and does not run for a player.

Object preferences, filed under the same namespace

These two commands handle a Sim's likes and dislikes for object types rather than personality traits, which is why they surface in trait searches. The first argument is a trait reference again, and preference_type defaults to GameplayObjectPreferenceTypes.NONE. The removal side, traits.remove_gameplay_object_preference, drops the preference argument. Which references are valid is not stated in the registration, so this page prints the signature and stops.

What this page does not print

A trait list. Every page ranking for this query has one, and none of them can point at the file it came from.

The trait names live in the game's tuning resources, not in the Python this site extracts, so a name list here would be a transcription of someone else's transcription. Trying a wrong identifier only costs you the ten seconds it took to type, but a borrowed list gives you no way to tell which of its entries have gone stale. The commands above are proven to the line that registers them. The names will be published the same way or not at all.

Enabling cheats and typing them

Ctrl+Shift+C opens the console, and it is the same combination on Mac: the Control key, not Command. Command+Shift+C is a macOS shortcut that the game never sees, so a Mac player who reaches for it gets nothing back and concludes cheats are broken.

On PlayStation and Xbox, EA documents the cheat box as opening when all four shoulder buttons are held at once, with the note that a keyboard attached to a console still uses Ctrl+Shift+C. Trait commands are the worst case on a controller: the argument is a long identifier typed on an on-screen keyboard, and one wrong character gets you a No names matched line instead of the trait.

EA's cheat FAQ states that cheat codes requiring testingcheats true disable achievements and trophies in the save being played, other saves unaffected, with build mode cheats exempt.

Traits change how a Sim behaves, not what a Sim needs, so if the goal is a Sim who stops complaining the faster route is how to kill a sim on the sims 4. Editing the Sim itself, including in Create a Sim, is the cas cheat sims 4.