- Apr 29, 2020
- 1,681
- 2,788
Have you looked into bypassing the API and webscraping the ChatGPT interface to cut down on cost?
Even saying that, $14 sounds pretty reasonable given that manually cleaning up DeepL translation of a large CommonEvent file could be as much as 16-20h of work. Playing your Sol/Rui After Mini translation I'm pretty impressed with ChatGPT's work. There are a few errors and weird phrasing, but mostly very understandable.
Looking through your code, you will encounter problems on more complex games. Firstly, you'll be missing all the displayed text that can be stored in plugins.js, and in nightmare scenarios, the plugins themselves. Most games include at least a few configuration/menu settings in the plugins.js file, but more complex features like quest guides and some custom erotic status menus also rely on it heavily. I see you commented out the 355 code, and probably for the best, that will be another place where things are fragile but important, and would require more processing by you (I don't know if ChatGPT can handle non-coding spaces, but they are sometimes important).
Another piece of advice for the code is to reduce the number of prompts you need to give to ChatGPT by cleaning up the RPGM code yourself a little. Replace \\I[38] with [i38] for example, then telling chatGPT to ignore anything in []. That way you can also handle colours \\C[4] to [c4], variables, etc. This would make it more robust for other users as well and require less intervention by the translator. After you get the translated text just restore the [i38] to \\I[38].
Even saying that, $14 sounds pretty reasonable given that manually cleaning up DeepL translation of a large CommonEvent file could be as much as 16-20h of work. Playing your Sol/Rui After Mini translation I'm pretty impressed with ChatGPT's work. There are a few errors and weird phrasing, but mostly very understandable.
Looking through your code, you will encounter problems on more complex games. Firstly, you'll be missing all the displayed text that can be stored in plugins.js, and in nightmare scenarios, the plugins themselves. Most games include at least a few configuration/menu settings in the plugins.js file, but more complex features like quest guides and some custom erotic status menus also rely on it heavily. I see you commented out the 355 code, and probably for the best, that will be another place where things are fragile but important, and would require more processing by you (I don't know if ChatGPT can handle non-coding spaces, but they are sometimes important).
Another piece of advice for the code is to reduce the number of prompts you need to give to ChatGPT by cleaning up the RPGM code yourself a little. Replace \\I[38] with [i38] for example, then telling chatGPT to ignore anything in []. That way you can also handle colours \\C[4] to [c4], variables, etc. This would make it more robust for other users as well and require less intervention by the translator. After you get the translated text just restore the [i38] to \\I[38].
Last edited: