Tutorial Rpgm Extractor v.2.1.2
Tutorial Rpgm Extractor v.2.1.2
Activation
How to change the language and graphics.
You'll find everything you need in the settings menu.
Every change will be retained thanks to the SETTINGS file.
Analysis and Translation
Before performing a translation, it's advisable to analyze the texts with all available parameters, in addition to those enabled by default (safe).
Why aren't all of them enabled?
In some games, certain parameters simply contain code that shouldn't be translated.
Once you have performed the simulation and selected the parameters you want to translate, press confirm to enable them during the translation
NB: The 408 code is one of the most deceptive, because even though it appears to be textual, it risks crashing the game if translated, as most of the time it's developer comments or code.
Furthermore, during the simulation, don't select "key": "text" and <english translation>.
These two parameters are used to translate games with a translation layer system.
In this procedure we perform an automatic translation without modifying the structure.
"optionally if the text goes out of the box we can add line breaks based on the number of characters"
with the functionality:
Tool > Wrap Text
What does merge parameter + wrap text enable do?
merge unifies consecutive parameters that are normally separate. (Thus leaving you with a single line.)
wrap text: forcefully wraps lines after a certain number of characters.
Result: The text is neater than wrapped text alone because the lines are first merged and then wrapped. Furthermore, the translator, receiving the entire dialogue, will translate it a little better.
When should I use Merge parameter without wrap text?
When games automatically handle line breaks.
If wrap is used in those cases, your line break will not be calculated. Furthermore, where it is applied, the two words will be stuck together.
For example: helloword
You're probably wondering what the point of not always enabling the merge parameter and wrap text feature is, given the better results.
The answer is that in some games, it creates layout issues. For example, Sword Art Online, which shouldn't use either the merge parameter or wrap text because it disrupts the layout, which has been overly strictly defined by the developer.
In these cases, it's best to translate it normally and change the font manually.
These three buttons are used to encode the enclosed variables. If enabled, they will encode them during translation; if disabled, they will remain free.
If disabled, they will still retain a minimum criterion by which they will be encoded, such as whether they are just numbers or enclosed signs.
Journal quests are those located inside the plugins.js file
The json quests are located inside the data folder usually called quest.json but sometimes they change the name.
To create a dictionary, you need to do a translation normally, then in the menu press on memory > save dict
In the video, I simulated a game update by deleting 8 lines of text from the dictionary.json to demonstrate how it recreates the translate.txt file with the 8 lines removed.
To load a translation into a game update, follow these steps:
Rebuild the structure if you used merge parameters in the previous version. Then: "Tool > Merge params" Otherwise, skip to step 2.
Load the dictionary: "Memory > Load Dict" (the program will automatically replace previously translated texts, automatically generating the untranslated dict).
From the menu, go to "Translator" and translate the newly generated file.
From the menu, go to "Extractor > Load Translation" to upload the new part.
If you previously used wrap text, apply it after step 4 with "Tool > Wrap Text"
Once the process is complete, you can save the dictionary again to update it with the new texts.