We need help with recvpackets extraction @bRO
Posted: 03 Sep 2012, 22:45
First of all, for those who are not aware, our situation is a bit different from other RO's community.
LUG (brazil's RO distributor) have been relentlessly fighting openkore. They change packet's ID every week, so we need to extract recvpackets from a new exe after every maintenance, figure out which packets have changed, and so on. On top of that, kLabMouse's extractors don't work very well due to LUG's anti-botting policy, which is very strict.
We have always relayed on the skills of quite a few people who held the knowledge of how to do the entire packets extraction process, send/receive.pm coding, etc.
Now we no longer can count on them for that, and we have to learn how to do these things on our own.
But we're not just waiting for it to happen. We're already joining forces, and thus we have figured out how the whole thing works. The only thing that is troubling us the most, is how to extract the recvpackets.txt, properly order.
kLabMouse has provided us with a correct recvpackets, but we believe it's sorted in such a way that we can't figure out the sync_request's list. And even though we might use this recvpackets (which has been of great use. thatnk you kLabMouse, for all your support), we need to learn how to build this on our own.
We're not asking for a ready-to-go extractor from you. We just wanted to be pointed out in the right direction, in an comprehensible way. We're not dumbs, but we're not pro's either. I', myself, have been messing with kore's coding for just a couple of weeks, and so have many of us.
We already know that we need to disassemble ragexe by using a tool such as OllyDBG, but we're having trouble into operating it, finding and identifying the values which really matters, comparing it with the previous exe, and coding a script which apropriately extracts our precious recvpackets.
For anyone who can offer any kind of help, our sicerely thanks.
LUG (brazil's RO distributor) have been relentlessly fighting openkore. They change packet's ID every week, so we need to extract recvpackets from a new exe after every maintenance, figure out which packets have changed, and so on. On top of that, kLabMouse's extractors don't work very well due to LUG's anti-botting policy, which is very strict.
We have always relayed on the skills of quite a few people who held the knowledge of how to do the entire packets extraction process, send/receive.pm coding, etc.
Now we no longer can count on them for that, and we have to learn how to do these things on our own.
But we're not just waiting for it to happen. We're already joining forces, and thus we have figured out how the whole thing works. The only thing that is troubling us the most, is how to extract the recvpackets.txt, properly order.
kLabMouse has provided us with a correct recvpackets, but we believe it's sorted in such a way that we can't figure out the sync_request's list. And even though we might use this recvpackets (which has been of great use. thatnk you kLabMouse, for all your support), we need to learn how to build this on our own.
We're not asking for a ready-to-go extractor from you. We just wanted to be pointed out in the right direction, in an comprehensible way. We're not dumbs, but we're not pro's either. I', myself, have been messing with kore's coding for just a couple of weeks, and so have many of us.
We already know that we need to disassemble ragexe by using a tool such as OllyDBG, but we're having trouble into operating it, finding and identifying the values which really matters, comparing it with the previous exe, and coding a script which apropriately extracts our precious recvpackets.
For anyone who can offer any kind of help, our sicerely thanks.