What I meant is 65536 is (0000 0000 0000 0001 0000 0000 0000 0000)bin. Notice that 1? It's (1 << 16).Try to change it and see what happens. Try to make it 2 or 3 or w/e and notice the change.
CloudSaint's Jar
06/11/2014 20:11
-impulse-#16
06/11/2014 21:07
InsomniacPro#17
Aha, there we go. Thanks a bunch Alex, completely understood!Quote:
What I meant is 65536 is (0000 0000 0000 0001 0000 0000 0000 0000)bin. Notice that 1? It's (1 << 16).Try to change it and see what happens. Try to make it 2 or 3 or w/e and notice the change.
05/03/2020 11:35
Mr.Junky#18
Sorry for pumping old posts
the problem here is when I go in team and someone else (not me) killing the mobs for my jar, it doesn't update in realtime, I need to re-log to see the updated count
I already tried to re-send packet 1022 with the updated info to the client but it doesn't update in front end, it works perfect in back end
Is there a way to re-send the packet from client to server to re-update the jar countQuote:
Durability is the amount of kills.
The client will automatically update the jar client side, all you need to do is update it server side so a re-log will show the count correctly.
It only sends packet 1022 once, which is the first time you hover the mouse over it.
This is to update the kill count within the client to display it correctly.
the problem here is when I go in team and someone else (not me) killing the mobs for my jar, it doesn't update in realtime, I need to re-log to see the updated count
I already tried to re-send packet 1022 with the updated info to the client but it doesn't update in front end, it works perfect in back end