From eb7c8e14f0481fed609ae1ec30795e1387653ff4 Mon Sep 17 00:00:00 2001 From: Sylvi <69098783+wingedcatgirl@users.noreply.github.com> Date: Sun, 18 Jan 2026 14:59:46 -0500 Subject: [PATCH 1/4] Mention `dump_loc` here --- Localization.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Localization.md b/Localization.md index eb59fa7..b5bbf60 100644 --- a/Localization.md +++ b/Localization.md @@ -114,6 +114,9 @@ return { } ``` +### Migrating to localization files +If you've been using `loc_txt` and wish to switch to using localization files, disable as many other mods as possible (if you have cross-mod content, you may wish to reconfigure it so it can load even with the other mod disabled), add `"dump_loc": true` to [your mod's metadata](https://github.com/Steamodded/smods/wiki/Mod-Metadata), and launch Balatro once. Steamodded will create a `dump.lua` file in your mod's localization folder, containing all modified localization entries. Remove any extraneous entries (e.g. from other mods you couldn't disable due to being dependencies) and rename this file to `en-us.lua`. + ## `loc_txt` Alternatively, you can define a `loc_txt` table on each object to create its description. This is more limited than the above option because it does not allow creating multiple descriptions for the same object or strings that don't belong to an object at all. The effort of maintaining translations of your mod while using this method is significantly higher. From 933d046a1169267bea29cde1309d463cdf6578e1 Mon Sep 17 00:00:00 2001 From: Sylvi <69098783+wingedcatgirl@users.noreply.github.com> Date: Sun, 18 Jan 2026 15:08:39 -0500 Subject: [PATCH 2/4] toc --- Localization.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Localization.md b/Localization.md index b5bbf60..d93a363 100644 --- a/Localization.md +++ b/Localization.md @@ -3,6 +3,7 @@ Steamodded offers multiple ways to load strings for in-game descriptions and oth - [Localization Files](#localization-files-recommended) - [Adding your descriptions](#adding-your-descriptions) + - [Migrating to localization files](#migrating-to-localization-files) - [`loc_txt`](#loc_txt) - [`mod.process.loc_text`](#modprocessloc_text) - [Text Formatting](#text-formatting) From 69fb95550157efbc33816f9444df6bd328cfc05b Mon Sep 17 00:00:00 2001 From: Sylvi <69098783+wingedcatgirl@users.noreply.github.com> Date: Sun, 18 Jan 2026 15:12:10 -0500 Subject: [PATCH 3/4] clearer phrasing --- Localization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Localization.md b/Localization.md index d93a363..cc4df61 100644 --- a/Localization.md +++ b/Localization.md @@ -119,7 +119,7 @@ return { If you've been using `loc_txt` and wish to switch to using localization files, disable as many other mods as possible (if you have cross-mod content, you may wish to reconfigure it so it can load even with the other mod disabled), add `"dump_loc": true` to [your mod's metadata](https://github.com/Steamodded/smods/wiki/Mod-Metadata), and launch Balatro once. Steamodded will create a `dump.lua` file in your mod's localization folder, containing all modified localization entries. Remove any extraneous entries (e.g. from other mods you couldn't disable due to being dependencies) and rename this file to `en-us.lua`. ## `loc_txt` -Alternatively, you can define a `loc_txt` table on each object to create its description. This is more limited than the above option because it does not allow creating multiple descriptions for the same object or strings that don't belong to an object at all. The effort of maintaining translations of your mod while using this method is significantly higher. +Alternatively, you can define a `loc_txt` table on each object to create its description. This is more limited than localization files because it does not allow creating multiple descriptions for the same object or strings that don't belong to an object at all. The effort of maintaining translations of your mod while using this method is significantly higher. You can provide a single table for every language, or provide a subtable for each language. If the currently selected language isn't provided, the `default` subtable, the English (`'en_us'`) subtable, or `loc_txt` itself will be used as defaults, in that order. Refer to your object's documentation for what fields need to go in `loc_txt`. From 40c2247ded6fecd251ef19a040b441673fa07008 Mon Sep 17 00:00:00 2001 From: Sylvi <69098783+wingedcatgirl@users.noreply.github.com> Date: Sun, 18 Jan 2026 15:14:18 -0500 Subject: [PATCH 4/4] don't forgor --- Localization.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Localization.md b/Localization.md index cc4df61..7d8b271 100644 --- a/Localization.md +++ b/Localization.md @@ -118,6 +118,8 @@ return { ### Migrating to localization files If you've been using `loc_txt` and wish to switch to using localization files, disable as many other mods as possible (if you have cross-mod content, you may wish to reconfigure it so it can load even with the other mod disabled), add `"dump_loc": true` to [your mod's metadata](https://github.com/Steamodded/smods/wiki/Mod-Metadata), and launch Balatro once. Steamodded will create a `dump.lua` file in your mod's localization folder, containing all modified localization entries. Remove any extraneous entries (e.g. from other mods you couldn't disable due to being dependencies) and rename this file to `en-us.lua`. +Remember to remove the `dump_loc` entry when finished! + ## `loc_txt` Alternatively, you can define a `loc_txt` table on each object to create its description. This is more limited than localization files because it does not allow creating multiple descriptions for the same object or strings that don't belong to an object at all. The effort of maintaining translations of your mod while using this method is significantly higher.