Advanced In-Game Admin and Ban Enforcer - AdKats

[ImportBot]

Originally Posted by AgentHawk*:

 

Thank you 4 this awesome Tool:smile:

 

1 wish

 

the Ping kicker with different Playercount settings. Like 32 140 Ping.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Thank you 4 this awesome Tool:smile:

 

1 wish

 

the Ping kicker with different Playercount settings. Like 32 140 Ping.

Perhaps in the future, sure.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Fixed some typos and misplaced elements in the user manual.

 

EDIT: Added surrender vote and auto-surrender/auto-nuke sections.

[ImportBot]

Originally Posted by Tryskull*:

 

little mistake, there are two B23 section with the v5.2.0.0

[ImportBot]

Originally Posted by TMiland*:

 

That means either your layer or your database have an incorrect UTC timestamp. That will cause a hefty amount of errors down the line when the systems are talking with each other. You need to correct the mismatch.

 

It's like having a clock that's 10 minutes fast, one of them is wrong.

I had to contact my Procon layer host to get the time corrected, the correction fixed the problem

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

little mistake, there are two B23 section with the v5.2.0.0

Thanks, there were a couple small errors i found with the surrender function too. Ill post an update later this week with the fixes. Giving more people time to find any problems now that it's pushed public.

[ImportBot]

Originally Posted by Tryskull*:

 

I'm not sure, but the "player locking settings" function causes an abnormal behavior with Multibancer.

my server often appear to have a difference of 4-5 players in a team for a long time.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I'm not sure, but the "player locking settings" function causes an abnormal behavior with Multibancer.

my server often appear to have a difference of 4-5 players in a team for a long time.

Locking only affects actions that happen within AdKats, blocking admin action on players. It does not affect multibalancer, or any other balancer/plugin for that matter, just denies in game commands on players.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I had to contact my Procon layer host to get the time corrected, the correction fixed the problem

Great! I added another script in the next update that will tell you which entity is incorrect for time, layer vs database. I'm pulling time from a global time server to check it. It's not an official server, but it works for my purposes.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I have no idea what caused the sudden surge in downloads 2 days ago... apparently 681 people downloaded 5.1.0.0 on the 25th, the day before 5.2.0.0 was released. The average is like 10 per day, so such a high number was very surprising.

 

Anyone know why this happened?

[ImportBot]

Originally Posted by Jasonpb*:

 

Auto update?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Auto update?

They downloaded version 5.1.0.0, which doesn't have any auto-update code in it. Quite confused.

[ImportBot]

Originally Posted by Ruger*:

 

Hello C3, I notice that the Internal Hacker Checker is banning for 20 years. Is there any way to change that time? Also what would be the best settings for each of the 3?

 

Thanks, Ruger

[Prophet731]

Originally Posted by Prophet731*:

 

Hello C3, I notice that the Internal Hacker Checker is banning for 20 years. Is there any way to change that time? Also what would be the best settings for each of the 3?

 

Thanks, Ruger

Why do you want to change the time if I may ask?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hello C3, I notice that the Internal Hacker Checker is banning for 20 years. Is there any way to change that time? Also what would be the best settings for each of the 3?

 

Thanks, Ruger

20 years is the default for "permanent" ban. You want it to temp-ban players for using hacks?

[ImportBot]

Originally Posted by naurel*:

 

Which commands are you using in that admin that AdKats does not cover?

It's not that i'm using command that isn't in AdKat, it's just that since my provider wont give us a database I'm using mine and it can take time to respond. Plus adkat is spamming quite often the chat, is there a way to disable that ? Like when someone request rule to not display to all admins that someone request rule. ?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

It's not that i'm using command that isn't in AdKat, it's just that since my provider wont give us a database I'm using mine and it can take time to respond.

Getting a database that is publicly accessible will cost much less than running a single 64p server, so there isn't much overhead.

 

Plus adkat is spamming quite often the chat, is there a way to disable that ?

You can disable many of the messages in section A12.

 

Like when someone request rule to not display to all admins that someone request rule. ?

There is not an option to disable that, as it's not chat spam. One might be added in the future if people request it.

[ImportBot]

Originally Posted by Ruger*:

 

Why do you want to change the time if I may ask?

The main reason I ask is it seems like Ive seen other streaming admins on metabans that only give 2 years bans. Maybe they are using a different program. Not sure.

20 years is the default for "permanent" ban. You want it to temp-ban players for using hacks?

No...I wouldnt want to temp-ban someone using hacks. But Id like to be sure that my settings are the best in order to ban true hackers. I was just noticing quite a few being banned with this feature turned on. See pix.

Capture.png

 

Also whats weird is I didnt change any of the numbers yet last night I saw that on one server the HSK trigger level was set to 60 on one server and 70 on the other which is why I ask what would be the best settings.

 

Do you recommend not using the cheatdetector plugin since I am using this?

 

I guess I just dont get how to read "HSK Automatic Ban [ACWR-81-158-128]" lol. Im getting old and wonder if Ill still be alive when these 20 year bans disappear.

[ImportBot]

Originally Posted by AgentHawk*:

 

what means_!

 

[18:38:56 78] [AdKats] WARNING: Role for ID 5 not found in role dictionary when assigning commands.

[18:43:06 89] [AdKats] EXCEPTION: Line Unknown: [CompleteRecordInformation][Error occured while completing record information.]: System.NullReferenceException: Object reference not set to an instance of an object.

at PRoConEvents.AdKats.FinalizeRecord(AdKatsRecord record)

at PRoConEvents.AdKats.CompleteRecordInformation(AdKa tsRecord record, String message)

[18:43:07 90] [AdKats] EXCEPTION: Line Unknown: [CommandParsingThreadLoop][Error occured in Command thread. Skipping current loop.]: System.NullReferenceException: Object reference not set to an instance of an object.

at PRoConEvents.AdKats.FinalizeRecord(AdKatsRecord record)

at PRoConEvents.AdKats.CompleteRecordInformation(AdKa tsRecord record, String message)

at PRoConEvents.AdKats.CommandParsingThreadLoop()

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

what means_!

The first one is because you deleted a role from the database manually without deleting the corresponding entries in the rolecommands table.

 

The second and beyond I'm not sure, but looking at the types, it could be because of the first one.

 

Find the entries you left in the rolecommands table with role ID 5 and remove them. Reboot your layers.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

The main reason I ask is it seems like Ive seen other streaming admins on metabans that only give 2 years bans. Maybe they are using a different program. Not sure.

 

No...I wouldnt want to temp-ban someone using hacks. But Id like to be sure that my settings are the best in order to ban true hackers. I was just noticing quite a few being banned with this feature turned on. See pix.

Capture.png

 

Also whats weird is I didnt change any of the numbers yet last night I saw that on one server the HSK trigger level was set to 60 on one server and 70 on the other which is why I ask what would be the best settings.

 

Do you recommend not using the cheatdetector plugin since I am using this?

 

I guess I just dont get how to read "HSK Automatic Ban [ACWR-81-158-128]" lol. Im getting old and wonder if Ill still be alive when these 20 year bans disappear.

2 years, for the life span of this game and the people who will still be playing it after that time, is basically a permanent ban. AdKats just defaults to permaban = 20 year temp-ban.

 

There is a whole section of the documentation about the auto-ban system for hackers: https://github.com/ColColonCleaner/A...with-whitelist

 

That even tells you what the different ban reasons mean, and gives suggested values for each of the settings .

 

Generally if you have a question, see if the docs answer it, most likely i wrote up how it works. I'm not sure why your settings are different for each server, the only reason you would want to have different settings is if you are running hardcore vs normal, the DPS trigger level should be slightly higher on hardcore servers.

 

You can still use the cheatdetector plugin if you want to, each plugin has features the others do not.

[ImportBot]

Originally Posted by naurel*:

 

Ok so I've testing the auto nuke since Sunday now, and here is what I can tell (fti : I'm on a Locker 64 Conquest Large and using the optimal Metro option)

 

The plugin will still nuke even 5 tickets left from the end.

Sometimes it sends 7 nuke row (wich is quite a lot) , sometimes just one.

It works well. A team can have all flags as long as they do not rape the other team too much and I love that.

People doesn't understand why they are being nuke when they aren't on the last flag (I'm using the sentence : "Auto-Nuking to prevent baseraping" maybe you have some better to advice for me).

 

Version used : 2.0.0.0

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Ok so I've testing the auto nuke since Sunday now, and here is what I can tell (fti : I'm on a Locker 64 Conquest Large and using the optimal Metro option)

 

The plugin will still nuke even 5 tickets left from the end.

Sometimes it sends 7 nuke row (wich is quite a lot) , sometimes just one.

It works well. A team can have all flags as long as they do not rape the other team too much and I love that.

People doesn't understand why they are being nuke when they aren't on the last flag (I'm using the sentence : "Auto-Nuking to prevent baseraping" maybe you have some better to advice for me).

 

Version used : 2.0.0.0

You are on lockers, and are using the metro option. Why? The optimal ticket rates for those maps are different...only use metro, on metro.

 

Here are the values we have for 64p lockers conquest:

 

 

There is not an option for max/min ticket count to allow auto-surrender to happen.

 

Also, there are a couple fixes i added to auto-surrender that are not in the full 5.2.0.0, please run the latest test branch 5.2.0.5 or later to use them.

[ImportBot]

Originally Posted by SmackDown*:

 

I have some questions about Admin Assistants.

 

If I activate this feature, how many reputation points does a player need to get this status, or is it strictly based on the number of player reports they make. Does reputation points effect Admin Assistant status?

 

Does a player only get to be an Admin Assistant if they make player reports or can they achieve that status if they acquire a certain number of reputation points?

 

Also, how do I assign what powers the Admin Assistant has. Say I only want them to be able to kick or temp ban a player only, how do I go about setting that up since at the moment I don't see any settings for Admin Assistants powers. Can we set this up so a player could become an Admin Assistant is they achieved a certain amount of reputation points? If so, I do I do this.

 

I have read the documentation for you great program and it doesn't answer my questions so I hope you can!

 

Thank you for your efforts, I love this program!

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I have some questions about Admin Assistants.

 

If I activate this feature, how many reputation points does a player need to get this status, or is it strictly based on the number of player reports they make. Does reputation points effect Admin Assistant status?

 

Does a player only get to be an Admin Assistant if they make player reports or can they achieve that status if they acquire a certain number of reputation points?

It is based solely on accepted reports, because that means they are a reliable reporter, the basis of the system. Some random dude could make a hundred bad reports and get AA simply because of reputation otherwise.

 

For those you trust, and don't need them to prove themselves via their reports being accepted, you can use the aawhitelist command.

 

Also, how do I assign what powers the Admin Assistant has. Say I only want them to be able to kick or temp ban a player only, how do I go about setting that up since at the moment I don't see any settings for Admin Assistants powers. Can we set this up so a player could become an Admin Assistant is they achieved a certain amount of reputation points? If so, I do I do this.

Admins assistants don't have access to any special commands, aside from !admins to view the list of online admins. What being an admin assistant means is that autoadmin can recognize and make sure valid reports they make are acted on, if admins are offline, or if admins miss the report. Valid reports are automatically acted on with a !punish on the targeted player.

 

Admin assistants don't have direct powers, because they are just that, assistants. All of their actions are put through a filter before being acted on, because we don't fully trust them; they were given powers by an automatic system after all. This is why the system needs to be based on accepted reports or whitelisting, not reputation, because real admins can directly control the former, not the latter.

 

If you want to give someone direct powers, add them as an admin.

[ImportBot]

Originally Posted by SmackDown*:

 

It is based solely on accepted reports, because that means they are a reliable reporter, the basis of the system. Some random dude could make a hundred bad reports and get AA simply because of reputation otherwise.

 

For those you trust, and don't need them to prove themselves via their reports being accepted, you can use the aawhitelist command.

 

 

 

Admins assistants don't have access to any special commands, aside from !admins to view the list of online admins. What being an admin assistant means is that autoadmin can recognize and make sure valid reports they make are acted on, if admins are offline, or if admins miss the report. Valid reports are automatically acted on with a !punish on the targeted player.

 

Admin assistants don't have direct powers, because they are just that, assistants. All of their actions are put through a filter before being acted on, because we don't fully trust them; they were given powers by an automatic system after all. This is why the system needs to be based on accepted reports or whitelisting, not reputation, because real admins can directly control the former, not the latter.

 

If you want to give someone direct powers, add them as an admin.

Thanks you for the explanation. It helped a lot.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Wow...slowmo on exception was activated in the 5.2.0.0 release, that's supposed to be dev only. I am releasing a patch in the next couple hours, your layers will auto-update themselves.

[ImportBot]

Originally Posted by Jasonpb*:

 

You are on lockers, and are using the metro option. Why? The optimal ticket rates for those maps are different...only use metro, on metro.

 

Here are the values we have for 64p lockers conquest:

 

 

There is not an option for max/min ticket count to allow auto-surrender to happen.

 

Also, there are a couple fixes i added to auto-surrender that are not in the full 5.2.0.0, please run the latest test branch 5.2.0.5 or later to use them.

What's your metro settings, thinking of giving this a go instead of the manual surrender as the multibalancer I've never got set right, just when I think I have for 4-5x rounds the next 3x result in base rape.

 

That minimum ticket gap seems low though, we run 2500 tickets on lockers and 1500 tickets on metro.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

What's your metro settings, thinking of giving this a go instead of the manual surrender as the multibalancer I've never got set right, just when I think I have for 4-5x rounds the next 3x result in base rape.

 

That minimum ticket gap seems low though, we run 2500 tickets on lockers and 1500 tickets on metro.

For metro conquest just use the setting "Use Optimal Values for Metro", the internal values are a little more verbose. It will not trigger unless a full baserape is happening.

 

There is a reason the gap is small for lockers, and even smaller for metro. When autobalance messes up, it can mess up BAD, where one team is spawn camped within a few minutes of starting the match. On lockers we give them time to come back with the 300 ticket difference minimum before it triggers off of the rates; On metro, no way, if they are spawn camped, they are done.

 

But first, update to 5.2.0.7

 

The best thing to to is experiment and see if it's triggering at what you would call the optimal time. The metro settings have been tested by us for a couple months now and seem to work great.

 

I might throw in another setting for optimal lockers settings if people give enough feedback for it.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Version 5.2.0.7 (29-OCT-2014)

Changes

 

• N/A

Enhancements

 

• Added more intuitive version update information after patches.
• Added global timing confirmation, along the same lines as database timing confirmation. Will not allow AdKats to boot if Procon layer UTC time is incorrect by over 5 minutes, and warn if incorrect by over 15 seconds.
• Added ticket counts to surrender vote record message.
• Exceptions posted to the database will include line numbers if the plugin debugging Procon option is enabled.

Bugs Fixed

 

• SlowMoOnException was mistakenly enabled in the 5.2.0.0 release. This is a dev-only setting that could, and most likely would, cause much lag for chat and console messages, slowing the entire program. This bug is why the 5.2.0.7 release was made so quickly after 5.2.0.0.
• Auto-Surrender could trigger multiple times in one round when ending it, causing record and chat spam.
• Surrender votes were allowed after a surrender vote was already complete, or after an auto-surrender was triggered.
• Plugin update messages to online admins and record source were being sent far too often, these have been reduced.

Upgrade SQL from 4.0.0.0 - Current

 

No upgrade SQL required.

 

If you are running 5.2.0.0, your layer will automatically update and only require a reboot to run this version.

If not, update one layer, run it to completion, then enable on your other layers.

 

https://sourceforge.net/projects/adk...atest/download