and they had to list the 2 worse games to confuzzle us... me and dan had a lan yesterday, i got him to get steam, and i loaded 3 wb's and ff he joined last and we tested while skulks were munching on our 2.0 base, if its fixed for that, its fixed for 3.0
<!--QuoteBegin-IBT+Aug 12 2004, 02:29 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (IBT @ Aug 12 2004, 02:29 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> and they had to list the 2 worse games to confuzzle us... me and dan had a lan yesterday, i got him to get steam, and i loaded 3 wb's and ff he joined last and we tested while skulks were munching on our 2.0 base, if its fixed for that, its fixed for 3.0 <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> No, it's fixed for all mods using the updated engine.dll or w/e the dll's name is.
<!--QuoteBegin-Flayra+Aug 11 2004, 05:59 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Flayra @ Aug 11 2004, 05:59 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> Way to go grep, Ari, Tyr, and all the others that helped find this one. It really was an impressive detective job. Once you guys narrowed it down, it took almost no time to find and fix the bug (I think Matt Boone fixed it in minutes).
Hallelujah! <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> He probably fixed it in minutes because it was probably some simple for loop or while loop error. Probably used the wrong comparison operator for the loop and all it took was a couple minutes to fix it, but this has been present for years... Amazing it wasn't noticed sooner.
the PSHB may be gone but I am still hearing excuses in servers that someone is still "bugged", maybe this problem will still be heard about for a while unfortunately
<!--QuoteBegin-Jim has Skillz+Aug 12 2004, 06:28 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Jim has Skillz @ Aug 12 2004, 06:28 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> He probably fixed it in minutes because it was probably some simple for loop or while loop error. Probably used the wrong comparison operator for the loop and all it took was a couple minutes to fix it, but this has been present for years... Amazing it wasn't noticed sooner. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> How do you suggest they would have noticed it sooner? If that's what the problem was, we're talking about a single character in the entire source code being wrong, so they're not just going to stumble on it by accident. And just look at how long it took the community just to figure out what the nature of the problem really was.
<!--QuoteBegin-Zek+Aug 12 2004, 08:12 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Zek @ Aug 12 2004, 08:12 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> <!--QuoteBegin-Jim has Skillz+Aug 12 2004, 06:28 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Jim has Skillz @ Aug 12 2004, 06:28 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> He probably fixed it in minutes because it was probably some simple for loop or while loop error. Probably used the wrong comparison operator for the loop and all it took was a couple minutes to fix it, but this has been present for years... Amazing it wasn't noticed sooner. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> How do you suggest they would have noticed it sooner? If that's what the problem was, we're talking about a single character in the entire source code being wrong, so they're not just going to stumble on it by accident. And just look at how long it took the community just to figure out what the nature of the problem really was. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> Sorry, I sounded like I was talking about searching through thousands of lines of code for obsure bugs, I meant I am amazed on how someone playing didn't notice it was the last slot that was creating the hitbox bug years ago.
I should have posted in this thread instead of the other, but anyhow I'll quote myself:
<!--QuoteBegin-Head crab+--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Head crab)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->The bug is fixed, the problem is that HLDS servers not running under Steam need to use the special update tool to receive new updates unlike servers running under Steam which receive them after a restart.
It's been tested and is definitely fixed in my very own test dedicated server which runs with Steam. However, our public servers are not yet updated, as it has to be done with the update tool by the server hosting maintenance people.
So there may be a lot of servers in the same situation...<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Most of the server hosting companies don't use Steam to run their servers, so most of the dedicated servers in the whole Half-Life community are not auto-updating, so they have use the HLDS update tool for any update to their server. Many servers will probably take a while to be updated because some server admins either have to rely on their hosting company to update HLDS or some server admins are totally unaware of the importance of updating their HLDS.
Server admins have to assume their responsabilities and update their server when needed. There's nothing we can do for those who won't update for any reason. The bug will remain on outdated servers, so don't be surprised to see it again. As a player, I guess you could ask your local server admin if his server has been updated if you want to avoid this bug again.
Eventually, the outdated servers might become incompatible with upcoming client updates to force server admins to update. At least that would be a good move on Valve's part.
Anyhow, admins whose servers are not running on Steam should update by running <b>hldsupdatetool.exe</b>, which, if I'm not wrong, is included with the non-Steam version of HLDS (the 420 mb one). If it's not, there are many mirrors for it on the web. The file itself is less than 1 mb. Visit the Steam forums for more informations on that tool.
<b>For the people who don't want to be bothered to read all of the above, here's what it says in short: the bug is fixed, it's just that some/many dedicated servers not running on Steam remain outdated.</b>
Comments
me and dan had a lan yesterday, i got him to get steam, and i loaded 3 wb's and ff he joined last and we tested while skulks were munching on our 2.0 base, if its fixed for that, its fixed for 3.0
<!--emo&::sentry::--><img src='http://www.unknownworlds.com/forums/html//emoticons/turret.gif' border='0' style='vertical-align:middle' alt='turret.gif' /><!--endemo-->
me and dan had a lan yesterday, i got him to get steam, and i loaded 3 wb's and ff he joined last and we tested while skulks were munching on our 2.0 base, if its fixed for that, its fixed for 3.0 <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
No, it's fixed for all mods using the updated engine.dll or w/e the dll's name is.
Hallelujah! <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
He probably fixed it in minutes because it was probably some simple for loop or while loop error. Probably used the wrong comparison operator for the loop and all it took was a couple minutes to fix it, but this has been present for years... Amazing it wasn't noticed sooner.
WOOT... now there wont be the conflict between the reserve slot system and the fix...
How do you suggest they would have noticed it sooner? If that's what the problem was, we're talking about a single character in the entire source code being wrong, so they're not just going to stumble on it by accident. And just look at how long it took the community just to figure out what the nature of the problem really was.
How do you suggest they would have noticed it sooner? If that's what the problem was, we're talking about a single character in the entire source code being wrong, so they're not just going to stumble on it by accident. And just look at how long it took the community just to figure out what the nature of the problem really was. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Sorry, I sounded like I was talking about searching through thousands of lines of code for obsure bugs, I meant I am amazed on how someone playing didn't notice it was the last slot that was creating the hitbox bug years ago.
<!--QuoteBegin-Head crab+--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Head crab)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->The bug is fixed, the problem is that HLDS servers not running under Steam need to use the special update tool to receive new updates unlike servers running under Steam which receive them after a restart.
It's been tested and is definitely fixed in my very own test dedicated server which runs with Steam. However, our public servers are not yet updated, as it has to be done with the update tool by the server hosting maintenance people.
So there may be a lot of servers in the same situation...<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Most of the server hosting companies don't use Steam to run their servers, so most of the dedicated servers in the whole Half-Life community are not auto-updating, so they have use the HLDS update tool for any update to their server. Many servers will probably take a while to be updated because some server admins either have to rely on their hosting company to update HLDS or some server admins are totally unaware of the importance of updating their HLDS.
Server admins have to assume their responsabilities and update their server when needed. There's nothing we can do for those who won't update for any reason. The bug will remain on outdated servers, so don't be surprised to see it again. As a player, I guess you could ask your local server admin if his server has been updated if you want to avoid this bug again.
Eventually, the outdated servers might become incompatible with upcoming client updates to force server admins to update. At least that would be a good move on Valve's part.
Anyhow, admins whose servers are not running on Steam should update by running <b>hldsupdatetool.exe</b>, which, if I'm not wrong, is included with the non-Steam version of HLDS (the 420 mb one). If it's not, there are many mirrors for it on the web. The file itself is less than 1 mb. Visit the Steam forums for more informations on that tool.
<b>For the people who don't want to be bothered to read all of the above, here's what it says in short: the bug is fixed, it's just that some/many dedicated servers not running on Steam remain outdated.</b>