Advanced In-Game Admin and Ban Enforcer - AdKats

ImportBot · October 31, 2013

Originally Posted by Berndel*:

question

3.51.5 on bf4 and old ban list from bf3 will there work ?

server id. is 2 for bf4 server and ban enforcer enabled

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

question

3.51.5 on bf4 and old ban list from bf3 will there work ?

server id. is 2 for bf4 server and ban enforcer enabled

Ban enforcer will work for new players, not bf3 players.

ImportBot · October 31, 2013

Originally Posted by Berndel*:

so if i have only bf4 server the best is an new DB ?

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

so if i have only bf4 server the best is an new DB ?

Yes, for now do not run bf4 and bf3 on the same database/schema, just create a new schema for your bf4 servers. This is mainly because 1, records would be mixed between games, confusing matters. 2, ban enforcer would attempt to enforce bans across games which won't manager nicely. And 3, i don't know what xpkiller is going to modify in his plugin/database.

ImportBot · October 31, 2013

Originally Posted by Mavy*:

Just thought id say i have been using version 1.1.0.2 of xpkiller's plugin on BF4 without issues.

I only use it for the chat logging tho, so i am not aware of any issues with the rankings etc.

ImportBot · October 31, 2013

Originally Posted by Hutchew*:

Yes, for now do not run bf4 and bf3 on the same database/schema, just create a new schema for your bf4 servers. This is mainly because 1, records would be mixed between games, confusing matters. 2, ban enforcer would attempt to enforce bans across games which won't manager nicely. And 3, i don't know what xpkiller is going to modify in his plugin/database.

Too late, but not seeing any issues as of yet.

ImportBot · October 31, 2013

Originally Posted by Mavy*:

I had the following error this afternoon and could not connect to my layer anymore. A restart of the layer fixed it.

Code:

[12:41:50] [AdKats] EXCEPTION: [fetchPlayer][Error while fetching player.]: MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'EA_BC8BF0ACE364D0BC9FCE25EE8F33DFF2',
                                    ''
 ' at line 9
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.GetResult(Int32 statementId, Int32& affectedRows, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
   at PRoConEvents.AdKats.fetchPlayer(Int64 player_id, String player_name, String player_guid, String player_ip)
[12:41:50] [AdKats] EXCEPTION: [playerListingThreadLoop][Error occured in player listing thread.]: System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.AdKats.playerListingThreadLoop()

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Too late, but not seeing any issues as of yet.

Lol, there wont be errors, it might just lead to more work for you down the road

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

I had the following error this afternoon and could not connect to my layer anymore. A restart of the layer fixed it.

Code:

[12:41:50] [AdKats] EXCEPTION: [fetchPlayer][Error while fetching player.]: MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'EA_BC8BF0ACE364D0BC9FCE25EE8F33DFF2',
                                    ''
 ' at line 9
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.GetResult(Int32 statementId, Int32& affectedRows, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
   at PRoConEvents.AdKats.fetchPlayer(Int64 player_id, String player_name, String player_guid, String player_ip)
[12:41:50] [AdKats] EXCEPTION: [playerListingThreadLoop][Error occured in player listing thread.]: System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.AdKats.playerListingThreadLoop()

Strange, your player had an empty string for IP address instead of null, i'll add a catch for it. Thanks.

ImportBot · October 31, 2013

Originally Posted by Mavy*:

And another error, not sure if its a bug with the plugin or just a random issue with the server but posting just in case:

Code:

[13:53:19 05] Error: Error in Startstreaming: 
[13:53:19 05] Message: BIGINT UNSIGNED value is out of range in '(`procon`.`tbl_playerstats`.`Deaths` + -(1))'
[13:53:19 05] Native: -2147467259
[13:53:19 05] Source: MySql.Data
[13:53:19 05] StackTrace:    at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.GetResult(Int32 statementId, Int32& affectedRows, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
   at PRoConEvents.CChatGUIDStatsLoggerBF3.StartStreaming()
[13:53:20 47] Error: getUpdateServerID1: System.InvalidOperationException: Nested transactions are not supported.
   at MySql.Data.MySqlClient.ExceptionInterceptor.Throw(Exception exception)
   at MySql.Data.MySqlClient.MySqlConnection.Throw(Exception ex)
   at MySql.Data.MySqlClient.MySqlConnection.BeginTransaction(IsolationLevel iso)
   at MySql.Data.MySqlClient.MySqlConnection.BeginTransaction()
   at PRoConEvents.CChatGUIDStatsLoggerBF3.getUpdateServerID(CServerInfo csiServerInfo)
[13:53:20 66] Error: Error in Startstreaming OuterException: System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.CChatGUIDStatsLoggerBF3.DisplayMySqlErrorCollection(MySqlException myException)
   at PRoConEvents.CChatGUIDStatsLoggerBF3.StartStreaming()

PS: I am using xpkillers plugin that came with your latest stable release. So i am unsure where to post this.

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

And another error, not sure if its a bug with the plugin or just a random issue with the server but posting just in case:

Code:

[13:53:19 05] Error: Error in Startstreaming: 
[13:53:19 05] Message: BIGINT UNSIGNED value is out of range in '(`procon`.`tbl_playerstats`.`Deaths` + -(1))'
[13:53:19 05] Native: -2147467259
[13:53:19 05] Source: MySql.Data
[13:53:19 05] StackTrace:    at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.GetResult(Int32 statementId, Int32& affectedRows, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
   at PRoConEvents.CChatGUIDStatsLoggerBF3.StartStreaming()
[13:53:20 47] Error: getUpdateServerID1: System.InvalidOperationException: Nested transactions are not supported.
   at MySql.Data.MySqlClient.ExceptionInterceptor.Throw(Exception exception)
   at MySql.Data.MySqlClient.MySqlConnection.Throw(Exception ex)
   at MySql.Data.MySqlClient.MySqlConnection.BeginTransaction(IsolationLevel iso)
   at MySql.Data.MySqlClient.MySqlConnection.BeginTransaction()
   at PRoConEvents.CChatGUIDStatsLoggerBF3.getUpdateServerID(CServerInfo csiServerInfo)
[13:53:20 66] Error: Error in Startstreaming OuterException: System.NullReferenceException: Object reference not set to an instance of an object.
   at PRoConEvents.CChatGUIDStatsLoggerBF3.DisplayMySqlErrorCollection(MySqlException myException)
   at PRoConEvents.CChatGUIDStatsLoggerBF3.StartStreaming()

PS: I am using xpkillers plugin that came with your latest stable release. So i am unsure where to post this.

no no man, you can't use any version of his plugin on bf4 servers yet. You can use it to create the database tables but that's it, that plugin has NOT been moved to bf4 yet. Just disable the stat logger plugin on your bf4 layers and run 3.5.1.5 of AdKats. We need to wait on xpkiller for his bf4 version, until then, this is my workaround.

ImportBot · October 31, 2013

Originally Posted by Mavy*:

Ok disabled it and upgraded tot 3.5.1.5. The thing is that it was running fine since Tuesday using that version.

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Ok disabled it and upgraded tot 3.5.1.5. The thing is that it was running fine since Tuesday using that version.

It may have seemed to be running fine, mainly because there are a lot of similarities between the two games, but some specifics are different, specifics I don't know yet since it's not my code. One thing i do know though, is the weapon codes are completely different between games. There are only a few weapon codes that are the same, which i believe is the cause of your error.

Writing up a post for AdKats use with BF4 until new stat logger release, hang tight everyone...

ImportBot · October 31, 2013

Originally Posted by Mavy*:

It may have seemed to be running fine, mainly because there are a lot of similarities between the two games, but some specifics are different, specifics I don't know yet since it's not my code. One thing i do know though, is the weapon codes are completely different between games. There are only a few weapon codes that are the same, which i believe is the cause of your error.

Writing up a post for AdKats use with BF4 until new stat logger release, hang tight everyone...

Figured it must have been something like that. Forgot that i had turned on stats this morning as a test. Past few days i had it running chat log only. One small request for the workaround tho. Could you filter the ID_CHAT_* messages? They are a bit of a waste of DB space

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Figured it must have been something like that. Forgot that i had turned on stats this morning as a test. Past few days i had it running chat log only. One small request for the workaround tho. Could you filter the ID_CHAT_* messages? They are a bit of a waste of DB space

Yes, was thinking of doing this as well, they really don't hold particular meaning for us. I'll filter them out. 3.5.1.6 will have this.

Prophet731 · October 31, 2013

Originally Posted by Prophet731*:

Yes, was thinking of doing this as well, they really don't hold particular meaning for us. I'll filter them out. 3.5.1.6 will have this.

Don't worry about filtering it for now. I'm actually thinking of somehow we can use it.

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Don't worry about filtering it for now. I'm actually thinking of somehow we can use it.

Of course it can be used, I have ideas myself, but i'm filtering it now for database size, at least for the public.

Prophet731 · October 31, 2013

Originally Posted by Prophet731*:

Of course it can be used, I have ideas myself, but i'm filtering it now for database size, at least for the public.

Ok well don't filter it for our use at least. I'm already working it into the live scoreboard chat (see below).

Also, have you figured out how to determine who is a commander and spectator from the player list?

ab430a4d60c62ce957edca597dfad8bd.png

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Ok well don't filter it for our use at least. I'm already working it into the live scoreboard chat (see below).

Also, have you figured out how to determine who is a commander and spectator from the player list?

ab430a4d60c62ce957edca597dfad8bd.png

Right now it appears the only way to confirm commander is someone who gets points without spawning in. Spectators are still up in the air.

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

AdKats Usage with BF3:

Use the latest stable download released on sourceforge: https://sourceforge.net/projects/adkats/

Use stat logger version 1.1.0.2 as released with that version of AdKats.

AdKats Usage with BF4:

Firstly I would suggest using a separate schema/database for your BF4 layers, especially if you are planning to use the AdKats WebAdmin. The AdKats plugin is able to operate on the same database as your BF3 instances, but when stat logger gets updated for BF4, and WebAdmin gets updated for BF4 you will not be able to use those on the same database.

This short guide assumes you are creating a new schema/database for your BF4 instances. This guide is only valid until xpkiller's stat logger is released for BF4. Everything should return to normal operation after that version is released, and a new guide will be pushed out.

STEPS:

Create your new schema/database and get credentials for it with ability to add/remove tables.
Install the original or modded stat logger on each of your layers
Enter your credentials and start it on each layer (make no other setting changes), this will insert the stat logger tables in the database, and also insert your server IDs in the server table.
At this time, all of your server IDs should be in the server tables. Disable stat logger on every layer and do not enable it again until an official update is released by XpKiller.

Run this query on your database (just copy/paste in and run it):Code:

DROP TABLE `tbl_chatlog`; 
CREATE TABLE `tbl_chatlog` (
`ID` int(11) NOT NULL AUTO_INCREMENT,
`logDate` datetime NOT NULL,
`ServerID` smallint(5) unsigned NOT NULL,
`logSubset` text COLLATE utf8_unicode_ci,
`logPlayerID` int(10) unsigned DEFAULT NULL,
`logSoldierName` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
`logMessage` text COLLATE utf8_unicode_ci,
PRIMARY KEY (`ID`),
KEY `ServerID` (`ServerID`),
KEY `PlayerID` (`logPlayerID`),
CONSTRAINT `tbl_chatlog_ibfk_1` FOREIGN KEY (`ServerID`) REFERENCES `tbl_server` (`ServerID`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `tbl_chatlog_ibfk_2` FOREIGN KEY (`logPlayerID`) REFERENCES `tbl_playerdata` (`PlayerID`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=565 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

Run the AdKats setup script on your database (Just copy/paste in and run it): https://raw.github.com/ColColonClean...ter/adkats.sql
Install the beta version of AdKats (3.5.1.5+) from the test branch: https://raw.github.com/ColColonClean...test/AdKats.cs
Enter the same DB credentials into AdKats and start it. All should function normally.

This will be much more automated once the official version of stat logger comes out. But for now, this is what we have to work with. AdKats will log chat (with player IDs now) and player data in the stat logger tables, live.

ColColonCleaner · October 31, 2013

Originally Posted by ColColonCleaner*:

Colon have them run this SQL instead. Update your post and once you do i'll edit my post here.

Nope, this is all temporary. I don't insert server ID in the server table, stat logger needs to be run on each server. I will write a script to import any data they acquire into xpkiller's real version once it's released, this is all a temporary patch for things to work until he posts.

ImportBot · October 31, 2013

Originally Posted by jking54*:

Boy this thread just blew up in the last few days, I'm still on 3.5.1.3...

ColColonCleaner · November 1, 2013

Originally Posted by ColColonCleaner*:

Boy this thread just blew up in the last few days, I'm still on 3.5.1.3...

Make sure you follow the steps listed or 3.5.1.5+ will not function properly.

ImportBot · November 1, 2013

Originally Posted by jking54*:

Make sure you follow the steps listed or 3.5.1.5+ will not function properly.

I missed it, where to d/l 3.5.1.5?

ColColonCleaner · November 1, 2013

Originally Posted by ColColonCleaner*:

I missed it, where to d/l 3.5.1.5?

Link to the steps is in the first post of this thread, just replying saying this so other people will go there too

ImportBot · November 1, 2013

Originally Posted by jking54*:

Link to the steps is in the first post of this thread, just replying saying this so other people will go there too

All I see is 3.5.0.1, no 3.5.1.5

ImportBot · November 1, 2013

Originally Posted by Mavy*:

I just realized that the webadmin uses the tbl_server for used slots. Any chance of adding that to the work around?

ImportBot · November 3, 2013

Originally Posted by TMiland*:

"Auto-Whitelisting"

https://github.com/ColColonCleaner/AdKats#teamswap

How would i set this to allow for the players in reserved slots to use the @moveme command?

ImportBot · November 4, 2013

Originally Posted by jking54*:

I get an error when I run that script on a fresh db in the first post, ideas?

Prophet731 · November 4, 2013

Originally Posted by Prophet731*:

I get an error when I run that script on a fresh db in the first post, ideas?

What's the error?

Sign In

Advanced In-Game Admin and Ban Enforcer - AdKats

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Prophet731

maddog

Hedius

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation

Important Information