1.5.2 clients show server 1.6.1 as 1.3 in Multiplayer screen
When viewing a 1.6.1 server in the Multiplayer menu on 1.5.2 it shows as 1.3. This has confused a few players of my server and I'm pretty sure its a glitch.
Screenshot: http://puu.sh/3qpkc.jpg
Definitely a 1.6.1 server: http://puu.sh/3qpn7.png
Linked Issues
is duplicated by9
MC-19747Minecraft Server 1.6.1 claims it's version 1.3DuplicateMC-197501.6.1 server shows up as 1.3DuplicateMC-19979I have my server running on 1.6.1 and on the server startup page it says 1.3 instead of 1.6.1DuplicateMC-20022Server reports as 1.3 instead of 1.6.1DuplicateMC-200261.6.1 - 1.3 server lagDuplicateMC-20798Server Is 1.3, when Server Is 1.6?DuplicateMC-212101.6.1 multiplayer server is showing as 1.3 on multiplayer server list.DuplicateMC-216971.6.1 server being listed as 1.3DuplicateMC-22174Some 1.6.1 servers appear as ??? to 1.5.2 clientsDuplicate
Created Issue:
1.6.1 showing as 1.3 in Multiplayer screen
When viewing a 1.6.1 server in the Multiplayer menu on 1.5.2 it shows as 1.3. This has confused a few players of my server and I'm pretty sure its a glitch.#
Screenshot: http://puu.sh/3qpkc.jpg
Definitely a 1.6.1 server: http://puu.sh/3qpn7.png
is duplicated by
is duplicated by
1.6.1 showing as 1.3in Multiplayer screenServer 1.6.1 reports version 1.3 to 1.5.2 clients in Multiplayer screen
Server 1.6.1 reports version 1.3 to 1.5.2 clientsin Multiplayer screen1.5.2 clients show server 1.6.1 as 1.3 in Multiplayer screen
When viewing a 1.6.1 server in the Multiplayer menu on 1.5.2 it shows as 1.3. This has confused a few players of my server and I'm pretty sure its a glitch.
#Screenshot: http://puu.sh/3qpkc.jpg
Definitely a 1.6.1 server: http://puu.sh/3qpn7.png
is duplicated by
is duplicated by
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 57% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 57% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Duplicate of MC-19592, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
Same here.
Definitely.
Confirmed.
In older clients, I'm also getting this,
http://www.imgwiz.com/OqL
After recreatiing the server I've recieved the same error, Instead of making another issue figure this was related.
Confirmed as well.
you should keep this issue as private...
Why would this need to be private? It has no security issues or anything. It's just an information error.
Why keep it private?
Don't mark issues as private, unless your bug report is a security issue containing information that may compromise your server/client. (Which this is not.) People cannot view issues that are private, and so there will be many more dupes.
In MC 1.6.1, the client sends a "Plugin Message" packet along with the request server info packet, the server responds correctly in this case.
If the server does not receive the plugin packet then it sends a pre-1.3 format response (that contains no protocol version info, so old clients assume 1.3)
Thanks for informing us. Makes sense now.
I can vouch for this, i actually got really confused on why it said that.
I guess this isn't really a bug then, however I would've expected it to say 1.5
Fixed.
I'm not sure if this is the same issue, but I'm getting the same problem (server reporting as version 1.3) with a 1.6.1 client and a 1.6.1 server...
Yes it's been confirmed fixed.
Confirmed, but still not fixed Cory. Just updated my server and it still showed at 1.3.
But to add (since I haven't seen anything said about it yet) the server does run 1.6 (or 1.6.1) and you can log in just fine with all the updates etc. Just a glitch in version display
(edit, added that glitch is still happening)
It is fixed for the (not yet released) version 1.6.2 not for 1.6.1
Aaron, it doesn't let me log in when it misdetects the version - the join server button is disabled. If I keep refreshing it sometimes picks up the server is 1.6.1 and then the button is enabled as normal and I can connect and play fine. I have three server instances on the same server (and on my list), and it randomly detects different ones as 1.6.1 each refresh, if indeed at all.
Thanks Kumasasa !
Jamie, I updated the jar file to 1.6.1, and updated to the latest launcher (same one from a week or so ago?) and when I logged in, I admit I freaked out a little, thought all my work in the snapshots was gone!
These server instances, are they different versions? or did you update all their jar files?
One of them is Craftbukkit, so 1.5.2 and irrelevant here, but the other two are using the stock 1.6.1 (just multiple invocations of the same jar).
Are we all on a mac?
Cause, my friends that have a PC (Which is all of them) doesn't say 1.3 in 1.6 servers.
I'm on a PC, and am getting this.
Please wait for 1.6.2 - Not much you we do at this point.
I have client v1.6.2 and server v1.6.2
The 1.6.2 server shows up as 1.3 in the 1.6.2 client. But only via Internet, not local.
Screenshot: http://i.imgur.com/4gvAuox.png
Connecting via local is possible and working perfectly. Connecting via Internet is not working.
I deleted the IP@Internet and local server and tried to connect to the dynamic DNS routed server before the "Join Server" button goes unclickable.
It does not work, but throws some errors: http://i.imgur.com/L7Ek1Tc.png