[thetwistedpanda]

Information:

• The punishment commands provided by BaseComm (sm_mute, sm_gag, and sm_silence) currently only allow you to punish players temporarily. These punishments expire as soon as the player disconnects, allowing them to reconnect and continue griefing.
• ExtendedComm corrects that behavior by providing the ability to save temporary punishments as well as create punishments for designated amounts of time all the while providing access to them across multiple servers.

Features:

• Provides a straightforward category in the sm_admin menu where administrators can punish players as well as view current comm punishments.
  • The original BaseComm menu option still exist, and will still function, due to my inability to remove them. If this is an issue for you, you'll have to recompile basecomm.sp commenting out the offending lines.
  • The category provides options for issuing new punishments, viewing current punishments (categorized based on the punishment), as well as a List feature that provides information about current punishments.
  • The category also modifies the player's names in all of the options to show what their current punishment is. [ ] = None, [G] = Gagged, [M] = Muted, [S] = Silenced.
• Temporary punishments are only saved on the server where the punishment were issued. Depending on configuration, these punishments can be saved until map change.
• Extended and Permanent punishments are saved to a MySQL/SQLite database and are automatically reapplied when the punished player connects to the server. This allows punishments to be applied across multiple servers.
  • Extended punishments will automatically expire in-game at the designated time.
  • Permanent punishments remain on the player until an administrator removes them.
• Punishments that expire while the client is outside of the server are removed in two manners:
  • Automatically removed when the client reconnects.
  • Pending configuration, the database is pruned of expired punishments every x maps, or administrators can use the sm_commprune to manually prune the database.
• ExtendedComm has support for protecting current punishments based on immunity levels. When a punishment is issued, the administrator responsible has their immunity level attached to the punishment. In order to modify or remove that punishment, the second administrator must have equal or higher immunity level. Punishments issued by console can only be removed by console.
• Support for viewing all in-game punishments via the ExtendedComm category in sm_admin as well as the sm_commlist command. This feature provides the ability to view the punishment, who issued the punishment, the time of issue, the time of expiration, the reason for the punishment, as well as the duration.
• Two configuration files are provided that allow the server owner to determine what per-defined durations and reasons are provided by ExtendedComm's category in sm_admin. These configs also provide the ability to restrict certain durations and reasons to a specific flag.
• Support for delaying in-game queries (the stuff that saves data to sqlite/mysql) until the client disconnects, or immediately after the punishment is issued/revoked.
• Additional logging support, that allows you to single out all actions/errors of ExtendedComm into their own files for easy viewing.

Installation:

Spoiler

ExtendedComm requires a basecomm from the 1.4.1 release. If attempting to use a version from 1.4.0 or prior, ExtendedComm will not function.
A zip file has been attached that provide all the necessary files, which can simply be extracted to your SourceMod directory. However, this is where the files go:
- extendedcomm.smx into /sourcemod/plugins/
- extendedcomm.phrases.txt into /sourcemod/translations/
- extendedcomm_times.ini into /sourcemod/extendedcomm/configs/
- extendedcomm_reasons.ini into /sourcemod/extendedcomm/configs/
If you wish to use an external database, or a database other than the local "storage-local", you will need to add that database to your /sourcemod/configs/databases.cfg as well as modifying the cvar extendedcomm_database in extendedcomm.cfg.

- Database: SQLite

Spoiler

extendedcomm_database "extendedcomm"
"extendedcomm"
{
"driver" "sqlite"
"database" "extendedcomm"
}

- Database: MySQL

Spoiler

extendedcomm_database "extendedcomm"
"extendedcomm"
{
"driver" "mysql"
"host" "localhost"
"database" "extendedcomm"
"user" "youruser"
"pass" "yourpass"
}