AcceptRules
AcceptRules - Made by rigor789, recoded by Lolmewn
What does this plugin do?
This plugin makes sure all players have accepted the rules before they can start playing.
The plugin is highly customizable, you can change everything around to your own liking!
Missing something? Make a ticket!
Other features
- Teleporting the player after accepting the rules (can be turned on/off in config)
- Teleporting the player on first spawn (can be turned on/off in config)
- Remembers if the user has accepted the rules
- Block building/breaking of blocks until player accepts the rules (can be turned on/off in config)
- Block commands, except for /rules and /acceptrules of course, until player accepts the rules (can be turned on/off in config)
- Forces the player to read the rules! Can't accept them before reading them!
- Send messages to OP's or players with permission node when someone accepts the rules!
- Let the player or console perform commands upon acceptation of the rules! Use %PLAYER% to add the playername to the command.
- Multiple pages of rules, you have to read all of them before you can do /acceptrules!
How to install
Installation of the plugin is dead simple. Simply download the plugin and drag it into your 'plugins' folder in the root directory of your server. Just like any other plugin!
Configuration
For a how-to on doing your configuration,click here!
Commands and Permissions
All permission nodes default to OP
Command | Permission | Description |
---|---|---|
/rules | Lets the user read the rules of the server. You can specify what rules will be shown in the /plugins/AcceptRules/rules.yml file | |
/acceptrules | Accept the rules. The /rules command must be run prior to this command | |
/acceptrules settp | acceptrules.settp | This command sets the spawning point players are teleported to when they accept the rules, and this function is enabled in the config |
/acceptrules setspawn | acceptrules.setspawn | This command sets the spawning point for players joining for the first time, if this function is enabled in the config |
/acceptrules reload | acceptrules.reload | Reloads the rules and users files |
acceptrules.notifyonaccept | When a player accepts the rules, all users with this permission node will be sent a message, telling the user that the rules were accepted by that player | |
/acceptrules player <player> | acceptrules.acceptForOthers | Accepts the rules for player <player>, as requested by ticket #14 |
/acceptrules reset <player/all> | acceptrules.reset | User has to re-read and accept the rules. Use all if you want everyone to re-accept the rules |
Multi-page setup
#This is page one 1: - "&2Rule one" - "&2Rule two" - "&2Rule three" #page two! 2: - "&2Rule four" - "&2Rule five" ...etc
Metrics
This plugin utilises a plugin metrics system, which means that the following information is collected and sent to bstats.org:
- A unique identifier
- The server's version of Java
- Whether the server is in offline or online mode
- The plugin's version
- The server's version
- The OS version/name and architecture
- The core count for the CPU
- The number of players online
- The Metrics version
If you wish to disable this feature (/me cries), you can do so by opt-ing out, which you can do in the config file under /plugins/bStats/
Auto-updater
This plugin has a built-in auto-updater, which connects to BukkitDev to check for updates. If you, for some reason, wish to disable this process, you can do so by setting 'update' to false in the plugins' settings file.
Changelog
You can find the changelog over at our changelog page.
dadee971
@dadee971
When the 1st person accepts the rules, a "users.dat" file is immediately created here: plugins\AcceptRules\users.dat
If you are not getting that file created immediately after accepting the rules, you need to find out why it cannot create the file (file permission issue?). You could also try and create an empty file as a placeholder if the plugin cannot create the file.
I have confirmed that version 2.0.4 works on both Windows and Linux. Give some more details if you still need help.
LHammonds
Hi, In features i can see: Remembers if the user has accepted the rules. But each time the server reboot, i'm obliged ti accept the rules again. Is there an issu for this?
I looked at version 2.0.4 but the plugin.yml still shows the internal version as 2.0.1 which makes it think it needs to update to 2.0.4 in a continuous loop. Again, the solution to bypass this is to set "update" to false in the config or edit plugin.yml to the correct version.
After accepting the rules, you are teleported no matter the settings in the config file. Here are my settings:
To ensure there are no problems with the TP after accepting the rules, I ran the "/acceptrules setspawn" and "/acceptrules settp" to be the same as the servers spawn point.
My server is now running version 2.0.4 and I appreciate you a whole lot!
Thanks,
LHammonds
@LHammonds
Should be all fixed in 2.0.4
@LHammonds
Woops, my bad. Fixing right away
When I started the server with AcceptRules 2.0.3, it threw this error on the console:
I set "update" from true to false in the config and it kept that error from showing up in the console.
I noticed the 2.0.1 reference so I opened up the jar and then the plugin.yml. The version shows 2.0.1 and needs to be updated to match the actual version.
In the installation steps, you might want to specify that with the default options, you should set the spawn points BEFORE typing /tpaccept because it could possibly teleport you unto the void, middle of rock or lava or mid-air. I'd recommend setting "TpAfterAccept" to false as a default.
The text is showing up just as configured in the text file (with color codes too!).
Thanks,
LHammonds
@LHammonds
v2.0.3 is in the queue, fixing this issue.
@LHammonds
Alright. I'm going to have to look into this further, as in theory it should display them like they are in the text file. Version 1.7 reads the text from the file every time /rules is performed, while 2.0.2 buffers the contents.
I'll keep you updated.
In the example I posted, I have something that looks like the following when you type /rules right now:
Example #1 (text file):
But when I installed AcceptRules 2.0.2 to test it out and placed the rules in plugins\acceptrules\rules.txt, the plugin jumbled around the text to make it look like the following in-game when you type /rules:
Example #2 (in-game):
Please note that when the server is shutdown and the plugins\acceptrules\rules.txt is viewed, it is still in the original order that was defined (example #1). This means the plugin is reading the contents of the file and performing some kind of line sort before being displayed rather than showing each line as it appears in the text file.
To test this even further, I placed the following in the rules.txt file:
Example #3 (text file):
This is what it looks like in-game:
Example #4 (in-game):
It appears it is not a "sort" of any kind that I can tell. It jumbles around the lines that are displayed. I cannot see a pattern but regardless, I cannot use this plugin if the lines get jumbled around.
EDIT: Version 2.0.2 and 2.0 both behave the same way. I tried version 1.7 and it properly displayed the text as it was in the text file.
@LHammonds
Oh you don't want it sorted? I guess you can scramble it yourself, and I don't see why you'd want it scrambled...
What I'm asking is for it "not" to sort it.
@LHammonds
It *should* sort it, ill try it out myself later too
Oh, sorry, I forgot to add my "tested on" line I usually add to all my posts. I used AcceptRules 2.0.2
OS: Windows 7, 64-bit (will also use on Ubuntu Server 12.04.2 LTS, 64-bit)
Java: Sun Java JRE 1.7.0_25, 64-bit
CraftBukkit: 1.6.2-R0.1 BETA (Build 2838)
@LHammonds
Which version?
Is there a way to have the lines in rules.txt displayed in the order that is set in the text file? When I type /rules, it shows what is in the text file but they are all jumbled around.
Example rules.txt:
@SamzRulez
Seriously, stop it. I can clearly see you deleted the comment for being 'old', as you also did on some other pages. http://puu.sh/4idNe.png - So please just stop.
@SamzRulez
You were the one who complained. I'm fine with dropping this, but you still tried to fool me. Reputation
;@RigiTv
Dude wtf I haven't done anything and tbh dude I really don't give a crap. So let's just drop this.
@SamzRulez
Since you deleted your comment, there's nothing to see.
Your comment was comment #112 And if you check the page there is 111 and 113 and 113 is a reply to your comment. Deleting your comment is trying to fool me. Please don't even bother.
@RigiTv
I don't see anything there, It doesn't work.