Demonic said:
Upon the bug happening - SQL does not talk at all - as long as the bug is in effect - how can you be so sure its not your SQL ??
Because I wrote the code myself, I know when SQL is/can be accessed, and its not when moving about.
Mrklawz said:
So its either down to a missmatch in the update of the coords of each entity. Its not just the JoB files either, its Korean EU and USA server too (i used to put it down to lag on the Korean server, guess i was wrong)
This is the cause of being stuck on mine.
The server and client become de-synced, the Server thinks there at one spot the client says there at another.
So when the client goes to move, it sends a packets with the coords it’s moving too, along with the direction. The server then works out where the client will be moving too, based on the direction sent. If they don’t match, the client isn’t allowed to move, and they are then stuck.
However yours sounds like a different bug, because when I get stuck I can’t move anywhere. I assumed the bug was the same, as I experienced it on Euro Mir 3, exactly the same as mine, wasn’t able to move anywhere.
But I also believe the problem is with the client, the client is either not sending the packet when moving, or it gets lost/corrupted.
I don’t think it could be getting lost/corrupted, as the only time you can get stuck is when running. Walking is absolutely fine.