Community Localizations (v1.1.6.0)

Create a Localization

Grim Dawn reads community localizations from the “/localization” subdirectory of the location the game is installed. This is usually similar to “Program Files\Steam\SteamApps\Common\Grim Dawn”. The game reads directly from a .zip file containing your localization files, which can be created using any standard .zip utility.

A community localization consists of a .zip file containing the localization texts along with a “language.def” file which tells the game the name of the localization as well as the font set to use.

example language.def:

author=John Smith

The name given in the language field is what shows up in in game options. Community localizations appear as “community_French” for example in the language selection box in game options.

Localizing DLC

Beginning with the release of the Forgotten Gods expansion (v1.1.0.0), the zip file format has changed to include two subdirectories, “fg” (Forgotten Gods), and “aom” (Ashes of Malmouth). Translation files specific to these expansions should appear in these subfolders, and the game will load them appropriately when the expansions are present. This change has been made to allow translations for the base game and expansions to be contained within a single zip file.

Currently the following font sets are available:

“CS” - Czech
“DE” - German
“EL” - Greek
“ES” - Spanish
“FR” - French
“HU” - Hungarian
“IT” - Italian
“KO” - Korean
“NL” - Dutch
“PL” - Polish
“RU” - Russian
“ZH” - Chinese
“SK” - Slovak
“PT” - Portuguese
“BG” - Bulgarian
“JA” - Japanese
“VI” - Vietnamese
“TH” - Thai
“TR” - Turkish

If you are working on a localization and require a font set for a different language, please PM me the request along with a link to the unicode alphabet for your desired language.

Item Localization

Gender Support

If you want to make use of gender support, you need to edit tagItemNameOrder (it’s the first tag in “tags_items.txt”) to use ‘a’ instead of ‘s’ for the genderized parameters, and specify the index of the parameter which contains the item gender to use for the item.

for example (genderized prefix/quality/style/suffix, with gender chosen by name)


Gender codes would then be given to each tag representing an item name. The code present in the name is then used to pick from the genders supplied in other tags.

for example, a masculine singular object would be defined as follows:


and a genderized suffix would be defined:


Recognized gender codes are:

[ms] Masculine Singular
[fs] Feminine Singular
[ns] Neuter Singular
[mp] Masculine Plural
[fp] Feminine Plural
[np] Neuter Plural

Reorder All Item Names

If you want to change the order in which item names are built for all items (from prefix/quality/style/name/suffix to some other order), you can change the parameter indexes around in tagItemNameOrder.

for example, name/quality/style/prefix/suffix (all items)


Recapitalize Item Names

If you want to recapitalize the item name string after it is created you can prepend ‘$’ to tagItemNameOrder. The string will be changed so that only the first letter is capitalized.


“Godly Plate of the Whale” would become “Godly plate of the whale”.

If you want to mark a specific tag to prevent recapitalization you can prepend ‘$’ to the tag.

tagSuffixWhale=$the Whale

The item name would then become “Godly plate of the Whale”.

Individual Item Tag Reordering

If you require it, you can reorder only some tags, for example to move a certain prefix to the end of the item name, you can prepend reordering info to the tags.

The code is |X where X is from 1 to 9 indicating the new location relative to the locations of other tags.


Tags without reordering info set are considered to have ‘|0’. The tags making up the item name are then sorted in order of their indexes and the item name is created.

In this case, Warrior’s would be moved to the end of the string since all other tags aren’t reordered.

Conversation Localization

Gender of Target

You can change npc speech in conversations based on the gender of the target the npc is talking to (usually the player) using gender tags.

Hello [[ms]sir[fs]madam], how are you today?

Support for Scriptio Continua

If your language uses scriptio continua and you are encountering text wrapping issues in conversations, add the line “wordmode=false” to your language.def file.


If you have game related issues with your translation you can post in this thread for help.

Thanks to the community localizers for their effort! (1.2 MB)


Hello Rhis,

Thanks for the files!

Here are the changes:\aom\aom\npc_necromancer.txt\aom\tagsgdx1_items.txt\fg\fg\npc_endlessdungeon_event_01a.txt\fg\npc_flavor_dreeg_01.txt\fg\npc_flavor_dreeg_02.txt\fg\npc_flavor_solaelweak_05.txt\fg\sq_13_riggsquest_01.txt\fg\tagsgdx2_creatures.txt\fg\tagsgdx2_items.txt\fg\tagsgdx2_skills.txt\fg\tagsgdx2_storyelements.txt\language.def\object_bounty_orderdeathsvigil.txt\object_defensesite_01.txt\object_defensesite_02.txt\object_defensesite_03.txt\object_defensesite_04.txt\tags_items.txt\tags_skills.txt\tags_ui.txt\tags_uimain.txt

1 Like

Thanks Rhis, spanish updated :slight_smile:

I notice a slight difference in some lines of the file “object_bounty_orderdeathsvigil”. They’re different from those in the bounty quest files with the removal of the newline tags {^n}{^n}. This is a mistake I think?

The change in the conversion is intentional to prevent excessive blank spaces in the dialogue UI.

1 Like

I got it, thanks for replying!

Thanks to early text distribution,
the Japanese translation file will be delivered to players at the same time as v1160 release.
Thank you, Dev! :+1:

One small update that is not in the translation pack in Tags_Tutorial.txt but will go live with the update:

tagTutorialTip20TextB=Right-click a component to select it, then left-click on the item you wish to attach it to. Note that each component can only go in certain item types.

tagTutorialTip20SubtitleB, tagTutorialTip20TextC, tagTutorialTip20TextD have been removed.


Russian localization ready to download.

1 Like

Thanks for your hard work. Could you please update the download interface so that it will display correctly as “v.” ? :smiley:


Version in the uploader has now been updated, thanks!


3 posts were split to a new topic: Problems with multiplayer after installing v1.1.6.0

Olá, tenho o Grim Dawn a algum tempo e recentemente comprei todas as expansões e agora com esta atualização não tem mais a opção de idioma em português e como utilizo pela Steam também não consigo usar a versão anterior, podem me ajudar?

1 Like

Alguém sabe se alguém tá fazendo em português?

“About … “If you are working in a location and need a font set for a different language, send me a request along with a link to the unicode alphabet of the desired language.” … Community of Brazil Request the language Portuguese - Brasil (Pt-Br) follows link of unicode alphabet: and the complement of “letters with accent” and “ç”: https: // unicode-table .com / en / # latin-1-supplement”

I would assume you’re already using such letters since they’re supported here on the forum, but not speaking Portugese I don’t know if the game does or not.

as recorded video of the game, when downloading the language, the interface does not show the option. how shall we proceed? follow link of recording:

If the translation is not for version then it does not run!!!

Look at the theme for your translation and check if there exist a new version available and that this version was also uploaded to Crate.

I downloaded all languages, only the Portuguese language does not appear as an option. watch the video:

Because the community hasn’t updated it atm. Last update was back in December so you’ll just have to wait until they get it done.