Posts: 219
Threads: 11
Joined: Dec 2013
Thanks: 0
Given 1 thank(s) in 4 post(s)
02-03-2014, 01:37 AM
(This post was last modified: 02-03-2014, 01:59 AM by daniel0916.)
I will start working to add the 1.8 changes (It's only a nextproject. Enchanting is more important.).
Now i will make the protocol. I will use the 1.7 Protocol and override the new things (like in older protocols. 1.6 or so..).
Okay, my code is shit.
But now i have it. I removed my old question.
Posts: 6,486
Threads: 176
Joined: Jan 2012
Thanks: 40
Given 156 thank(s) in 838 post(s)
Without the actual on-wire data, there's very little debugging we can do.
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 0
Given 4 thank(s) in 61 post(s)
You need to make it virtual if you want any non-overirden methods to use it. If you dont want to use it in non-overriden methods then you need to remove the override keyword.
Posts: 219
Threads: 11
Joined: Dec 2013
Thanks: 0
Given 1 thank(s) in 4 post(s)
Okay. Now i will start working with 14w03a.
The new datatype position is long. So i need a ReadLong and WriteLong in the ByteBuffer.
But i don't know how can i create this. Can someone help me there?
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 0
Given 4 thank(s) in 61 post(s)
02-04-2014, 04:27 AM
(This post was last modified: 02-04-2014, 04:28 AM by worktycho.)
They already exist, there just called readBEInt64 and writeBEInt64
Posts: 6,486
Threads: 176
Joined: Jan 2012
Thanks: 40
Given 156 thank(s) in 838 post(s)
02-04-2014, 05:04 AM
(This post was last modified: 02-04-2014, 05:04 AM by xoft.)
I think you should instead make a cPacketizer::WritePosition(x, y, z) and inside it compose and write the 64-bit value. I think you're overflowing the arithmetic here, but that's just a wild guess.