A small question

[cyberinferno]

I was trying to use Windows Packet Editor(WPE) sometime back while playing A3 in my local server. What I did was I logged into GM character, attached WPE to A3Client.exe, started recording packets sent to my server. Then in game I spawned 3 grahsaths using GM command. I minimized the game to check what my client had sent to server. I observed that all the 3 times when I used that command the client sent the same packet to the server. So I tried replicating the spawn command through WPE. I sent the same packet to the server using WPE and went back into the game expecting to have another grahsath in my inventory. But actually I saw a 'Disconnected from server' dialog box. I thought I did some mistake and so I started over the whole process again. This time again server kicked me. Why is the server kicking the character? I was sending the same packet that was being sent when I used actual command in game. How did server know that this packet was not coming from A3Client.exe? Not only this packet. If you send any packet from WPE which is related to the logged in character, the server kicks that character from game. If anyone knows the reason behind this please reply

 

[chrissdegrece]

What exactly are you replicating?

The @ITEM command?

 

[cyberinferno]

What exactly are you replicating?

The @ITEM command?

Yeah @ITEM command

 

[chrissdegrece]

Check full communication with server, it shouldn't be so easy to just duplicate a packet.

Maybe there is a slight diff in packets which may be some packet ID, ACK, or anything that may confirm to the server that someone didn't try to do what you did.

 

[getdeepz]

Check full communication with server, it shouldn't be so easy to just duplicate a packet.

Maybe there is a slight diff in packets which may be some packet ID, ACK, or anything that may confirm to the server that someone didn't try to do what you did.

It must work, check whether the data you are spoofing is 100% ditto.

 

[cyberinferno]

It must work, check whether the data you are spoofing is 100% ditto.

Its 100% ditto because I re-sent the same packet which has sent from A3Client.exe and captured by WPE.

 

[mav3r1cksandy]

If you are using WPE let me tell u my friend. Packets might be the same but each packet has a different unique code that the server takes in.. With WPE u can edit ur chars armor props but that wont be taken by the server. That means, your char will be reset to normal when u relogin. And also the server kicked you because u sent too many packets with the same Unique ID. Server disconnected you because there is usually a limit to the server on how many packets it can monitor ( with same Unique ID). If there was a lag, our client sends the same packets sometimes and for the same reason the server dcs the client to resync with the char.

 

[onyourrisk]

I faced the same issue while trying to replicate the shout, when I changed the target to server and then i logged a packet that sent a shout to the game, I found it using the text i used in the shout "GM : Hello guys !!" and the exact was there in the packet when i send it to the server using WPE it did the shout in game, I edited the packet and changed the message and char name and sent it again it worked very well.

But when i sent the same packet by an external program I made to send shout packet, my ZS hangs up.

 

[mav3r1cksandy]

Packets of items have time stamps and UniqID requests.. As far as i can remember.. But i may be wrong..

 

[cyberinferno]

If you are using WPE let me tell u my friend. Packets might be the same but each packet has a different unique code that the server takes in.. With WPE u can edit ur chars armor props but that wont be taken by the server. That means, your char will be reset to normal when u relogin. And also the server kicked you because u sent too many packets with the same Unique ID. Server disconnected you because there is usually a limit to the server on how many packets it can monitor ( with same Unique ID). If there was a lag, our client sends the same packets sometimes and for the same reason the server dcs the client to resync with the char.

I see. That might me the problem!

 

[Feurial]

@Mav3r1cksandy i know this name it was password of some a3acc dnt remember now