HLGuard 1.8 Released

[CSN NewsBot]

Not one to leave the CS 1.6 community high and dry, the HLGuard team (The Z Project crew) has been hard at work on the latest version of their server-side anti-cheat system. Hitting version 1.8, the latest offering houses a number of updates, fixes, and additions. Read up on some of the more major additions below, including the addition of SkyWalk Guard which prevents a number of map exploits for a handful of supported maps.[break="1.8 changelog"]

• [Added] SkyWalk Guard, HLGuard mode 8 (See release notes)
  
  
• [Added] Rapid name changing detection, HLGuard mode 7
  
  
• [Added] hlg_startdelay cvar. The agreement/first scan will be delayed this many seconds (User request)
  
  
• [Added] Time since last successful Steambans login to hlg_menu (User request)
  
  
• [Added] Time since last config update check to hlg_menu.
  
  
• [Added] %S config variable. Returns the slot of the player (User request)
  
  
• [Added] Uniqueid checking (User request)
  
  
• [Changed] Merged old style namebanning into HLGuard mode 7
  
  
• [Changed] hlg_checkversion is now a public viewable cvar
  
  
• [Changed] Recoded the socket system used by the config updater for better performance and flexibility. (See release notes)
  
  
• [Changed] Delayed actions executed immediately after a detection by a half second each to avoid lag on client executions, like Exec'n'Check detections.
  
  
• [Changed] The configs got another makeover and should be more simple to understand now. Most namebans were removed as well as they were well outdated.
  
  
• [Changed] The Rapid/Burstfire detection has been made a tiny bit less sensitive.
  
  
• [Changed] The client console will no longer be cleared upon Exec'n'Check detections.
  
  
• [Fixed] Description for the hlguard command
  
  
• [Fixed] Server crash if client connected with steambans client on and alias scanning off
  
  
• [Fixed] Config updater will now re-check latest value of hlg_checkversion before updating
  
  
• [Fixed] Possible fix to config loading crash in case of invalid files
  
  
• [Fixed] 3x Possible fix to random hlg_reset crashes
  
  
• [Fixed] Missing error message when hlg_loadmode was executed with an invalid argument.

[FL!P]

Cheats are bad.

[Pan the Goat God]

Mmkay

[pimpdad82]

Is HLGuard compatible with VAC?

[Thortok2000]

Completely, as far as I know. As far as VAC2, that's anyone's guess, but the answer is 'Should be'.

[GeOTek]

"[Changed] The Rapid/Burstfire detection has been made a tiny bit less sensitive." lol ive actually seen someone use this strange cheat just recently.

[m4elite]

that rapidfire detection is stupid..



if you fire your gun as fast as the game allows..



you get banned..



-_-

[HACKER HELL STORM]

*smiles at week old potd* oh i get it now!

[Thortok2000]

Rapid/Burstfire does get a lot of false positives, or used to. Like people who'd use mousewheel for attack.



I still remember when a newbie accused me of rapid burstfire because I shot off 50 1-bullet bursts with a para while trying to shoot someone at long distance. Like I'm really going to spray a para at someone a mile away, sheesh.

[Spedmaster]

Thortok2000 wrote...

Like I'm really going to spray a para at someone a mile away, sheesh.

*1950s instructional video voice*

Of course you are, Johnny. It's the American thing to do. What are you? A Commie?

[doomhag]

does this effect CS:S? if not, what's the point? CS code is so old (q1) and has so many loopholes this is a waste of time. Instead of complaining about CS:S being bugy, more people should help the new and better CS feel more like the Old CS (1.5 and before, 1.6 blows hamster nuts really).

[HACKER HELL STORM]

yea i played 1.5 until they killed the won servers..



DEATH TO STEAM! DEATH TO 1.6!

[-:Nighthawk:-]

Spedmaster wrote..

*1950s instructional video voice*

Of course you are, Johnny. It's the American thing to do. What are you? A Commie?

Hahaha, nice. :) One of the greatest parts of Dodgeball, too...

doomhag wrote..

does this effect CS:S? if not, what's the point? CS code is so old (q1) and has so many loopholes this is a waste of time. Instead of complaining about CS:S being bugy, more people should help the new and better CS feel more like the Old CS (1.5 and before, 1.6 blows hamster nuts really).

So because you don't approve of CS1.6, everyone should instantly give it up and convert to CS:S even if their computers can't run it and they can't afford better? Here I always thought the fact that well over 3x as many people play CS1.6 as play CS:S meant that the CS1.6 community might still be worth supporting.



Damn... what was I thinking?!?

[GeOTek]

Edited by [user="44043"] @ [time="1121244737"]

-:Nighthawk:- wrote..

Hahaha, nice. :) One of the greatest parts of Dodgeball, too...



So because you don't approve of CS1.6, everyone should instantly give it up and convert to CS:S even if their computers can't run it and they can't afford better? Here I always thought the fact that well over 3x as many people play CS1.6 as play CS:S meant that the CS1.6 community might still be worth supporting.



Damn... what was I thinking?!?

Not to say steam's stats arent of integrity. But xfire shows for some reason more minutes played by thier users on source. I see no clear reason why so many more source players would use xfire than 1.6 players? better comps maybe? or maybe because xfire is somewhat new and 1.6 players are more rigid to change of any kind.

[Equalizer!]

Ha, when you say "Not one to leave the CS 1.6 community high and dry" You are infact talking about the majority of people who play on Steam.



1.6 still most popular. Thanks and bye.