Hit-scan weapons instantly search for the targets, tracers are sent to the client to be displayed as the effect. Tracers have nothing to do with hitscan hit-detection, if thats what you were implying at.
Also, there still is the crouching fade issue, which may have factored into the lack-of hit registry.
<!--QuoteBegin-ViPr+Jul 5 2004, 01:19 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (ViPr @ Jul 5 2004, 01:19 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> this is disgraceful. this thread has gone off the front page and basically nothing has been done. i followed the link and read the thread in the other forums of the fix. the server admins don't understand what the hell is going on and how the fix fixes this bug. the reason they don't understand how it fixes the bug is because it doesn't fix the bug. it just introduces another bug that causes this bug to be avoided. and again how are we supposed to know that a server has this fix and even if it is working. this is not a solution. Flayra or Valve needs to do something. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> I will make a great set of colors to make sure you see it right:
The <span style='font-size:14pt;line-height:100%'><span style='color:red'>dev team</span> <span style='color:blue'>knows</span></span> about this bug, <span style='color:blue'>that also includes</span> <span style='font-size:14pt;line-height:100%'><span style='color:red'>Flayra</span></span>, and the <span style='font-size:14pt;line-height:100%'><span style='color:red'>dev team</span></span> is <span style='font-size:14pt;line-height:100%'><span style='color:blue'>currently</span></span> in the process of <span style='font-size:14pt;line-height:100%'><span style='color:blue'>fixing this bug</span></span> and all its <span style='font-size:14pt;line-height:100%'><span style='color:blue'>side-effects</span></span>.
For us, <span style='color:red'>poor and innocent coders</span> that can only do <span style='font-size:14pt;line-height:100%'><span style='color:red'>server-side fixes</span></span>, there is <span style='font-size:14pt;line-height:100%'><span style='color:blue'>no other way</span></span> to fix this bug than to <span style='font-size:14pt;line-height:100%'><span style='color:blue'>block the last slot</span></span> in a way or another.
Stop yelling at us as if we were responsible of this bug. We found this bug and we are offering temporary fixes for it. Accept them or ignore them. You should be grateful that we are releasing temporary fixes. We were not forced to do it and we were not forced to spend mostly wasted hours to find this bug either.
im sure all the major bugs will be fixed there is nothing to worry about <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo--> just give them some time they are only human
<!--QuoteBegin-moomin.+Jul 5 2004, 10:18 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (moomin. @ Jul 5 2004, 10:18 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> I'm pretty sure that while the last slot player is always bugged, there is another slot that is bugged too. I was playing as a fade today in a pug and I was being shot at directly (as in the tracers were going into me) and taking little or no damage. Server slot ID was #4. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> I was just playing last night with a "friend" of mine, who did "crazy" stuff and thaught himself that he was bugged. We checked, and he didn't have the last slotid, just slot #4, so we thaught maybe it was just server lag, bad aiming, whatever. But now, since you mentioned something similar ...
[edit] Hm, just did some testing, and seems like slot #4 is slighlty (?) bugged. I was running in a straight line with celerity, he shot from behind and it took him around 20 bullets, instead of 9 - 10. While Bunnyhoping I even survived with 10/0, and without any upgrades and running in a straight line he still needed 15 - 18. Oh well, pretty insignificant compared to the real thing though, and maybe his aim was just off or whaterver <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html//emoticons/wink.gif' border='0' style='vertical-align:middle' alt='wink.gif' /><!--endemo-->
<!--QuoteBegin-moomin.+Jul 6 2004, 12:21 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (moomin. @ Jul 6 2004, 12:21 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> The teams who win and consistently get good scores on multiple servers? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> lol no
Someone needs to get around to server admins and tell them what the bug is, or make a post and link server admins to it. Now we all know that the last slot on the server is bugged, and some servers have taken precautionary measures and either reserved that last slot, (a good idea) or had the slot taken by a bot (again, a good idea).
Now alot of people do not know what the bug is, or if they do, they think they know the problem. For instance, I had joined the <span style='color:white'>URL omitted.</span> server today, and to my surprise after playing for about 5 minutes, (yes it didn't take long), I had noticed I wasn't taking full damage, and check the console. I was, infact, bugged, and when I had mentioned it to the admin and rest of the server, with an apology, to my surprise I was ridiculed. The admin had told me that the bug only occurs on co_pulse (which made me laugh), and that there was no possible way I could have been bugged. And before I could tell him that the only way I couldn't be bugged anymore, was to restart the server, I was kicked and banned, because I was dwelling on me being bugged, and that the admin was wrong.
I really think someone needs to make a stickied post about how the bug is reproduced, and how it can be prevented, as well as a way to tell if a person is bugged.
It's too bad that you come into my servers, try and convince everyone that you have the PSHB with your slot 21, EVEN THOUGH I told you the server has a fix and has 22 slots (so 22 would be the max). Everyone else says you don't have it, but you continue to rant about it. Then you excessively FLAME the users on the server.
I believe the threads function is fulfilled; I'm now going to <span style='color:red'>***lock***</span> before the mounting frictions make more drastic actions necessary.
Again, a big thanks to everyone who participated in identifying this.
Comments
Also, there still is the crouching fade issue, which may have factored into the lack-of hit registry.
I will make a great set of colors to make sure you see it right:
The <span style='font-size:14pt;line-height:100%'><span style='color:red'>dev team</span> <span style='color:blue'>knows</span></span> about this bug, <span style='color:blue'>that also includes</span> <span style='font-size:14pt;line-height:100%'><span style='color:red'>Flayra</span></span>, and the <span style='font-size:14pt;line-height:100%'><span style='color:red'>dev team</span></span> is <span style='font-size:14pt;line-height:100%'><span style='color:blue'>currently</span></span> in the process of <span style='font-size:14pt;line-height:100%'><span style='color:blue'>fixing this bug</span></span> and all its <span style='font-size:14pt;line-height:100%'><span style='color:blue'>side-effects</span></span>.
For us, <span style='color:red'>poor and innocent coders</span> that can only do <span style='font-size:14pt;line-height:100%'><span style='color:red'>server-side fixes</span></span>, there is <span style='font-size:14pt;line-height:100%'><span style='color:blue'>no other way</span></span> to fix this bug than to <span style='font-size:14pt;line-height:100%'><span style='color:blue'>block the last slot</span></span> in a way or another.
Stop yelling at us as if we were responsible of this bug. We found this bug and we are offering temporary fixes for it. Accept them or ignore them. You should be grateful that we are releasing temporary fixes. We were not forced to do it and we were not forced to spend mostly wasted hours to find this bug either.
I was just playing last night with a "friend" of mine, who did "crazy" stuff and thaught himself that he was bugged. We checked, and he didn't have the last slotid, just slot #4, so we thaught maybe it was just server lag, bad aiming, whatever. But now, since you mentioned something similar ...
[edit] Hm, just did some testing, and seems like slot #4 is slighlty (?) bugged. I was running in a straight line with celerity, he shot from behind and it took him around 20 bullets, instead of 9 - 10. While Bunnyhoping I even survived with 10/0, and without any upgrades and running in a straight line he still needed 15 - 18. Oh well, pretty insignificant compared to the real thing though, and maybe his aim was just off or whaterver <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html//emoticons/wink.gif' border='0' style='vertical-align:middle' alt='wink.gif' /><!--endemo-->
It's time for the happy dance!
If I explain the bug.
Till this gets fixed, I hope most players will know about this bug.
celerity lerk thats bugged can be half impossible to kill
well there goes for skill, will we ever know who are the best in ns?
lol no
although at first you might think so!!!!
Now alot of people do not know what the bug is, or if they do, they think they know the problem. For instance, I had joined the <span style='color:white'>URL omitted.</span> server today, and to my surprise after playing for about 5 minutes, (yes it didn't take long), I had noticed I wasn't taking full damage, and check the console. I was, infact, bugged, and when I had mentioned it to the admin and rest of the server, with an apology, to my surprise I was ridiculed. The admin had told me that the bug only occurs on co_pulse (which made me laugh), and that there was no possible way I could have been bugged. And before I could tell him that the only way I couldn't be bugged anymore, was to restart the server, I was kicked and banned, because I was dwelling on me being bugged, and that the admin was wrong.
I really think someone needs to make a stickied post about how the bug is reproduced, and how it can be prevented, as well as a way to tell if a person is bugged.
Again, a big thanks to everyone who participated in identifying this.