Link: https://store.steampowered.com/app/3920860/RPG_Developer_Bakin_Localization_Toolkit/

Before you would have to use translator++ which required paying for 2 months of the patron for an in progress plugin which was buggy and could quickly lead to errors. Now you can buy the official DLC for around the same price. It's required for this guide.

Click on localize and wait for it to load.

Select EN for the fallback language.

Then add any languages you want and select the codes for the languages. Rows F+ will be new languages.

Then select Export. This will give localize.xlsx

This is something smaller, but I should cover it if you are like me and reference text like a name/item thought multiple events and variables.

Grouped: Better overall if you do not mess with reusing text over a bunch of variables. It's also guaranteed you won't miss anything as it's automatically grouped. (Note, if you have too many references to at least one text that is reused a bunch, then Bakin will not export the file and 100% will fail to import it.

Ungrouped: This is purely if you reference things too much or reuse a bunch of the text time for item chests for example. Most of this can be avoided with using common events for controlling certain logic, like chests, that have to be reused. Other times the code can't help but have repeated references for strings and checking them. Ungrouped takes a very long time. For me it took over an hour, some people have had it take longer. Depends on how much text you have. For that reason only do this if you need to where it won't import/export otherwise.

Take localize.xlsx and import it into google sheets. You have to create a new google sheets and then import from there and replace the default document.
In Column F row 2, you have two options:

1. =GOOGLETRANSLATE(E2, "en", "COUNTRY CODE FOR THE LANGUAGE") Then drag it down to the bottom row with the blue dot

2. =BYROW(E2:E(whatever number the last now is), LAMBDA(x, GOOGLETRANSLATE(x, "en", "COUNTRY CODE FOR THE LANGUAGE"))) (WARNING, this will active break all of the code when editing a single line. It's why you should use the first option, but you can use this if you let it translate, copy and paste the values, and then do the edits.)

You might be asking why to do one over the other. The first one is more straight forward but is much slower as it will apply to every single row at a time to prevent any crashes. The second one will do it row by row in order and apply the code, and doesn't require dragging the blue dot to the bottom of the page.

Either way this process takes 15-20 minutes for each language, it depends on how much text there is. Since google sheets is online, it does it in the background automatically even if you click off the page.

Even if you are using an actual translator, it's best to import into google sheets anyways for easier sharing and viewing of content. You can see if they are importing or using google translate anyways through the edit history of the document.

Before exporting and importing again, you need to select every row from F2 to the end and copy it. Paste it with values only. This is so the values can become imported into RPG developer Bakin normally.

Go to file and export and download it in the xlsx format.

Go back to Bakin and select to import. Select all of the code outside the original language. This is so it's not reimported over which gives Bakin more work for nothing to gain.

This will take a while for Bakin to compile everything being imported, since Bakin's base language content is a couple of thousand lines on it's own.

Once it has imported, press apply, then ok, then save.

It should work well, but you might want to make sure. The only thing you have to check is if text codes got overwritten or in certain cases if text needs to be exact, then you make sure it's exactly translated or reused in a string. It's very easy to miss anything.

THIS IS IMPORTANT, SINCE BROKEN TEXT CODES ANYWHERE BREAKS THE EXPORTED GAME IN THAT LANGUAGE.

Ironically I would leave the rows with text codes, mainly layout codes, blanks for translation so they aren't screwed up. You can edit in manually. Later only if it requires it. It does make text with textcodes done with variables annoying, but it's best to name them so google translate doesn't think they are a word.

Everything should be finalized by this point where you can export the game and it will be running perfectly.

If you enjoyed this simple guide, why not take a look at some RPG developer Bakin games and give a wishlist if you desire to?

https://store.steampowered.com/app/3908320/Conviction_Chronicles/

https://store.steampowered.com/app/3174830/Throne_Requiem/