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
Hey, could you please add an option to let essentials print out the number of warnings in its motd? Alternatively you could make it possible to put in a certain amount of seconds BEFORE the number of warns is printed..... Would be awesome :)
AND: @mesud18
Just give them all the permissions listed above sw.mod
I need help ASAP i put - sw.mod and it doesnt work and i have to give staff single permissions but i really want the admin commands to work. Please help me i need help asap
Can you make a config.file where we can edit the text? I have a norwegian server and I want to have the text on Norwegian...
@chsedv
You're new to servers aren't you? Plugins aren't mods they can be used cross versions.
pls update to bukkit 1.7.2
Hey, Can you make a language file?
can you make the plugin check the players warnings on login and ban them if they have reached the maximum warnings? this would be useful for people running bungeecord
Thnx usefull plugin
can you create a command, /allwarnings so we can see everyone warnings?
and something like sw.antiban so some players like admins can't get bannned.
Can you give a source code?
Can you please make this in German pls
New Command Suggestion
A type of warning that isn't affected by the warning expired feature. (Perhaps /ewarn or /warne for exepmt warning?)
Also a permanant warning that isn't removable ingame. Like only the console can run the command to remove it, but the warning can be given by an ingame player.
EDIT: Fixed, sorry about that.
@ViscousSummer88
Hehe yea.
@elfoe
I don't have this problem, for me it shows the reason of the last warning
I don't think the ban message shows up when someone tries to log in, it is just the default message.
@Arton123
Well, you could test it.... or http://dev.bukkit.org/bukkit-plugins/simplewarnings/files/32-simple-warnings-0-9-1/
would 1.6.1 work with 1.5.2?
A request really... Is it possible to add a [Level] feature? The command would then look like... /warn [playername] [Warning] [Level] Other than that, thank you for the plugin. This is just an idea, for now writing the level in the warning reason is working well enough.
New idea:
Different ladders of warning. So like you do the command /warn <player> <ladder> <warning>
So that you can configure ladders and max warnings and what each warning does. Like for on the griefing ladder the first warning is a ban while on the spam ladder the first warning is a kick. This would be configurable like permissions and allow for any name of ladder.
Other idea is a system where a certain offense is worth so many points. Like a warning in the Griefing is 10 points and in the Spam ladder is 1 point. Then you can configure when a Player gets so many points something happens. Also can have it co-mingle with the rest of the plug so if someone gets a warning in another ladder (like the griefing ladder) that action is still carried out. Also have it be able to be configured so you can define points per warn so for example the 1st warning in the spam ladder is worth 1 point and the 2nd in the spam ladder is worth 3 points and the 3rd is worth 7 points. This would allow a lot of configuration and customization.
Examples:
So if Player A gets a warning in the griefing ladder and you have it set so that any warning in that ladder stands alone too so then Player A gets 10 points put towards his record but still banned as the first warning is a ban in the Griefing ladder.
Player B has 3 spam ladder warnings and a warning in the Trolling ladder. Neither ladder has warnings on their own but Player B will get 3 points from the spamming and 6 for the Trolling warnings. He would have 9 and lets say when 9 points are reached he is temp banned for 3 hours then that command is ran.
Example config:?
Point Warns: 10: kick %player% 20: ban %player%
Ladders: Griefing: PunishAlone: true Warning1: jail %player% 5m Points: 3 Warning2: ban %player% Points: 10 Spam: PunishAlone: false Warning1: kick %player% Points: 1 Warning2: kick %player% Points: 1
(You can probably think of a better layout)
What do you think? Thanks for the read. Give me your thoughts. Hope you add this!