wrote:

And if being far from reality means that most of ppl in e+ uses these tricks to gain some respect, well, i'm glad to be so far from reality.

Ur far from reality because noone here managed to bring up some evidence for that high ping advantage >_<

well shankey, you have no point.

Delight:
Cl_maxpackets different of 125 should be forbidden.
->Irrelevant, maxpackets below 125 and above 63 mean a random delay of 8msec for a shoot.

Bozo:
No, it isn't. It's the rounded half of 125 and the ideal number of packets for low-bandwidth connections.
->
true, it is the ideal number, most numbers above get decreased to 63 maxpackets anyways, you can set 70 and it would still only sent 63.
an exception is 100, that one seems to work too. However 100 desyncs

delight:
I was shooting randomly to prove that just by doing this you can shoot randomly, it kills.
->
In ur vids I can clearly see the moment you press the button and ur mostly on the enemy, depending on video quality.

drukqs:
ping definitely affects the way rails hit (you don't need to aim/time your shots accurately with a high ping, you're more likely to hit 2 or more enemies that are far from being lined-up with one single shot, rail someone who had already bfg-moved etc)
->
not exactly, the delay is between ur click and the moment the rail gets displayed. the displaying of a rail/frag takes exactly pingX2

Delight:
I think just some old players here should stop to take other players for dumbasses and to stop to abuse other players about their real skill.
->
funfact, all Professional Players of the past like HQ, Torzelan, Flex etc, even people with a lot of knowledge about Quake3 tried their best to get 125maxpackets on low ping.

GMZ:
High ping and artificial high ping are ways too different.. when low pingers spec high pingers or watch MVDs of high pingers in general the delag system makes it look like if one could shoot anywhere near target.. however, high pingers see different than what MVD records or what low pingers see while specing..
->
try XP_delagdemo 0/1/Ping (Off/On with Autoping/Manual Setting)

Ov3r:
First, one guy using it, will never gonna learn how to aim correctly
->
Funfact, Unlagged does exactly the opposite, you only hit if you aimed correctly.

shankey:
The rail shots from these players always used to look a little away from the target making me wonder how is it possible because when i shoot an enemy i always shoot point blank at the target not beside /nearby him.
->
XP_delagweapons 0/15, 15 instantly displays your rail, but is inaccurate since the client predicts rails to be elsewhere and elsewhen (creating false hits) as server does. Whenever you spec an enemy, you only see the ping delayed Rail. IF these people would have ping zero they would be perfectly on. An example - even a 30ms pinger can hit left or right of a fast moving target and still hit. Same effect in a smaller degree.

Shankey:
they will see the game a bit delayed as is the usual theory which helps in timing shots better
->
this is the only true advantage a high pinger can have, congratz. Since people see you late they also react late by exactly your Ping (if they have ping zero).

Anyways, here are the basics:
Quake3 is a vm based server running @ sv_fps, every frame is called an snapshot (exact state of the server, on connect its always 'awaiting snapshot')
for every frame it calculates the changes made in the game, wraps it up in a snap and sends it to the client. The server calculates frames in the row it receives packets from all clients.
the snaps client cmd sets the amount of snapshots the client orders from the server. The server sends the wanted amount. However on a sv_fps 30 server, if you have snaps 60, you receive 2 times the exact same state. therefor your practical snaps is 30 anyways.
the server can recieve any amount of maxpackets from the client.
having 63 maxpackets means the server recives around 2~ position updates from you every snapshot. A player appears laggy below 2 (theoretically 1 Update is enough, but practically for all the interpolations to run correctly you seem to need more.)
the 3% packetloss sometimes displayed are due to 30 being a good value, but not exactly fitting in a second. While 125 is 8msec per frame, 30 is 33,3ms per frame.
Hitbox is calculated by server and as long as you send enough updates to not lag, you are perfectly hitable, not depending on ping!
You can sync your own client with the server having exactly 1:1 the position - its called g_synchronousclients 1.
So how does the netcode actually work? Just for urself, you make a position change, go ahead and send the server the change. The server recieves, calculates if the change is possible and sends you your correct position back. This is why u sometimes hang up on corners when you have spikes in lagometer.
But this also means, if you come around a corner, you are your own ping ahead compared to server view.

and here comes in the disadvantage/advantage calculations. The funny thing is, these having nothing to do with ANY game setting. They aren't even Quake specific, they work in EVERY online shooter without g_sync.
for simplification, we first gotta look @ the advantages vs a person with zero ping (same view as server).
Player A: Server view, Zero Ping, Standing.
Player B: Client view, 30 MS, strafemoves exactly to enemy (maxspeed)

In this case, Player B comes around a Corner, Sees player A 30 msec ahead of server view (advantage), clicks and shoot is delayed by his ping (disadvantage) = +-0
THIS MOVE WILL BE ALWAYS +-0 NO MATTER WHICH PING, GG.

In same case, Player A sees Player B late by 30 msec and therefor reacts 30msec late (disadvantage).

So in this game Situation, not depending on pov, the Pinger gets 30 msec out of it. Result = Campers get punished, ALWAYS.

Next case:
Player A: client view, ping 30ms, standing
Player B: client view, ping 100ms, strafemoves exactly to enemy (maxspeed).

In this case, Player B comes around a Corner, Sees Player A 100 msec ahead of server view (advantage), clicks and shoot is delayed by his ping (disadvantage) = +-0
In same case, Player A sees Player B late by 100msec and his own ping, 30msec. If he clicks his overall disadvantage is 160msec.

This is the most simplified version, it also depends on Player speed (since a player is also 24 units wide and Cam is in middle), angle and enemy Player speed.

Now for the record, whenever you camp, ur 'disadvantage = Attackerping + UrOwnPingX2'
stuff gets even more confusing when both Players are in motion. There the advantages are somewhere between Zero and Max Disadvantage of a Player.

Anyways, back to topic. Highping and 63 maxpackets as dirty little helper is a mystery because as long as movement is consitent on server, hitbox doesn't change.
Also as lowpinger of 30ms, your max disadvantage is somewhere between 0 and enemyPing +60. As highpinger of 90ms your max disadvantage is somewhere between 0 and enemyping+180.

Therefor the advantage disadvantage rule for ping is, as higher the ping, as bigger the extremes get. As higher ur ping, as more probably a mistake will kill you.
Now comes the joke of all this, excessivespeed like bfg jumps are so fast you always get the advantage out of a situation. Same goes for grenade jumps if they are done properly.
And some geniuses increased movement possibilitys, reduced switchtime etc in plusN. Considering netcode wise, its more of a ping lame instead of a real battle with a dogfight.

so yes, there is an advantage, but it has NOTHING to do with not being hitable and stuff. As said, thats a mystery.

PS: if you guys think I prepared this for days or something, I do such stuff on the fly and therefor take no warranty of the informations being valid