Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth.com website
Is your suggested feature related to a problem? Please describe.
Plugin developers currently cannot provide different plugin builds for different languages. For plugins with complex logic, maintaining translations inside a single JAR is often harder than generating separate language-specific JAR files. This limits localization flexibility and makes it more difficult to distribute plugins to a global audience.
Describe the solution you'd like
Add an option to publish multiple language-specific JAR files for the same plugin version. During download, users could select their preferred language, and the platform would provide the corresponding JAR file.
Describe alternatives you've considered
Using a single JAR with built-in translations is possible, but for complex plugins it increases maintenance complexity and may not cover language-specific files, comments, or resources as effectively. Generating separate JARs for each language is easy to automate with Maven or Gradle and provides cleaner localization.
Additional context
No response
Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth.com website
Is your suggested feature related to a problem? Please describe.
Plugin developers currently cannot provide different plugin builds for different languages. For plugins with complex logic, maintaining translations inside a single JAR is often harder than generating separate language-specific JAR files. This limits localization flexibility and makes it more difficult to distribute plugins to a global audience.
Describe the solution you'd like
Add an option to publish multiple language-specific JAR files for the same plugin version. During download, users could select their preferred language, and the platform would provide the corresponding JAR file.
Describe alternatives you've considered
Using a single JAR with built-in translations is possible, but for complex plugins it increases maintenance complexity and may not cover language-specific files, comments, or resources as effectively. Generating separate JARs for each language is easy to automate with Maven or Gradle and provides cleaner localization.
Additional context
No response