-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
"Duplicate key" with fields that are equally named #11
Comments
We upgrading to paper 1.21 and now getting the same error in PlayerChunkMap
|
@DerMistkaefer |
This PR since May will close it #9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using ProGuard to obfuscate a plugin that I maintain, together with a
-overloadaggressively
setting that I got from a template back then. Today I learned what that actually does and that it is apparently fully legitimate to have fields be equally named on the bytecode level (source):Which leads to the following error:
Related PR: #9
The text was updated successfully, but these errors were encountered: