#Rpg vx ace rtp translator free
#Rpg vx ace rtp translator windows

In these cases the following procedure works best Sometimes games are coded in a way where a script will look up a choice by the actual Japanese string. I was playing a translated game and got an error message that closed the game, wtf?ДЇirst thing: CONFIRM THAT THE ORIGINAL, UNTRANSLATED GAME DOES NOT HAVE ANY ERRORS Even if you have 100% of the blocks pre-cached it will take several minutes to work through. The main part of the tool is also written in ruby which is not exactly known for its blazing speed.

#Rpg vx ace rtp translator free

The API is one of the only free to use translation APIs and as such, to respect the API maintainer, its usage is throttled. If you start with a blank translation file for a new language or just are unfortunate in that whatever game you are translating needs to call the API a bunch, it will be slow. Some larger games can have 10s of thousands of blocks to translate. Sometimes text is hardcoded in scripts themselves as well which would require much more effort to translate since simple translating all strings would most likely break things.

Game variable names themselves are also not translated to prevent script errors. Other caveats exist such as text lines which contain variables like 'text:text' are skipped, translating bits of these lines has adverse affects so it errs on the side of caution. The tool will run for these and recognize some common data files to automatically skip over but to translate the actual text requires you to work with those other scripting engines and is not currently possible. I ran the translator but some text is still in Japanese, wtf?Д¬ertain games, especially those by OneOne1 read most of their dialog and text from different script engines not native to RPG Maker.

#Rpg vx ace rtp translator windows

Ruby in Windows cannot seem to handle the copy when Japanese chars exist in the path. The other common reason for this both the source and the destination directory cannot contain Japanese anywhere in the path. The most common reason this would happen is if your output directory does not exist. I hit translate and it gave no output and stopped immediately, wtf? In this way after several games are run and the translation file starts getting large, the cache file could be pruned of all entries which were accessed less than X number of times. The major feature that didn't make it in was keeping a record of the number of times each cache entry is hit. Processed 843440 lines in 17342.666943 seconds Originally planned but scrapped Best way to ensure a translation is complete is to look for all OK on the processing from JSON -> data files then a final log statement which looks like: Partial translation is not clearly indicated to the user after a run.If it starts snapping up then back down turn off auto scroll then turn it back on again to snap to last line.

The behavior of the scrollbar is a little wonky when it's translating.

Move the main data file to a (.backup) version to force RPG Maker to load in the new files.

Re-create the data files from the translated json files.

if it isn't cached hit translation API and cache result.

For each block check cache and return if it's cached already.

Break the string for the original tag into 'blocks' by only translating uninterrupted sequences of Japanese characters.

For each line check for an 'original' tag.

Loading a cache file for the output language if it exists.

Run translation for all non-skipped files.

Extract all the data files and assets from the main data file.

Back up any original data files that exist in the original's Data directory (pre-translated).

Copy the source directory to the output directory (/).

The script runs several steps which can be altered by the settings: There are three main dependencies for this tool that are included and one that is not. There is currently no extract or translation aid tool for MV. The tool supports RPG Maker XP, VX, and VX Ace. It is this author's hope that a master cache translation file can be built up for each language allowing quick and easy translations in the future. It supports output into several languages supported by the underlying API. The GUI app runs this script and hooks into its logs as well as providing functionality to edit settings and cached translations. The core of this tool is a ruby script called auto_translate.rb.