Thanks for the reply, I am not translating so other people can play, i purely do it for myself so i can understand how to continue the game as I know 0 of Japanese.
So do you have any tips and tricks about how to fast translate a game (even bad translation) without breaking it ?
I also know 0 japanese and have had moderate success in mtl-ing RPGmaker games for personal use with translator++. If you want something mostly functional as quick as possible (HIGHLY dependent on the length of the game):
-Uncheck Animations, CommonEvents, MapInfos, Scripts, System, and Tilesets before batch translating. These files tend to contain lots of text that will break the game if translated. If you want to be extra sure, also uncheck States and Skills to reduce the chance of errors in battle without messing up dialogue.
-This is a good time to wrap text so that the in-game text stays within the dialogue boxes. Check all the translated files and then right-click -> 'With all' -> 'Wrap texts'. 'Source column' should almost always be 'Initial', 'Target Column' is where the program will put the wrapped text.
-At this point, I would save and name the project ('gamename_v01') and then immediately click 'Save As' again ('gamename_v02'). Use v02 as your starting point and keep v01 so that you can quickly replace any translated text you accidentally delete. Ctrl-z works and is super useful, but sometimes you don't realize the mistake until reviewing.
-Look through every file you MTL'd line-by-line to check for potential issues. Yes, every file. Delete any translated text that looks like it's part of the scripting language; these are usually pretty obvious once you get a sense for what you're looking for. Here are some examples of text to look for taken from a tiny project I did yesterday: "MP_SET_MOVIE p2_a Normal_1", "showHpGauge B", " <enemy:104>", anything in [] <>.
-I've found that the best rule is to delete anything I think is even a bit suspicious. It's much easier to start with a limited translation that you know is stable and expand it later than search through thousands of lines of text to solve one issue only to immediately run into another.
If you follow the above, things like the pause/option menus, locations, skill/status names will probably be in japanese, but the majority of the dialogue for objects/characters should be MTL'd. Good luck.
The analogy that comes to mind is wanting to go to the moon by yourself but not being an engineer and not wanting to spend time and resources to learn how to build a rocket. Again, please consider a modicum of patience and hard work in what you're doing; otherwise it will cause problems.
This is a poor analogy. Akrex's goal is to put together a stable and mostly accurate translation for personal use that gives enough information to get them from step 1 to step 2 in a game. MTL is only a step or two above gibberish, but if you're trying to figure out basic information like "what is the next boss weak to" or "where is the item for this quest located", it is an effective, fast, and low/no cost tool.