Online Members
None
Online Guests: 8
TeamSpeak 3 Status
Your Next Award

Please login.

New InGame Admin System (plus more)!
Forum » Battlefield Hardline » General Discussion
Joined: 7th Sep 2013
Rank: First Knight
Likes 95
7th Jan 2014

So I upgraded our admin systems.  We were having trouble with some of the basic commands working for our admins plus we needed a way to assign more roles.  Well I spent some time today upgraded it.  Our new systems is quite extensive.  It uses a database to track everything that goes on, it has a punish/forgive points system so we can track troublesome players, it has roles that I can customize and assign (I made Full Admin, Officers, Assisstants, and VIP so far), it has a report player and Call Admin function and all sorts of goodies.  Here is what it can do.

Admin Toolset with a plethora of features, basically the default "In-Game Admin" with 1500+ hours of enhancements and features added. AdKats focuses on making in-game admins more efficient and accurate at their jobs, with flexibility for almost any setup. Includes a cross-server ban enforcer more reliable and complete than others available, and the AdKats WebAdmin for out-of-game control has been released. Designed for groups with high-traffic servers and many admins, but will function just as well for small servers

  • Basic Action Commands. Standard commands for player killing, kicking, punishing, banning, unbanning, moving, etc...Over 30 available in-game commands. Commands can be accessed from almost anywhere: In-game, Procon's chat window, database, HTTP server, other plugins, etc, etc...
  • Editable Ranks and Roles. Custom ranks and roles can be created for users, with each role given access to only the commands you want them to access. Default guest role is given to all players, and can be edited to your desired specs. All roles and powers are automatically synced between servers, so you only need to change user information once. Soldiers assigned to users will also keep their powers even if they change their in-game names.
  • Admin and setting sync between servers. All changes to plugin settings are stored in the database, and can be automatically synced between your Procon layers.
  • Infraction Tracking System. Punish/Forgive players for infractions against your server. Everything is tracked, so the more infractions they commit, the worse their punishment gets. Made so all players are treated equally. Heavily customizable.
  • Quick Player Report and Admin Call Handling, with email support. Notification system and quick handling features for all admin calls and player reports. Reports can be referenced by number for instant action.
  • Orchestration and Server List Management. Server reserved slots, server spectator slots, and autobalancer whitelising through MULTIBalancer can all be automatically done through the AdKats user list.
  • Admin Assistants. You can choose to give a small perk to players who consistently provide you with accurate player reports. Documentation linked below.
  • BF3/BF4 "Hacker-Checker" with Whitelist. BF3Stats and BF4Stats are internally used to pull player information, and can be enabled for hacker-checking with a couple clicks. Please read documentation before enabling.
  • Email Notification System. Email addresses can be added to every user, and once enabled they will be sent emails for player reports and admin calls. I am currently working on adding command parsing on reply to emails, and possibly text message command support in the future.
  • Fuzzy Player Name Completion. Fully completes partial or misspelled player names. I've been consistently able to find almost any player with 3-4 characters from their name.
  • Player Muting. Players can be muted if necessary.
  • Player Joining. Player's squads can be joined via command, and locked squads can be unlocked for admin entry.
  • Yell/Say Pre-Recording. Use numbers to reference predefined messages. Avoid typing long reasons or messages. e.g. @kill player 3
  • Server rule printing. Just like "Server rules on request" except multiple prefixes can be used for rule commands at the same time, and requests for rules are logged.
  • External Controller API. AdKats can be controlled from outside the game through systems like AdKats WebAdmin, and soon through other plugins like Insane Limits.
  • Internal Implementation of TeamSwap. Queued move system for servers that are consistently full, players can be queued to move to full teams once a slot opens. Greatly improved over the default version. Documentation linked below.
  • AdKats Ban Enforcer. AdKats can enforce bans across all of your servers, and can enforce on all metrics at the same time. The internal system has been built to be more complete and reliable than others available, including metabans, and is further enhanced by using AdKats WebAdmin. It will automatically import all Procon bans from all your servers and consolidate them. It will also import any existing bans from the BF3 Ban Manager plugin's tables. Full documentation linked below.
  • Editable In-Game Commands. All command text, logging options, and enable options can be edited to suit your needs.
  • Full Logging. All admin activity is trackable via the database per your custom settings for every command; So holding your admins accountable for their actions is quick and painless. And, if you are using AdKats WebAdmin nobody but your highest admins will need direct Procon access.
  • Performance. All actions, messaging, database communications, and command parsing take place on their own threads, minimizing performance impacts.
[size]

You can download an HTML printout of all in game commands (guests, assisstants, officers, and even full admin) here ...

http://www.blackknightsclan.com/downloads


Last Edit: 7th Jan 2014 by T-Bird
Joined: 7th Sep 2013
Rank: First Knight
Likes 95
7th Jan 2014

Here are the in game commands.  I suggest you save this and maybe print it out ...

[html]<a name="available-in-game-commands" class="anchor" href="#available-in-game-commands"><span class="octicon octicon-

link"></span></a>Available In-Game Commands</h3>

<p>
<b>You can edit the text for each command to suit your needs in plugin settings.</b>
</p>

<p>
Commands can be accessed with '@', '!', '/!', '/@', or just '/'.
</p>

<p>
Any action command given with no parameters (e.g. '@kill&#39 will target the speaker. If admins want to kill, kick, or
even ban themselves, simply type the command without any parameters.
Any action command when given a player name (other than moving players) will require a reason.
</p>

<table>
<tr>
<td><b>Command</b></td>
<td><b>Default Text</b></td>
<td><b>Params</b></td>
<td><b>Description</b></td>
</tr>
<tr>
<td><b>Kill Player</b></td>
<td>kill</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>The in-game command used for killing players.</td>
</tr>
<tr>
<td><b>Kick Player</b></td>
<td>kick</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>The in-game command used for kicking players.</td>
</tr>
<tr>
<td><b>Temp-Ban Player</b></td>
<td>tban</td>
<td>
<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>
The in-game command used for temp-banning players.
Default time is in minutes, but the number can have a letter after it designating the units. e.g. 2h for 2 hours. Valid

suffixes are m, h, d, w, and y.
</td>
</tr>
<tr>
<td><b>Perma-Ban Player</b></td>
<td>ban</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>The in-game command used for perma-banning players.</td>
</tr>
<tr>
<td><b>Unban Player</b></td>
<td>unban</td>
<td>
[player]
</td>
<td>
The in-game command used for unbanning players. Only usable when ban enforcer is enabled.
</td>
</tr>
<tr>
<td><b>Punish Player</b></td>
<td>punish</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>
The in-game command used for punishing players.
Will add a Punish record to the database, increasing a player's total points by 1.
</td>
</tr>
<tr>
<td><b>Forgive Player</b></td>
<td>forgive</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>
The in-game command used for forgiving players.
Will add a Forgive record to the database, decreasing a player's total points by 1.
</td>
</tr>
<tr>
<td><b>Mute Player</b></td>
<td>mute</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>
The in-game command used for muting players.
Players will be muted till the end of the round, X kills then kick if they keep talking.
Admins cannot be muted.
</td>
</tr>
<tr>
<td><b>Move Player</b></td>
<td>move</td>
<td>
None<br>
OR<br>
[player]<br>
OR<br>
[reportID]
</td>
<td>
The in-game command used for moving players between teams.
Will add players to the "on-death" move list, when they die they will be sent to TeamSwap.
</td>
</tr>
<tr>
<td><b>Force-Move Player</b></td>
<td>fmove</td>
<td>
None<br>
OR<br>
[player]<br>
OR<br>
[reportID]
</td>
<td>
The in-game command used for force-moving players between teams.
Will immediately send the given player to TeamSwap.
</td>
</tr>
<tr>
<td><b>Join Player</b></td>
<td>join</td>
<td>
[player]<br>
OR<br>
[reportID]
</td>
<td>
The in-game command used for joining player's squads.
Will immediately send the speaker to the target if possible, within access limitations.
</td>
</tr>
<tr>
<td><b>TeamSwap Self</b></td>
<td>moveme</td>
<td>None</td>
<td>
The in-game command used for moving yourself between teams.
Will immediately send the speaker to TeamSwap.
</td>
</tr>
<tr>
<td><b>Round Whitelist Player</b></td>
<td>roundwhitelist</td>
<td>
None<br>
OR<br>
[player][reason]<br>
OR<br>
[reportID]<br>
OR<br>
[reportID][reason]
</td>
<td>
The in-game command used for round-whitelisting players.
2 players may be whitelisted per round.
Once whitelisted they can use TeamSwap.
</td>
</tr>
<tr>
<td><b>Report Player</b></td>
<td>report</td>
<td>[player][reason]</td>
<td>
The in-game command used for reporting players.
Must have a reason, and will inform a player otherwise when used incorrectly.
Will log a Report in the database (External GCP pulls from there for external admin notifications), and notify all in-

game admins.
Informs the reporter and admins of the report ID, which the punish system can use.
</td>
</tr>
<tr>
<td><b>Call Admin</b></td>
<td>admin</td>
<td>[player][reason]</td>
<td>
The in-game command used for calling admin attention to a player.
Same deal as report, but used for a different reason.
Informs the reporter and admins of the report ID, which the punish system can use.
</td>
</tr>
<tr>
<td><b>Admin Say</b></td>
<td>say</td>
<td>
[message]<br>
OR<br>
[preMessageID]
</td>
<td>
The in-game command used to send a message through admin chat to the whole server.
</td>
</tr>
<tr>
<td><b>Player Say</b></td>
<td>psay</td>
<td>
[player][message]<br>
OR<br>
[player][preMessageID]
</td>
<td>
The in-game command used for sending a message through admin chat to only a specific player.
</td>
</tr>
<tr>
<td><b>Admin Yell</b></td>
<td>yell</td>
<td>
[message]<br>
OR<br>
[preMessageID]
</td>
<td>
The in-game command used for to send a message through admin yell to the whole server.
</td>
</tr>
<tr>
<td><b>Player Yell</b></td>
<td>pyell</td>
<td>
[player][message]<br>
OR<br>
[player][preMessageID]
</td>
<td>
The in-game command used for sending a message through admin yell to only a specific player.
</td>
</tr>
<tr>
<td><b>Admin Tell</b></td>
<td>tell</td>
<td>
[message]<br>
OR<br>
[preMessageID]
</td>
<td>
The in-game command used for to send a message through both admin say and admin yell to the whole server.
</td>
</tr>
<tr>
<td><b>Player Tell</b></td>
<td>ptell</td>
<td>
[player][message]<br>
OR<br>
[player][preMessageID]
</td>
<td>
The in-game command used for sending a message through both admin say and admin yell to only a specific player.
</td>
</tr>
<tr>
<td><b>What Is</b></td>
<td>whatis</td>
<td>[preMessageID]</td>
<td>
The in-game command used for finding out what a particular preMessage ID links to.
</td>
</tr>
<tr>
<td><b>VOIP</b></td>
<td>voip</td>
<td>None</td>
<td>
The in-game command used for sending VOIP server info to the speaker.
</td>
</tr>
<tr>
<td><b>Kill Self</b></td>
<td>killme</td>
<td>None</td>
<td>
The in-game command used for killing the speaker.
</td>
</tr>
<tr>
<td><b>Restart Level</b></td>
<td>restart</td>
<td>None</td>
<td>
The in-game command used for restarting the round.
</td>
</tr>
<tr>
<td><b>Run Next Level</b></td>
<td>nextlevel</td>
<td>None</td>
<td>
The in-game command used for running the next map in current rotation, but keep all points and KDRs from this round.
</td>
</tr>
<tr>
<td><b>End Round</b></td>
<td>endround</td>
<td>[US/RU]</td>
<td>
The in-game command used for ending the current round with a winning team. Either US or RU.
</td>
</tr>
<tr>
<td><b>Nuke Server</b></td>
<td>nuke</td>
<td>[US/RU/ALL]</td>
<td>
The in-game command used for killing all players on a team. US, RU, or ALL will work.
</td>
</tr>
<tr>
<td><b>Kick All Players</b></td>
<td>kickall</td>
<td>[none]</td>
<td>
The in-game command used for kicking all players except admins.
</td>
</tr>
<tr>
<td><b>Confirm Command</b></td>
<td>yes</td>
<td>None</td>
<td>
The in-game command used for confirming other commands when needed.
</td>
</tr>
<tr>
<td><b>Cancel Command</b></td>
<td>no</td>
<td>None</td>
<td>
The in-game command used to cancel other commands when needed.
</td>
</tr>
</table><h3>
[/html]


Joined: 7th Sep 2013
Rank: First Knight
Likes 95
7th Jan 2014

And now for the extensive list of features ...

Features
Infraction Tracking System
Infraction Tracking commands take the load off admins remembering which players have broken server rules, and how many times. These commands have been dubbed "punish" and "forgive". Each time a player is punished a log is made in the database; The more punishes they get, the more severe the action gets. Available punishments include: kill, kick, temp-ban 60 minutes, temp-ban 1 day, temp-ban 1 week, temp-ban 2 weeks, temp-ban 1 month, and permaban. The order and severity of punishments can be configured to your needs.
Detailed Stuff: After a player is punished, their total points are calculated using this very basic formula:(Punishment Points - Forgiveness Points) = Total Points Then an action is decided using Total Points from the punishment hierarchy. Punishments should get harsher as the player gets more points. A player cannot be punished more than once every 20 seconds; this prevents multiple admins from accidentally punishing a player multiple times for the same infraction.
IRO Punishments
When a player is punished, and has already been punished in the past 10 minutes, the new punish counts for 2 points instead of 1 since the player is immediately breaking server rules again. A punish worth 2 points is called an "IRO" punish by the plugin, standing for Immediate Repeat Offence. "[IRO]" will be appended to the punish reason when this type of punish is activated.
Punishment Hierarchy
The punishment hierarchy is configurable to suit your needs, but the default is below.

Total Points Punishment Outcome Hierarchy String
Less than 1 Kill kill
1 Kill kill
2 Kill kill
3 Kick kick
4 Temp-Ban 1 hour tban60
4 Temp-Ban 2 hours tban120
5 Temp-Ban 1 Day tbanday
6 Temp-Ban 1 Week tbanweek
7 Temp-Ban 2 Weeks tban2weeks
8 Temp-Ban 1 Month tbanmonth
9 Perma-Ban ban
Greater Than 9 Perma-Ban

Players may also be 'forgiven', which will reduce their Total Points value by 1 each time, this is useful if you have a website where players can apologize for their actions in-game. Players can be forgiven into negative total point values which is why a 'less than 1' clause is needed.
You can run multiple servers with this plugin on the same database; A different ID is automatically assigned to each server. If you want punishments to increase on this server when infractions are committed on others set "Combine Server Punishments" to true. Rule breaking on another server won't cause increase in punishments on the current server if "Combine Server Punishments" is false. This is available since many groups run different rule sets on each server they own, so players breaking rules on one server may not know rules on another, so they get a clean slate.
Suggestions: When deciding to use this system, 'punish' should be the only command used for player rule-breaking. Other commands like kill, or kick are not counted in the system since sometimes players ask to be killed, admins kill/kick themselves, or players get kicked for AFKing. Kill and kick should only be used for server management. Direct tban and ban are of course still available for hacking/glitching situations, but that is the ONLY time they should be used.

Ban Enforcer
AdKats can now enforce bans accross all of your servers within seconds of the ban being issued. The Ban Enforcer will import and consolidate all bans from every Procon instance you run. Bans can be made by name, GUID, IP, any combination, or all at once. The default ban is by EA GUID only, this default can be edited but is not recommended. Banned players are told how long their ban will last, and when a banned player attempts to re-join they are told the remaining time on their ban. Using ban enforcer also gives access to the @unban in-game command.
The Enforcer works properly with all existing auto-admins, and any bans added manually through Procon will be automatically imported by the system. A mini-ban-management section is added to the plugin settings when you enable this, however, for full ban management it requires AdKats WebAdmin. Ban enforcer's options are simply too much for the plugin setting interface to house properly. Use of the ban enforcer is optional because of this slight dependency, and is disabled by default.
Ban Enforcer can be enabled with the "Use Ban Enforcer" setting. On enable it will import all bans from your ban list then clear it. Once you enable enforcer you will be unable to manage any bans from Procon's banlist tab. Disabling ban enforcer will repopulate Procon's banlist with the imported bans, but you will lose any additional information ban enforcer was able to gather about the banned players.
Reasoning behind creation, for those interested: We had tried many other ban management systems and they all appeared to have some significant downfalls. Developing this allowed for some nice features not previously available. I can bypass Procon's banlist completely, this way no data is lost on how/why/who created the ban or on who it's targeted. I can enforce bans by any parameter combination (Name, GUID, IP), not just one at a time. Players can now be told how much time is left on their ban dynamically, every time they attempt to join. And tracking of bans added through in-game commands or autoadmins on any server is a cakewalk now, so clan leaders don't need to go great lengths to look things up. Several other reasons as well, but overall it was a fantastic move, and thankfully we had the devs available to make it. .

Report/CallAdmin System w/Email Support
When a player puts in a proper @report or @admin all in-game admins are notified. All reports are logged in the database with full player names for reporter/target, and the full reason for reporting. All uses of @report and @admin with this plugin require players to enter a reason, and will tell them if they haven't entered one. It will not send the report to admins unless reports are complete, which cleans up what admins end up seeing for reports.
Using Report IDs
All reports and calls are issued a random three digit ID which expires either at the end of each round, or when it is used. These ID's can be used in any other action command, simply use that ID instead of a player-name and reason (e.g. waffleman73 baserapes, another player reports them and gets report ID 582, admins just use @punish 582 instead of @punish waffleman73 baserape). Confirmation of command with @yes is required before a report ID is acted on. Players are thanked for reporting when an admin uses their report ID.



Last Edit: 7th Jan 2014 by T-Bird
Joined: 7th Sep 2013
Rank: First Knight
Likes 95
26th Jan 2014

bump


Joined: 6th Nov 2013
Rank: Knight of the Rose
Likes 11
26th Jan 2014

pretty
Forum » Battlefield Hardline » General Discussion
Please login or register to reply.
Donate

Donate

Recent Donations
Benny79
$100.00 USD
12th Dec 2014
BK Evanescence
$160.00 USD
7th Dec 2014
Chat Box
Events
« Jun 2017 »
M
T
W
T
F
S
S
 
 
 
1
2
3
4
5
6
7
8
9
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
 
Birthdays
BK SISU Yooper
37 years old 25th Jul
Most Liked Members
TeeRekts
1 Likes

Lukeyson
1 Likes