Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


TonyOffermans last won the day on May 26

TonyOffermans had the most liked content!

About TonyOffermans

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

185 profile views
  1. Still crashes on a daily basis. I am trying to run my layer with procon.console.exe now, it gives much better response in my client. But still it decides to just give up on me every now and then. Resource consumption is fairly stable and low. It does produce these messages every few seconds though: How to get rid of those messages? What is it that causes them? Are they just the commands sent by procon I can see in my console log? And is there any option to debug the crashes or better still, to try and prevent them? Thanks for your advice!
  2. Forgot to mention I am running Procon and InnoDB 10.3.16
  3. Hi, I run my own layer on a VM (3 cores, 8GB) and my SQL database is also running on this VM. I also have Ty_ger07's stats page running on another machine. I have some issues with this setup. A few times a day (although some days it runs fine), Procon will crash or start looping. On the VM I find it 'No Longer Works' or it is unresponsive using 98% CPU. It is fine after restart. I also see HD activity spiking 100% for prolonged periods but unable to find the process responsible (I suspect XAMPP MySQL but it does not show in task manager). Nothing else is running on the VM. I am looking for options to debug the crashes. Any advice? Is it better to run the MySQL on a different server? Any experiences with the stats page being attacked causing MySQL to refuse connections (I had this yesterday, my plugins got disabled and were unable to connect (MySqlException (0x80004005): Host '' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts') ? I have no clue how this situation could arise... My hat off for your thoughts, thank you.
  4. Yes this would be the solution but as posted before, it is not accepted in this version. I fixed it by adding a trigger: delimiter | create trigger fix_datetime before insert on tbl_playerdata for each row begin SET NEW.created_at = NOW(); end | DELIMITER ; Far from ideal but it works. Table is updated properly on creating new playerID's Thanks all for your fine support!!
  5. Well, still problems... When I checked the data, it appears all new players have a created_at value of 0000-00-00 00:00:00. I could not set a default value for the datatype as it is not accepted prior MySQL 5.6. Of course I can set it on the old SQL server (which has 5.6.5) but I will run into the same problems again. Not sure why, but these are the only TIMESTAMP expressions in the DB (all others are DATETIME) so it must be for some reason.... Any suggestions?
  6. I just changed this into `created_at` datetime NOT NULL and the table was defined properly and I got all my data restored. Btw I also had to remove a lot of DEFINER= statements from the dump because my credentials were different on the new SQL server. (I used the cygwin sed utility to do it in one pass: huge dump file). And update the tbl_server to reflect my new IP address and keep all the stats from the existing serverID. That's basically what was needed. Thanks for the support!
  7. Anyone able to help me with this? I am moving my DB contents to another provider. I created a self-extracting dump file that contains the entire structure and data. I used this procedure before against the original tables. But when I try to restore my dump into the new schema it throws an error when creating the tbl_playerdata: ERROR 1293 (HY000) at line 1282: Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Version used for the dump: MySQL dump 10.16 Distrib 10.1.41-MariaDB, for debian-linux-gnu (x86_64) My new provider has MySQL 5.5.60-MariaDB. I am reading the TIMESTAMP limitation has been lifted in MySQL 5.6 Is there a workaround feasible? Like using DATETIME NOW() instead of the first TIMESTAMP? Should I ask my provider to update to a more recent version? Or am I doomed? When I start AdKats regardless, it tries to ADD the columns but only succeeds in adding the 'created at' and produces a lot of errors for non-existent admin users... This is the generated script from the dump: -- -- Table structure for table `tbl_playerdata` -- DROP TABLE IF EXISTS `tbl_playerdata`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `tbl_playerdata` ( `PlayerID` int(10) unsigned NOT NULL AUTO_INCREMENT, `GameID` tinyint(4) unsigned NOT NULL DEFAULT '0', `ClanTag` varchar(10) DEFAULT NULL, `SoldierName` varchar(45) DEFAULT NULL, `GlobalRank` smallint(5) unsigned NOT NULL DEFAULT '0', `PBGUID` varchar(32) DEFAULT NULL, `EAGUID` varchar(35) DEFAULT NULL, `IP_Address` varchar(15) DEFAULT NULL, `DiscordID` varchar(50) DEFAULT NULL, `IPv6_Address` varbinary(16) DEFAULT NULL, `CountryCode` varchar(2) DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`PlayerID`), UNIQUE KEY `UNIQUE_playerdata` (`GameID`,`EAGUID`), KEY `INDEX_SoldierName` (`SoldierName`), KEY `created_at` (`created_at`), KEY `updated_at` (`updated_at`) ) ENGINE=InnoDB AUTO_INCREMENT=110949 DEFAULT CHARSET=latin1; /*!40101 SET character_set_client = @saved_cs_client */; ...
  8. I've decided to let the plugin kill players on spawn when using gunner soflam. It is just too disruptive on the map I always run. It works fine, but sometimes a player can still use it (which is not fair, of course). Trying to figure out how and spectating them, I noticed sometimes they are bugged and their loadouts are not showing. But sometimes they are showing. I have enabled backup autoadmin but I doubt it will be able to detect this item (it does not trigger events like killing with a weapon). Any suggestion how to debug/improve?
  9. Neat!!!! Still I cannot find which setting you are referring to, nor the documentation section that describes it. Can you give me one more clue? Thanks!
  10. @CCC: I use the e-mail report function. I get a nice overview of the case with some chatlog and links to websites no longer in service: BF4 Battlelog Profile (which is fine) BF4Stats Profile AntiCheat, INC. Search Metabans Search I changed the adkats.cs to contain the following: CustomHTMLAddition = @"<br><a href='http://battlelog.battlefield.com/bf4/de/user/%player_name%/'>BF4 Battlelog Profile</a><br> <br><a href='https://battlefield.agency/?search=%player_name%'>Battlefield Agency profile</a><br> <br><a href='http://bf4cheatreport.com/?pid=&uid=%player_name%&cnt=&startdate='>BF4 Cheatreport</a><br> <br><a href='https://www.247fairplay.com/CheatDetector/%player_name%'>247Fairplay Profile</a><br>" I have overwritten the old links, nowhere can I find any string BF4Stats anymore. I know I am running the changed plugin because I also put an eyecatcher in the details tab. YET I still receive an e-mail with the obsolete links! I must be overlooking something... Can you help out, or maybe even adopt my URL's? Thank you!
  11. RTFM did help. I wanted to use a server-wide variable and it must be coded %server_knifekills%...
  12. Try something like: On Kill; Map Guilin; Mapmode Deathmatch; Weapon Claymore; Say %p% no Claymore allowed here; Kill (not tested this, see documentation if conditions are not correct) If you want to PREVENT usage of claymore's altogether I suggest to take a look at the loadout enforcer: https://github.com/AdKats/AdKats-LRT
  13. Hey! Sorry to wake you up, man. I was trying to update the Proconrulz topic in Plugin subforum and it clearly has this same bar 'Post a reply to this topic...' now... My bad.
  14. Hey! I like the new look of the forum! However, I can't seem to find a way to update a topic? Obviously starting a new one is easier.
  15. You DID configure 'Chat, GUID, Stats and Mapstats Logger' plugin and let it run for at least a complete round, didn't you? It should create all the necessary tables for Adkats to do its magic. AdKats can not succesfully initialize without the logger being ran first.
  • 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.