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

[BUG] Settings can not be multilingual #3359

Closed
GoddenXD opened this issue Jun 30, 2024 · 4 comments
Closed

[BUG] Settings can not be multilingual #3359

GoddenXD opened this issue Jun 30, 2024 · 4 comments
Labels
🐛 bug Something isn't working 👷 development build development build issue 🌑 nextgen

Comments

@GoddenXD
Copy link

GoddenXD commented Jun 30, 2024

LiquidBounce Branch

Nextgen

LiquidBounce Build/Version

all

Operating System

Windows 11

Minecraft Version

1.20.4

Describe the bug

I want to use the local language as the descriptive name so that other users can understand its meaning. The default setting is in English, which causes difficulty for other users to understand (this is a very common issue)

Steps to reproduce

such as create a setting

private val clip by float("距离",10.0f,1.0f..10.0f)
'
Open the GUI menu and click on the module with this setting and the GUI will crash freeze

Client Log

This problem I did not find the output error in the log

Screenshots

bug

@github-actions github-actions bot added 🌑 nextgen 🐛 bug Something isn't working 👷 development build development build issue labels Jun 30, 2024
@CzechHek
Copy link
Contributor

So you suggest, that values should have normal and translated names, where you would see the corresponding translated name and use those names to change the settings via commands. But they would remain saved in native English, so that they would remain universal. That is easily implementable.

@superblaubeere27
Copy link
Contributor

@CzechHek gave a good summary (👍🏻). This is not an issue, just use english names. Our translation files do support chinese so you can just add translation values :)

@superblaubeere27 superblaubeere27 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
@CzechHek
Copy link
Contributor

So this is already a thing? Cool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working 👷 development build development build issue 🌑 nextgen
Projects
None yet
Development

No branches or pull requests

4 participants
@superblaubeere27 @CzechHek @GoddenXD and others