Basically a chat shout plugin. If you are using a local area chat plugin you might want to have a way to override it. Here is WyrdShout. It overrides the local area chat and lets people shout to the whole server. PermissionsEx prefix support is on it's way and will show you which rank you're talking with. To override local area chat is essentially for all servers because people can't communicate easily without some way to shout. But to bigger servers it's not a good idea to allow people to chat globally because it would spam the chat. Thereby you need WyrdShout. You can allow your players to communicate easily without having them to spam the chat. WyrdShout is using a customizable timer to ensure it's able to run on every server.
Functions:
Make people able to shout to the whole server
Choose your own custom shout prefix
Choose the delay between shouting
Override timer through permission
Commands:
/wyrdshout
Aliases: ws, shout, wshout
Argument
Example
Message
<message>
/ws <message>
/wyrdadmin
Aliases: wa, wadmin
Argument
Example
Show version
version
/wa version
Set delay
delay
/wa delay <time>
Set shout-prefix
shout-prefix
/wa shout-prefix &c[s]
Config file:
Config
Default
Shout prefix
shout-prefix
'&c[shout]'
Delay between shouts
delay
150
Permissions
Permission
For use
Example of users who need that permission
wyrdshout.*
For all commands
Owners
wyrdshout.admin.*
For all admin commands
Trusted users
wyrdshout.admin.delay
Access to set delay ingame
Trusted users
wyrdshout.admin.shout-prefix
Access to set shout prefix ingame
Trusted users
wyrdshout.shout
Access to shout
All
wyrdshout.override
Override the timer for shout
Donation rank/staff rank
I know the permissions seems confusing. My bad. I will fix it in next update.
@EndCraftMC Please create a ticket and remember to include your setup. I'm really sceptic because 0.2.1 was a panic-update because it didn't create a config.yml, which needed to be fixed. when it doesn't show up in the /pl probably means you haven't set the server correct up.
That would be an excellent feature but I would have to rewrite the whole plugin and it's much more inefficient. I won't add that feature... Please use this forum to post suggestions.
I cant use this plugin everytime i am starting my server with only this plugin i get a message like this
org.bukkit.command.CommandException: Unhandled exception executing command 'ws'
in plugin wyrdshout v0.2.1
I've found the problem. It's because I'm using java 7 to compile the plugin and only java 7 can run it then. You can fix it by updating your java or you can wait until next update (I'm going to use java 6 which works with both java 6 and java 7).
I'm working on v0.2 right now. It will have PermissionsEx and normal permissions support (must be configured in config.yml), and timer too. If you had checked the change log you would know that I added 3 aliases: wshout, shout, ws. I will try to get v0.3 to have PermissionsEx prefixes support.
@simpsda
I've found the problem. This means that you can only use this if you're op. But then staff can use this to talk to the whole server.
Will be fixed in next patch.
I wen't on your server and tried "/ws Hello world!" and I got perms denied. Same thing is happening on my server.
@EndCraftMC Please create a ticket and remember to include your setup. I'm really sceptic because 0.2.1 was a panic-update because it didn't create a config.yml, which needed to be fixed. when it doesn't show up in the /pl probably means you haven't set the server correct up.
The 0.2.1 version doesn't seem to create a config. Nor does it show up in /pl
@FrostedDarkness
That would be an excellent feature but I would have to rewrite the whole plugin and it's much more inefficient. I won't add that feature... Please use this forum to post suggestions.
@highace2
Awesome, perhaps add a feature where if you put a ! before the message it behaves as a shout but doesn't display the !
@FrostedDarkness
Thanks for the good words! And it doesn't support pex prefixes yet but will in next update!
After months of searching, I find this. Absolute godsend, thanks so much.
EDIT: Does the pex support support pex prefixes?
@ceoepts
Please create a ticket with the whole stack trace! Go to ticket tab and create one...
I cant use this plugin everytime i am starting my server with only this plugin i get a message like this org.bukkit.command.CommandException: Unhandled exception executing command 'ws' in plugin wyrdshout v0.2.1
Pleas help me :(
@simpsda Try send me how you've set up permissionsex(permissions.yml). As far as I can see there should be no errors...
Updated to java version "1.7.0_147-icedtea" Config generated :)
Now i'm just getting permissions denied, even as OP. Same goes to my users. I tried setting permissionsex: false and still nothing.
I really appreciate you for making this and your trouble shooting time :)
I've found the problem. It's because I'm using java 7 to compile the plugin and only java 7 can run it then. You can fix it by updating your java or you can wait until next update (I'm going to use java 6 which works with both java 6 and java 7).
I get this to work on my test server without running any plugins except essentials, permissionsex, worldedit and vault.
On my live server, I get this on load up: http://pastie.org/3835908
Might be a plugin conflict. I am using about 50 plugins on my live server.
I've found the problem and I'm uploading it asap. I've added some other features too but they haven't been checked completely yet.
same, no config is loading for me either.
@bfathman6
No. Did you get any stack trace? It should create itself and it does when I try to run it.
I Put this plugin on my server and still No Config file loads is that suppose to happen.
I'm working on v0.2 right now. It will have PermissionsEx and normal permissions support (must be configured in config.yml), and timer too. If you had checked the change log you would know that I added 3 aliases: wshout, shout, ws. I will try to get v0.3 to have PermissionsEx prefixes support.
Should add a permission, so that some groups don't see the shouts.