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
If you're taking feature requests, may I request an editing warnings feature /ewarn <player> <id> <newly edited reason/warning>
This saves people from deleting and re-issuing a warning just to change something.
@AngellitoX
Yeah, that's a good idea
One good improvement is to add something to "see" who put the warning ingame at the same time it's put.
So, when you type /warn AngellitoX1 Stop using Mods. It says
AngellitoX1 has received a warning by AngellitoX: Stop using Mods
Greetings! :)
yeah a 30 sec thing is good
@Odiumxxx
Can you please add a feature to make it so players can only get warned once per 30 seconds. This would be a great help on my server because when multiple moderators are online sometimes they accidentally warn the same person at the same time.
Would it be possible for you to add an update checker to notify admins when an update is available? Cheers.
@MatrixCA
Sounds like your config.yml is incorrect. Try something like this
@lDarkeen
Try using a yaml parser to ensure your yaml is structured correctly
Hi, i've a bug with this plugin. When I change the config and then start server, this file was overwritten by default values. Please check this.
When my tempban command is called on the max warning, no message or warning is given but the player gets banned normaly.
@killertudse
Not as yet, no.
@Marium0505
1. Yes
2. sw.mod
@MatrixCA
Can you be more specific, why do warnings not reset, and why is no message sent?
CustomCommandOnMaxWarning is executed before the warning and my command is /tempban so the warnings don't reset and no message is send. Could you fix this please? Thanks.
I have two questions.
1. Does the plugin work on the most recent bukkit dev build?
2, Is there a permission to let players in a group see when playeers warns a player?
Is it possible to add 2 commands to be executed at a specific warning?
Like
Warning1: jail %player% 3m Warning1: mute %player% 10m
@baemboo
That has always been the case.
players who arent admins cant see who warned a player. did you change the permissions?
@Legendrunner Happy to help :D
@Legendrunner Fixed!
Another issue!
The donation button redirects me to your website which redirects me to my home screen of paypal, can't donate... must..
Aha! I think I just found the problem. I totally forgot to check the layout of that table. I migrated the existing data and created the table by extracting anything I saw in the SQLite file. Now don't get me wrong.. I know how to handle SQL.. but I think I had my head somewhere.. *cough*
Anyway. DESCRIBE SimpleWarnings; shows me that the expiration column must be a timestamp, may be null and defaults to 0000-00-00 00:00:00. Which -probably- results in having it set to the time the warning was given due to the insert time (same as the date works).
I think I can fix it. If not.. I'll report back. Thanks for your help!!
Ps: It's fixed! Thanks again for the help. Donation coming your way :)
@Legendrunner
That is indeed an issue. I'm hoping you retained your SQLite database so you can reinstate any lost data?
I've test the MySQL expirations again just now, and have been unable to replicate the error with the expected database input, as such my concern is with how your data migration was handled.
If you can view your MySQL database, seeing as you've warning expirations turned off, under the 'expiration' column each field should be 'NULL'. My suspicion is that this is not the case, and as such it's causing warnings to expire.
To explain, when a player joins, any warnings they have will only look to expire if the warning 'expiration' is anything but 'NULL'.
If warning expirations are turned off, (set to 0 in config) then every time a warning is set the expiration is set to 'NULL' and as such that warning will never look to expire itself.
@Odiumxxx
Right now there's kind of an epidemic on my server. Our simplewarns SQLite database had serveral hundred entries but due to recent development on our side for our custom playerportal, we had to switch to MySQL. We migrated all the data but now the following bug occurs:
Everytime a player joins his/her warnings will disappear and as an admin, I get the message: x of <player>'s warnings has expired. Where x is the amount of warns he/she had.
We didn't have this problem earlier. Right now I'm running version 0.9 with 1.4.7 R0.1. I am aware of the fact that 0.8.8 is compatible with 1.4.7 R0.1 and 0.9 is for R1.0, but I had 0.8.8 then switched over to 0.9 to see if the problem was solved due to the changelog saying: "Fixed an issue with SQLite expirations". I had hope.. so to say.
My config:
By the way, the MySQL does work, it still holds warnings of player's who didn't joined yet.