Bukkit

Upgrading from 0.8.7 or below?

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, if you're upgrading from a previous version.

Change-Log:

0.1
- Updated: 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 not defined the final warning is displayed instead.
- Setup multiple commands for all scenarios (customcommand / customcommandoneach / customcommandonmax)
0.9
- Fixed an issue with SQLite expirations
- Updated placedby & name varlength from 16 to 32
0.8.9
- Bugfix: Fixed /cwarns wiping all warning records
0.8.8
- Updated: Data storage to from YAML to SQL
- Added: Conversion tool for previous YML data to the new SQL data (/fixwarn)
- Added: Warning Expirations
- Bugfix: NPE if KickOnWarning enabled and warned user not online
0.8.7
- Bugfix: Menu Fixed
Admin permission repaired.
NPE on menu display from console. (warn)
- Bugfix: onplayerjoin user/admin warning notification separated.
0.8.6
- Fixed bug: Auto-ban on warning limit not triggering 0.8.5
- Added configurable, individual custom commands for each warning
- Minor code improvements
0.8
- Added execution of custom commands on Warn & MaxWarning
- Conversion to lowercase data handling (TYPE /FIXWARN TO UPDATE RECORDS TO 0.8+ COMPATIBLE)
- Cleaned up config
0.7
- Major rewrite - Fixed all known bugs. - Changed output and appearance - Groundwork for coming upgrades 0.6
- Fixed warning users from console
- Minor Updates
0.5
- Fixed trailing '.' causing 'cannot set empty path' error in CBR1.3(Beta)
- Added sanity check in /dwarn
0.4.9
- Fixed bug with warning warning offlineplayers while KickOnWarn is enabled
0.4.8
- Added description for config options in config.yml
- Fixed stray console output on playerjoin
- Code clean-up / onjoin warning notifiers improved.
0.4.7
- Fixed a bug in /dwarns that left some data behind
- Fixed setting warnings from console
- Updated 'fixwarn' to remove excess data left behind by aforementioned bug in /dwarns
- Added a check on player join to automatically update/repair any outdated/buggy warning records
0.4.6
- Added option NotifyAdminOnJoin
0.4.5
- Fixed console commands
- Updated menu
- Added NotifyUserOnJoin option, to notify a user of their warnings onjoin as opposed to a broadcast
- Fixed bug which caused an error when deleting a warning which does not exist
0.4.4
- Added numbers to warnings
- Added menu alias (/warn)
0.4.3
- Bugfix: minor fixes to permissions
- Update: fixwarn command for updating warnings set before v0.4
0.4.2
- Added option for kick on warning
- Added new/changed permissions
- Added option for Personalising final ban message.
- Added command for clearing all of a user's warnings /cwarn
0.4.1
- Bugfix: Some users couldn't see their own warnings
- Update: Dates and Formatting
0.4
- Updated the way a player's name is retrieved / handled
- Added dates and times to warnings
- Cleaned up formatting

0.3
Bugfix: users warning record not cleared when final warnings removed.

0.2
- Bugfix: Fixed permissions so all users can check their own warnings
- Added /sw commands menu

0.1
- set, check, and delete warnings
- broadcast warnings and on join, autoban + config & permissions

If warning limit is raised, banned players with less than the new maxwarnings will not see the defined BanMsg or final warning upon attempting to rejoin.
[Will be fixed in next version.]