image-2023-12-17-13-32-50-219.png
[SPIGOT-7546] messages.outdated-client not used Created: 17/Dec/23 Updated: 25/Dec/24 Resolved: 23/Dec/23 |
|
| Status: | Resolved |
| Project: | Spigot |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Zhenya Zima | Assignee: | Doc |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
image-2023-12-17-13-32-50-219.png
|
| Version: | 1.20.4 |
| Guidelines Read: | Yes |
| Description |
|
Server uses outdated-server message, if client's version 1.20.1 but the server's version is 1.20.4. |
| Comments |
| Comment by Doc [ 18/Dec/23 ] |
|
Related to https://bugs.mojang.com/browse/MC-231561 (added to ticket) where this starts to happen also i check the lang files and currently the message for client/server outdated are the same then in vanilla in all cases show the same message, i try find this and not found then i create another ticker for that (unless is duplicated) https://bugs.mojang.com/browse/MC-267365 |
| Comment by md_5 [ 18/Dec/23 ] |
|
Yeah that is the issue, and it's present in Vanilla too. We should probably fix though, just need someone to check if there is a Vanilla bug we can reference first. |
| Comment by Doc [ 17/Dec/23 ] |
|
Maybe the issue is most the static value used in NMS https://hub.spigotmc.org/stash/projects/SPIGOT/repos/spigot/browse/CraftBukkit-Patches/0019-Configurable-Messages.patch#14 based in the patch show by md_5 |
| Comment by Zhenya Zima [ 17/Dec/23 ] |
|
3973-Spigot-ce0f71e-e37e29c (1.20.4) w/o plugins |
| Comment by Doc [ 17/Dec/23 ] |
|
This was tested in a vanilla server? |
| Comment by md_5 [ 17/Dec/23 ] |
|
Looks to be a Vanilla bug |
| Comment by Zhenya Zima [ 17/Dec/23 ] |
|
So strange.. |
| Comment by md_5 [ 17/Dec/23 ] |
|
You sure about that? https://hub.spigotmc.org/stash/projects/SPIGOT/repos/spigot/browse/CraftBukkit-Patches/0019-Configurable-Messages.patch |
| Comment by Zhenya Zima [ 17/Dec/23 ] |
|
(completely updated issue and apologize for activity flood; after checking, the previous issue was not with Spigot, but in its fork, which I launched instead due to inattention) |