Packet change in patch 4312

Trust me I hadn't planned on it I just wanted to fix it for me to use whenever I decide to play on a trojan


Maybe I should release it without the aimbot would that be better?

Yes that would be great cause the other functions of it I enjoyed using to get to places faster.

Quote:

Originally posted by ~Unknown~@May 31 2006, 03:57 Trust me I hadn't planned on it I just wanted to fix it for me to use whenever I decide to play on a trojan Maybe I should release it without the aimbot would that be better?

the auto follow auto loot auto hunt functions would be more then enough

o thx for confirming me there is a packet change.

Yes it is confirmed that there is a packet change and I think I'll wait for some more opinions before I release it without the aimbot.

Quote:

Originally posted by ~Unknown~@May 30 2006, 22:10 I'm working on a fix for Qonquers Proxy atm. Got it to run ok but the aimbot isn't fuctioning right. =/ Perhaps someone has the structure for the old 0x3f2 packet?

would be good if ya dont release the aimbot tho can ya post the old 0x3f2 structure if ya manage to find it

Quote:

Originally posted by Etain@May 30 2006, 14:12 Disappointed with TQ...all they do is just change Packet ID 0x3f2...causing QOProxy not functioning...take less than an hour to fix most error...Since Cotobo also use Packet ID 0x3f2 to get the coor...this maybe why the orc dropper is not working... I have confirm that Cotobo ore dropper fail due to coor, solution 1 : wait for Chocoman to fix it solution 2 : use QOProxy to detect the dropitem packet and correct it solution 3 : write a new autominer from QOProxy code I used solution 3, have it working but is not user friendly(Need to write a GUI :(). The new Packet ID 0x3f2 is 24 byte in length with byte 22 as the sub-function code. x-coor for sub-function 0x68 and 0x56 is at byte 16 & 17 y-coor for sub-function 0x68 and 0x56 is at byte 18 & 19 x-coor for sub-function 0x85 is at byte 12 & 13 y-coor for sub-function 0x85 is at byte 14 & 15 sub-function 0x68 is used when startup sub-function 0x56 is used when Warp or teleport sub-function 0x85 is used when Jumping Hope this infor help...good luck cracking.....

I'll write you a frontend if you need help, unfortunately I dont work with packets so cant help there otherwise id already have started doing the same. You dont have to send me your code just a dll if you dont wanna trust me.

Although judging by your post your doing it in JAVA so maybe nvm :p

Thats if you need help, depends how busy you are irl

hmm seems there are more changes anyidea which is the playerID in the new 0x3f2 packet ?
And they belive they also change the jumpdelay cuz QOProxy with the cyclone was never d/cing and now it d/c even tehre is jumpdelay=1130
im going to find out the new jumpdelay value that it wont d/c with

I have confrim a change in Packet ID 0x3f1 sub function 3 (drop item) also...
they swap x and y coor...

meaning in new Packet
x-coor is at byte 10 & 11
y-coor is at byte 8 & 9

PlayerID in the new 0x3f2 packet is still in the same location btye 8-11...
Just that for some function two 0x3f2 packet is received instead of one.

if there is no change in the player id it seems there is change in the skill packet when its related to playerid,becosue when u lock with Tornado it say it has been locked on 321321. About the jumpdelay i tried with jumpdelay 2000 and it still disconect with Invalid jump.

Quote:

Originally posted by ~Unknown~@May 30 2006, 21:57 Trust me I hadn't planned on it I just wanted to fix it for me to use whenever I decide to play on a trojan Maybe I should release it without the aimbot would that be better?

NO, don't release it AT ALL
keep it to yourself, you shouldn't have fixed it in teh first place.

who is working on cotobo 0.36?

he/she should add an option that heals u at 200hp automaticaly:D

well would be nice i mean dont send out the aimbot but send us out the rest of the fixd things.... i have all the damn files and everything and im currently trying to fix it myself but im no expert and if someone fixes it i would like to get some tips....i dont really want it for free i rather idk get tips and do the rest myself.

Ok this is what I've noticed here. You said that it's a 24 byte packet with the 22nd byte as the sub-function code. Now I trust you and all but I just used a proxy to filter the 0x3f2 packet and I notice that byte 22= 00 and byte 23 is the sub-function code... Now I'm not sure what your seeing but this is what I'm seeing unless I did something wrong? Can someone else also check this?

This is the packet I got..



Client to Server - Length:24 PacketID:0x3f2
18 00 f2 03 32 c2 90 04 2b 9c 11 00 c2 03 2f 02
c3 03 30 02 00 00 85 00

Server to Client - Length:24 PacketID:0x3f2
18 00 f2 03 32 c2 90 04 2b 9c 11 00 c2 03 2f 02
c3 03 30 02 00 00 85 00