Packet change in patch 4312

Hmm. I got it to log into the server, but instantly got teleported to bot jail.

*sigh* I'm a noob with bitwise operations. :(

ok it works for me now !!

QOProxy works for me now too... not sure what commands are stil functioning... But yah the normal jump delay isn't enough??? I'm d'cing alot with speed hack on... You guys tried 2k and it still disconnect?

Wondering... Q's cyclone autosat did it not?? And does the jump delay control the time between speeding?? I want to lengthen the time the char sits.... then i think it wont disconnect.... any ideas how to do this.....

i just havnt bothered with much decoding just changed the packet so far....

Alright, I the speed hack is working fine now, and i got the aimbot to work... sort of, although it does not auto fb/ss ppl anymore like it used to, u need to lock onto the target, than use the double lock mode to FB/SS them now, does anyone know how to get the auto attack working again and for the speed hack, pressing "lie" button does not work anymore, u have to type in " #cyclone " so if anyone could help me with these 2 things I'd appreciate it. thx :)

im a nubcake with java how do i edit the packets??#


also could someone upload a copy of the old Qonquer so i can try to fix it myself...

or someone upload it , even without the aimbot function

so if I swap the x and y coord and change the packet structure as choco said the packet based bots are going to work again?

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.....

Could you tell us what were the old Sub-fonction codes and all ?

Quote:

Originally posted by Hybris+Jul 10 2006, 18:18--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Hybris @ Jul 10 2006, 18:18)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin--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.....

Could you tell us what were the old Sub-fonction codes and all ? [/b][/quote]
lol.... Check stickies first....

old sub-function codes as requested...
[Only registered and activated users can see links. Click Here To Register...]

Quote:

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

I already saw that, but i need these olds.

Quote:

Originally posted by Hybris+Jul 10 2006, 18:45--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Hybris @ Jul 10 2006, 18:45)</td></tr><tr><td id='QUOTE'> 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 [/b]

I already saw that, but i need these olds.

<!--QuoteBegin--chocoman4k@May 31 2006, 21:11

// ACTIONSTRUCT::Type
#define ACTIONSTRUCT_TYPE_GESTURE 126
#define ACTIONSTRUCT_TYPE_WARP 131
#define ACTIONSTRUCT_TYPE_HEROSPAWN 137
#define ACTIONSTRUCT_TYPE_JUMP 142
#define ACTIONSTRUCT_TYPE_MINE 159
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<<< OLD
#define ACTIONSTRUCT_TYPE_GESTURE 81
#define ACTIONSTRUCT_TYPE_WARP 86
#define ACTIONSTRUCT_TYPE_HEROSPAWN 74
#define ACTIONSTRUCT_TYPE_JUMP 133
#define ACTIONSTRUCT_TYPE_MINE 99
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<<< NEW
They are in decimal... convert to hex... = sub function codes....

*sigh* I thought posting the link to this was enough...[/quote]
................................. >.>.................

Look deeper ffs....

Quote:

Originally posted by WaRpEd+Jul 10 2006, 18:54--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (WaRpEd @ Jul 10 2006, 18:54)</td></tr><tr><td id='QUOTE'> Quote: Originally posted by -Hybris@Jul 10 2006, 18:45 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 I already saw that, but i need these olds. <!--QuoteBegin--chocoman4k@May 31 2006, 21:11 // ACTIONSTRUCT::Type #define ACTIONSTRUCT_TYPE_GESTURE 126 #define ACTIONSTRUCT_TYPE_WARP 131 #define ACTIONSTRUCT_TYPE_HEROSPAWN 137 #define ACTIONSTRUCT_TYPE_JUMP 142 #define ACTIONSTRUCT_TYPE_MINE 159 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<<< OLD #define ACTIONSTRUCT_TYPE_GESTURE 81 #define ACTIONSTRUCT_TYPE_WARP 86 #define ACTIONSTRUCT_TYPE_HEROSPAWN 74 #define ACTIONSTRUCT_TYPE_JUMP 133 #define ACTIONSTRUCT_TYPE_MINE 99 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<<< NEW They are in decimal... convert to hex... = sub function codes.... *sigh* I thought posting the link to this was enough...

................................. >.>.................

Look deeper ffs.... [/b][/quote]
loOL already had noticed that, but what were the old bytes lol ?
I know adresses but not bytes for x-coor for example.

o.o y do u need to know that... look at old QO code and u'll see the old ones??? Then change to new ones...

Quote:

Originally posted by WaRpEd@Jul 10 2006, 19:06 o.o y do u need to know that... look at old QO code and u'll see the old ones??? Then change to new ones...

Ok thx, lol i wasnt working QOProxy thats why ^^

OK which x and y do you need... Like which sub functions I can post you the old x and y for them I think...

Quote:

Originally posted by WaRpEd@Jul 10 2006, 20:28 OK which x and y do you need... Like which sub functions I can post you the old x and y for them I think...

Its ok i downloaded QOProxy, and i'm working on this old version too now. Thx for tips.