[flintridge]

Hi Bugsy,

I want your opinion on something. Would it be possible when a person is firing to tell the size of the zone their cursor fires in, or always fires in?

I have check and it seems most the popular aimbots all have some kind of FoV size they shoot in and a hit box zone(Also something called Bones). People do not seem to change this size much once they are use to it. So if they always fire in a zone and if you can find that zone size. then i was thinking you could use that zone size for were the bot should be spawned from the cursor's center point, then fire the 2 shots and see what happens.

I was also curious if when time to check, that you could force a freeze on them. That they can do nothing, then spawn the bot and fire the 2 shots. Of course this would only work if we are using the key they are using to activate the aimbot for firing.

[flintridge]

Originally Posted by flintridge Hi Bugsy, I was also curious if when time to check, that you could force a freeze on them. That they can do nothing, then spawn the bot and fire the 2 shots. Of course this would only work if we are using the key they are using to activate the aimbot for firing.

A bit more thought on this one, maybe a way to scroll threw several key choices to see what fires the aimbot while doing the test. Say it test mouse1, then mouse2, mouse3, mouse4, mouse5, shift or what not, you get the idea i think. If it does not catch on mouse1 next test would be mouse 2, third test be on mouse 3 and so on.

Even with out the freezing this would be a good option i think, at least force players to start picking less convenient buttons, lol.

[DumbServerWontWork]

So does this work well? And does it do amx_banip?

[Pamaliska]

It sometimes gives false detections, especially on small maps.

[Bugsy]

The language file has been updated to include missing Lithuanian translations.

Originally Posted by .Owyn. could you add an option to disable autowatch on knife maps? could you add an feauture to give player who previously passed aim monitor tests have lower priority in autowatch than new players who have not

Yes I will consider both for future releases.

Originally Posted by flintridge Hi Bugsy, I want your opinion on something. Would it be possible when a person is firing to tell the size of the zone their cursor fires in, or always fires in? I have check and it seems most the popular aimbots all have some kind of FoV size they shoot in and a hit box zone(Also something called Bones). People do not seem to change this size much once they are use to it. So if they always fire in a zone and if you can find that zone size. then i was thinking you could use that zone size for were the bot should be spawned from the cursor's center point, then fire the 2 shots and see what happens. I was also curious if when time to check, that you could force a freeze on them. That they can do nothing, then spawn the bot and fire the 2 shots. Of course this would only work if we are using the key they are using to activate the aimbot for firing.

I'm not 100% sure about implementing something like that. It would probably hinder the performance of the plugin since it would be constantly monitoring all players shoot zone. If anyone has any ideas how to efficiently do this, I'm all ears.

Originally Posted by DumbServerWontWork So does this work well? And does it do amx_banip?

It does what it can, it won't catch them all but it will catch some. Yes it has amx_banip.

[flintridge]

Originally Posted by Bugsy I'm not 100% sure about implementing something like that. It would probably hinder the performance of the plugin since it would be constantly monitoring all players shoot zone. If anyone has any ideas how to efficiently do this, I'm all ears.

I was thinking more along the lines of once they were being considered for watching that it do that to that person and only that person at that time.

But i am more interested in the second concept now. ^^

A bit more thought on this one, maybe a way to scroll threw several key choices to see what fires the aimbot while doing the test. Say it test mouse1, then mouse2, mouse3, mouse4, mouse5, shift or what not, you get the idea i think. If it does not catch on mouse1 next test would be mouse 2, third test be on mouse 3 and so on. Even with out the freezing this would be a good option i think, at least force players to start picking less convenient buttons, lol.

Would it be possible to make it fire them two shoots differently? Say i have it set to pass 5 test before aimwatch removed. Test one is +attack, test to tries mouse 1, test three tries mouse 5, test four tries left control key and so on. Maybe even a way to where i can set the number of tests and the keys of my own choosing to test for?

PS This is my favorite plugin to date. ^^ Good work!

[Bugsy]

Originally Posted by flintridge I was thinking more along the lines of once they were being considered for watching that it do that to that person and only that person at that time. But i am more interested in the second concept now. ^^

I will have to look into a way to do this and if it is feasible.

Originally Posted by flintridge Would it be possible to make it fire them two shoots differently? Say i have it set to pass 5 test before aimwatch removed. Test one is +attack, test to tries mouse 1, test three tries mouse 5, test four tries left control key and so on. Maybe even a way to where i can set the number of tests and the keys of my own choosing to test for? PS This is my favorite plugin to date. ^^ Good work!

Triggering MOUSE1 is on the top of the list of my things to do. I'm not sure if it is possible since it is more of a client-side thing. I will look into it though. Hopefully I will figure it out for v1.2 release.

v1.2 changes so far:
- Removed get_user_attacker because of a bug that was causing the gun and hitzone params to return 0; see v1.1 changelog and thread. Hitzones are now determined via fakemeta call get_pdata_int(g_BotID, m_LastHitGroup). Re-added get_user_weapon to retrieve what weapon the bot was shot with for determining hit-points.
- Changed get\set origin to fakemeta; all origins are now floats.
- Removed fun module; it was being used only for set_user_hitzones. Replaced with fm_set_user_hitzones (written by samurai), slightly edited. As with the ham forwards that are enabled\disabled when needed, the same is done for the fm_traceline forward used in fm_set_user_hitzones. The forward is enabled if 1+ players have shootblanks punishment and is disabled when all shootblanks-punished players disconnect.

[flintridge]

Originally Posted by Bugsy Triggering MOUSE1 is on the top of the list of my things to do. I'm not sure if it is possible since it is more of a client-side thing. I will look into it though. Hopefully I will figure it out for v1.2 release.

There is a plugin called amx_exec i believe that somehow executes anything client side you want to the player. If you could borrow a part of that code or write something similar i think you could force it that way in a set of sequences. It sounds good to me when i type it, but sadly i lack any skills in plugin writing to know if that is reasonable suggestion.

[Bugsy]

Originally Posted by flintridge There is a plugin called amx_exec i believe that somehow executes anything client side you want to the player. If you could borrow a part of that code or write something similar i think you could force it that way in a set of sequences. It sounds good to me when i type it, but sadly i lack any skills in plugin writing to know if that is reasonable suggestion.

Execute client can be used to set binds and run commands on the clients machine but I dont think you can actually call a key-press or mouse-click server-side. amx_exec pretty much emulates the players console

[nitz]

Heylo Bugsy,

This plugin has been wonderful! I've got many hackers on my server with it, rather impressive.

However, since I updated from 0.9 to 1.0 and now 1.1 the plugin is no longer working. I have tried to compile it myself, the plugin runs just fine, you can use the command amx_aimwatch player 1 or amx_aimautowatch and all the cvars. The watch is done alright however it's not watching automatically for players, there was players with 30/2, 26/0 and nothing happened, they kept headshotting and I've never got anything on my log since 0.9.

What might be wrong with this? Unfortunately I didn't keep a backup of the 0.9.

I'm running the lastest AMXX and Hlds with many custom plugins.

Thank you