Programing Proxy problem.

11/22/2007 15:59 nataro#31
Quote:
Originally Posted by inSertCoiN View Post
Well basically the server does that on hes own. If I send him sit packet, he sends the same sit packet back to the client. The problem is nothing happens then. I mean I actually did sit but I can't see that on my client.
When I use V3n0M I can't see the characters use AutoSit, But it certainly does :D Just watch the Stamina Rise! :D lol
11/22/2007 17:02 bone-you#32
Sitting is handled by the client. The server does not tell you you're sitting because the client should already be sitting. I believe if you send the sit packet to the client as well it will show you as sitting.
11/22/2007 17:47 inSertCoiN#33
Quote:
Originally Posted by Queen-Of-Evil View Post
Cant you send a packet from the Proxy to the CO client Manuelly? :confused: Not that I could see why you would want to see yourself autosit,,, except for pleasure sake, Even Net and Caff didnt finish that ^^ Nice to see your getting there though :cool:
Thats not the point. Its not for pleasure. I'll try to explain differently.
I'm standing on some coordinates.
I send a packet to jump to the new coordinates.
If you look at the character from another client you'll see that he jumped to the new coordinates.
But on the client where the proxy is the character is still standing on the old coordinates.

You see the point? I need a way to tell the client to jump to the new coordinates too, not just the server.
I don't think sending the same packet to the client will work because when the server receives the packet, it sends the same packet to the client.
So if I did send the packet to the client, the client will receive 2 same packets, 1 from the server and 1 from the proxy.

Quote:
Originally Posted by bone-you View Post
Sitting is handled by the client. The server does not tell you you're sitting because the client should already be sitting. I believe if you send the sit packet to the client as well it will show you as sitting.
Its not the siting I'm worried about. Same goes for jump and probably for all actions (I just tested sit and jump).
11/22/2007 20:46 Queen-Of-Evil#34
Quote:
Originally Posted by inSertCoiN View Post
Thats not the point. Its not for pleasure. I'll try to explain differently.
I'm standing on some coordinates.
I send a packet to jump to the new coordinates.
If you look at the character from another client you'll see that he jumped to the new coordinates.
But on the client where the proxy is the character is still standing on the old coordinates.

You see the point? I need a way to tell the client to jump to the new coordinates too, not just the server.
I don't think sending the same packet to the client will work because when the server receives the packet, it sends the same packet to the client.
So if I did send the packet to the client, the client will receive 2 same packets, 1 from the server and 1 from the proxy.



Its not the siting I'm worried about. Same goes for jump and probably for all actions (I just tested sit and jump).
Have you tried sending the Jump packet but BLOCKING the reply packet from the server? Like I mean after yourve sent the Jump packet block the packet reply from the server saying yourve jumped?

This method is I believe how Net7 made the Target feature work in Nproxy and how Net7 also did the Autohunts refresh. :cool:


If its any help ;)
11/22/2007 22:14 flowerpot!#35
You need to send a different packet to the client to have it update the position of the character - it'll ignore jumps/actions for itself. In fact, I was trying to solve this exact problem when unknownone found the original teleport packet... :D
11/22/2007 23:55 inSertCoiN#36
Quote:
Originally Posted by flowerpot! View Post
You need to send a different packet to the client to have it update the position of the character - it'll ignore jumps/actions for itself. In fact, I was trying to solve this exact problem when unknownone found the original teleport packet... :D
Have you come up with something? Do you know which packet it is or the packet structure?
11/23/2007 05:34 XtremeX-CO#37
Ah the refresh packet :), thats a hell of a packet to find... Thats the single problem I had when i did my proxy... Just keep looking for it... its a 0x3f2 packet, just gotta find the right identifier :)