[Bugsy]

We will have to go with all green or just have the heading green.

ie.
[Aimbot Detector] bugsy was detected using an aimbot

or

[Aimbot Detector] bugsy was detected using an aimbot

[Owyn]

why not green then team-color? that's a nice way

[Bugsy]

Originally Posted by .Owyn. why not green then team-color? that's a nice way

Ok, that does look nicer than all green. It is done, final product:

Terrorist:
[Aimbot Detector] Bugsy is being watched for aimbot

Counter-Terrorist:
[Aimbot Detector] Bugsy is being watched for aimbot

Edit: Here's the current changes for the next release. Does anyone have any requests or bug reports:

v1.3
- Added a block so the plugin will not recognize the bot taking damage for detection if not inflicted by a bullet or if not by the watched player. Previously, we were just returning HAM_IGNORED which made the bot still take damage but not let the player get detected. Now if the damage is done by a player other than the watched player or if the bot is hurt by anything other than a bullet, we return HAM_SUPERCEDE so bot takes no damage. Also added HAM_SUPERCEDE at the end of the takedamage forward so the bot will not get hurt even if shot by the watched player. This will allow it to take an unlimited number of shots without dying.
- Added blockage of bot being spawned if the watched players victim is killed with a grenade
- Removed checking if victim ground distance is too close to killer. Now only the aiming angle is checked from the watched player to the location where the bot will be spawned. If the bot spawn origin is outside of the acceptable angle range, we do not spawn the bot. The angle ranges currently being used are Angle < 40 & fAngle > 10. This solves the bug where a player gets falsely detected because his gun is already in the aiming direction of where the bot is spawned. This error has been reported a few times on cs_assault when the watched player is on the ground outside and has killed an enemy that was standing on the roof. The player kills the enemy and then the bot gets spawned and hit by shots because the player is already aiming in the direction. Thanks to owyn for his reports and stupok for the angle calculation code.
- Added colorized chat messages. [Aimbot Detection] will appear green and the actual msg will be in team color (blue\red)
- Added cvar to enable\disable chat notifications.

[joaquimandrade]

Originally Posted by Bugsy Ok, that does look nicer than all green. It is done, final product: Terrorist: [Aimbot Detector] Bugsy is being watched for aimbot Counter-Terrorist: [Aimbot Detector] Bugsy is being watched for aimbot Edit: Here's the current changes for the next release. Does anyone have any requests or bug reports: v1.3 - Added a block so the plugin will not recognize the bot taking damage for detection if not inflicted by a bullet or if not by the watched player. Previously, we were just returning HAM_IGNORED which made the bot still take damage but not let the player get detected. Now if the damage is done by a player other than the watched player or if the bot is hurt by anything other than a bullet, we return HAM_SUPERCEDE so bot takes no damage. Also added HAM_SUPERCEDE at the end of the takedamage forward so the bot will not get hurt even if shot by the watched player. This will allow it to take an unlimited number of shots without dying. - Added blockage of bot being spawned if the watched players victim is killed with a grenade - Removed checking if victim ground distance is too close to killer. Now only the aiming angle is checked from the watched player to the location where the bot will be spawned. If the bot spawn origin is outside of the acceptable angle range, we do not spawn the bot. The angle ranges currently being used are Angle < 40 & fAngle > 10. This solves the bug where a player gets falsely detected because his gun is already in the aiming direction of where the bot is spawned. This error has been reported a few times on cs_assault when the watched player is on the ground outside and has killed an enemy that was standing on the roof. The player kills the enemy and then the bot gets spawned and hit by shots because the player is already aiming in the direction. Thanks to owyn for his reports and stupok for the angle calculation code. - Added colorized chat messages. [Aimbot Detection] will appear green and the actual msg will be in team color (blue\red) - Added cvar to enable\disable chat notifications.

In my opinion colorized chat messages will make it look less professional.

[Bugsy]

Originally Posted by joaquimandrade In my opinion colorized chat messages will make it look less professional.

To be honest, I'm not 100% sold on the idea either, I just want the messages to standout more vs. the stream of normal chat. Perhaps maybe I will just colorize the [Aimbot Detector] heading.

[joaquimandrade]

Originally Posted by Bugsy To be honest, I'm not 100% sold on the idea either, I just want the messages to standout more vs. the stream of normal chat. Perhaps maybe I will just colorize the [Aimbot Detector] heading.

Try with another phrase format without changing the color like this:

* You are on a killstreak with %d kills.

[Owyn]

Edit: Here's the current changes for the next release. Does anyone have any requests or bug reports:

what about my bug report when spawned bot is not being accepted as a target by a cheat?

ps - have you sent me anything yet? i got no new mail

[Gizmo]

or maybe like this
[Aimbot Detector] Bugsy is being watched for aimbot

[Bugsy]

Originally Posted by Gizmo or maybe like this [Aimbot Detector] Bugsy is being watched for aimbot

owyn no, I will send it now. what do you mean by that bug, I don't understand fully.

I like this one, nice and subtle.
[Aimbot Detector] Now watching bugsy

[PauliusBa]

Originally Posted by Bugsy I think so too, too many huds can get annoying. I think I will add some color just to make the msg stand out compared to normal chat. I will add an option for no notification now that you've said that. What do you think about the below color format? [Aimbot Detector] Now watching bugsy

There at least could be a cvar for that... I always notice the Aimbot Detector messages. And only people with ADMIN_CVAR access can see them anyway, because not all admins understand the principles of this plugin (and they don't need to) because could get confused.
PS: I have added a " * " in front of every aimbot message in .sma, that means exclamation. Some more important messages use ** [sth] sth - that is the way most plugins are done. Regular announcements don't have the " * ", so strings with that " * " do get noticed.
* [Aimbot Detector - autowatch] blah blah
I never miss them. Colorizing them would not only, in my opinion, make it look less professional, but annoy some admins, too. It's just that people get checked occasionally.
"Aimbot Detected" stuff, though, could be in color.

PS: i had sumbitted "final" [lt] ML some time ago.