Advanced In-Game Admin and Ban Enforcer - AdKats

[ImportBot]

Originally Posted by buzZzer*:

 

Buzz, there is nothing wrong, the spambot only runs when a round is active and there are players in the server. Simply join your server and spawn, the spambot will run. This is to avoid unnecessary log entries.

Ohhh ok, I had not known. Thanks for your help!

[ImportBot]

Originally Posted by spatieman*:

 

for some unknow reasons.

we get get sudenly this messege when we kill some1 on our server.

example for test

!kill pix test ,even with pixe ,iam ,iama no result

Code:

Invalid PreMessage ID, valid PreMessage IDs are 1-4

the ingame admin plugin is disabled, and with enabled it also wont work.

we had a very long time not used the command, (was almost never needed)

what did i mess up ?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

for some unknow reasons.

we get get sudenly this messege when we kill some1 on our server.

example for test

!kill pix test ,even with pixe ,iam ,iama no result

Code:

Invalid PreMessage ID, valid PreMessage IDs are 1-4

the ingame admin plugin is disabled, and with enabled it also wont work.

we had a very long time not used the command, (was almost never needed)

what did i mess up ?

You enabled 'Require Use of Pre-Messages' in setting section A12. Disable that and it will return to normal.

[ImportBot]

Originally Posted by spatieman*:

 

You enabled 'Require Use of Pre-Messages' in setting section A12. Disable that and it will return to normal.

works again..

thank you!

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hello.

I'm have 5 servers and run on 3 servers adkats and procon logger, bot on other 2 see this error

Attachment 4017

Can you help me with this?

So 3 servers run correctly but the other two error out on startup. Strange.

 

Try updating to the latest test version and see if you get the same error on those layers. Your running instances can grab that version with /pupdate

[ImportBot]

Originally Posted by ChaTon*:

 

Hello again

 

After checking the logs, I have noticed that when the server reboots, so does procon I get the following error:

 

Code:

[AdKats] EXCEPTION-67080-D-GetDisplayPluginVariables-AccessFetching13: [Error while fetching display vars.][System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.AdKats.GetPingLimitStatus()
   at PRoConEvents.AdKats.GetDisplayPluginVariables()]

And I have to disable adkats and enable it again so it can work, otherwise the settings don't show up

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hello again

 

After checking the logs, I have noticed that when the server reboots, so does procon I get the following error:

 

Code:

[AdKats] EXCEPTION-67080-D-GetDisplayPluginVariables-AccessFetching13: [Error while fetching display vars.][System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.AdKats.GetPingLimitStatus()
   at PRoConEvents.AdKats.GetDisplayPluginVariables()]

And I have to disable adkats and enable it again so it can work, otherwise the settings don't show up

Getting display plugin vars is a huge function, i'll need you to enable plugin debugging on your layer to find where that triggered.

 

procon.cfg

procon.private.options.enablePluginDebugging True

 

Once you see the D in your exception is replaced with a number, post an issue on github.

[ImportBot]

Originally Posted by duna3*:

 

Sorry if this is not the appropriate fórum

 

DPS not work 100% sure

 

I banned unreason, i never use or have hack

 

Not how the system works but I think dont it's safe. Considering that there are many values that could give a false positive.

bad connection, packet loss, data is not recorded on the server, netcode, etc. too posible i shot opponet with low health what no register in server.

 

I need for kill 10 bullest and few times 4 (headshot or low health) and same time lose de connect 10seg and i run in map 200 meter and go back (teleport)

 

this is the last match on the server where dps ban me

 

pardo_daxer bf4

 

http://battlelog.battlefield.com/bf4...416/248089607/

 

The problem is not to be a single server ban. The problem is being on a list metabans of hacker that many servers use or search Nick and assume that is hacker.

 

sry my english

[ImportBot]

Originally Posted by duna3*:

 

Sorry if this is not the appropriate fórum

 

DPS not work 100% sure

 

I banned unreason, i never use or have hack

 

Not how the system works but I think dont it's safe. Considering that there are many values that could give a false positive.

bad connection, packet loss, data is not recorded on the server, netcode, etc. too posible i shot opponet with low health what no register in server.

 

I need for kill 10 bullest and few times 4 (headshot or low health) and same time lose de connect 10seg and i run in map 200 meter and go back (teleport)

 

this is the last match on the server where dps ban me

 

pardo_daxer bf4

 

http://battlelog.battlefield.com/bf4...416/248089607/

 

The problem is not to be a single server ban. The problem is being on a list metabans of hacker that many servers use or search Nick and assume that is hacker.

 

sry my english

[ImportBot]

Originally Posted by ChaTon*:

 

Will do so as soon as the database is up running again for this server

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

The 'magic bullet' catch is going quite well, and it is catching them after a single round of usage.

 

Players banned for 'Code 7' on our servers have triggered this automatic catch, and it appears to be free of false positives after tweaking the trigger criteria.

[ImportBot]

Originally Posted by Subman_9*:

 

The 'magic bullet' catch is going quite well, and it is catching them after a single round of usage.

 

Players banned for 'Code 7' on our servers have triggered this automatic catch, and it appears to be free of false positives after tweaking the trigger criteria.

Nice to hear that I want to ban those 'magic bullet' cheaters as soon as possible. When you will enable it on the TEST branch ?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Nice to hear that I want to ban those 'magic bullet' cheaters as soon as possible. When you will enable it on the TEST branch ?

I'll enable it there once I'm sure it's not issuing false positive bans.

[ImportBot]

Originally Posted by iraqiboy90*:

 

Hi

 

With all my recent attempts on various offline players. It would never find the offline player when running a command while ingame or from procon chat.

Time since offline is not certain, but the last one I tried atm is a day since offline.

Also, procon was not restarted meanwhile.

 

running 6.6

 

Is acting on offline players an "always should work" feature, or is it time-based or cache-based?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hi

 

With all my recent attempts on various offline players. It would never find the offline player when running a command while ingame or from procon chat.

Time since offline is not certain, but the last one I tried atm is a day since offline.

Also, procon was not restarted meanwhile.

 

running 6.6

 

Is acting on offline players an "always should work" feature, or is it time-based or cache-based?

Update your plugin, some changes to that were made.

[ImportBot]

Originally Posted by squidextreme*:

 

Does adkats support BFH?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Does adkats support BFH?

Yes.

[ImportBot]

Originally Posted by iraqiboy90*:

 

Update your plugin, some changes to that were made.

Thanks. It's working fine now after update to test build.

 

Btw, any documentation on new features that has been added to the test build?

[ImportBot]

Originally Posted by iraqiboy90*:

 

The 'magic bullet' catch is going quite well, and it is catching them after a single round of usage.

 

Players banned for 'Code 7' on our servers have triggered this automatic catch, and it appears to be free of false positives after tweaking the trigger criteria.

I'm curious, how does the detection work?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I'm curious, how does the detection work?

It looks for kills on reports that are gained without a weapon that's registered on battlelog. Some things trigger this legitimately like DamageArea, or VehicleUpsideDown, but it filters those out when running the calculations. So far it's been 100% accurate with this design.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Thanks. It's working fine now after update to test build.

 

Btw, any documentation on new features that has been added to the test build?

There have been around 150 patches since 6.6, and I have not had the chance to write up docs for any of it.

[ImportBot]

Originally Posted by dyn*:

 

Woke up this morning to reports of admin not working... thinking that procon must be down. Looks like we suffered quite a large data loss to our database. Bans, records, and user groups are gone. Using 6.7.0.83

 

ADKATS plugin settings are still there as are logs from chat and player stats.

 

Seeing 200,000+ rows in the debug table for the last 1 day including:

[PlayerListingThreadLoop][Error occured in player listing thread. Skipping loop.]: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

at System.ThrowHelper.ThrowKeyNotFoundException()

at System.Collections.Generic.Dictionary`2.get_Item(T Key key)

at PRoConEvents.AdKats.AssignPlayerRole(AdKatsPlayer aPlayer)

at PRoConEvents.AdKats.PlayerListingThreadLoop()

Backups... We meant to do the backups "tomorrow" (lol_). =(

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Woke up this morning to reports of admin not working... thinking that procon must be down. Looks like we suffered quite a large data loss to our database. Bans, records, and user groups are gone. Using 6.7.0.83

 

ADKATS plugin settings are still there as are logs from chat and player stats.

 

Seeing 200,000+ rows in the debug table for the last 1 day including:

 

 

Backups... We meant to do the backups "tomorrow" (lol_). =(

If records or bans are removed this event did not come from the plugin, there is no code in the plugin to delete records or bans as they are meant to be a permanent record.

 

It sounds like someone ran the AdKats setup script on your database. That would have wiped everything and returned it to initial state, then the plugins would have posted their current settings back to the database. That setting post happens every 5 minutes and explains why your settings were still there, or rather were restored from the running instances.

 

Those errors you see are because the plugin initially loaded data but it didn't exist anymore on the db side, so the plugins are freaking out wondering why their info was suddenly gone.

[ImportBot]

Originally Posted by Subman_9*:

 

I have some suggestion ColColonCleaner. I think it would be good, if AdKats Internal-Hacker-Checker will give less detailed informations to a cheater. If autoadmin is banning a cheater with a message like "Hacking/Cheating DPS Automatic Ban [LIVE 100][PP2000-100-21-0-21]" then you are giving a lot of information to him, so he can try to avoid this kind of ban on a new BF4 account. Maybe AdKats should return only this information: "Hacking/Cheating" and the more detailed information of this ban should be visible only to the admin. It could be stored for example in the ban_notes column in the adkats_bans table, so the final result could be like this http://i.imgur.com/H1PrQ6i.png

 

What do you think about this ?

[Prophet731]

Originally Posted by Prophet731*:

 

I have some suggestion ColColonCleaner. I think it would be good, if AdKats Internal-Hacker-Checker will give less detailed informations to a cheater. If autoadmin is banning a cheater with a message like "Hacking/Cheating DPS Automatic Ban [LIVE 100][PP2000-100-21-0-21]" then you are giving a lot of information to him, so he can try to avoid this kind of ban on a new BF4 account. Maybe AdKats should return only this information: "Hacking/Cheating" and the more detailed information of this ban should be visible only to the admin. It could be stored for example in the ban_notes column in the adkats_bans table, so the final result could be like this http://i.imgur.com/H1PrQ6i.png

 

What do you think about this ?

The ban notes can easily be overwritten so you would lose that information if it happened. This could be something done though in AdKats 7 as we're massively overhauling the tables because of how limited they are now too us. So this could be something then.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I have some suggestion ColColonCleaner. I think it would be good, if AdKats Internal-Hacker-Checker will give less detailed informations to a cheater. If autoadmin is banning a cheater with a message like "Hacking/Cheating DPS Automatic Ban [LIVE 100][PP2000-100-21-0-21]" then you are giving a lot of information to him, so he can try to avoid this kind of ban on a new BF4 account. Maybe AdKats should return only this information: "Hacking/Cheating" and the more detailed information of this ban should be visible only to the admin. It could be stored for example in the ban_notes column in the adkats_bans table, so the final result could be like this http://i.imgur.com/H1PrQ6i.png

 

What do you think about this ?

This would be a change to how bans are processed, and really wouldn't be worth it in this version. I'll add it to the list of things we can implement in the revamp.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

A notification for all those on TEST builds:

 

In the latest TEST version the global damage mod automatic bans, LIVE damage mod automatic bans, and magic bullet automatic bans are hardcode enabled. The updated magic bullet catch has been 100% accurate so-far during testing.

 

All other sections of the hacker-checker remain optional. The only sections hardcode enabled are those I am certain at this point will not issue false-positive bans. If you have any questions about bans it issues please PM me with all information about the bans and I'll make sure they are valid.

 

Once I write up the docs on the ~150ish patches since 6.6.0.0 i'll be pushing this public and ~1000 servers will automatically grab it, so I want to have a reasonable testing base before that happens.

[ImportBot]

Originally Posted by GitSum*:

 

I need to move my database to a new host

 

Can I just use something like NaviCat to do a data transfer from one database to the other?

[ImportBot]

Originally Posted by Subman_9*:

 

Unfortunately there's something very wrong with DPS Automatic Ban on the TEST AdKats branch, because... I've been just banned by my own AdKats

http://stats.bullet-point.pl/players/424/Subman-CNP-

and it must be of course a false-positive.

 

Here is what AdKats tell me about me: DPS Automatic Ban [LIVE 100][AEK971-90-20-1-22]

90 damage, 20 kills, 1 headshoot, and 22 hits

 

What happened in last one hour ?

1. I've joined another server (Metro) without AdKats and I've played there with AEK-971, then admin suddenly decided to change a map, so there's no battlelog report for this round.

2. After this I've joined my server with AdKats 6.7.0.83 version. I've played at the beginning with AEK-971, and then I've switched to shootgun. Battlelog report: http://battlelog.battlefield.com/bf4...384/309463633/

3. After about 30 seconds after the new round started (Paracel Storm) when I did not shoot to anybody I've received a ban from AdKats... Battlelog report: http://battlelog.battlefield.com/bf4...288/309463633/

 

In this situation I've disabled a whole Internal Hacker-Checker module in AdKats and I've disabled all "LIVE" bans. Also I'm wondering how reliable are the normal DPS bans and HSK bans. Let me know, if you need some more informations.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Unfortunately there's something very wrong with DPS Automatic Ban on the TEST AdKats branch, because... I've been just banned by my own AdKats

http://stats.bullet-point.pl/players/424/Subman-CNP-

and it must be of course a false-positive.

 

Here is what AdKats tell me about me: DPS Automatic Ban [LIVE 100][AEK971-90-20-1-22]

90 damage, 20 kills, 1 headshoot, and 22 hits

 

What happened in last one hour ?

1. I've joined another server (Metro) without AdKats and I've played there with AEK-971, then admin suddenly decided to change a map, so there's no battlelog report for this round.

2. After this I've joined my server with AdKats 6.7.0.83 version. I've played at the beginning with AEK-971, and then I've switched to shootgun. Battlelog report: http://battlelog.battlefield.com/bf4...384/309463633/

3. After about 30 seconds after the new round started (Paracel Storm) when I did not shoot to anybody I've received a ban from AdKats... Battlelog report: http://battlelog.battlefield.com/bf4...288/309463633/

 

In this situation I've disabled a whole Internal Hacker-Checker module in AdKats and I've disabled all "LIVE" bans. Also I'm wondering how reliable are the normal DPS bans and HSK bans. Let me know, if you need some more informations.

This is why I made sure it was being used on testing servers, it would have been awful if something like this hit every server running this without the proper testing. Tonight i'll bring it back to ours only.

 

No need to worry about the reliability of global bans, the global ones are using overall stats from battlelog which every other stat-based system uses and has been reliable for years. The LIVE system is completely new and parses its stats differently.

 

Basically what it does is on-join it checks your stats on battlelog for all weapons, pulls that down and stores it for later use. Whenever a round ends it waits for the round report to post then checks your stats again for an update. It compares the kills/hits for each weapon in your stat list between the two fetches, finding the difference in kill count and hit count.

 

When it fetched for you, you gained 20 kills and 22 hits on the AEK.

 

If I find that weapon specific data cannot be relied on from round to round I will be thoroughly disappointed, this had caught so many legitimate ones and if their data is randomly unreliable that means the whole LIVE system needs to be canned.

 

But, if it's an issue with how/when the data is grabbed, and not with the source, that can be fixed. I'll need as much info as you can provide about the incident. Anything more than just those reports?

 

EDIT: Please send your plugin console logs from around the time the ban happened. Also send details about your previous game, the one which does not have a report. I'm just happy it happened to someone that can be trusted as legitimate so it's not being questioned as valid during testing.