SimpleAnnounce
SimpleAnnounce
Create timed announcements/news messages with ease with SimpleAnnounce
You can create messages that are printed server-wide after a certain delay, and have it repeat every x seconds if you'd like. If you wish to send it only to users with certain permissions, or a lack of certain permissions, so it sends to exactly those whom you wish the message to send to.
Features
- Timed server-wide announcements/news messages
- Easily configurable
- Configure one-time or repeating messages
- Configure messages to only send to users with or without certain permission nodes
- Config auto-generation on first-run
- Optional debug mode to track down who is/isn't receiving messages and why
- Optional automatic config reloading to retrieve new messages
- '/simpleannounce reload' to reload on command!
- Permissions:
- simpleannounce to use '/simpleannounce' for help
- simpleannounce.reload to use '/simpleannounce reload' or '/simpleannounce r'
- Permissions:
Configuration Overview
Details
Config Nodes
auto-reloadconfig(int): <Time in minutes to check/reload config for message updates(0 for off)> NOTE: When config is reloaded, will reset delays for messages and cause one-time messages to resend debug-mode(boolean): <Should we pring debug to server.log(true/false)?> NOTE: Look for fine and finer level log messages in server.log messages: Add messages below this, see below
Messages config overview
<message label>(String, req.): message: <Message to send>(String, req.) delay: <Delay to send message on in secs>(int, optnl - default 0) repeat: <time between repeat sends in secs>(int, optnl) includesperms: (String list, optnl) - <only send to those with this perm> - <and this one> excludesperms: (String list, optional) - <don't send to those with this perm> - <and this one>
Default/Example config
auto-reloadconfig: 20 debug-mode: false messages: default1: message: Repeating message! delay: 15 repeat: 60 default2: message: Repeating message for those w/ build perm delay: 30 repeat: 60 includesperms: - permissions.build default3: message: One-time message! delay: 45
Project & Source
See our project page for activity and source instructions.
@itsmei123
Color works fine just don't use the & use the native minecraft symbol
I am using Linux and the colour system is not working. Please fix this I feel it is one of the most important parts!
Thanks
@RowdyKingDippy
'/simpleannounce reload' exists to reload
Something like /sa reload would be nice!
@taylorjb
I'm using your example:
And get this:
Plugin version 0.5.2 and craftbukkit 1772
The only thing this plugin is missing is coloured text
Please add colours such as &a,&7,&e such and such
Color would be greatly appreciated. Should of been in the initial release :)
I see you are already considering it, but please add the ability to use colors. Can't use § in Ubunutu.
Did someone figure out if the §(color)-code works on OpenJDK or if it's a problem of Linux?
@Folas1337
Does work on linux...running it on my server, with the Ubuntu 11.10 OS
option for random announcements. So that people can see many different messages at set times and not the same.
§e Does not work on Linux. I'm not sure if it's caused by the OpenJDK or that linux doesn't like it, but you could really implement the &x-Code. I'm gonna open a ticket because of that if you don't mind :D
@taylorjb
The only reason why I said it was hard to find was because I am on a Mac :P , it's probably easier to find on a Window's OS. Edit: When i add the "§0" it doesn't show colors :(
@Lars1011
Created a ticket for it, if you care to follow. http://dev.bukkit.org/server-mods/simpleannounce/tickets/1-intuitive-color-codes-in-messages/
@taylorjb
alright, thanks for telling :) , didn't know.
@Lars1011
Well I don't do anything with it, that's just the character to make colors in chat for Minecraft. There's nothing in my code to parse it. If you do a print out of ChatColor.BLUE or ChatColor.BLACK etc that is what you get. If C+P is too inconvenient for most I'll add some more intuitive codes to parse in later but not my top priority.
Thanks for the suggestion =)
@taylorjb
It took me a while to figure out how to get the "§" key, but i got it :), it would be much easier to make it "&", just a suggestion though.
@Folas1337
That would be a silly thing to suggest, then you'd have to change the delay every time you started the server to make it run at the right time.
Anyway that's a good idea, it's just a tiny bit more complicated since there is no scheduler to execute at a certain time, but it's easy enough to work around.
You should also include something like
message: Repeat this every day at 00:30
time: 00:30
I think some other plugins have this and it would be really helpful for scheduled serverdowns and announcing them etc. Just a suggestion :P Don't tell me I should use a 23 hours 45 minutes delay after restarting the server to do that. I would be a little bit complicated
@MindEngineer
In short, yes.
Bukkit permissions api does not support groups in terms of checking if a user is in a group, rather assigns users permissions based on what the "group" is in the config. Certain plugins support groups more deeply but I don't want to require certain other plugins to be present for this to be used, so instead you can add a list of includes and excludes to make it "group specific". This also allows some alternative ways depending on what you feel is simpler. Another way to do it would be to invent permission nodes for groups like 'group.user', 'group.mod', etc, and have includesperms have that permission. Also, you could make permissions for a message like 'message.donate' and put that in all groups you wish to receive the message and includes perms would again have that permission.
You can do as many permissions as you want, for example:
and it would only send to people that satisfy all of those.