Bukkit

@Roalith

Sorry, I should read more carefully. You will want sleep.ignore to be false to treat your admins like any other player.

By default this Sleep plugin won't treat your admins any differently and they should have to use a bed just like all other players. So, my guess is you are giving your admins some type of * permission somewhere else and that is inappropriately giving them sleep.ignore.

It will depend on what permissions plugin you are using as to how to properly configure it. Be aware of warnings like PermissionsEx has regarding usage of the * node. Generally speaking it's almost always better not to use the * node and instead identify specific permissions you want to give out.

@Roalith

Setting sleep.ignore to true for your admins is what you are looking for.

If you still have trouble after that I'd need to see your permissions configuration and maybe have you set logLevel: ALL in your /plugins/sleep/config.yml and then look closer at your server.log file to try and determine what is going on.

@sbhouse

My apologies. I thought you were editing the file. Indeed, if the file is being generated automatically and it is still presenting an error, there is something I'm apparently overlooking in my configuration file management.

I'll see if I can download MineOS this weekend and get a test environment setup for myself to witness and troubleshoot the error.

@sbhouse

Unless you've made specific world configurations under /plugins/Sleep/Worlds/ it will just be /plugins/Sleep/config.yml

Can you paste your config.yml file up to somewhere like http://gist.github.com/ for me to test with myself?

Also what encoding are you saving your config.yml file as?

Lastly, can you setup a test server in MineOS with just the Sleep plugin perhaps and the -Dfile.encoding=UTF8 system parameter set, and save your config.yml file there as UTF-8 to see if that works at all?

@sbhouse

If you are on Windows, your YAML configuration files need to be saved as ANSI (windows-1252/Cp1252).

If you are on Unix, you need to save them as UTF-8.

My hunch is you are on Windows and you saved as UTF-8 because you have some special characters that ANSI wouldn't save properly? If that's the case, your options get tricky. The overall "best" approach will probably be to start the Java VM with a parameter to force the default encoding to UTF-8. HOWEVER, please head my warning that this has the potential to destroy all your existing configuration files initially. If you are lucky, all your plugins will be coded smart enough to compensate. However, chances are something will go bad somewhere.

How to change your default encoding for configuration files to UTF-8 Please ensure you make a proper backup of everything before

1. Rename all your existing configuration files (most will probably be under /plugins/PLUGIN_NAME/config.yml) to something like config.old
2. Run CraftBukkit with the file.encoding system property explicitly set: java.exe -Dfile.encoding=UTF8 -jar CraftBukkit.jar
3. Stop CraftBukkit
4. Edit all the new config.yml files created to reflect any changes you made in the originals

Hope this helps clarify a bit. Let me know any specifics and I can try to help you through this. I wish I could make it easier somehow... I think I'll try to add a message to hopefully clarify this into the plugin also.

@disturbedpigeon

Have you tried configuring your /plugins/Sleep/config.yml file to contain the following?

force:
    enabled: true
    count: 1
    percent: -1

The Configuration page explains this a bit more.

You will need to issue a /sleep:reload command (or restart your server) after you edit your config.yml file.

@WingedSpear

Try setting your /plugins/Sleep/config.yml logLevel: CONFIG value and then reload to see what the console logs that it is set to after a /sleep:reload command.

Also make sure you are setting enabled: true under the force: section.

@WingedSpear

I just put another beta (6.1.0b3) up. It now has a colorCode: '§' configuration value you can use to change the color code character with. You can change that to '&' for instance and then change all the § characters to &.

My number one pet peeve with most plugins is when authors think they know how everyone wants their messages to look or are simply too lazy to provide a customization option. I really want to make message customization easy for everyone. I originally figured using the native section sign character was the smartest to keep everything basic and predictable. However, you highlighted a clear usability problem with that choice. Some environments may not make it easy to interact with unicode characters. Now you can have a choice how you want to do it.

@WingedSpear

Ah, this makes a bit more sense. So, do you edit the config.yml file locally on your computer and not the server then and then upload through FileZilla? Or does TCAdmin provide some text editor interface?

If you edit locally on your computer and it's Windows and perhaps you are using Notepad? Make sure you save the file as UTF-8 (File > Save As... > Encoding = UTF-8). Then also make sure FileZilla is uploading the file as a binary file. (I think you can right click the binary/ascii indicator in the status bar to change it.) This will prevent FileZilla from trying to interpret the encoding itself and making assumptions.

If it's a custom TCAdmin text editor, there might be some choice there or that may not be usable if it's not able to let you choose what encoding and then you'll have to do a Notepad/FileZilla solution instead.