lord_jag Report post Posted December 11, 2007 Well... i dont know how many other bots had this issue, but the server used to accept a 16 bit value as a 32 bit value... You used to be able to send 5 bytes in the Put item for trade (36) message(use a 16 bit amount). No longer. Now you MUST use a 32 bit amount which means you have to send 7 bytes. Just thought you should know. It's now just ignoring 16 bit values that were not in the protocol to begin with, but used to work nonetheless. Share this post Link to post Share on other sites
Learner Report post Posted December 11, 2007 Well... i dont know how many other bots had this issue, but the server used to accept a 16 bit value as a 32 bit value... You used to be able to send 5 bytes in the Put item for trade (36) message(use a 16 bit amount). No longer. Now you MUST use a 32 bit amount which means you have to send 7 bytes. Just thought you should know. It's now just ignoring 16 bit values that were not in the protocol to begin with, but used to work nonetheless. Anyone that had been using 16 bits in the past was at risk for being scammed if lots of gc was involved (specially with bots that made change). The changed over to 32 bit for bots should have been done a long time ago. Share this post Link to post Share on other sites
nicky Report post Posted December 22, 2007 Yeah, after the server change i had to modify the packet size for certain transactions. Our code used to send whatever size fit the amount of gc's we wanted to put up. Ent mentioned bug fixes in the release, so i assumed this was one of them. Share this post Link to post Share on other sites
