
Since the problem seems to be server side, the "hack" would have to involve writing proper netcode and somehow forcing SE to implement it.Slightly evil thoughts here.
I wonder, since pos hacks exist, if it would be possible for some clever programmer to develop a 3rd-party hack that would just read your current location according to the client and force it along to the server more often. Say, 25-100 ms instead of 300 (only when position values are actually changing; it'd be stupid to ramp it that high when you're standing still).
I'm sure if that were possible, it would be very problematic if it became popular (the increase in incoming traffic would likely not be good for their servers). But if it helped alleviate the issue, it would also be pretty clear evidence that 300 ms is far too long a wait.
Last edited by Goreth; 10-25-2013 at 10:20 PM.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote

