Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for mod translations done using 'yamlang' Gradle plugin #2339

Open
Octol1ttle opened this issue Jul 29, 2024 · 1 comment
Open

Support for mod translations done using 'yamlang' Gradle plugin #2339

Octol1ttle opened this issue Jul 29, 2024 · 1 comment
Labels
feature: i18n status: future This is something we'd like to do, but we don't have the time now status: pr welcome We probably won't implement the issue ourselves, but we may be willing to merge a PR type: enhancement

Comments

@Octol1ttle
Copy link
Contributor

Minecraft Development for IntelliJ plugin version

2024.1-1.8.0

Description of the feature request

Some Minecraft mods have switched to using a Gradle plugin called yamlang for their translation files. This Gradle plugin allows mod developers to write their language files in nestable YAML and have it be automatically converted to a game-readable JSON file during build. However, Minecraft Development does not recognize these files as language files, and such can't provide its useful inspections such as missing translations. The request is to make MCDev's functionality support translation files written in YAML.

@enjarai
Copy link

enjarai commented Jul 29, 2024

I personally have begun using yamlang for all my new mods. It's a massive improvement over the default json file Minecraft uses. Having support for it in Intellij would be amazing.

@RedNesto RedNesto added status: future This is something we'd like to do, but we don't have the time now feature: i18n status: pr welcome We probably won't implement the issue ourselves, but we may be willing to merge a PR and removed status: unverified Needs triage labels Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: i18n status: future This is something we'd like to do, but we don't have the time now status: pr welcome We probably won't implement the issue ourselves, but we may be willing to merge a PR type: enhancement
Projects
None yet
Development

No branches or pull requests

3 participants