Threaded Mode | Linear Mode

***Feeh*** · (03-16-2014)

(03-16-2014 02:25 AM)Coruja Wrote: I can filter packet sent to server to get some packet data, but I don't get the point on how to handle everything in the correct order to sync all packets and make they work together

I'll try to describe the (packet key based) complete detection process I'm using on my RunUO, the default method is omitted

Code:

@Player login

-Initialize a new stack with 6 keys and send it to the client

-player tag.stackwarn set to 0

-player tag.moves set to 0

//Stack = array of keys stored on the server

@Player movement

IF player changing direction

    IF stack count > 15

        -Reset the stack, add 6 new keys and store them

    ENDIF

    -Send a new single key and store it to the stack

    -Handle movement

    return;

ENDIF

IF stack contains key AND player tag.moves < 6

    -Remove key from stack

    -increase player tag.moves by 1

    -Initialize the separated thread FastWalkHelper if not initialized (we do not want 2 threads working)

ELSE

    -Possible fastwalk detected, block movement (paralize) for 0.2s (rejecting movement causing client to stop walking until teleport)

    -increase player tag.stackwarn by 1

ENDIF

-Handle movement

@player resync request

-Add a new key to the stack and send it to the player

@FastWalkHelper

WHILE player tag.moves > 0 AND player connected

    -wait run speed seconds (0.1 for mounted / 0.2 for foot)

    -decrease player tag.moves by 1

    IF stack count > 15

        -Reset the stack, add 6 new keys and store them

    ENDIF

    -Add a new key to the stack and send it to the player

    IF player tag.stackwarn > 0

        -decrease player tag.stackwarn by 1

        IF player tag.stackwarn > 5

            -report to the staff team the fastwalking player (movement was already blocked)

            //break while ?

        ENDIF

    ENDIF

ENDWHILE

-player tag.stackwarn set to 0

-thread end, exit and dispose resources

The FastWalkHelper is a separated thread, it runs asynchronous from the main thread, one thread per player (a bit unoptimized here)
The run time for each thread should not be any longer than 1 second and does not consume much memory and processor usage.
Tested with ~100 bots running from the same machine as the server (my pc) with some of them speedhacking

It can be possible to translate the thread to timer(f)-based but I have no idea on how Sphere handles the timers.
SQLite based tables could do the trick, but would require and incredible sync (time<>key<>move speed)

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