Ah sorry I think I misunderstood what the clead command does! I thought it was the amount that the hitboxes are moved "back in time" at the server, but I guess it is kind of the opposite.
So if I set clead to 0, does that mean I shouldn't have to lead? If this is the case, then I guess what I wanted was to be able to set clead to a negative value (but still fairly close to 0). *But*, I should test it again now that I (think I) understand it. Thanks again.
Edit:
Scratch that! I guess what I would like is for clead (or some other command) to be what I said first: the amount the hitboxes are "moved back in time" for this particular player at the server.
Thus, it is not affected by the player's ping at all, which is the entire reason I wanted this feature -- I wish to override the server's calculated value with a constant value that I (the player) believe is correct (within reason, of course). Thanks again.
Edit2: I just played on server "©". With nolead enabled, around 40 ping and without issuing /clead, I was having to consistently lead by a constant amount. Again, this was confirmed using my client-side tool. Hence my request for wanting to override the hitbox adjustment amount with a constant value that I can set. I do not believe it is possible for the server to calculate the correct value. This might be because the correct value is based on the one-way latency from the client to the server, which cannot be calculated from the ping (which I believe is the round-trip time), as the different directions may not have the same latency. Or it may be something else entirely. Either way, overriding it with a constant value ensures the best possible experience for those willing to adjust it. Thanks again.
Bookmarks