lastest MAM security 2.2

[jww]

where do i find this thanks.

[Floyd]

You can get it if you upgrade CI. However, there appears to be problems with it and Spearhead.

We had to revert back to an older version of the MAM Security pk3 to keep from kicking everyone on the server.

If you upgrade, keep a close eye on the server! The upgraded CI and the older Security pk3 will work together, but at this point I couldn't tell you what the consequences or lack of benefits are.

Perhaps, Buzz could explain further.....

FYI, I was forcing skins and models with Hammer's v2.2 at every map change. However, even after disabling that, we were still getting kicked...

Floyd

[razorbakill]

well i was working on this problem all morning, and the only thing i came up with is that when you enable the new anti-hacked skin feature it forces skins that end with the #2. (ex. allied_airborne_2) If you dont have these skins in your authorized list it will kick everybody. Do a rcon serverinfo and see what the security skin is and then see if you have them in your authorized list. I run mohaa and those skins weren't in the authorized skin list, but they were in the spearhead one, so i copied and pasted them into the mohaa one. The only problem now is that when it forces players to these skins it also checks the box on their computers to force models and now everyone gets the Z code hack for forced models, argh lol. Also I still dont know what it means by a "large percentage of wallhacks" is. I tested it with several and it didnt detect any of them , :( oh well

[DCFA-Anex]

The new anti-cheat skin feature is actually supposed to work in line with forced screenshots. By forcing a non existent skin, a player not cheating will have their models screen empty, whereas the cheater with cham skins would not. The goal is to catch those using toggleable skins during the forced SS, they can switch all they want but when it shows a "good" skin/model in the screen they send you, you can say bye bye them and hello to my banned list.

The forced models on part is to aid in this new feature. Yes I know it's going in a different direction then other mods (codesecurity or DMZ), but the forced SS is the only true way to catch a cheater in the act (Pandora prevents, forced SS catches...whether they send it in or not).

It's not the greatest way, but it does bring us one step closer to catching them.

[DCFA-Anex]

Oh, I forgot to add, the problem with your people getting kicked is not becuase of MAM_Security.pk3, version 2.2, but rather, as one of the recent posts stated, is that you did not have the skins used in the hack check added to your authorized skin list.

MAM mods do not kick, only the users or program(s) interfaced with it does that.

BTW, MAM_Security.pk3, version 2.3, will be released soon. I've tweaked a few things and fixed up some problems I didn't have time to fix in 2.2. It's being reviewed by my testers now but I hope to have it released within the next couple days.

[Buzz_Litebeer]

I have had no real input on the making of the security since version 2.0