Skip to content

Latest commit

 

History

History
230 lines (230 loc) · 13.8 KB

CHANGELOG.md

File metadata and controls

230 lines (230 loc) · 13.8 KB

Development

Started by ColColonCleaner for A Different Kind (ADK) on Apr. 20, 2013

Changelog

0.0.1 (20-APR-2013)

Main:
* Initial Version

0.0.2 (25-APR-2013)

Changes
* Added plugin-side punishment.
* Initial DB test, tables updated.

0.0.3 (28-APR-2013)

Changes
* In-game commands no longer case sensitive.
* External DB test, tables updated.
* First in-game run during match, minor bugs fixed.

0.0.4 (29-APR-2013)

Changes
* Added editable in-game commands for forgive/punish.

0.0.5 (30-APR-2013)

Changes
* Removed global player access for production version.
* Added admin list for access.
* Added 'Low Server Pop' override system

0.0.6 (1-MAY-2013)

Changes
* Added access to database admin list.
* Fixed minor bugs during testing.

0.0.7 (1-MAY-2013)

Changes
* Added view definitions to display current player point values.

0.0.8 (2-MAY-2013)

Changes
* Updated player-say messages when punishment acted on. More informative message used.
* Added editable minimum reason length.

0.0.9 (3-MAY-2013)

Changes
* Added direct kill, kick, tban, and ban commands.
* Made direct commands work with database.
* Removed editable command list.

0.1.0 (5-MAY-2013)

Changes
* Refactor record creation to increase speed.
* Enumerate all database commands to parse in-game commands.
* Implement xTeamSwap functions within this plugin.
* Create database whitelist definitions for TeamSwap.
* Add move, fmove, moveme as commands that use TeamSwap.
* Refactor database logging to work with all commands.
* Code cleanup and organize.
* Player and admin messaging changes.

0.1.1 (6-MAY-2013)

Changes
* Punish and forgive commands changed to 'pun' and 'for', for ease of use in high punish/minute instances.
* Now a player may only be punished once every x minutes, this removes the case where two admins can punish a player for the same infraction.

0.1.2 (8-MAY-2013)

Changes
* Re-added editable command list.

0.1.3 (9-MAY-2013)

Changes
* Refactored settings and parsing to make the plugin more heavy while changing settings, but much lighter once in use.
* Added setting for whether a command will be logged or not. Adding '|log' to the end of a setting name will make the plugin log uses of that command in the database. Default is logging for all action commands (which should be fine for performance). Right now only Punish and Forgive are required to be logged.
* Fixed move command, now sends player to TeamSwap once they have died.

0.1.4 (10-MAY-2013)

Changes
* Fixed bugs in command logging interface and command setting initialization.

0.1.5 (12-MAY-2013)

Changes
* Cleaned up messaging. Small bug fixes.

0.1.6 (14-MAY-2013)

Changes
* Optimized calling of listPlayers to a maximum of only once every 5 seconds or on call from a move command.
* Fixed console spam at start of plugin.
* Added update of admin list/teamswap list if a player isn't on it and trying a command.
* Gave plugin control over table creation if not setup beforehand.

0.1.7 (15-MAY-2013)

Changes
* Reconfigured Database connection handling and connection testing to follow best practices seen elsewhere.
* Fixed bugs in the database structure confirmation and table setup sequence.
* All yell messages will now be changed to uppercase before sending.
* Added confirm action to all round targeted commands.

0.1.7.2 (16-MAY-2013)

Changes
* Console Errors displayed when players enter invalid settings made more descriptive.
* Added presay and preyell commands.

0.1.7.3 (17-MAY-2013)

Changes
* Made plugin description download github stored README and CHANGELOG instead of storing it plugin-side.

0.1.8.0 (18-MAY-2013)

Changes
* Improve the player name prediction system.

0.1.9.0 (19-MAY-2013)

Changes
* Add a report ID to reports, so admins can act on reports directly.
* Add a thank you for reporting when a report gets acted on.

0.1.9.1 (20-MAY-2013)

Changes
* Added banning admin name to all kick/ban logs.
* Fixed bug in logging when commands were given in uppercase.

0.1.9.2 (20-MAY-2013)

Changes
* Added player mute system.
* Added global adminsay when a player gets kicked or banned by an admin.

0.1.9.4 (20-MAY-2013)

Changes
* Added round-whitelisting for players.

0.1.9.9 (21-MAY-2013)

Changes
* Removed actionlist, made entire record table two-way accessible.
* Added report ID usage to all player interaction commands.
* Added display of current database admins and whitelisted players in plugin settings.
* Added pyell to dev for plugin information in certain cases.
* All action commands can be called via the database now.

0.2.0.0 (21-MAY-2013)

Changes
* Minor bug fixes for version 2 release.

0.2.5.0 (4-JUNE-2013)

Changes
  • Admin List GUI. You can now modify the database reflected admin list through AdKats settings. You can edit who the admins are, and what level of access they have, without needing to access the database manually. All instances of the plugin on your database will reflect the admins you enter.
  • Admins now have multiple levels of access. They range from full admin (0) to normal player (6). List of commands for each level is given below. Admins can issue commands at or below their level. All commands on an admin's access level can be used on other admins of any level with the exception of muting.
  • Commands now have levels of access. Admins need to be at or above certain levels of access to use certain commands.
  • HTTP Server Online. Commands can now be sent to AdKats using procon's internal HTTP server, or through the database. Info given below on security of this system.
  • Player name suggestion system improved. System now considers player names starting with what was typed more correct than those with it just somewhere in their name. System will also perform a "fuzzy" player-name search if the text admins entered is not valid for any players.
  • Ghost Commands Fixed. Commands admins send but don't confirm will be auto-canceled if they move on to other things. This stops unwanted commands from being acted on after the fact.
  • TeamSwap can now auto-whitelist X random players in the server each round. The random list is changed each round. Use this to generate hype for players to get full access to teamswap. Players are told the first time they spawn that they have access. Players who already have access are not added to the auto-whitelist.
  • Player report logging improved. Whether a report was used by an admin is now logged.
  • "Admin Assistant" position added. Players who consistently send useful player reports get a small bonus. Details below. This can be disabled.
  • Round Report Handling Improved. Handling changed so admins can enter new reasons that override the report reason. The new reason entered will be used instead, and must follow the requirements for a reason defined in settings.
  • Pre-defined messages usable in all commands. All player interaction commands (not say or yell), will accept preMessageIDs as input for reasons now. e.g. @kill charlietheunicorn 4 --> charlietheunicorn killed for Baseraping Enemy Spawn Area.
  • Server IDs can be different now, yet still have punishments increase across servers. Now the origin of reports wont show as coming from the same server, since same server ID was required before for global punishments.
  • Added new commands. Kick all Players, and Nuke Server.
  • Commands can now operate in shortened hidden mode. When commands are issued in hidden mode they normally require an extra character. e.g. /@kill target reason. They now work with just the slash. e.g. /kill target reason.
  • Commands will target the speaker when entered with no parameters. Most player interaction commands will now target the speaker when entered with no parameters. So "@kill" == "@kill SourcePlayerName Self-Inflicted". Report and call admin will not do this, in addition to commands meant for targeting multiple players.
  • Additional ban message option added. e.g. Optionally add "appeal at www.yoursite.com" to the end of bans.
  • 30 seconds now hardcoded as punishment timeout. Setting was only editable for testing purposes.
  • Optimizations in code, database, and settings handling.

0.2.5.1 (6-JUNE-2013)

Changes
  • Bug-fixes. Some documented bugs in the issues section (milestone 0.2.5.1) are fixed.
  • Punishment Enhancements. Punishment timout has been reduced to 20 seconds.
  • IRO Punishments Added. Immediate Repeat Offence. If a player gets punished more than once in a 5 minute time span, the subsequent punishes were be worth 2 infraction points instead of just 1.
  • Messaging Enhancements. Pre-say and pre-yell commands have been removed, and now the preMessage IDs can be used in regular say, yell, and any other commands that need a reason or message.
  • Pre-Message Enhancements. Use of pre-defined messages can be required now.

0.3.0.0 (13-JULY-2013)

Changes
  • Performance. All actions, parsing, and database communications take place on their own threads now, increasing performance greatly.
  • Setting Sync. All plugin settings are now stored in the database, specific to each procon instance. Usage shown in readme.
  • Dependencies. XPKiller's Stat logger is now REQUIRED for AdKats to function. It provides much useful information regarding both player and server statistics, which the new Ban Enforcer and AdKats itself use to improve your admin abilities.
  • AdKats WebAdmin API. A website from which you can manage all aspects of your server and playerbase. Direct control of players within the server, command feeds, all logs, ban management, and server statistics are all included in this site.
  • AdKats Ban Enforcer. Due to lacking functionality and/or bugs in other ban managers, an internal Ban Enforcer is now coded into AdKats. AdKats can now enforce bans accross all of your servers. The Ban Enforcer will import and consolidate all bans from every procon instance it's enabled on. Once enabled, bans made on one of your servers will be enforced on all others within seconds of issuing the ban. Bans can be made by name, GUID, IP, any combination, or all at once. The enforcer works with all existing auto-admins, and requires AdKats WebAdmin for ban management. You can use it without WebAdmin, but you will be unable to manage any bans, lift them early, or modify them in any way once submitted. Use of the ban enforcer is optional because of this dependency, and is disabled by default.
  • Punishment Enhancements. IRO punishments can now override the low population count and act normally.
  • Kick/Ban Messages Improved. Frostbite has a 80 character limit for ban/kick messages, and the new ban/kick messages comply with that. Also, all kick/ban messages are more descriptive than before, and ban messages in particular will tell the player how long their ban is.
  • Small bug-fixes and enhancements. Messages for errors, player information, and commands, are more informative to the users now. Small bugs fixed.
  • Debug Soldier Added. Set the debug soldier name in settings to get the speed of commands on your server sent to you in-game. Time is in milliseconds, from the time you entered it until all actions resulting from that command have finished.

0.3.0.1 (3-AUG-2013)

Changes
  • Bug-fixes. Documented bugs in the issues section (milestone 0.3.0.1) are fixed.
  • Added delayed kill. When a player dies and is then admin killed, kill will be performed when they spawn.
  • Ban-Sync process revamped. All ban enforcer sync methods have been reworked to be more reliable and efficient.
  • Admin list sorted by level then name. Simple visual fix.

0.3.0.2(6-SEP-2013)

Changes
  • Bug-fixes/Enhancements Documented bugs in the issues section (milestone 0.3.0.2) are fixed.
  • Teamswap Queues Removed Temporarily. Until the queuing problem can be fixed, queues for teamswap have been removed. All moves, force-moves, and self-moves will be called directly.
  • Import from BF3 Ban Manager Added. When AdKats Ban Enforcer is enabled, a check for BF3 Ban Manager tables is performed. All bans managed through BF3 Ban Manager will be automatically imported into AdKats.

0.3.0.3(8-SEP-2013)

Changes
  • Bug-fixes/Enhancements Small but extremely important bug fixed. Necessary for WebAdmin.