SimpleWarnings
Description:
SimpleWarnings is just that, a simple warnings system which allows server admins to set, check, and delete warnings.
SimpleWarnings can be easily configured to execute custom commands on warning, auto-ban a user and/or execute a custom command once they've exceeded a pre-defined warning limit, broadcast a users total number of warnings to the server on join, kick a user when they receive a warning and much more...
Quote:Upgrading to 0.8.8 or above?
In Simplewarnings-0.8.8 the data handling is changed from YAML to MySQL/SQLite.
However this doesn't mean you'll lose your previous warning data, as you can update your previous warning records quickly and easily.
To update your warning records to 0.8.8+ compatibility, simply type /fixwarn to begin the update process.
Remember: You only need run it once, and only if you're upgrading from a version earlier than 0.8.8
Installation:
1. Download the .jar
2. Place the .jar in your plugins directory
3. Restart the server
Configuration:
For details on configuration see here: Configuration
Commands: | |
/sw or /warn | View the SimpleWarnings Commands Menu |
/sw reload | Reload Simplewarnings config |
/warn <playername> <warning> | Issue a player with a warning |
/warnings [playername] | Review your own or another player's warnings |
/dwarn <playername> <warning number> | Delete a player's warning |
/cwarns <playername> | Clear a player's warnings |
/fixwarn | Update warnings records from YAML to SQL (0.8.8+) |
Permissions: | |
sw.warn | Users with this permission may issue a warning |
sw.check | Users with this permission may view their own warnings |
sw.check.other | Users with this permission may view other player's warnings |
sw.delete | Users with this permission may clear/delete other player's warnings |
sw.mod | Users with this permission may do all of the above |
sw.reload | Users with this permission may reload the config |
sw.fix | Users with this permission may update outdated warning records |
Quote:Recent ChangeLog:
1.0
- Updated for UUID compatability
0.9.3
- Updated: DefineFinalBanMsg now refers to the message a banned user will see upon attempting to rejoin, if not set they will see their last warning instead
- Updated: Final warning will be shown as kick message and in the final warning broadcast, instead of the final BanMsg
- Fixed: SimpleWarnings no longer interferes with other banned players ban messages, only banned players with the max number of warnings.
0.9.2
- Fixed bug introduced in v0.9.1 - config.yml not generating on first use due to character conflict
0.9.1
- Updated Autoban BanMsg to be displayed when banned player attempts to log in, if BanMsg not defined the final warning is displayed instead.
- Added: Multiple commands for all custom commands & penalties
@Re4ly
Change the size of the UUID field from varchar(32) to varchar(36) and it will work.
Works fine with 1.8, you missed that minecraft UUIDs are not 32 characters in length, so you will need to change the size of the UUID field to 36 or more in the database (if you are using mysql), then the plugin will work.
a German Translation would be nice :)
Need update for 1.8 !
I can translate to Polish :) But i need source or translate files.
Hi,Could I translate your SimpleWarnings to Chinese?
MySQL dont work in Version 1.0.
Is there a variable for the warning typed, like %warning%? Id like to config a custom command of:
CustomCommandOnEachWarning: true
Penalties:
Warning1: tempban %player% 1d %warning%
So it shows why they are banned when they try to log onto the server.
When upgrading to 1.0, existing database won't be upgraded by the plugin. When starting from scratch, database structure is VARCHAR(32) for UUID while VARCHAR(36) is needed. UUID for players are inconsistent with Mojang and server report, hence they're probably invalid. Any hope to fix those issues?
Hi,
I am getting this with using SQL on 1.7.9
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'uuid' at row 1
I was able to alter the table for uuid and placedby to VARCHAR(80) and everything is fine. So if you run into it with SQL try it out.
Is it possible to have a cooldown feature (eg. 5-10 seconds) that ensures a user can only be warned once within a period of time?
I get the following error if i want to /warn a player
[Server] INFO §7[SimpleWarnings] §cError: §fjava.lang.NullPointerException
Thank you for updating this for UUID's, that's one less plugin I have to worry about.
@robotnikthingy
awesome, thank you so much
Update was just released, guess it just has to be approved by bukkit staff now before everyone else can access it
Update this plugin, or give the sources files !
Is this plugin abandoned? If not does it work with 1.7.9? Is there a way to list all warnings?
Is it possible to get /vwarn? As in a verbal warning, it is recorded in the players /warnings as a verbal warnung with the reason, and can issue a custom message to the player. I find warnings where a punishment is issued can be harsh, this way all staff know if a member has already been issued a verbal warn, and then a /warn can be issued. Ive set up my /warns, to be quite harsh.
Add the Command /listwarnings (or so) and that command list all Users with warnings:
xIPad3Zockerx: 2 Warnings
will you update the plugin to the new uuid system?