Change-Speed Detectation

Thread Rating:

0 Votes - 0 Average
1
2
3
4
5

Threaded Mode \| Linear Mode Change-Speed Detectation
Author	Message

Feeh

Sphere Developer

Posts: 156
Likes Given: 6
Likes Received: 40 in 29 posts
Joined: Sep 2012
Reputation: 4

Post: #19

RE: Change-Speed Detectation

(03-16-2014 03:36 PM)Coruja Wrote: The only safe way to detect fastwalk: push a key after EACH 0x21, 0x22, (=send 0xbf sub 2) check in 0x02 for stack emptyness.

If you send a key after 0x21/0x22, when you receive the next 0x02 the stack will never be empty, right? Although RUOSI provides the most complete packet guide I started to find it not-so-much reliable or not well described
PS: I don't know if you're still in the test phase of the script or started the real development, but these keys you send to the client must be stored in the server, once it is possible to hijack the packets it is possible to send non-zero keys and bypass the fast walk check Smile

(03-16-2014 10:39 PM)Ben Wrote: ok, I just had a look into the source... surprise surprise... This seems to have already been implemented if you activate the DebugFlags = 0x80 in sphere.ini; 0x80 is DEBUGF_WALKCODES.

What about the DEBUGF_WALK 02000? It does use the F0/F1 packet?

Feeh/Epila - Nightly releases / SphereWiki / Github Issues / Sphere's GitHub

03-17-2014 02:09 AM