Translator v4.3.31 has some bugs:
If you export the project to tpp, the save file name changes from translator.trans to autosave.json.
Workaround: You need to save before you export the game. After the export, close the translator and reopen the translator to load your translate.trans.
The new parser for RPGMaker VX ace is broken.
For games that use RPGMaker's default weather and light system, the system will be broken. Like Games: RJ144501, RJ176529.
If the game contains a main.rvdata2, the parser cannot export it back to game files. There is a parser error without a error description. (RJ406267)
If the game has big map files or a big commonevents file, the Translator closes itself without error message during export back in game files. (RJ354108, RJ215065, RJ176529). For some games it does work if you export the single files in little groups.
If the directory name of Translator++ contains a space (example "Translator++ Ver.4.3.31"), the parser fails sometimes to export the game.
A script got an error without adding a translation to it -> there was a additional %s in line ':rem_state => "-%s%s"'. This crash took a long time to find.
It is in script "LNX11aconf_XPスタイルバトル#コンフィグ" of all games with the new parser.
DECORATION_TEXT = { # 規定値
:add_state => "+%s", # "+%s%s" / ステート付加
:rem_state => "-%s%s", # "-%s%s" / ステート解除
:add_buff => "%s UP", # "%s UP" / 能力強化付加
:add_debuff => "%s DOWN", # "%s DOWN" / 能力弱体付加
:rem_buff => "-%s Buff", # "-%s Buff" / 能力強化/弱体解除
}
I had to disable "Multi threading" because sporadically a few files were missing in Translator++ when creating the project. Also sometimes translator gets stuck during export if enabled.
Edit 2022-12-11:
The new parser for RPGMaker VX is broken.
During export of the scripts, translator++ converts the files to UTF8-BOM which crashes the game. The source files in project are correct UTF8.
Example game RJ273729.
I gave up, you have to wait a few more years for the free version to work. ( I also tried V4.7.30)
