HeroicRebuke Reloaded

Heroic Rebuke Reloaded

The original heroicrebuke is now abandoned and incompatible with recent builds. This is a drop-in replacement for the original, based off of the original code, with the blessing of the original authors. See the original thread.

Features

• Warn players for lesser infractions not meriting a kick or ban
• List a player's previous actions to track chronic violators
• Supports partial name matching for online players (Squall, ed3, and LLSEE all match SquallSeeD31)
• Supports SQLite or MySQL
• Warnings can optionally root players, preventing all movement (including teleports)
• Acknowledging your warning can optionally require a randomly-generated code, preventing automation and encouraging thorough review of the message
• Commands can also be issued from the server console
• Support for permissions, defining your own list of admins or just using Server Ops
• Configurable display colors for messages, names, and key information

Installation

HeroicRebuke works best with a database (SQLite or MySQL). The plugin is configured to look for the database connector "sqlitejdbc-v056.jar" (SQLite) or "mysql-connector-java-bin.jar" (MySQL) in the "/lib" directory of your server root. If you already have these files, you do not need to re-download them.

• Download latest .ZIP archive from the link at the top
• Extract the archive into your main server directory (archive contains directory mapping)
• Open /plugins/HeroicRebuke/config.yml and configure to taste
• Save configuration file and reload your server
  • Using MySQL
• Check to be sure "mysql-connector-java-bin.jar" is in /lib (from server root)
• Set options.database to "mysql" in your config.yml
• Set options.mysql.location to the path (IP:port/DatabaseName) to your MySQL server
• It is not necessary to create a new Database for HeroicRebuke, but is recommended. The only table created currently is "warnings"
• Set options.mysql.username to a username that has access to the named Database on your MySQL server
• Set options.mysql.password to that user's password
• Save config.yml and reload your server

Configuration

config.yml - The config file contains default text colors, options, and designated HeroicRebuke admins (if not using the Permissions plugin). This file is saved in the YAML format, so please be sure to maintain the formatting and change only the element values.

Default configuration:

# HeroicRebuke Configuration
## Color options
## message: Text color of all notifications, wrapped around info and names.
## name: Color for player names.
## info: Color for informational elements to make them "pop", such as command usage
#Color is defined according to the Bukkit enum ChatColor
#Acceptable entries:
##BLACK
##DARK_BLUE
##DARK_GREEN
##DARK_AQUA
##DARK_RED
##DARK_PURPLE
##GOLD
##GRAY
##DARK_GRAY
##BLUE
##GREEN
##AQUA
##RED
##LIGHT_PURPLE
##YELLOW
##WHITE
#
#If color entered is inappropriate, HeroicRebuke will default to the following values:
##message: RED
##name: DARK_AQUA
##info: GOLD
colors:
    message: RED
    name: DARK_AQUA
    info: GOLD

options:
    database: sqlite
##ACCEPTABLE VALUES:
###sqlite - Expects "sqlitejdbc-v056.jar" in the "/lib" directory of your server root, and uses SQLite.
###mysql - Expects "mysql-connector-java-bin.jar" in the "/lib" directory of your server root, and uses MySQL. MUST configure options.mysql section for this to work
###<anything else> - HeroicRebuke will not use a database and no data will persist over a server restart
    permissions: Permissions
#String containing which permissions system to use.  Acceptable values:
##Permissions - builtin bukkit perms or any modern permissions plugin
##Config - Define your own HeroicRebuke admins below under the "admins:" property (untested)
##Ops - Only Server Ops can use HeroicRebuke (Ops can use HeroicRebuke anyway regardless of setting)
    code:
        use: true # If true, a random alphanumeric code will be generated on warning, preventing users from automating the /warn acknowledge command.
        length: 5 # Length of random code string to use
    server_name: SERVER # Name to display when warnings are issued from the server console
    block_move: true # Whether or not to restrict a user from moving (and teleporting) when being warned.  Move block is aggressive.
    only_warn_online: false # If true, you can only warn players who are online (enables partial matching)
    lines_per_page: 5 # How many warnings to display when using /warn active and /warn list commands
    timeformat: MM/dd/yyyy HH:mm:ss z # Uses format strings from Java SimpleDateFormat.  Read all here: http://download.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html
    mysql: # If using "database: mysql", you must define the location, username and password to your MySQL server
        location: localhost:3306/HeroicRebuke
        username: myuser
        password: mypass
#If you want to use the "Config" permissions system, define your admins here
#Each line below "admins:" *MUST* be formatted as such-> "    - 'username'"
#Four spaces, hyphen, space, single quote, name of the admin, single quote
admins:

Permissions

heroicrebuke.add (use /warn add)
heroicrebuke.clear (use /warn clear)
heroicrebuke.delete (use /warn delete)
heroicrebuke.active (use /warn active)
heroicrebuke.info (use /warn info)
heroicrebuke.list (use /warn list - Displays only YOUR previous warnings)
heroicrebuke.list.others (use /warn list <name> to display OTHER players' warnings)
heroicrebuke.notify (send a notification when any user acks a warning)

Recommended Settings:
Admins:
- 'heroicrebuke.*'

Moderators:
- 'heroicrebuke.add'
- 'heroicrebuke.clear'
- 'heroicrebuke.active'
- 'heroicrebuke.info'
- 'heroicrebuke.list.others'

Players:
- 'heroicrebuke.list'

Changelog

v1.4.2
* Tested new perms setup proper
* Fixed new perms setup
v1.4.1 (beta)
* Removed old permissions checks
v1.4
+ Added heroicrebuke.notify
* Fixed colors (if everything is white, just delete that section from the config, it'll be reset to defaults)
* Fixed broken message templates (caused "[{0}] message" in console)
+ Started other feature requests
v1.3-a2
+ Changed to new Bukkit event system.
* Fixed ban thresholds
* Removed some legacy permissions stuff
v1.3 (Initial reloaded release)
* Changed to new event system
* Fixed strangeness with 1.0 and 1.1
+ Added "Movement disabled! Do this:" messages
+ Throttled those messages
* More

v1.2 and earlier: See original plugin

Source

Available at GitHub