Hey all, I've been tossing this idea around with some of my regulars who are java students/contractors and it seems very possible (but they're also very lazy ). What: A plugin that (is compatible with permissions as it seems to be incredibly popular) keeps people in a default group that cannot build or place unless they agree to the /rules. Why: Because server rules are very often overlooked. How: That's up to you guys Imagine it, PlayerZ logs in but can't build or place, instead he's prompted with a message in chat Welcome PlayerZ, it appears you're new to the server. In order to play you have to agree to the rules so type /rules to begin. and at the end of the rules (I use essentials for it) we can have a line of text saying, "Now that you've read the rules, type /iagreetotherules (or something ) and you can then build and destroy blocks." You could even remind them every 5 minutes or so with something like "PlayerZ, you haven't read and agreed to the rules yet! You can't build/destroy! "Type /rules to read them and continue" This way, -The person has read the rules or at least agreed to them, waving all the drama of "oh but I didn't know the rules". -The person has just typed that they agree to the rules after reading the command which is ONLY accessible if they read /rules ! Thoughts?
I was going to suggest a plugin similar to this, but this is basically what I want. For rules trigger it would be cool if the messages about reading the MOTD + Rules appear every time he tries to place or destroy a block until he /agree or /disagree
Perhaps integrate it with Permissions for now or would it take too much effort to change it from Permissions -> native craftbukkit groups?
When I create my UserRequests plugin for bukkit I will add this feature before a player can make a build rights request. I do however have to wait for Bukkit to add a Permissions system. UserRequests is a plugin where new users to the server are greeted and told they have to request build rights, when they do this gets sent to a defined group of mods (by who has access to the command) and they can accept the build request. This gives the player build rights. It is very useful to combine this plugin with Cuboid or Similar to actually change what the player can do, as with hMod is just changes groups. I will see how Bukkit implements their system.
Sounds good, I'm keen to have any sort of plugin (working ) that supports the automated rule acceptance system.
I'm currently using mPasswordProtector for this. It works for me, even though it doesn't meet all of your requirements. I was looking for something like you described and found this thread. Just thought I'd share what I found.
