Anti FastFire v1.2 - Page 2

Xanimos · 10-16-2005 , 01:06

Quote:

Originally Posted by Zenith77

I'm a bit confused, Would this not register data to the wrong slot ?

Code:

g_nCurWeapon[id-1]

E.g. Player in slot 14 has fired, but data is registered to a player in slot 13 ?

Nope. He defines the variable as g_nCurWeapon[32] for a 32 man server. So he saves data as id-1 so you dont have an empty array. Like when you use g_nCurWeapon[33] then g_nCurWeapon[0] will never be used. So this way he saves data. As long as he always refers to the variable as id-1 then he wont have a problem.

DarkSnow · 10-16-2005 , 02:32

It does not realy matter anyway since im not using any of the data in question

Its just there to make sure that the client is firing, not realoading or something like that

AngryMouse · 10-23-2005 , 11:17

I really liked the sound of this plugin so put it on my server straight away. I noticed a lot of people were getting banned so I tested it myself, shot a full clip into someones head from point blank with an M4 and bam! I was banned from my own server. This is a great idea so please keep working on it but at the moment its unsafe for my server.

DarkSnow · 10-24-2005 , 19:01

Quote:

Originally Posted by AngryMouse

I really liked the sound of this plugin so put it on my server straight away. I noticed a lot of people were getting banned so I tested it myself, shot a full clip into someones head from point blank with an M4 and bam! I was banned from my own server. This is a great idea so please keep working on it but at the moment its unsafe for my server.

Ouch, terrible sorry about it. I tested it myself, pumping rounds after rounds and i didnt get booted myself for it =/ Though on the testserver it banned cheaters that you could tell were cheaters (testserver non vac2)

You can however reglate the sensetivety of the rate of fire by "amx_af_max" whitch is by deffault 16, try increasing it to something closer then 20 and those problems should go away. Sorry about your bans and thanks for the feedback.

genesis · 10-26-2005 , 04:47

I recommend making an advisory mode where it will display information to admins only about possible* cheating. This would be a separate mode but it could be permanent, as many ppl don't like leaving everything automated but don't mind some automation.

DarkSnow · 10-26-2005 , 22:07

Quote:

Originally Posted by genesis

I recommend making an advisory mode where it will display information to admins only about possible* cheating. This would be a separate mode but it could be permanent, as many ppl don't like leaving everything automated but don't mind some automation.

Yea i guess i should

It will be done in the merged version though, i dont think i will evolve this any futher.

RasterMan · 10-30-2005 , 11:05

Using mouse wheel for firing is counted as cheating that's why HLGuard bans people for it

It gives an unfair advantage to the player using it

DarkSnow · 10-31-2005 , 11:14

Yea, simply dont do it

Anyway, i belive you can check the firingrate against number of times klicked on +fire for the dual pistols if you for some reason want people to be allowed to bind mwhelup/down to +fire.

Dzyzus · 06-20-2006 , 19:49

What i must change to use it with amx bans?

taheri6 · 06-24-2006 , 05:24 Re: Anti FastFire v1.1

Try this.

Find

server_cmd("banid 0.0 %s",Authid)

and replace with

server_cmd("amx_ban 0 %s FastFire hack detected",Authid)