New minecraft version. (1.15)
#71
If you were an op / admin, and suddenly blocks started disappearing around you, I think you'd start caring Smile
True, this is quite far-fetched. We'll see.
Reply
Thanks given by:
#72
It's almost time for 1.7: https://mojang.com/2013/10/minecraft-1-7...the-world/
Reply
Thanks given by:
#73
I've just glanced through the 1.7 protocol, I have to say I'm pleasantly surprised. FINALLY they decided to include a length field for each packet, so that it can be easily parsed Smile
Reply
Thanks given by:
#74
1.7.2 is released.
Reply
Thanks given by:
#75
I guess I'll have to more-than-glance at the protocol docsTongue
Reply
Thanks given by:
#76
I seem unable to run the vanilla 1.7.2 server. I start the exe, the java process starts and then terminates within a second, without showing any window or even spitting anything in the console. Does this happen to anyone else?

Ah, found it - not enough RAM. When run with less RAM in the -Xmx and -Xms params, the server started just fine.

It wouldn't be Mojang if there weren't a stupid twist in the protocol.

The packet type 0 is used for 0 different things, based on whether one has been already received or not - initial handshake or keepalive. WHY?

Also, they renumbered the packets, just so that the numbers are different now. No logical reason behind the renumbering, the packets aren't grouped any better than before.

And the packets have different numbers in each direction? WTF are they smoking there? Why is a chat packet type 1 in one direction, but type 2 in the other?
Reply
Thanks given by:
#77
Yup, sounds like something Mojang did Smile
You know something's wrong when their protocol starts making sense
Reply
Thanks given by:
#78
Networking is completely re-written, so... good luck!
Reply
Thanks given by:
#79
It is doable, we just lost a bit of in-source documentation - we had comments like "sends an UpdateWindowProperty (0x69) packet", which are now mostly invalid.
Reply
Thanks given by:
#80
The server issue persists, it seems I've hit this one:
https://mojang.atlassian.net/browse/MC-33014

When I specify the -Xms1024M param, the server crashes with the error; if I use 512M instead, it starts fine. I have enough free phys & virt RAM to run 1024M.
Reply
Thanks given by:




Users browsing this thread: 2 Guest(s)