Translation

[alexey-va]

Changes

• Added translation via configuration
• Broken pom and main class a bit (could not compile with dough) so it needs a little tweaking

Not very clean yet

Checklist

• I followed the existing code standards and didn't mess up the formatting.
• I did my best to add documentation to any public classes or methods I added.
• I have added Nonnull and Nullable annotations to my methods to indicate their behaviour for null values
• I have fully tested the proposed changes and promise that they will not break world generation, mob spawning, and the like.

[alexey-va]

the way you inject sources and trades in lore is a problem though. I personally added config option to disable injecting them at all. Also one can add something like this in translation:

drops-on: "Drops on:"
possible-piglin-reward: "Possible Piglin reward:"

then all thats left is to translate sources and rewards

[alexey-va]

More or less ready I think. Also added some useful config options

[FN-FAL113]

big pr, could have been segmented nonetheless I appreciate your effort and time for doing the feature and chores. I will check this out from time to time as I am currently busy with life.

[alexey-va]

Broke it into 3 steps:

• Translating items
• Translating messages
• Translating sources/trades

Didn't take much time though, I just wrote proxy classes so that when you create items or use sources/trades they are appended to translation config file. Took like 1-2 hours total. Most lines don't have any logic, only main class needs rework on your part (I broke dough integration cuz couldn't compile with it)

[FN-FAL113]

Broke it into 3 steps:

• Translating items
• Translating messages
• Translating sources/trades

Didn't take much time though, I just wrote proxy classes so that when you create items or use sources/trades they are appended to translation config file. Took like 1-2 hours total. Most lines don't have any logic, only main class needs rework on your part (I broke dough integration cuz couldn't compile with it)

can you revert back to using dough common and dough updater but only updating the commit hash using recent successful build/s from jitpack dough jitpack. If you're using intellij you can try clearing and invaliding cache. For vscode it will ask to update the classpath. Reason why I use updater and common as I do not use the whole dough-api and at the same time to lessen uber jar size.

[alexey-va]

updating to latest build from jitpack solved the issue

[FN-FAL113]

There's just small conflict on this caused by the newly merged pr.