IWarnYou
IWarnYou
IWarnYou is a simple warnings plugin designed to alert users of there wrong doings but also so staff can check if a user has previously broke the rules.
> Download v1.5.3 Here <
Want a custom plugin or want this one rebranded? Add me on skype (craig-egerton) or check out http://mc.craigegerton.com/
IMPORTANT - CURRENTLY WORKING ON v2
UPDATE 20/12/2012: I have been doing work on this and it is very much improved but every time I get it close to release, I have learnt a bunch more about coding and end up redoing everything much better in every way you can think of, due to this it was terribly delayed! I have decided I will recode this plugin only one more time and I am guaranteeing that it will be released for you guys to use, once that is released and bug free I may improve on it more but you can expect the next version (1.4.6 compatible) to be released in the next few weeks :)
Thanks to learning more about Java coding and the Bukkit API I am currently working on a complete recode and remake of the plugin that will complete reinvent the way it works, what it can do and how well it works, it will make everyones life easier when handling the warnings and the weight each warning has (because currently a spam warning weighs as much as a grief warning even though they make a big difference).
I have currently implemented in to the remake:
- Simple config file (both layout and the way the plugin handles it)
- MCBans Support
- A version update detector with auto downloading
- Any normal startup code has been cleaned up to be more efficient
- Permissions
- Swear detector
- Warning check signs
- Freeze warn (freeze the player when they are warned)
NOTE: Sorry about the delays in the update, my computer went crazy and I could not use it properly to get coding again until now, I have started development on the update again and am making good progress :)
Commands/Permissions
Command | Shortcut | Permission | Description |
---|---|---|---|
/warn (username) (reason) | N/A | iwarnyou.warn | Warn a user |
/warnings [username] | N/A | iwarnyou.check | Check yours or another users warnings (must be op or have node to view others) |
/clearwarns (username) [id] | /cwarns | iwarnyou.clear | Clear the warns set to a user, add a ID to the end to remove a specific warning |
/modifywarn (username) (id) (reason) | /mwarn | iwarnyou.edit | Modify a already created warning |
/twarns | N/A | iwarnyou.twarns | Toggle the ability for users to view there warnings without accessing the config file |
/iwyreload | N/A | iwarnyou.reload | Reload IWarnYou |
/iwy | N/A | N/A | View available commands |
To create a warnings sign you need the permission node iwarnyou.sign if you have it create a sign with [Warnings] on the top line to view the users own warnings or add a username on the second line so when you right clicked it will tell you that users warnings!
Configuration
By default the configuration file shows this:
# IWarnYou config file WarningsToBan: 5 BanMsg: You have been banned for reaching &4%num&f out of &4%total&f allowed warnings! ShowAllOnLogin: false ShowOnLogin: true AutoBan: false viewOwnWarnings: false announceWarnings: true
Here is a rundown of all the settings:
- WarningsToBan
- How many warnings a user can have at any one time before they are auto-banned (AutoBan must be set to true)
- BanMsg
- The message a user gets when they are banned
- ShowAllOnLogin
- Should the user see all there warnings when they sign in
- ShowOnLogin
- Should the user see a warning count when they sign in
- AutoBan
- Should users be auto banned when they reach the WarningsToBan limit
- viewOwnWarnings
- Should the user be able to view their own warnings without having the permission node or being a op
- announceWarnings
- Should every user in the warned users world see that they where warned
Currently added in next version
- Only OPs and people with the iwarnyou.sign permission node can destroy [Warnings] signs
ToDo
- Cursing blocker that automatically warns the user and blocks the fowl language
- Ability to add location to warning with extra argument (e.g. -loc)
- Warnings time out (edit time in config file)
- Temp ban with a adjustable time to be banned
- Plugin will tell you when a update is available
Contact Me
If you have any problems, bugs or ideas then please contact me at [email protected] or leave a comment!
Changelog
05/03/2012 - v1.5.3
- Updated to the latest recommended build (CB 1.1-R6)
31/10/2011 - v1.5.2
- Fixed error that stopped a ingame user warn a offline user
- Added colours to the [Warnings] signs
- Happy Halloween!
30/10/2011 - v1.5.1
- Fixed database update error
30/10/2011 - v1.5
- Warnings have there own unique ID which is stated after the # when you type /warnings [username]
- Automatically updates the old databases to support the new ID's
- The ability to delete a warning by ID
- The ability to edit a warning by ID
- A warning sign that when you right click tells you information
29/10/2011 - v1.4
- Removed some debugging I forgot to remove (when it says the server didnt reload ignore it)
- Added the ability to announce the warning to everyone in that world (change in config)
- OPs can see version number in /iwy
- Fixed the /clearwarns bug when typed in game and the user is offline
- Case insensitivity if the player is online, otherwise warns case sensitive offline user
27/10/2011 - v1.3
- Fixed a bug where clearing a offline users warnings would create a error
- Added /twarns so you can toggle if users can view there own warnings without accessing the config
- Updated HelpMe support to work with the new Maven system
- Added /twarns to HelpMe
27/10/2011 - v1.2
- Added HelpMe support (HelpMe must be installed)
27/10/2011 - v1.1
- Adding console support (commands now work in the console)
26/10/2011 - v1.0
- Initial Release
Can you just get this working with PEX directly, some people won't want to use Permissions Compat, and it will be outdated soon enough
Thanks, it works! I did encounter another problem though. I can't warn people that are offline. This is probably due to change of bukkit. It seems the author is not looking at this page anymore sadly enough.
And by the way, the warn ID (1st warn is #1, 500th warn is #500) doesn't appear anymore when checking a user with /warnings.
Here you can get Permissions.jar - http://dev.bukkit.org/server-mods/permissionsex/files/6-permissions-ex-v1-17-package/
Could you supply me of the correct Permissions.jar?
@Legendrunner Then you are 150% wrong :D I just tested that, no errors what so ever and permissions work.
I can figure that does a TON of errors...
Hehe got it working. Guess they don't call me a genius for nothing :D
I am assuming you are using PEX 1.19 or higher. Well IWarnYou doesn't support PEX directly, it worked because of the PermissionsCombat.
So just download PEX 1.17 again get the Permissions.jar file and slap that in your plugins folder next to PEX 1.19 and try then :D Works for me.
It does not. I gave my moderators the permissions: - iwarnyou.warn - iwarnyou.check - iwarnyou.clear - iwarnyou.edit
But it still doesn't work. They have no permission it says. And have also tried iwarnyou.* My permission plugin is PEX, lastest dev build and Craftbukkit 2036 (lastest beta).
@everyone Latest version should work on latest CraftBukkit because I have seen it running on CB 1.2.3 servers.
Also the latest version is 1.2.3 not just 1.2 :D
It has already been asked but 1.2 please :)
@CraigEge Heyho,
/warn username works on online users, not on offline users. Error: http://pastebin.com/dbw97Ffj
AutoBan: false WarningsToBan: 0 If I do a warn on my own, I'm banned! *confused*
On fresh installation, the new config is empty.
Hello?
I looked into the error more carefully instead of just pasting it. According to the error I posted a day ago it seems as if there is some variable that is being processed that -can- be null without checking if it is null first.
At this time it is NOT possible to give any user (except someone with a * permission wildcard) permission nodes for any of the commands IWarnYou 1.52 for bukkit 1.1-R6 has to offer. This goes for atleast PEX and PermissionsBukkit.
The plugin is, in it's current state, not working.
How is that error even related to PEX?
That error refers that the "warn" command isn't working.
There seems to be an issue with warn commands. Also, the permissions iwarnyou.* and iwarnyou.check won't work for PEX. Error log: http://pastebin.com/Rz1Hzc87
Hi, sorry to be a bother, but what permmisions systems work with your plugin? I'm using PEX and it doesn't seem to be reading any of the permissions, and it doesn't grant any permissions by default, so no one but Ops can do anything. I'm on the latest builds for both CB and your plugin. Thanks.
When I open the config file there is nothing inside, help? :D Thanks
Plugin does not create a default config file, only a default config folder.
This working in 1.2?