ScheduledAnnouncer
Please use the ticket link to the right for issues! ->
Accepting new feature requests! Please use the ticket link to the right! ->
Scheduled Announcer is a very simple tool, which only does what's its name told us. It automatically sends a broadcast out of a list controlled by a scheduled.
Features:
- Sends Scheduled Broadcast to all Players
- Easy to configure by 'config.yml' or ingame with the '/announce' command.
- Supports colors (&1, &2... &9, &a, &b... &f) and newlines with &n.
- Supports executing commands inside Announcements. (Like "Now it will become day!&n/time day")
- Supports newest Bukkit permissions system!
Setup:
- Download the latest Release
- Upload it into your plugin/ directory
- Restart or reload your server
Or have a look at the Video Tutorial by BrandonHopkins
Configuration:
# # ScheduledAnnouncer Configuration File # ===================================== # # Don't use tabs in *.yml file! # # Please note that there is a 85 (with the default prefix) character # limit on announcements. # # If you mess this config up, feel free to delete this one, and let # the plugin create you a new one! # announcement: # Use this flag to temporary disable the announcements. # enabled: false, means that there wouldn't be any announcements. enabled: true # Set this to true will announce in random order. # 'false' will announce in sequential (one after another) order. random: false # Defines the prefix for the announcement. Use & + hex char for color codes. prefix: '&c[Announcement] ' # The time of one interval in seconds. interval: 100 # List of messages to announce. You could use color codes by using & + hex chars too. messages: - 'This is the first default announcement!' - 'Use /announce help to get info how to config this plugin.' - 'You can also configure this plugin with its config.yml too!' # Use to enable or disable the motd. motdEnabled: true # Use to define the motd. motd: 'Test announcement.'
Commands:
/announce add <message>
Needed Permission: announcer.add
Adds a new announcement with the Message: <message>
/announce broadcast [<index>]
Needed Permissions: announcer.broadcast
Broadcast an existing announcement NOW.
/announce delete <index>
Needed Permissions: announcer.delete
Removes the announcement with the passed index.
/announce enable [true|false]
Needed Permissions: announcer.moderate
Enables or disables the announcer.
/announce interval <seconds>
Needed Permissions: announcer.moderate
Sets the seconds between the announcements.
Calling it without an interval to set will return the current interval.
/announce list
Needed Permissions: announcer.moderate
Lists all announcements.
/announce random [true|false]
Needed Permissions: announcer.moderate
Enables or disables the random announcing mode.
Only calling /announce random without true or false, will return current mode.
/announce setmotd [motd]
Needed Permissions: announcer.moderate
Sets the MOTD
Only calling /announce motd without string will return current motd.
/announce motdenabled [true|false]
Needed Permissions: announcer.moderate
Enables or disables the motd
Only calling /announce motdenabled without true or false, will return current mode.
/announce say [message]
Needed Permissions: announcer.moderate
Announces a message to the server without saving it to the config.
/announce reload
Needed Permissions: announcer.admin
Reloads the config.yml.
/announce prefix <prefix>
This sets a new prefix. Note that you need to place the ['s in there again. Color codes also work.
Permissions:
Only people with the permissions announcer.receiver will receive announcements, but everybody owns the permissions by default.
Source can be found at https://github.com/mjoell/ScheduledAnnouncer
Supported Color/Formatting Codes:
http://mcstats.org/plugin/ScheduledAnnouncer2
Added Metrics 4 days ago, and already that many servers. I see it in the top 100 soon!
@PluginErrorsSuck
I'm getting that too!
So as an Owner with all permissions, I receive the MOTD but my users do not. I do not see any permission that needs to be added. Is it possible to left it out??
How do I stop EVERYONE having access to it?....
@PluginErrorsSuck
remove the permission for defualts?
ether do
- -announcer.moderate
or
- ^announcer.moderate
Using on 5.152.199.138:25702
Can you make it so when it is set to Random, it can never display the same announcement twice in a row?
Could you make it so only /announce works, and not /announcer? Either that, or make it possible to have certain messages only broadcast to certain groups. Atm, we require two separate plugins for this, and commands are interfering. Thanks!
Is there any way to add mysql support? I change my announcements very often and it's will be very handy to edit them on phone/tablet and reload it using connectbot. Or maybe timed announce reloading?
OMG! Excuse me! why can players do /announce say With NO permission node for it. people come and spam and spam!
Ty for your plugin ! I have to use the version 1.6.1, because the last version bug for me. I have the "help advice" again and again and again ^_^.
@obscurehero
I thought it would be that easy, but the plugin doesn't seem to have an easy way to implement a permission for the command. Unless, of course, that was because I was looking at the code at 4AM.
@jflory7 @KIMB00P just edit the plugin.yml in the jar. That should fix the default permissions, correct?
@EpicxOzone
This did not work for me.
@mrpandagraal
It's a fix for the issue, but it's not mentioned anywhere on the plugin page that this needs to be done, so anyone downloading the plugin who doesn't read the comments won't know. We need to get the author's attention on this issue.
@EpicxOzone <- Read his comment below it is the solution
Everyone has access to /announce say
This can cause quite a scare and needs to be fixed to OP only players!
@Proeliumm
@Coro123x00
YES! I can absolutely confirm that the way things are coded into the plugin right now, ALL PLAYERS HAVE ACCESS TO "/announce say <message>"! What the plugin developer has done is allow it so that the "/announce say <message>" command defaults to non-OP players, thus giving anyone access to use this command.
I am going to message all of the developers to change this ASAP, because I've had all sorts of players coming into my server using this command, and it's been an absolute hell trying to figure out what was going on.
best Announcer that I have tried. keep up a good work
I have fixed this problem by doing this in my permissions file (I use pex)
@Proeliumm
No all players have access to /an say, which broadcasts, how do I disable this?