Jump to content

Advanced In-Game Admin and Ban Enforcer - AdKats


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

Originally Posted by jking54*:

 

Right... 150% > 130%, not seeing the issue here. I'm more worried about his 92% hsk with an automatic pistol.

C3, actually I entered his ban info wrong, it was actually this:

 

Hacking/Cheating DPS Automatic Ban [G18-29-51-47], which is 161%, a total legit ban by a mile.

 

How is the 92% obtained from this, I'm still unclear how to read this data?

 

Regarding my HSK setting which is at 40, I got this one:

 

Hacking/Cheating HSK Automatic Ban [AUGA3-47-147-70]

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

Originally Posted by ColColonCleaner*:

 

C3, actually I entered his ban info wrong, it was actually this:

 

Hacking/Cheating DPS Automatic Ban [G18-29-51-47], which is 161%, a total legit ban by a mile.

 

How is the 92% obtained from this, I'm still unclear how to read this data?

 

Regarding my HSK setting which is at 40, I got this one:

 

Hacking/Cheating HSK Automatic Ban [AUGA3-47-147-70]

weapon-dps-kills-headshots

weapon-hsk-kills-headshots

 

47/51 = 92% hsk.

 

DPS bans take priority over hsk bans, so they trigger first. The reason he has such a high dps is not actually because of a dmg mod, it's an aimbot. A lot of his shots are headshots so for those shots he gets the 200% damage boost the game already has. DPS bans take priority because they are the most conclusive.

 

And for your hsk ban, i would suggest removing it if they dispute, considering that's that player's "most hacked" weapon it's still possible with a fluke.

Link to comment

Originally Posted by Hutchew*:

 

Jab back at you.

 

It's already there. Did you update to the latest version here

I did now, and thanks for the ban button. But, JabJab, the reasons are not working...........JabJab..........

 

lol:cool:

* Restored post. It could be that the author is no longer active.
Link to comment
  • Administrators

Originally Posted by Prophet731*:

 

I did now, and thanks for the ban button. But, JabJab, the reasons are not working...........JabJab..........

 

lol:cool:

clear your local cache for it. simple force reload should do the trick.

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

Originally Posted by Hutchew*:

 

clear your local cache for it. simple force reload should do the trick.

Ok, reasons work from scoreboard now, but do not from player page (issue manual ban).

 

Also, if you mess around in the player popup from scoreboard, then try to go to "full info" it gives a 404 error.

 

Getting there, though. Thank you.

 

Hutchew

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

Originally Posted by ColColonCleaner*:

 

Ok, reasons work from scoreboard now, but do not from player page (issue manual ban).

 

Also, if you mess around in the player popup from scoreboard, then try to go to "full info" it gives a 404 error.

 

Getting there, though. Thank you.

 

Hutchew

Shhhh, no bugs, only dreams.
Link to comment

Originally Posted by jking54*:

 

weapon-dps-kills-headshots

weapon-hsk-kills-headshots

 

47/51 = 92% hsk.

 

DPS bans take priority over hsk bans, so they trigger first. The reason he has such a high dps is not actually because of a dmg mod, it's an aimbot. A lot of his shots are headshots so for those shots he gets the 200% damage boost the game already has. DPS bans take priority because they are the most conclusive.

 

And for your hsk ban, i would suggest removing it if they dispute, considering that's that player's "most hacked" weapon it's still possible with a fluke.

Thanks a bunch C3, this helps in my understanding now. If my setting had been the suggested 50 for HSK, he'd have beaten it by 3 with his headshots only less than half of his total kills, I've since removed his ban but he was skirting the fence as it were.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Ralphvd*:

 

No i do not have the Default In-Game Admin plugin running. (it worked like a charm before)

 

Hm i did remove my soldier. and added again. Now it say that im not allowed to use the command cause im a default guest. Hmm but procon says full admin. When i assigne a level to my soldier, ingame doesnt give any log.

 

Seems like something is bugging my soldier, database?

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

Originally Posted by ColColonCleaner*:

 

No i do not have the Default In-Game Admin plugin running. (it worked like a charm before)

 

Hm i did remove my soldier. and added again. Now it say that im not allowed to use the command cause im a default guest. Hmm but procon says full admin. When i assigne a level to my soldier, ingame doesnt give any log.

 

Seems like something is bugging my soldier, database?

"You do not have enough privileges to move players" Is a message from the default in-game admin, so yes you had it running.

 

This permission issue could be happening because you have a soldier in both BF3 and BF4, is that the case? If so, i already have a fix for this. Try using this beta version of AdKats, i've changed the user system interface slightly so it might show you what is going wrong: https://raw2.github.com/ColColonClea...test/AdKats.cs

 

Once this is running, try deleting your soldier then adding it again.

Link to comment

Originally Posted by Ralphvd*:

 

I am sure default in-game admin was disabled, but i enabled and disabled it again just to be sure.

 

With your beta version everything is working fine for now. Im glad it is working again!

BTW:

In procon log i got a error when i added my soldier to the useraccount.

[10:58:20 61] [AdKats] ERROR: Command was null in hasAccess.

[10:58:20 63] [AdKats] ERROR: Command was null in hasAccess.

[10:58:20 75] [AdKats] ERROR: Command was null in hasAccess.

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

Originally Posted by ColColonCleaner*:

 

I am sure default in-game admin was disabled, but i enabled and disabled it again just to be sure.

 

With your beta version everything is working fine for now. Im glad it is working again!

BTW:

In procon log i got a error when i added my soldier to the useraccount.

[10:58:20 61] [AdKats] ERROR: Command was null in hasAccess.

[10:58:20 63] [AdKats] ERROR: Command was null in hasAccess.

[10:58:20 75] [AdKats] ERROR: Command was null in hasAccess.

The beta version has a couple extra commands that need to be added to your database so those errors go away.
Link to comment
  • Plugin Developer

Originally Posted by ColColonCleaner*:

 

Did you add the reserved players table, since it's closed on github?

Knew you would be posting on this immediately :P

 

 

DROP TABLE IF EXISTS `adkats_specialplayers`;

CREATE TABLE IF NOT EXISTS `adkats_specialplayers`(

`specialplayer_id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,

`player_group` VARCHAR(30) NOT NULL,

`player_id` INT(10) DEFAULT NULL,

`player_game` TINYINT(4) UNSIGNED NOT NULL,

`player_server` SMALLINT(5) UNSIGNED DEFAULT NULL,

`player_identity` VARCHAR(30) DEFAULT NULL,

PRIMARY KEY (`specialplayer_id`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci COMMENT='AdKats - Special Player List';

 

 

ALTER TABLE `adkats_specialplayers`

ADD CONSTRAINT `adkats_specialplayers_game_id` FOREIGN KEY (`player_game`) REFERENCES `tbl_games`(`GameID`) ON UPDATE NO ACTION ON DELETE CASCADE,

ADD CONSTRAINT `adkats_specialplayers_server_id` FOREIGN KEY (`player_server`) REFERENCES `tbl_server`(`ServerID`) ON UPDATE NO ACTION ON DELETE CASCADE,

ADD CONSTRAINT `adkats_specialplayers_player_id` FOREIGN KEY (`player_id`) REFERENCES `tbl_playerdata`(`PlayerID`) ON UPDATE NO ACTION ON DELETE CASCADE;

 

 

Examples:

 

-- Will add player with id 3281 to reserved slots on all servers

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_id`)

VALUES

('slot_reserved', 3281);

 

 

-- Will add player with name ColColonCleaner to reserved slots on all servers

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_identifier`)

VALUES

('slot_reserved', 'ColColonCleaner');

 

 

-- Will add player with name ColColonCleaner to reserved slots on servers with game ID 1.

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_game`, `player_identifier`)

VALUES

('slot_reserved', 1, 'ColColonCleaner');

 

 

-- Will add player with name ColColonCleaner to reserved slots only on server 3.

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_server`, `player_identifier`)

VALUES

('slot_reserved', 3, 'ColColonCleaner');

 

Valid groups are currently slot_reserved, slot_spectator, whitelist_multibalancer, and whitelist_hackerchecker. If you use player IDs then you wont need to update player names if they change their names, the player names will automatically update the next time they join the server.

Link to comment

Originally Posted by TMiland*:

 

Knew you would be posting on this immediately :P

Lol! Yes, i have been patiently waiting for the update, i'm still on the old AdKats version, and it looks like i will be for a while more...

 

Thanks for the detailed explanation! :smile:

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

Originally Posted by ColColonCleaner*:

 

Lol! Yes, i have been patiently waiting for the update, i'm still on the old AdKats version, and it looks like i will be for a while more...

 

Thanks for the detailed explanation! :smile:

As long as you're happy with it and things are working properly, no real reason up update :smile:. The update process will just take longer when moving to 4.0 though :P
Link to comment

Originally Posted by TMiland*:

 

As long as you're happy with it and things are working properly, no real reason up update :smile:. The update process will just take longer when moving to 4.0 though :P

True! The only reason for updating i can think of is the double kill on !punish bug i have with this version.

 

Well, and i really want to keep up with the new functions ;D

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Ralphvd*:

 

Knew you would be posting on this immediately :P

 

 

DROP TABLE IF EXISTS `adkats_specialplayers`;

CREATE TABLE IF NOT EXISTS `adkats_specialplayers`(

`specialplayer_id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,

`player_group` VARCHAR(30) NOT NULL,

`player_id` INT(10) DEFAULT NULL,

`player_game` TINYINT(4) UNSIGNED NOT NULL,

`player_server` SMALLINT(5) UNSIGNED DEFAULT NULL,

`player_identity` VARCHAR(30) DEFAULT NULL,

PRIMARY KEY (`specialplayer_id`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci COMMENT='AdKats - Special Player List';

 

 

ALTER TABLE `adkats_specialplayers`

ADD CONSTRAINT `adkats_specialplayers_game_id` FOREIGN KEY (`player_game`) REFERENCES `tbl_games`(`GameID`) ON UPDATE NO ACTION ON DELETE CASCADE,

ADD CONSTRAINT `adkats_specialplayers_server_id` FOREIGN KEY (`player_server`) REFERENCES `tbl_server`(`ServerID`) ON UPDATE NO ACTION ON DELETE CASCADE,

ADD CONSTRAINT `adkats_specialplayers_player_id` FOREIGN KEY (`player_id`) REFERENCES `tbl_playerdata`(`PlayerID`) ON UPDATE NO ACTION ON DELETE CASCADE;

 

 

Examples:

 

-- Will add player with id 3281 to reserved slots on all servers

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_id`)

VALUES

('slot_reserved', 3281);

 

 

-- Will add player with name ColColonCleaner to reserved slots on all servers

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_identifier`)

VALUES

('slot_reserved', 'ColColonCleaner');

 

 

-- Will add player with name ColColonCleaner to reserved slots on servers with game ID 1.

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_game`, `player_identifier`)

VALUES

('slot_reserved', 1, 'ColColonCleaner');

 

 

-- Will add player with name ColColonCleaner to reserved slots only on server 3.

INSERT INTO

`adkats_specialplayers`

(`player_group`, `player_server`, `player_identifier`)

VALUES

('slot_reserved', 3, 'ColColonCleaner');

 

Valid groups are currently slot_reserved, slot_spectator, whitelist_multibalancer, and whitelist_hackerchecker. If you use player IDs then you wont need to update player names if they change their names, the player names will automatically update the next time they join the server.

Will you make a new .sql file for this with the update?
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by jking54*:

 

Right... 150% > 130%, not seeing the issue here. I'm more worried about his 92% hsk with an automatic pistol.

C3, can you say aimbot? A nice 185% winner :smile:

 

Hacking/Cheating DPS Automatic Ban [MP443-50-63-63]

 

got this one late last night...

 

lmao, golly :woot:

* Restored post. It could be that the author is no longer active.
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.

×
×
  • 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.