Page 741 of 744 FirstFirst ... 241641691731739740741742743 ... LastLast
Results 7,401 to 7,410 of 7437
  1. #7401
    Quote Originally Posted by ColColonCleaner View Post
    Those move loop messages are from AdKats fighting with your auto-balancer when you move a player with an admin command or they move themselves via !assist. Both plugins want the player to be on opposite teams so they fight over the player, but i made AdKats detect the loop and stop fighting. You can ignore those messages when they happen.

    As for the delayed ban, in section 13-2 turn off BF4 lenient kick. In BF4 for people joining through the in-game client they can't see ban messages, why they were banned, so by default it spams them with say/yell messages before kicking them out of the server. But turning off that leniency will make it immediately eject them.
    Okido CCC, thanks. Extreme coincidence this message was regarding the only player (of 35.000) with an active battlecry. I immediately assumed it had something to do with it. BF4 lenient kick was already set to false, normally a ban is immediate (it is now too), but in this case I issued the command three times (different reason texts) and even tried banning via procon before the first command was in effect (perma ban message was shown with first reason text). Weird. Would not expect the hack to have such an impact on either server or layer performance.

  2. #7402
    Quote Originally Posted by TonyOffermans View Post
    Okido CCC, thanks. Extreme coincidence this message was regarding the only player (of 35.000) with an active battlecry. I immediately assumed it had something to do with it. BF4 lenient kick was already set to false, normally a ban is immediate (it is now too), but in this case I issued the command three times (different reason texts) and even tried banning via procon before the first command was in effect (perma ban message was shown with first reason text). Weird. Would not expect the hack to have such an impact on either server or layer performance.
    Yeah, if procon itself wasn't able to kick them out properly then that's not something my plugin can handle either. We had a similar problem in BF3 where you were unable to kick players but that was from a glitch they abused with their player names where the name on the server side didn't match what was displayed in game so any name-driven commands you tried to issue against them would fail. On top of this they utilized a secondary glitch that let them connect to the server without a valid GUID so you couldn't ban them that way either. After those issues were patched though i haven't seen it, but there might be other newer hacks that have put in kick blocking.
    ____

  3. #7403
    Is there a safe way to delete a particular soldier's record out of the database ? we have one that never can display anything properly in the dashboard ( blade errors ) and can't see anything different anywhere ... so thought maybe we could just blast him as though he never visited.

  4. #7404
    Quote Originally Posted by sixpax12 View Post
    Is there a safe way to delete a particular soldier's record out of the database ? we have one that never can display anything properly in the dashboard ( blade errors ) and can't see anything different anywhere ... so thought maybe we could just blast him as though he never visited.
    Run these, in order, with their player id, and you should be good.

    delete from adkats_bans where player_id = ?
    delete from adkats_records_debug where source_id = ?
    delete from adkats_records_debug where target_id = ?
    delete from adkats_records_main where source_id = ?
    delete from adkats_records_main where target_id = ?
    delete from tbl_playerdata where playerid = ?
    ____

  5. #7405
    Senior Member
    Join Date
    Feb 2015
    Location
    netherlands
    Posts
    344
    ah, now this is more as use full !!!
    thnxs for the tip CCC !

  6. #7406
    Quote Originally Posted by ColColonCleaner View Post
    Run these, in order, with their player id, and you should be good.

    delete from adkats_bans where player_id = ?
    delete from adkats_records_debug where source_id = ?
    delete from adkats_records_debug where target_id = ?
    delete from adkats_records_main where source_id = ?
    delete from adkats_records_main where target_id = ?
    delete from tbl_playerdata where playerid = ?
    I completed the above with no issues shortly after you posted this. The offending player_id revisited a server a short time ago and somehow re-inherited the same player_id that was removed ?

  7. #7407
    Quote Originally Posted by sixpax12 View Post
    I completed the above with no issues shortly after you posted this. The offending player_id revisited a server a short time ago and somehow re-inherited the same player_id that was removed ?
    Perhaps cached in the BFACP somewhere? Not sure how that could happen otherwise. Unless you kept your procon layers running while you deleted the records so they were still there in your running instance. If you did that delete without shutting down AdKats first it probably just realized something weird happened and re-loaded the player into the database.
    ____

  8. #7408
    Community Contributor
    Join Date
    Nov 2011
    Posts
    3,069
    The recommendation to stop the AdKats plugin (or the layer altogether) before making the change makes sense. But even if you already did that (or do that in the future), I have noticed that SQL servers seem to have a memory and refill old rows when similar data reappears, instead of starting a new auto-incremented row. In my experience, after deleting a row, a user with the same information, unexpectedly repopulated an old deleted row, while new users properly populated new auto-incremented rows as expected. Old deleted rows should normaly remain a gap in auto-incremented numbering instead of being filled back in. But it seems that something to do with the index caching causes auto-incrementing to stop working properly when the same information is given to the database which matches an old user/data which used to occupy a deleted row. In my experience, to avoid the oddity of the SQL server repopulating an old deleted auto-incremented row, after deleting the row(s) in the respective table(s), run the SQL optimize table query. That seems to take care of that problem. Optimizing the tables seems to clear the index cache and causes it to auto-increment new rows instead of re-filling old rows. The Optimize table process is real easy inside phpMyAdmin. You don't even need to know the SQL command(s). Just check-mark all tables, click the "with selected:" dropdown, and click Optimize table.
    Last edited by ty_ger07; 25-04-2019 at 11:55.

  9. #7409
    Quote Originally Posted by ty_ger07 View Post
    The recommendation to stop the AdKats plugin (or the layer altogether) before making the change makes sense. But even if you already did that (or do that in the future), I have noticed that SQL servers seem to have a memory and refill old rows when similar data reappears, instead of starting a new auto-incremented row. In my experience, after deleting a row, a user with the same information, unexpectedly repopulated an old deleted row, while new users properly populated new auto-incremented rows as expected. Old deleted rows should normaly remain a gap in auto-incremented numbering instead of being filled back in. But it seems that something to do with the index caching causes auto-incrementing to stop working properly when the same information is given to the database which matches at old user/data which used to occupy a deleted row. In my experience, to avoid the oddity of the SQL server repopulating an old deleted auto-incremented row, after deleting the row(s) in the respective table(s), run the SQL optimize table query. That seems to take care of that problem. Optimizing the tables seems to clear the index buffer and causes it to auto-increment new rows instead of re-filling old rows. The Optimize table process is real easy inside phpMyAdmin. You don't even need to know the SQL command(s). Just check-mark all tables, click the "with selected:" dropdown, and click Optimize table.
    most awesome info, thanks !

  10. #7410
    hi
    in the console are constantly warnings
    [20:37:49 45] [AdKats] WARNING: Ahmed_AJ spawned without being in player list.
    [20:37:49 55] [AdKats] WARNING: nikhilxx18 spawned without being in player list.
    these warnings appear every second for different players.How to fix it?

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •