Tool RPGM SLR Translator - Offline JP to EN Translation for RPG Maker VX, VX Ace, MV, and MZ

[Shisaye]

Hello Shisaye, thanks for the tools.
I got a bit problem when translating this game :

You must be registered to see the links

It does have f95 thread but it had the same problem, i don't know what's OP's translator tools though. https://f95zone.to/threads/the-innk...o-earn-money-in-the-dungeon-sweetspot.231741/

So the problem is there's item named shining that can be appraised to get 1 equipment and it's random, when using translator the shining item keep reappering then nothing can be appraised. So i tried to removed all translation about words "shining" "shiny" "something shining", the item shining didn't reappear anymore but it just poof gone and didn't get the equipment.
Here's the picture using translator:
View attachment 4896411
Then here's using original game:
View attachment 4896413
When using original jp game i got the equipment.

When i fix cells i got 1 purple but i deleted the translation:
View attachment 4896416
View attachment 4896417

**Just when i typed this post, i got what is the problem, it seems Armor.json is the culprit, when i swap Armor.json from original Jp to translated ones it get appraised and i got the item, so what caused this? when i see this i think there's no problem.
Edit2: although changing Armor.json seems to fix item appraisal, turns out the shining item sometimes went poof gone.
Edit3: changing Weapon.json fix edit 2 problem, now the item won't go poof gone, but how to keep item translated without this bug?
Edit 4: Deleting initial translation on all Armor.json and Weapon Json all works fine just without translation(only wrap), new problem occur that all shining item now have infinite uses lol.
View attachment 4896476


View attachment 4896463
View attachment 4896466
View attachment 4896464

The item names repeat in the Commonevents and the Maps.
They are tagged red because they are from a weird custom plugin not recognized by the system.
My assumption is that if you translate all occurrences of the item names the same way it will work normally.
The context for those cells includes: "MZ Plugin Command/RandomItem/random_item/" You can find them by switching the "Target:" in the search menu to "Context".
But they are over 4000 cells so you might want to wait until I've added proper automation for that plugin. I will try to do that for v1.130 as well.

If I ever actually manage to release it...

 

[Shisaye]

Being at prototype 28 36 now, I think it's fair to say that I'm just never going to be happy with it and if I continue like this it's not going to be out before I eventually die from an energy drink overdose.

I need some second opinions.

If you are interested in the DSLR format, meaning using SLR Translator with other LLMs. (The focus right now being on the latest experimental build of DeepSeek.)
And you have actually used complex LLMs before. PM me. (Start Conversation.)
I will explain you the current translation process and available options, and send you the latest prototype for evaluation.

You can then tell me if you believe this is usable for a general audience or not.

THE BIG FAT DISCLAIMER:
DSLR is experimental in nature and not properly tested at all. Unless you have an absolute monster of a rig there is no way to use DSLR without spending money. There is absolutely no guarantee that you get a usable result. You need to understand the cost and risk of using AI and you need to make sure that the api key you use can only use credits you are willing to loose.

 

[Shisaye]

I've released v1.130. (After 38 in between prototype versions...)
Not really because I'm fully happy with DSLR, but because I've fixed so much other stuff for normal SLR that it doesn't make sense to stall the update further.
The main changes for someone who doesn't care about DSLR are:
-Better help menu (Please actually use it. Press F1)
-Better word wrapping
-Automation for new MV/MZ plugins
-Experimental new parser to get rid of de-duplication of cells (Still very slow and clunky, turned off by default)
-More consistent batch sizes (Translations should be faster)

 

[Shisaye]

Apparently I managed to use a wrong folder when uploading the 1.130 release and it had outdated files from an earlier prototype.
Please update to v1.131 and do not try to use DSLR with v1.130, you're just going to waste tokens.

 

[Shisaye]

On the topic of "why would I even care about DSLR?" if there's so many other options to run LLMs on Jsons.

Because I have successfully automated arguing with the LLM and even getting upset with it if it fucks up the entire batch.

All those other engines just accept the output or just have some automatic retries that just ask the same thing again.
Mine detects problems of individual translations and actually specifically tells the LLM how it fucked up. (Among other stuff.)
Here's some examples of the current ones: