DragonAnnouncer
This project is no longer being maintained. While the latest release is (hopefully still) stable, please look at this link to see similar plugins like DragonAnnouncer - http://dev.bukkit.org/bukkit-plugins/bar-api/#w-plugins-using-bar-api
Dragon Announcer:
The plugin works just like you'd expect. Instead of having a message be broadcast to the chat (where it is soon covered in other messages), it'll appear on everyones screen, for a set amount of time, every set amount of time. You can add, remove, and edit messages in the configuration file (if you feel like it), or use commands in-game (meaning you don't have to reload the plugin every time).
Requirements:
At the moment, because I wanted to get this plugin ready for you guys a.s.a.p., I decided to make use of the BarAPI. Therefor, you will be required to download and install the BarAPI plugin. You will not have to configure anything, or do anything with the plugin though. Note that the requirement for the BarAPI plugin will be removed in an upcoming version!
Features:
- Broadcast per world on an easy-to-configure schedule
- Instantly announce a message to a world
- Edit information form the config with a simple command
- Color Code Support
- Metrics Support
- Updater Support (Coming Soon!)
Installation:
- Drag and Drop the plugin into your plugins folder
- Drag and Drop BarAPI into your plugins folder
- Start / Reload / Restart the server
- Edit the configuration file / use the in-game commands
- Reload / Restart the server if you edited anything in the configuration file
Commands:
Note, instead of /dragonannouncer you can also use: /dragon , /announcer , /announce , /da , and /dbroadcast
/dragonannouncer help
/dragonannouncer addmessage [duration] [world] [message]
/dragonannouncer addworld [id] [message]
/dragonannouncer delworld [id] [world]
/dragonannouncer editmessage [id] [message]
/dragonannouncer editduration [id] [duration]
/dragonannouncer getids
/dragonannouncer getduration [id]
/dragonannouncer getworlds [id]
/dragonannouncer worldannounce [duration] [world] [message]
Permissions:
dragonannounce.help
dragonannounce.addmessage
dragonannounce.addworld
dragonannounce.editmessage
dragonannounce.editduration
dragonannounce.getids
dragonannounce.getduration
dragonannounce.getworlds
dragonannounce.worldannounce
Example Configuration File:
# Main Configuration File # DragonAnnouncer by: AnUnknownMiner # Now for 1.7.9! # Interval (time to wait in between announcements (in seconds)!): interval: 60 # Startup Delay (time to wait before the plugin starts broadcasting (in seconds)!): # You might to have a bit of delay to help with lag. startup-delay: 2 # If a player joins when an announcement is already shown, should the player see it? show-on-join: true # Do you want DragonAnnouncer to send data to McStats? No personal information will be taken with it! Metrics: true # Announcements (duration = time it will stay on the screen, worlds = the worlds it will be visible in!): announcements: 0: message: 'DragonAnnouncer Plugin by AnUnknownMiner!' duration: 5 worlds: - world 1: message: '&4With &6colour &acode &9support&7!' duration: 10 worlds: - world 2: message: '&aSupport this server by becoming a &bDonor&a!' duration: 30 worlds: - world
This plugin uses Metrics, a free and open source statistics documenter, all the information gathered can be seen at http://mcstats.org/plugin/DragonAnnouncer
Feature Ideas:
- Remove BarAPI Requirement
- Ability to broadcast a specific message in the configuration file
- Ability to see the remaining time for a broadcast / break
Source Code:
https://github.com/AnUnknownMiner/DragonAnnouncer
Deveopment on hold! I'm sorry to announce, but another project has come to me, that I really need to finish before I am able to continue working on this. I should be able to continue working on this plugin in about two weeks!
@BeastMC No I do not, nor will I ever. I've tried GitHub once, and I didn't like it. Once my website is updated, downloads will be posted there as well.
@TheMcScavenger
Do you have a GitHub or something we can compile it from outselves? I hate having to wait for BukkitDev approval to download fixes/patches.
@TheMcScavenger
That's great, thanks!
@KTJx2 Like I said, IMO it's not needed, but I'll take it into mind.
@zedadiaswick What a list, great ideas, thanks :)
Interval ignores duration: Known bug, should be fixed in either 1.0.2 or 1.0.3
Listed Announcements vs. Quickannounce: Hmm, good idea. I'll get working on that :)
Console: Yes, this is indeed a bug. It should be fixed in either 1.0.2 or 1.0.3
Randomised: I've never really been a fan of randomising things on servers, if more people request it though, I'll add it.
Show on join: I've actually already added that, but I forgot to add it to the ideas list. It'll be implemented in 1.0.2.
Broadcast [x]: Will be added in 1.0.2
Seeing remaining time + next announcement: Will be added in either 1.0.2 or 1.0.3
Hi there, just loaded up the plugin on my test server and am loving it. I have found a few issues with it (as far as my own use cases go, atleast):
Interval ignores duration; The period of time between messages should be interval+duration of previous message, so an interval of 30 seconds following a message with a duration of 60 seconds should not cause the second message to replace the first before the duration period has ended.
Listed announcements should not cut out quickannounce messages; if a quickannounce has been set, the timed broadcasts should pause to allow the quickannounce message to display. If an interval of 120 seconds has only counted 90 seconds, the timer should stop for the duration of the quickannounce and then resume from 90 seconds once the quick announce has been displayed.
quickannounce should work from console; I suspect this is just a bug. I get an error when I enter the command 'da quickannounce 55 &cScheduled restart; prepare for the Lobby!' into the console. Error log here: http://pste.me/t28Hk
Randomised display from announcements list; I would prefer it to display a random message from the list of announcements, rather than go through them in order. Probably best if this is a config option.
Show currently displaying messages to players who join after the message has started broadcast; if a player joins after a message has been set to broadcast, whilst the duration is counting down, they will not see the message. Would be very useful to keep just-joined players updated with important announcements. One example is announceing server restarts, normally I give a 60 second warning in the chat, but anyone who joins after that may be quite surprised when the server shutsdown. Having the Dragon Announcement display with the timer counting down to the restart would be VERY nice.
General commands for displaying announcements and seeing status of announcements; Being able to manually broadcast announcement 6 from the list, and a command to see how long until the next announcement (maybe even what the next announcement will be) would be pretty useful!
Those are my main thoughts, a few others things could be added like seperate lists with permissions as to who gets to see them would be nice. But I think the above are my core wants from the plugin. I can see this being a really great addition to anyserver, very user friendly (much nicer than spamming the chat with information players generally have to learn to ignore in order to continue chatting). Thanks for working on this!
@TheMcScavenger
"@Tunix2: Go I'm working on removing the need for /reload as much as possible, and so far, there's only one or two cases you actually need to reload it. A /da reload would be unnecessary IMO, as there's simply /reload"
/reload is bad for the server.
@BeastMC Thanks for letting me know. I'll go find the problem right now, so it'll be fixed in the next version :)
@TheMcScavenger
Server freezes up with you use /dragonannouncer getids. Here's the stack trace: http://pastebin.com/raw.php?i=DTkLv0bp
@Predaaa95 Please read the description. It clearly mentions that I'm using the BarAPI. Also, as far as I know, it's not possible to do this, and even if it were possible, I like this better myself (a nice handy time indication) :)
@cloclo8003 Thanks :)
@Bac_ Hmmm, I'll give it some thought :)
@Tunix2 I'm working on removing the need for /reload as much as possible, and so far, there's only one or two cases you actually need to reload it. A /da reload would be unnecessary IMO, as there's simply /reload.
/da reload please.
Different announcements based on permission levels would convince me to use this plugin
Awesome, that's what I was looking for!
Hello First of all I am French and I use GoogleTranslate, grieve if some words are not common in English, I found this handy plugin but I have some purple aesthetic advice to give you. To begin you should remove the bar that defines the time focus a little more on-screen message and have possibilitée add color to the text. This thank you to you for this plugin and I hope you will take my advice into account not coming up to me ...
@maxlehot1234 You can set the duration it's on the screen for per broadcast, however you cannot set custom times. If you have a scheduler (like in the Multicraft Panel) you can run the "/da quickannounce" command to announce it exactly at that time.
@PredictedPumpkin It's Christmas, and the Bukkit Dev team isn't working on approving any projects or files. I guess we'll both have to wait until they make time.
@PredictedPumpkin The Hive may have something like this, but it's not this one. I don't own the Hive, I don't even play on it :)
TheHive has the plugin are you the Owner?
If so can we meet on the Hive
pleeaaaaaaaaaassssssssseeeeeeeeeee put link up or send me it in comments I really want a announcer plugin that doesn't get filled up by chat
Is it possible to add broadcast time for each announcement?
EX: i have 3 broadcast, the first one show eache 120 seconds and the second one show each 2000 second. The third one show in the chat at 11H45 PM (15 minutes before the server shut down for planned restart)
If you can, it can be awesome
Still not approved...
@KTJx2 That's because the Bukkit Dev Staff still hasn't approved the files after 32 hours ;)