-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
1.21 -> 1.20 #861
Comments
Please update all Via* plugins from https://ci.viaversion.com/.In case the issue still persists send the new dump and the issue will be reopened |
The versions are updated... Same dump: https://dump.viaversion.com/483840ca39aab4a180c42604860b8fb9f3458c6cb6009a6b3cda5aaa488dcf70 |
Please update all Via* plugins from https://ci.viaversion.com/.In case the issue still persists send the new dump and the issue will be reopened |
This is visual only. Duplicate of #830 |
Please update all Via* plugins from https://ci.viaversion.com/.In case the issue still persists send the new dump and the issue will be reopened |
Yes, i know that, but is there any way to make it visually to be the same? |
Cause even that is a visual error, is very dellusional on a box pvp server if the player joins on 1.20 |
Sorry for the spam, but it's not okay to already close that.. is still a issue.. the players don't know that is just visual |
'/viaversion dump' Output
https://dump.viaversion.com/7bf691fc14c362655cf2fec3b1ef0fbca51ca23e580033fdb167f074184e38c1
Console Error
No errors
Bug Description
Basically, on the new 1.21 i was able to edit the durability for the armors with ExecutableItems, so i've set a custom durability on the Leather Armor (600), but with ViaBackwards if you join wiht 1.20 that armor has the default durability and the player cand go with the armor on a negative durability but it will still not break
Steps to Reproduce
Expected Behavior
The armor should have the same durability as the player see on 1.21
Additional Server Info
There is a screenshot:
https://dump.viaversion.com/7bf691fc14c362655cf2fec3b1ef0fbca51ca23e580033fdb167f074184e38c1
Checklist
The text was updated successfully, but these errors were encountered: