I can confirm LHammonds "An internal error occurred while attempting to perform this command" when using only exception permissions and Group Manager.
EDIT: Just so you know, I set it up so that Admins' deaths would not pop up by putting all the exceptions into the default player permission, then subtracting the death exception permission for the admins. When all the messages were still suppressed, I received an error message when I tried to view the exceptions.
Here is another curveball...when I tested this on my Windows 7 PC, it works just fine (with PEX now instead of bPermissions) but when I copied the same server to an Ubuntu Server, it doesn't work (just like before...not reading the config)
The only difference I know of between a Windows system and Linux is that Linux differentiates between upper and lowercase letters in path and filenames and the direction of the slash/backslash in the path.
The actual path to your config is this the following for each OS:
Linux: plugins/DisableMessage/config.yml
Windows: plugins\DisableMessage\config.yml
Could it be that your plugin is hardcoded to use backslashes in the path or using a different case in the names such as "Config.yml"?
Here's a kicker for ya. I was using bPermissions (tried various versions up to 2.10.7) while having this issue. I just swapped over to using PermissionsEx 1.20.1 (for an unrelated issue) and it started reading the config file correctly (same config file as before) and now all messages are disabled except for the join message which is how I have it configured. Even turned on death messages and the /dm show command recognizes the settings.
I had no idea it was somehow related to bPermissions (does not make sense to me)...but thought I'd let you know.
I ran into a hiccup. I had a request to re-enable the join messages so I edited config.yml and set "enable-join: true" and restarted the server, but the join messages remain suppressed.
I enabled all the messages but they all remain suppressed.
I tried "/dm show" and it shows the following:
[DisableMessage] Configuration:
Join messages: OFF
Quit messages: OFF
Death messages: OFF
Kick messages: OFF
An internal error occurred while attempting to perform this command
I then typed "/dm j Joined the game" to see what it does with the config file. The config file was wiped out with only the following line in it:
exempt-join: Joined the game
I restored the file to look like this:
enable-join: true
enable-quit: false
enable-death: false
enable-kick: false
exempt-join: §7%p joins %s!
exempt-quit: §8%p leaves %s!
exempt-death: §c%p is died!
exempt-kick: §4%p was kicked from %s!
servername: HamCraft
And then ran "/dm reload" which said:
[DisableMessage] The config is reloaded sucessfully!
(yes, successfully was spelled that way)
The join message still does not show. So it seems the code that loads the config file is not working and only goes off the default settings.
Thanks for creating and sharing this plugin. Version X works on CraftBukkit 1.6.2 (BETA Build 2838) running on Java 1.7.0_25, 64-bit with Windows 7 and Ubuntu Server 12.04.2, 64-bit.
Install went flawless, config file auto-created, default settings were perfect. Only changed the generic server name to reflect my actual server name. Startup and shutdown of the server produced no errors and all join and quit messages were suppressed as well as the death messages just as described.
I will be installing this on my production server soon,
Hello, nice plugin!
Can i ask you to add in new build ability to hide custom messages? Messages from server console.. or it's more complicated, that what already done?
Ok, that's bad! I tested it right now with _147 and it worked like a charme... :D Try to create it on a completely new server and export the config to your existing server.
No, wait! :D You don't need the old config if it's your first time with my plugin... You only need to save the old config when you already used my plugin because then you can simply copy and paste your settings!
Still works great in 1.8 and 1.9, but I wish you could deactivate overriding the plugin, add a config node to disable overriding perms.
Maybe u shld update this to 1.7.2
I can confirm LHammonds "An internal error occurred while attempting to perform this command" when using only exception permissions and Group Manager.
EDIT: Just so you know, I set it up so that Admins' deaths would not pop up by putting all the exceptions into the default player permission, then subtracting the death exception permission for the admins. When all the messages were still suppressed, I received an error message when I tried to view the exceptions.
Thanks for your time!
Here is another curveball...when I tested this on my Windows 7 PC, it works just fine (with PEX now instead of bPermissions) but when I copied the same server to an Ubuntu Server, it doesn't work (just like before...not reading the config)
The only difference I know of between a Windows system and Linux is that Linux differentiates between upper and lowercase letters in path and filenames and the direction of the slash/backslash in the path.
The actual path to your config is this the following for each OS:
Linux: plugins/DisableMessage/config.yml
Windows: plugins\DisableMessage\config.yml
Could it be that your plugin is hardcoded to use backslashes in the path or using a different case in the names such as "Config.yml"?
LHammonds
Here's a kicker for ya. I was using bPermissions (tried various versions up to 2.10.7) while having this issue. I just swapped over to using PermissionsEx 1.20.1 (for an unrelated issue) and it started reading the config file correctly (same config file as before) and now all messages are disabled except for the join message which is how I have it configured. Even turned on death messages and the /dm show command recognizes the settings.
I had no idea it was somehow related to bPermissions (does not make sense to me)...but thought I'd let you know.
LHammonds
@LHammonds
Thank you for this information! That sound really bad... :( If I have a little bit time I try to check that!
I ran into a hiccup. I had a request to re-enable the join messages so I edited config.yml and set "enable-join: true" and restarted the server, but the join messages remain suppressed.
I enabled all the messages but they all remain suppressed.
I tried "/dm show" and it shows the following:
I then typed "/dm j Joined the game" to see what it does with the config file. The config file was wiped out with only the following line in it:
I restored the file to look like this:
And then ran "/dm reload" which said:
(yes, successfully was spelled that way)
The join message still does not show. So it seems the code that loads the config file is not working and only goes off the default settings.
LHammonds
@LHammonds
Thank you for this very big info! :) Have fun with it. I try to bring out a 1.6.2 release but I haven't much time... I try to do my best.
Thanks for creating and sharing this plugin. Version X works on CraftBukkit 1.6.2 (BETA Build 2838) running on Java 1.7.0_25, 64-bit with Windows 7 and Ubuntu Server 12.04.2, 64-bit.
Install went flawless, config file auto-created, default settings were perfect. Only changed the generic server name to reflect my actual server name. Startup and shutdown of the server produced no errors and all join and quit messages were suppressed as well as the death messages just as described.
I will be installing this on my production server soon,
LHammonds
@joehot200
Thank you verryyyy muuuuch! I'm glad to hear this. :)
Now i am growing again and have 60+ people online at all times, members and staff alike complained about the chat spam :)
This solves ALL the spam on my server.
Thanks :)
@Pirog17000
Do you mean server console messages with /say?... When it's something other it will be difficult for me... :(
@Elrontur
Hello, nice plugin! Can i ask you to add in new build ability to hide custom messages? Messages from server console.. or it's more complicated, that what already done?
@Malvagio87
Ok, that's bad! I tested it right now with _147 and it worked like a charme... :D Try to create it on a completely new server and export the config to your existing server.
plugin created a folder and config file but did not create any information in the config file.
Same thing goes for when i use versions _147 and _152
@7pr0digy
No, wait! :D You don't need the old config if it's your first time with my plugin... You only need to save the old config when you already used my plugin because then you can simply copy and paste your settings!
I never had the old config, can someone post their default config?
@Elrontur
I already got it, will test it later. Thank you!
Edit: Working perfectly! Thanks
@H8llfire
Now I tried my best to add your wished content! :) It must be approved and then you can test it on your own.
@Elrontur
Why would you need a recommended build, lol. Whatever, take your time.