Cratos said:
About 80% of ppl do demorec their matches. Still it seems impossible to get any demo of a serious 'bug' that happens to some players all the time? <sarcastic mode>Maybe the 'bug' contains a virus that deletes it's demos to keep itself secret?</sarcastic mode>
Anyway the demos you sent me are running LeagueAS135 :X
Noone complained about problems with LeagueAS135. The complaints were that leagueAS136 introduced the 'bug' while everything was fine in 135. Seems with these demos you are proofing (by accident) the opposite of what you initially wanted to proof?
Didnt want to prove anything, was just trying to assist in delivering potential evidence for you to examine. I was pretty sure they were with 136, but you were sounding so mad at ppl not having demos that i wanted to slap you with one so hard that i didnt check the details and picked the only one i could remember with a rox problem. But hey, on msn u said, before getting the files, it could be just a bit of lag. Mostly i dont have the rox prob in 136 myself, more trouble with them missing alot and sometimes a feeling of firedelay and blowing them catastrophically into a wall cuz i get ass-spammed by a tm. Only really seen some launching effects maybe less than 5 times, that could not be explained by health/armor. Anyhow, if you did watch the one i was talking about you know someone was going on about lag lag lag, telling me to stop lagcheating after that single odd occurrence, but he was already annoyed for another reason.
My theory on the matter is basically that sometimes the momentum transfer happens in 1 tick and the damage gets applied 1 tick later, when the target has already been knocked quite a bit from the splash epicenter. However why that should be so, who knows. Maybe 136 runs slower than 135 making it happen more often? Maybe you ppl changed something despite claims that nothing was touched. Maybe some oher change is interfering with it. There was some trouble with rox delay in 1 or 2 of the 136 betas, and this was mentioned in those threads, so could be its not completely fixed. Maybe you could 'just' change the code so damage always comes first, launching second, then it will no longer matter if its/was down to timing what happens first or even in same tick.
back to lag, If laggy targets (sniping through ppl that should be hit) show up on demos and not just as a wrong aim, i'll try to collect some. There are definitely some ppl who consistenly require dramatically different approaches to lagprediction to be hit compared to most 'normal' ppl, without having significant ping differences, that is to say they have the same kinds of ping that low/normal lag players have.
Most annoying are those cases where u would bet alot that they were moving straight along the fire trajectory (or so close to it that it doesnt matter) for enough time before and after shot, to be hit.
Maybe 135 was the same for that, maybe it wasnt. Could be ppl using sophisticated tools for making lag or nameacheathere. So its a cynical attitude, well some ppl dont want to play fair or have severely norm-deviating definitions of fair. Abuse of netspeed and similar primitive methods should be hint enough that the desire is there but morals are lacking. Just because ppl dont get caught doesnt mean its not going on. Just reading a bit on the ut admins webpage is an education. Bot me here, hack me there, just lacking ut sourcecode for custom builtin cheats, and made-to-order and pay via creditcard webshop for the aspiring but unscrupulous player, complete with complementary set of steak knifes and a 6 months pornsite subscription, for those ordering the full deluxe suite.
Now dont fall off your chair and have a cow sideways. Psy could handle a rant like this and so can you.
