CraftBukkitUpToDate

Keep your Server/Plugins up to date

After the plugin detect a new build, it download to bukkit_update in the main-Folder. After that you must stop your server and copy the craftbukkit.jar from bukkit_update to your main-Folder.

After Version 1.4 I support plugins if a new version found it download to build_update/plugins. After that stop your server and copy/move the new files to your plugin-Folder

This is no autoupdater, it only download the new Version do the update-Folder, the user have to copy the files. On this way, he know which plugins he update and can check if he like to update.

I recommend to save your old craftbukkit.jar/plugin before update. Not all builds from CraftBukkit work correctly.

Features

Download the newest build to build_update Config-File in plugins/CraftBukkitUpToDate/CraftBukkitUpToDate.properties

to enable/disable automatic download
updateChannel (to choose between rb, beta or dev)
set craftBukkitName (Default: craftbukkit.jar)
deactivate pluginLog
deactivate craftBukkitUpdateCheck
blacklist to add Plugins, you don't want to update (blacklist=test1.jar;test2.jar)
deactivate automatic pluginUpdateCheck
deactivate serverLog if new Version available (broadcastOnlyToOps=true) Check for update in a configurable period.
Configurable in CraftBukkitUpToDate.properties in milliseconds lowest value is 24 hours standard is 24 hours Broadcast if new update available (To all Ops, or via Permissions).
Configurable in CraftBukkitUpToDate.properties default value is true

Command to start plugin-Check, to start type /uptodate plugin

Command to start the update-Check, to start type /uptodate update

All commands work also at Server-Console type only craftbukkituptodate or uptodate without /

Automaticly download new updates for Plugins

Download new updates in build_update/plugins
plugin.properties with links to the plugins, this one download automaticly if a new one at my server

Pail Gui-Support check Thread for more infos

Permissions

Permissions/GroupManager is optional else only ops can use the commands. Available permission nodes are (case sensitive):

craftbukkituptodate.broadcast - these users get a message if a new build available
craftbukkituptodate.plugin - these users can use plugin-Command
craftbukkituptodate.update - these users can use the update-Command

Automatic update

For Linux-User, if you like to move your new plugins automaticly, try the script from Myx0x3: http://forums.bukkit.org/threads/ad...ugins-up-to-date-400.5026/page-10#post-122380

or for more features use the one from Tealk: http://dev.bukkit.org/server-mods/linux-server-startscript-menu/

or use the Bukkit-Build-In: You can configured it by yourself, all you must do is to open the bukkit.yml and change the update-folder to ../bukkit_update/plugins. I don't recommend this, because all plugins updated automaticly without any user-interactions.

My Plugin didn't supported, how i get it to work with CButD?

There are three ways, you have to make only one of them:

1. Add it to http://dev.bukkit.org/. Your link should be like the jar-File-Name if your jar-File example.jar your link on dev.bukkit.org should be http://dev.bukkit.org/server-mods/example/. If not no problem you have two other options:

2. Add dev-url to your plugin.yml this should look like : dev-url: http://dev.bukkit.org/server-mods/example/, please replace the url with your one, else it didn't work. Also you should know that only dev.bukkit.org-Urls works.

Here is a example plugin.yml:

name: Your name
main: Your main class
version: Your version
dev-url: http://dev.bukkit.org/server-mods/replace this with your url of dev-Bukkit/
commands:
    your command:
        description: descrition
        usage: /<command> <function> [buildnumber]
        aliases: [alias1, alias2]

3. If option 1 and option 2 didn't work for you let me know this and I add it to my plugin.properties. Please remember I only support dev.bukkit.org-Plugins.

Also you should know that your project at dev.bukkit.org should contain file-Downloads, else I have no chance to check for updates and download the newest version.

Forum

Need help or have any questions use the Forum: http://dev.bukkit.org/server-mods/craftbukkituptodate/forum/

FAQ

Did the plugin.properties update automaticly?

Yes, if a new one available it update automatic.

Did you download all plugins every time to check for updates?

No, I use the rss-Feed of dev-bukkit

Do you automatic update my plugins?

No I'm only download the new version to bukkit_update/plugins you have to copy them to your Plugin-Folder. I will never implement a autoupdater, you are the Admin and you have to choose which plugins you like to update. This is only a little help to do this.

How can I choose if between recommend and beta version?

In CraftBukkitUpToDate.properties set recommendedBuild=true, if you like the recommend Build, or recommendedBuild=false if you like the beta-Version.

Now that Bukkit supports a plugin update folder, will CBUTD add support for it, so we are able to run a /reload after CBUTD runs and have the updated plugins load?

Not by default. But you can configured it by yourself, all you must do is to open the bukkit.yml and change the update-folder to ../bukkit_update/plugins. I don't recommend this, because all plugins updated automaticly without any user-interactions.

You must login to post a comment. Don't have an account? Register to get one!

211 comments
1
2
3
6
9
12
15
18
20
21
22
Next →

- Reply
- #220
NoahDTheHorse May 21, 2013 at 01:07 UTC - 0 likes
please update to 1.5.2 r2

Noah David
- Reply
- #219
kreezxil May 14, 2013 at 15:59 UTC - 0 likes
I have a feature request:

Can you make it so that it can also check an another directory of plugins?

Reason is that I have a disabled_plugins directory that I store plugins that have begun to malfunction in. Having the ability to check that folder as well would make checking on if those plugins have been updated and ready for new testing a breeze.

You could make that a configurable option so that only those who need the power to do it can.

Cheers and awesome plugin!

No Babies is a Craftbukkit 1.5.2 server featuring a mature staff. Our goal is to create a server-side version of FTB. Emphasis is on player enhancing plugins. Try us out at 69.162.69.10:25565
- Reply
- #218
parisfuja May 14, 2013 at 00:09 UTC - 0 likes
Awesome plugin!
- Reply
- #217
14manj01 May 13, 2013 at 02:14 UTC - 0 likes
Works with SpiGot 1.5.2

Last edited May 13, 2013 by 14manj01
- Reply
- #216
skymasterbest May 07, 2013 at 22:46 UTC - 0 likes
Update to 1.5.2
- Reply
- #215
mdp123 May 01, 2013 at 17:07 UTC - 0 likes
Any chance an update is coming soon? I just updated to the latest dev drop 1.5.2 and getting lots of errors for the craftbukkitupdate plugin.
- Reply
- #214
TheMasterWolf Apr 29, 2013 at 16:56 UTC - 2 likes
Update 1.5.1, please !
- Reply
- #213
FateAverie Mar 27, 2013 at 02:53 UTC - 1 like
@hardwarewizard: Go

I agree, why should we be limited to using the command manually only every 24 hours when the reason bukkit had to many connections was because the automatic update check cooldown was every hour or so, having a 24hr cooldown on the automatic check is perfectly fine, but don't restrict the manual one as well.
- Reply
- #212
hardwarewizard Mar 17, 2013 at 12:40 UTC - 0 likes
/uptodate plugin
tells me it has been run less than 24hours ago
(not good after an update and everything is broke)

and bukkit's request that there be a 24hr limit should only apply to an automatic process.
IMHO if their server can't hack it they need an upgrade.

/uptodate update
works fine
- Reply
- #211
NoFear13 Mar 17, 2013 at 11:53 UTC - 0 likes
@hardwarewizard: Go

Command to start plugin-Check, to start type /uptodate plugin

Command to start the update-Check, to start type /uptodate update