Jump to content

Advanced In-Game Admin and Ban Enforcer - AdKats

ColColonCleaner

By ColColonCleaner
in Plugins

Prophet731
Message added by Prophet731,

If you've been banned from a server then you will need to appeal the ban with the owners/community of that server. We do not control any bans done on servers that utilize AdKats as all bans are local to that server.

Recommended Posts

  • Replies 8k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Prophet731
Prophet731

I did a increase on the limit and pushed it up. You can get the updated minor version here..  

maddog
maddog

Thanks for all your help on this, with the def being correct, then the live HSK should not have triggered a sniper rifle? Could be anything to do with my post below and github? I have seen someone els

Hedius
Hedius

LOL. just lol. this has nothing to do with your procon version. The connection from your server to github fails. This is neither related to the plugin nor to procon.

Posted Images

  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

maybe a Bug:

 

Since the Update is our Chat Log all the time Off (PRoCon Chat, GUID, Stats and Map Logger) If I turn it On its automatically off after 2-4min.

Because you enabled "Post Stat Logger Chat Manually" in section A16. When that is enabled, it disables it in the stat logger plugin. Posting it manually is a good thing.
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

Just a suggestion since we know when a player is killed, is it possible to count the number of player killed by people and to substract this number to the ticket rate in order to have the ticket loss ratio with objectives (ie : without the kill/death of players). It would be a better way to know how many objectives are captures by a team (depending on the ticket loss ratio set on by default on the server of course). And this would work for all gamemode !

It will not work for rush or TDM, whose ticket loss rates are directly based on player deaths.
Link to comment
ImportBot Advanced Member

ImportBot

Posted
Posted

Originally Posted by BandofBrothers*:

 

Hello CCC, im pretty new to this so I apologize in advance for anything I might not know.

I get following error:

http://gyazo.com/296eededeaf526b3d903b36314bc7ae8

I checked up on SQL and I saw no column for GameID on tbl_playerdata:

http://gyazo.com/492df657c353458115ecaa3bc3733cb6

What should i do now?

 

Ah forgot to mention, Im running a BF3 Metro Server

* Restored post. It could be that the author is no longer active.
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

Hello CCC, im pretty new to this so I apologize in advance for anything I might not know.

I get following error:

http://gyazo.com/296eededeaf526b3d903b36314bc7ae8

I checked up on SQL and I saw no column for GameID on tbl_playerdata:

http://gyazo.com/492df657c353458115ecaa3bc3733cb6

What should i do now?

1. Which version of stat logger are you using?

2. Is this BF3 or BF4?

3. Try the test version i posted just above.

Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

http://gyazo.com/ef610ed98b3e60fda703768233e4e789

Got a new exception with duplicate key, and the gameid issue is still there

But for the first time it completed startup :smile:

Shut it down. Do not run it with those exceptions being thrown.

 

It looks like there is an incompatability with your version of stat logger...although its strange this is only coming to light now. I think something in the 5.1+ update changed it. I'll look into the issue.

Link to comment
ImportBot Advanced Member

ImportBot

Posted
Posted

Originally Posted by BandofBrothers*:

 

I should also mention, when I first saw this error, I deleted everything the db, re-installed statslogger and adkats. And still got those problems.

Ok ill shut it down till i hear more of you.

I thank you for your hard work.

Regards, BoB

* Restored post. It could be that the author is no longer active.
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

I should also mention, when I first saw this error, I deleted everything the db, re-installed statslogger and adkats. And still got those problems.

Ok ill shut it down till i hear more of you.

I thank you for your hard work.

Regards, BoB

Try this version. 5.1.9.4: https://raw.githubusercontent.com/Co...test/AdKats.cs
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

Is there a specific changelog that's viewable for each point release? tried looking on github but couldn't really see any way of sorting things like that.

I always post full changelogs when making stable version releases. In the meantime you can see the list of closed tickets for 5.2.0.0, which is basically a changelog, here: https://github.com/ColColonCleaner/A...22+is%3Aclosed
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

Version 5.2.0.0 (25-OCT-2014)

Changes

 

  • Plugin description and changelog are fetched at a 60 minute interval now, instead of only on startup.
  • New line characters are removed from messages posted to Procon's chat window.
  • Server info is now requested at a 10 second interval.
  • Rule list can no longer be sent to offline players.
  • MULTIBalancer unswitcher is now temporarily disabled when a SwapNuke is issued.
  • All records are now posted in database UTC time instead of Procon layer UTC time, unless specific requirements are met.
  • Assist command is nolonger allowed while a surrender vote is active, or if the round is not playing.
  • Yell duration now limited between 0 and 10 seconds.
Enhancements

 

  • Added option to disable new player notification.
  • Added option to disable player name change notification.
  • Added messaging commands for private conversations between players, either in the same server, or between any of the servers on the database.
  • Startup process messages are cleaned up in debug and procon chat.
  • Startup progress now shown to players attempting commands during AdKats startup.
  • Players attempting commands during AdKats startup are now be told once commands are fully online, not just admins.
  • Greatly reduced the amount of database overhead required after first fetch of the user list.
  • Added command to send private message to admins. /adminmsg
  • Added player reputation to the admin report notification.
  • Added special player group for Admin Assistants.
  • Added command to add players to the Admin Assistant list.
  • Released Ping Enforcer publicly.
  • Added notification and startup block if the Procon layer and database have significantly different values for UTC time.
  • Added 2 day and 3 day ban options to the punishment hierarchy.
  • Released Commander Manager publicly.
  • Added optional automatic player lock on admin action.
  • Added option to modify both manual and automatic player lock duration.
  • Added Internal SpamBot with optional whitelisting for admins and players.
  • Added SpamBot whitelist command.
  • Added surrender/votenext/nosurrender commands, with a full fledged surrender system.
  • Added reportlist command, to list the last 6 missed round reports.
  • Added plugin restart command.
  • Added server shutdown/reboot command.
  • Reputable players are now informed when admins join the server. Disable option provided.
  • Messages sent to procon admin are now bolded for visibility.
  • Notification of glitched players in the server are now sent to admins. The battlefield server must be rebooted in these cases, they cannot be kicked/banned.
  • Released Auto-Surrender/Auto-Nuke publicly.
  • Added option to only send report emails when admins are in the server.
  • Added option to tell players their reputation and infraction count on first-spawn, after the welcome message.
  • Added option to override stat logger chat posting, and post manually.
  • Added option to disable targeted player left notification.
  • Added better response to report ID usage if the report was already acted on.
  • Implemented linear interpolation on moving averages for ticket loss rates, score rates, and ping calculations.
  • Tell messages are no longer shown in procon chat as both say and yell, simply one line as tell to reduce spam.
  • Added commands for previous temp/perm bans, so old bans can be identified, and also will not affect player reputation.
  • Added automatic database updater, so global fixes to database issues can be fixed without requiring plugin updates.
  • Version status is now tracked for running instances, so issues with specific versions can be found and fixed.
  • Added global definition for special player groups, so external tools can access all valid group information.
Bugs Fixed

 

  • Fixed bug where some threads would not exit quickly when disabling/restarting AdKats.
  • Fixed messages in console marked as warning when they should just be information.
  • Fixed bug where SwapNuke would attempt to move commanders and spectators.
  • Fixed bug where certain commands marked as logging "Unable" were still attempting logging.
  • Fixed bug where, when AdKats started with no players in the server, player listing would be stuck in an endless loop until first player join.
  • Fixed bug where AdKats was unable to detect stat logger tables after changing database connection mid-instance.
Upgrade SQL from 4.0.0.0 - Current

 

No upgrade SQL required.

 

Update one layer, run it to completion, then enable on your other layers.

 

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

Link to comment
  • Administrators
Prophet731 Advanced Member

Prophet731

Posted
  • Administrators
Posted

Originally Posted by Prophet731*:

 

The BFAdminCP v2.0.0-RC1 would have been released along side this update as well as that's what we were aiming for. However, what I needed to get done couldn't be completed today so its delayed until tomorrow. The new version will require a minimum version of AdKats to run now. Anything 5.2.0.0 or higher will now be required to run the BFAdminCP.

The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

spacer.png

Link to comment
ImportBot Advanced Member

ImportBot

Posted
Posted

Originally Posted by HappyGotLucky*:

 

About every 5 minutes seeing this on all 12 layers:

 

[22:06:38 00] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

[22:11:43 56] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

[22:16:45 66] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

 

Intentional?

* Restored post. It could be that the author is no longer active.
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

About every 5 minutes seeing this on all 12 layers:

 

[22:06:38 00] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

[22:11:43 56] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

[22:16:45 66] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

 

Intentional?

Nope.

 

Found out why and fixed the update, you should not see that message anymore.

Link to comment
ImportBot Advanced Member

ImportBot

Posted
Posted

Originally Posted by durangod*:

 

i updated to 5.2 and i deactivated it first in procon. uploaded the new files to the server and then reactivated it. But it says i cant until its finished shutting down

 

Threads still existing: roundticketlogger [14]

 

so i restarted the server and same thing.

 

Please advise. thanks

 

 

update: i restarted the layer but went from one issue to a dif issue.

 

[07:09:05 08] [AdKats] ENABLED! Beginning startup sequence...

[07:09:05 40] [AdKats] SUCCESS: Populated reputation dictionaries.

[07:09:05 44] [AdKats] SUCCESS: Populated group dictionaries.

[07:09:05 44] [AdKats] SUCCESS: Server IP is 8.6.77.86:25210

[07:09:06 28] [AdKats] SUCCESS: Database connection open.

[07:09:11 00] [AdKats] SUCCESS: Database confirmed functional for AdKats use.

[07:09:11 20] [AdKats] ERROR: Your PRoCon layer and database have a 10m54s UTC timestamp mismatch. UTC-Database:sad:10/26/2014 12:58:17 PM) UTC-Procon:sad:10/26/2014 1:09:11 PM)

[07:09:11 21] [AdKats] INFO: Shutting down AdKats.

[07:09:11 74] [AdKats] AdKats 5.2.0.0 Disabled! =(

* Restored post. It could be that the author is no longer active.
Link to comment
  • Plugin Developer
ColColonCleaner Advanced Member

ColColonCleaner

Posted
  • Author
  • Plugin Developer
Posted

Originally Posted by ColColonCleaner*:

 

i updated to 5.2 and i deactivated it first in procon. uploaded the new files to the server and then reactivated it. But it says i cant until its finished shutting down

 

Threads still existing: roundticketlogger [14]

 

so i restarted the server and same thing.

 

Please advise. thanks

 

 

update: i restarted the layer but went from one issue to a dif issue.

 

[07:09:05 08] [AdKats] ENABLED! Beginning startup sequence...

[07:09:05 40] [AdKats] SUCCESS: Populated reputation dictionaries.

[07:09:05 44] [AdKats] SUCCESS: Populated group dictionaries.

[07:09:05 44] [AdKats] SUCCESS: Server IP is 8.6.77.86:25210

[07:09:06 28] [AdKats] SUCCESS: Database connection open.

[07:09:11 00] [AdKats] SUCCESS: Database confirmed functional for AdKats use.

[07:09:11 20] [AdKats] ERROR: Your PRoCon layer and database have a 10m54s UTC timestamp mismatch. UTC-Database:sad:10/26/2014 12:58:17 PM) UTC-Procon:sad:10/26/2014 1:09:11 PM)

[07:09:11 21] [AdKats] INFO: Shutting down AdKats.

[07:09:11 74] [AdKats] AdKats 5.2.0.0 Disabled! =(

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.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing


  • Our picks

    • EZRCON Update (9/4/2021)

      Prophet731 posted a topic in News,

      Game Server Hosting:

      We're happy to announce that EZRCON will branch out into the game server provider scene. This is a big step for us so please having patience if something doesn't go right in this area. Now, what makes us different compared to other providers? Well, we're going with the idea of having a scaleable server hosting and providing more control in how you set up your server. For example, in Minecraft, you have the ability to control how many CPU cores you wish your server to have access to, how much RAM you want to use, how much disk space you want to use. This type of control can't be offered in a single service package so you're able to configure a custom package the way you want it.

      You can see all the available games here. Currently, we have the following games available.

      Valheim (From $1.50 USD)


      Rust (From $3.20 USD)


      Minecraft (Basic) (From $4.00 USD)


      Call of Duty 4X (From $7.00 USD)


      OpenTTD (From $4.00 USD)


      Squad (From $9.00 USD)


      Insurgency: Sandstorm (From $6.40 USD)


      Changes to US-East:

      Starting in January 2022, we will be moving to a different provider that has better support, better infrastructure, and better connectivity. We've noticed that the connection/routes to this location are not ideal and it's been hard getting support to correct this. Our contract for our two servers ends in March/April respectively. If you currently have servers in this location you will be migrated over to the new provider. We'll have more details when the time comes closer to January. The new location for this change will be based out of Atlanta, GA. If you have any questions/concerns please open a ticket and we'll do our best to answer them.
      • 5 replies
      Prophet731

      Picked By

      Prophet731,

    • EZRCON Update 5/13/2021

      Prophet731 posted a topic in News,

      Hello All,

      I wanted to give an update to how EZRCON is doing. As of today we have 56 active customers using the services offered. I'm glad its doing so well and it hasn't been 1 year yet. To those that have services with EZRCON, I hope the service is doing well and if not please let us know so that we can improve it where possible. We've done quite a few changes behind the scenes to improve the performance hopefully. 

      We'll be launching a new location for hosting procon layers in either Los Angeles, USA or Chicago, IL. Still being decided on where the placement should be but these two locations are not set in stone yet. We would like to get feedback on where we should have a new location for hosting the Procon Layers, which you can do by replying to this topic. A poll will be created where people can vote on which location they would like to see.

      We're also looking for some suggestions on what else you would like to see for hosting provider options. So please let us know your thoughts on this matter.
      • 4 replies
      Prophet731

      Picked By

      Prophet731,

    • Procon Version 1.5.3.5 Released

      Prophet731 posted a topic in News,

      Added ability to disable the new API check for player country info


      Updated GeoIP database file


      Removed usage sending stats


      Added EZRCON ad banner



      If you are upgrading then you may need to add these two lines to your existing installation in the file procon.cfg. To enable these options just change False to True.

      procon.private.options.UseGeoIpFileOnly False
      procon.private.options.BlockRssFeedNews False



       
      • 2 replies
      Prophet731

      Picked By

      Prophet731,

    • Procon, Database & BFACP Hosting

      Prophet731 posted a topic in News,

      I wanted I let you know that I am starting to build out the foundation for the hosting services that I talked about here. The pricing model I was originally going for wasn't going to be suitable for how I want to build it. So instead I decided to offer each service as it's own product instead of a package deal. In the future, hopefully, I will be able to do this and offer discounts to those that choose it.

      Here is how the pricing is laid out for each service as well as information about each. This is as of 7/12/2020.

      Single MySQL database (up to 30 GB) is $10 USD per month.



      If you go over the 30 GB usage for the database then each additional gigabyte is charged at $0.10 USD each billing cycle. If you're under 30GB you don't need to worry about this.


      Databases are replicated across 3 zones (regions) for redundancy. One (1) on the east coast of the USA, One (1) in Frankfurt, and One (1) in Singapore. Depending on the demand, this would grow to more regions.


      Databases will also be backed up daily and retained for 7 days.




      Procon Layer will be $2 USD per month.


      Each layer will only allow one (1) game server connection. The reason behind this is for performance.


      Each layer will also come with all available plugins installed by default. This is to help facilitate faster deployments and get you up and running quickly.


      Each layer will automatically restart if Procon crashes. 


      Each layer will also automatically restart daily at midnight to make sure it stays in tip-top shape.


      Custom plugins can be installed by submitting a support ticket.




      Battlefield Admin Control Panel (BFACP) will be $5 USD per month


      As I am still working on building version 3 of the software, I will be installing the last version I did. Once I complete version 3 it will automatically be upgraded for you.





      All these services will be managed by me so you don't have to worry about the technical side of things to get up and going.

      If you would like to see how much it would cost for the services, I made a calculator that you can use. It can be found here https://ezrcon.com/calculator.html

       
      • 11 replies
      Prophet731

      Picked By

      Prophet731,

    • Procon Version 1.5.3.4 Released

      Prophet731 posted a topic in News,

      I have pushed out a new minor release which updates the geodata pull (flags in the playerlisting). This should be way more accurate now. As always, please let me know if any problems show up.

       
      • 9 replies
      Prophet731

      Picked By

      Prophet731,
    View All
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.