|
EqualsCode:stream.createFrame(214); stream.method433(anInt1084); stream.method424(j1); stream.method433(anInt1085); stream.method431(mouseInvInterfaceIndex);
NOTCode:int window = stream.readUnsignedWordBigEndianA(); // Not sure what content type 206 for interfaces is, but this changes to 1 if the content type is 206 otherwise its 0 stream.readUnsignedByteC(); int from = stream.readUnsignedWordBigEndianA(); int to = stream.readUnsignedWordBigEndian();
Code:int somejunk = stream.readUnsignedWordA(); // junk int itemFrom = stream.readUnsignedWordA();// slot1 int itemTo = (stream.readUnsignedWordA() - 128);// slot2
there is no junk sent in jagex packets
But the method it uses parameters are already identified, I think it's just laziness that it wasn't changed.
Code:moveItems(final int from, final int to, final int moveWindow)
No, it causes a couple of issues. You can see the issues it causes when moving items past slot 128 of the bank. The item moves then goes back to its original slot as the to and from are in the - values, nearly every single server suffers from it, also the interface id is incorrect from it too, so don't forget to update those in the moveItems function.
the interface that uses content type 206 is the bank btw
so 1 = bank
0 = other
Yea i agree with 1776
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |