Andirz.com

Introduction

The Sims 4 separates most player-facing text from gameplay tuning.

A trait, buff or interaction can contain a reference to a string key, while the actual localized text lives inside an STBL resource.

Tuning

Defines the gameplay resource and contains fields that reference localized text.

String key

A numeric identifier that points to a localized string.

STBL

A String Table resource containing keys and their text for one locale.

Locale

The language/region version of that string table.

Mental modelTuning usually says “show string X.” The active locale's STBL says what string X actually displays.

What is an STBL?

STBL means String Table. It stores localized text entries as key/value pairs.

Conceptually:

0x12345678 → "Certified Mechanic"
0x23456789 → "This Sim knows their way around an engine."
0x34567890 → "Repair Vehicle"

The visible text is not identified by its wording. It is identified by its key.

That allows one tuning resource to display different text depending on the player’s game language.

Trait tuning
  → display name key 0x12345678
  → EN: "Certified Mechanic"
  → DE: "Zertifizierter Mechaniker"
  → ES: "Mecánico certificado"
  → RU: "Сертифицированный механик"
  → JA: "認定メカニック"

Localization keys

A localization key or string key is the identifier used to find a text entry in an STBL.

Key firstThe key identifies the semantic string. Every locale should reuse that same key and provide its own text value.

Same key, different language

Key 0x12345678
EN → "Certified Mechanic"
DE → "Zertifizierter Mechaniker"
ES → "Mecánico certificado"
RU → "Сертифицированный механик"
JA → "認定メカニック"

Do not create a new key just because you are translating a string. New keys are for genuinely new strings.

String tokens and placeholders

Some STBL values are not complete static sentences. They contain tokens that the game replaces with runtime values such as a Sim name, number, amount of money or another string.

Hello, {0.SimFirstName}!

If token slot 0 contains Bella Goth, the displayed text can become:

Hello, Bella!

Common tokens

These are useful starting points. Slot 0 below demonstrates the syntax; use the index actually supplied by the caller. A Sim, an object, a number and a string are different kinds of runtime values, so the token must match what its slot contains.

Token Meaning
{0.SimFirstName} First name of a Sim/value supplied in token slot 0
{0.SimName} Full Sim name from slot 0
{0.SimLastName} Last name from slot 0
{0.ObjectName} Name of the object supplied in slot 0
{0.Number} Number supplied in slot 0
{0.Money} Money value supplied in slot 0
{0.String} Another dynamic/localized string supplied in slot 0
More tokens: names, pronouns, objects, time and points

This completes the 36-token catalog offered by STBL Studio’s Token Assistant. The seven common tokens above are not repeated. Each token needs a compatible runtime value in its slot; selecting it in the assistant does not make the caller supply that value.

Names & Pronouns

Token Intended value
{0.SimFirstNameList} List of Sim first names
{0.SimNameAndPronouns} Sim name with pronoun information
{0.SimPronounObjective} Object pronoun, such as him/her
{0.SimPronounPossessiveDependent} Possessive before a noun, such as his/her
{0.SimPronounPossessiveIndependent} Standalone possessive, such as his/hers
{0.SimPronounReflexive} Reflexive pronoun, such as himself/herself
{0.SimPronounSubjective} Subject pronoun, such as he/she
{0.SimPronouns} Sim pronoun information

Objects

Token Intended value
{0.ObjectCatalogDescription} Object catalog description
{0.ObjectCatalogName} Object catalog name
{0.ObjectDescription} Object description

Time

Token Intended value
{0.DateLong} Long date format
{0.DateShort} Short date format
{0.DayOfWeekLong} Long weekday format
{0.DayOfWeekShort} Short weekday format
{0.TimeLong} Long time format
{0.TimeShort} Short time format
{0.Timespan} Duration/time-span format
{0.TimespanShort} Short duration/time-span format

Other

Token Intended value
{0.ClubPoints} Club points
{0.Currency} Currency value
{0.FamePoints} Fame points
{0.GalacticCredits} Galactic credits
{0.Influence} Influence value
{0.OccultPoints} Occult points
{0.PerkPoints} Perk points
{0.Points} Points value
{0.RecyclingBits} Recycling bits
{0.RecyclingPieces} Recycling pieces

The pronoun examples describe grammatical roles; custom pronouns may supply different forms.

Suffixes at a glance

A suffix is a modifier inside the same braces: {1.ObjectName|xxUpper}. Preserve its spelling and the token index when translating. It is not a command to decline a Sim name.

Suffix syntax, available modifiers and limitations

A suffix is a formatting modifier written inside the same braces, after the token name and a pipe (|):

{index.TokenName|suffix}

Without a suffix: {0.SimFirstName}
With a suffix:    {0.SimFirstName|capitalize}

The index is still 0, and the token is still SimFirstName. This is not another argument or an M/F branch. In the assistant, None means “omit the suffix”; do not write |None.

The assistant offers capitalize, enAn, enHouseholdNamePlural, xxAllCaps and xxUpper. For example, choosing slot 1, token ObjectName and suffix xxUpper produces:

{1.ObjectName|xxUpper}

Selecting None for that same slot and token produces:

{1.ObjectName}

The assistant generates the syntax; the game performs the actual formatting. Check a matching game string and its rendered result before relying on a modifier’s exact behavior. Do not assume the capitalization options are interchangeable or every modifier works with every token and locale.

The en... options are English-specific article/household-name formatting options, not universal grammar rules for other languages. None of these options is a general command to decline a Sim name into a different case.

When translating an existing token, preserve the index, token name and suffix spelling. Do not translate suffix names, alter their capitalization or add a modifier simply because the translated sentence begins differently. A deliberate change to a language-specific modifier needs a matching target-locale example and an in-game check.

What do 0, 1, 2… mean?

The number is the token argument index.

0 = first supplied token
1 = second supplied token
2 = third supplied token
3 = fourth supplied token
…

For example:

{0.SimFirstName} greeted {1.SimFirstName}.

If slot 0 contains Bella and slot 1 contains Mortimer, the result is:

Bella greeted Mortimer.
0 does not automatically mean Actor, and 1 does not automatically mean TargetSim.
The system displaying the string decides which runtime values are placed into token slots 0, 1, 2 and so on. The mapping must be read from the caller/context.

The same index is used by grammatical branches:

{M0.He}{F0.She} → gender of token slot 0
{M1.He}{F1.She} → gender of token slot 1
{M2.He}{F2.She} → gender of token slot 2

Changing the number changes the runtime value that controls the branch.

Index ruleIf a word describes token 1, its gender/pronoun branch must also refer to token 1. M1/F1 is not interchangeable with M0/F0.

Grammar branches: gender, stems and plural

Gender branches allow one string to contain alternative text for a Sim token.

{M0.actor}{F0.actress}

The letter selects the branch; the number selects whose gender controls it.

M0 / F0 → token 0
M1 / F1 → token 1
M2 / F2 → token 2

Branch only the part that changes

A branch does not need to contain a whole word. If two forms share a stem, keep the common text outside the token and put only the changing ending inside it.

Language Example What changes?
English {0.SimFirstName} is ready. No gender branch needed in this sentence.
German {0.SimFirstName} ist bereit. No gender branch needed in this sentence.
Spanish {0.SimFirstName} está list{M0.o}{F0.a}. The adjective ending changes: listo/lista.
Russian {0.SimFirstName} готов{F0.а}. The feminine ending is added: готов/готова.
Japanese {0.SimFirstName}は準備ができている。 No grammatical male/female branch is needed.

Every row means the same thing: the named Sim is ready. Different grammar does not change the state being described.

Use a whole word or phrase only when the forms differ enough that a shared stem is no longer practical.

Best practiceKeep shared text outside the branch and branch only the smallest readable part that actually changes.

Singular and plural branches

S and P are used for singular/plural logic, not for English custom pronouns.

Craft {0.Number} {S.candle}{P.candles}

Do not confuse P1 with “pronoun 1”. The P prefix belongs to pluralization syntax; English pronoun tokens use forms such as {1.SimPronounSubjective}.

Translating English custom pronouns

English has special dynamic pronoun placeholders because Sims can use He/Him, She/Her, They/Them or custom pronouns.

Token Role
{0.SimPronounSubjective} subject pronoun
{0.SimPronounObjective} object pronoun
{0.SimPronounPossessiveDependent} possessive before a noun
{0.SimPronounPossessiveIndependent} standalone possessive
{0.SimPronounReflexive} reflexive pronoun

The leading number still means the token index:

{0.SimPronounSubjective} → pronoun for token 0
{1.SimPronounSubjective} → pronoun for token 1

Other locales often use M/F branches or rewrite the sentence instead of reproducing the English custom-pronoun system directly.

Prefer a natural, gender-neutral rewrite when the target language allows it. For example, Spanish can use su for a dependent possessive, and German ist bereit needs no gender branch. If a pronoun is necessary, use the target language’s appropriate form and keep the original controlling index.

Translation examples: subject, object and possessive pronouns

Worked example: subject pronoun

Slot 1 contains the Sim who says they are ready. All four versions express that same meaning:

EN: {1.SimFirstName} says that {1.SimPronounSubjective} is ready.
DE: {1.SimFirstName} sagt, dass {M1.er}{F1.sie} bereit ist.
ES: {1.SimFirstName} dice que está list{M1.o}{F1.a}.
RU: {1.SimFirstName} говорит: «Я готов{F1.а}».

German uses M1/F1 because the pronoun refers to slot 1. Spanish can omit the subject pronoun but still agrees with that same Sim. Russian uses direct speech and agrees with the same Sim, without declining the inserted name.

Worked example: object pronoun

Slot 0 contains the Sim who saw someone; slot 2 contains the Sim who was seen. The translations retain that relationship:

EN: {0.SimFirstName} saw {2.SimPronounObjective}.
DE: {0.SimFirstName} hat {M2.ihn}{F2.sie} gesehen.
ES: {0.SimFirstName} {M2.lo}{F2.la} vio.
RU: {0.SimFirstName} увидел{F0.а} {M2.его}{F2.её}.

The object-pronoun branch belongs to slot 2. The Russian past-tense ending belongs to slot 0 because it describes the Sim who saw someone.

Worked example: dependent possessive

All four versions say that the Sim in slot 1 lost their bag:

EN: {1.SimFirstName} lost {1.SimPronounPossessiveDependent} bag.
DE: {1.SimFirstName} hat {M1.seine}{F1.ihre} Tasche verloren.
ES: {1.SimFirstName} perdió su bolsa.
RU: {1.SimFirstName} потерял{F1.а} свою сумку.

German needs seine/ihre here because Tasche is feminine. Spanish su and Russian свою do not need an M/F branch for the possessive; Russian still needs agreement in the past-tense verb.

Do not copy English custom-pronoun tokens unchanged into a translated sentence whose grammar needs a different construction. This applies to subjective, objective, dependent possessive, independent possessive and reflexive forms. A rewrite or M/F branch is a localization choice; it does not reproduce the full English custom-pronoun system.

Tokens and Participants are related, but not identical.
Participants & Resolvers explains roles such as Actor and TargetSim. The caller decides which of those values, if any, are supplied as token 0, token 1, token 2 and so on.

How tuning connects to text

Many tuning classes expose localized string fields such as display names, descriptions, interaction names, tooltips, notification text, picker titles, career titles and buff/trait text.

The exact field name depends on the tuning class.

Example

A custom trait can contain a display-name field pointing to string key 0x12345678. If the English STBL contains that key with the value Certified Mechanic, that is what an English game displays.

Missing strings

If the active locale does not contain the expected key/value, the player can see missing or blank text, a placeholder, raw-looking output or other fallback behavior depending on the UI path.

Separate gameplay bugs from localization bugs.
If an interaction executes correctly but its label is empty, inspect the string reference and locale STBL before changing the gameplay tuning.

Supported languages and locale codes

The Sims 4 supports 18 game locales.

Language Locale code
English (US) en_US
German de_DE
French (France) fr_FR
Russian ru_RU
Polish pl_PL
Swedish sv_SE
Spanish (Spain) es_ES
Italian it_IT
Dutch nl_NL
Norwegian nb_NO
Danish da_DK
Finnish fi_FI
Portuguese (Brazil) pt_BR
Czech cs_CZ
Chinese (Traditional) zh_TW
Chinese (Simplified) zh_CN
Japanese ja_JP
Korean ko_KR
English is the source language.
For custom Sims 4 mods, author the original strings in the English (`en_US`) STBL. Do not treat the source/primary language as an arbitrary choice when building a normal multilingual mod.

English fallback for untranslated locales

Every locale resource should contain a usable value for every string key your mod exposes to players.

If you do not yet have a translation for a language, copy the English text into that locale’s STBL instead of leaving the value empty.

For example:

Key 0x12345678
EN → "Certified Mechanic"
DE → "Zertifizierter Mechaniker"
ES → "Certified Mechanic"        ← English fallback
RU → "Certified Mechanic"        ← English fallback
JA → "認定メカニック"

The player may see English for an untranslated string, but they will not see a deliberately empty label.

Fallback ruleMissing translation = copy the English value. Do not create empty locale entries.

STBL Studio vs Sims 4 Studio

Frankk’s Online STBL Studio handles this fallback workflow for you when creating localization projects: untranslated language entries can be populated from the English source instead of being left blank.

If you build or maintain STBL resources manually in Sims 4 Studio, you need to ensure this yourself. Create the locale STBL and copy the corresponding English values for every key that has not yet been translated.

A locale table should not be a half-empty skeleton.
Keeping all keys synchronized across English and every other shipped locale also makes later translation updates much easier to audit.

Localizing and translating mods

There are two related but different jobs:

Localization-aware modding

Create stable string keys, author the English source text, reference those keys from tuning and ship synchronized locale STBLs.

Translation

Take those existing keys and replace the English fallback value with equivalent text for another supported locale.

A translator normally should not need to edit gameplay tuning. The task is to preserve every key and token relationship while translating the text values.

Preserve formatting and ordinary placeholders

Keep ordinary placeholders such as {0.Money}, {1.Number}, {2.String} and {1.SimLastName} exactly as supplied. Do not translate their names, change their indices or replace them with example values. The same applies to name tokens. Grammatical M/F branches and English custom-pronoun tokens may need language-specific adaptation, but they must still describe the same runtime slot.

Formatting is also part of the string. Preserve tags such as <font color="#00FF00">, </font>, <b>, </b>, <i>, </i>, <u>, </u>, <br/>, <t> and </t> exactly: keep tag names, attributes, quoting, order, line breaks and whitespace inside and immediately around them. Translate the visible text while retaining its formatting boundaries.

EN: Give gift to <b>{1.SimFirstName}</b>
RU: Сделать подарок: <b>{1.SimFirstName}</b>

Do not swap paired tags, move a line-break tag or replace a literal line break with the characters \n. When working in an exported format such as JSON, preserve that format’s required escaping as well.

Names stay in their base form

The game inserts names through tokens; a translation cannot assume that it will decline them into the case required by the surrounding sentence. This matters in Polish, Russian, Czech and other languages with grammatical cases.

The same source label, Gift for {1.SimFirstName}, illustrates the problem in both languages. The token supplies Anna in Polish and Анна in Russian, while dla and для require the genitive: Anny and Анны.

Language Incorrect: the name cannot decline Rewritten: the name stays in its base form
Polish Prezent dla {1.SimFirstName}
In game: Prezent dla Anna
Prezent — odbiorca: {1.SimFirstName}
In game: Prezent — odbiorca: Anna
Russian Подарок для {1.SimFirstName}
In game: Подарок для Анна
Подарок — получатель: {1.SimFirstName}
In game: Подарок — получатель: Анна

Both rewrites mean Gift — recipient: [name]. They identify the same gift and recipient without requiring a declined name. The token and its index stay unchanged. Check verbs as well as prepositions: either can require a case that the inserted name cannot provide.

Translate meaning and game terminology

Use the target locale’s established Sims 4 terms for Sims, Simoleons, traits, lots and other game concepts. German player-facing instructions normally use Du. Keep labels concise and descriptions natural without adding effects, requirements, quantities or gameplay promises absent from the source.

For AI-assisted translation of a single value, request only the translated string: no introduction, explanation, quotation marks or Markdown wrapper. Keys and file structure belong to the export/import workflow and must remain intact.

Practical translation guide
For the screenshot-based workflow in STBL Studio and language-specific grammar guidance, see Translating Sims 4 Mods.

Overrides, conflicts and custom strings

Custom string

A custom mod normally uses its own stable string keys. This avoids replacing EA text and keeps the mod self-contained.

String override

If a package provides a different value for an existing EA string key in the same locale, it can replace the displayed text wherever that key is used.

One key may be reused in more places than you expect.
Before overriding an EA string, check where the key is referenced. Changing a shared string can alter text in multiple unrelated interfaces.

Key collisions

Two custom mods using the same custom string key for different text can conflict. Good tooling and consistent key-generation practices reduce this risk.

A practical localization workflow

1
Create the English source

Author the original string in the English en_US STBL.

2
Reference its key

Use the same stable string key from tuning.

3
Mirror the key to every locale

Use a real translation where available; otherwise copy the English value.

4
Preserve tokens, grammar and formatting

Keep argument indices, ordinary placeholders and formatting intact. Rewrite names and pronouns naturally for the target locale.

5
Test actual game locales

Check names, descriptions, tooltips, notifications, picker text and token-heavy strings in game.

Common beginner mistakes

1Using a non-English locale as the source instead of authoring the original string in en_US.
2Leaving untranslated locale values empty instead of copying the English fallback.
3Creating a new key for a translation instead of reusing the English key.
4Changing token indices such as 0/1/2 and accidentally making grammar depend on the wrong runtime value.
5Changing an EA key without checking where else it is used.
6Assuming a blank UI label means the gameplay tuning itself is broken.
7Translating token names or changing formatting tags and their attributes.
8Putting a name token into a sentence that requires the name to be declined.
9Copying English pronoun tokens into another locale without adapting its grammar.

Quick reference

Term Meaning
STBL String Table resource containing localized text
String key Identifier shared across locale versions of the same string
English STBL Source/original text for a normal custom mod (en_US)
Locale Language/region version of an STBL
Token index Runtime argument slot: 0, 1, 2…
M/F Gender-dependent branches tied to a token index
S/P Singular/plural branch syntax
English fallback English text copied into a locale until a real translation exists
Override Replacing the value of an existing key
Key collision Two unrelated resources unintentionally using the same key
The core idea
Gameplay tuning references a key; English defines the source text; every shipped locale provides a value for that same key; and tokens insert runtime data into the final sentence.