Inactive [ADMN] AutoSave v2.0.1 - Automatic World Saves [935]

Discussion in 'Inactive/Unsupported Plugins' started by cereal, Feb 13, 2011.

Thread Status:
Not open for further replies.
  1. Offline


    AutoSave is now on Bukkit Dev! Plenty of information and it is overall much better documented there than it has been here. Wiki pages really help organize all the information that is needed.

    Discuss AutoSave on Bukkit Dev and get information, files, and more from there!

    AutoSave - Automatic World Saves:
    Version: 2.0.1

    AutoSave is meant to provide a simple method to automatically save your world at a defined interval! This plugin ONLY saves to the proper world directories within the Minecraft server. It is not a backup plugin, it is meant to increase persistence and reduce the affects of a server crash.

    • Performs a world saves (same as save-all on console)
    • Repeats the above at user defined interval!
    • Warning messages
    • Multi-World Support
    • Configurable messages
    • Option to disable broadcast message
    Download The Plugin
    Source Code

    Version 2.0.1
    • Small library changes
    Version 2.0.0
    • Color Messages support!
    • Support for Multiple Permissions Plugins (natively)
    • No more version nagging
    • ASync Tasks instead of Sync Tasks (possible performance increase)
    Version 1.3.0
    • Perform save after last player leaves (quits/kicked).
    Full Changelog

    Future Release To-do List:
    • Calculate and create variable for time elapsed during save
    • Make bacon
    • Get more feature suggestions

    You can configure the plugin via an XML file located at "plugins/AutoSave/".
    • message.broadcastpre: Message broadcast to all players prior to save
    • message.broadcastprost: Message broadcast to all players after save completed
    • message.insufficentpermissions: Customizable generic insufficient permissions message
    • message.saveplayers: Customizable players save message
    • message.saveworlds: Customizable worlds save message
    • message.warning: Customizable warning message
    • Customizable value of "off"
    • value.on: Customizable value of "on"
    • var.broadcast: True or False value specifying if broadcasts should be used
    • var.debug: True or False value specifying for additional console output
    • var.interval: Number of seconds between saves
    • var.permissions: Bypass permissions entirely
    • Toggles reporting thread
    • var.uuid: Anonymous identification
    • var.warntime: n time before the save happens when a warning is broadcast to players, multiple values can be passed by separating by commas
    • var.worlds: Comma seperated list of loaded worlds to be saved. * indicates ALL worlds will be saved.
    If you want to user colors, its simple. Just use one of the following in the appropriate location (config file):
    • Aqua: %AQUA%
    • Black: %BLACK%
    • Dark Aqua: %DARK_AQUA%
    • Dark Blue: %DARK_BLUE%
    • Dark Gray: %DARK_GRAY%
    • Dark Green: %DARK_GREEN%
    • Dark Purple: %DARK_PURPLE%
    • Dark Red: %DARK_RED%
    • Gold: %GOLD%
    • Gray: %GRAY%
    • Green: %GREEN%
    • Light Purple: %LIGHT_PURPLE%
    • Red: %RED%
    • White: %WHITE%
    • Yellow: %YELLOW%
    Copyright 2011 MilkBowl (

    This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of this license, visit or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.


    Note: ALL of the below commands can start with autosave instead of save if another plugin is using the save command such as WorldEdit. This will always allow access to the in game configuration of the plugin.

    Saves the world outside of the interval.​
    Requires Permission:​
    /save help
    Displays help dialogue​
    /save toggle
    Toggles the automatic saves (turns off or on depending on current setting)​
    Requires Permission: autosave.toggle​
    /save status
    Prints status message about the current state of automatic saves​
    Requires Permission: autosave.status​
    /save interval {seconds}
    Sets or gets the interval setting in seconds​
    Requires Permission: autosave.interval​
    /save addworld [value]
    Adds world to the World Save List​
    Requires Permission:​
    /save remworld [value]
    Removes world from the World Save List​
    Requires Permission:​
    /save world
    Displays the World Save List​
    Requires Permission:​
    /save broadcast {on|off}
    Sets or gets the broadcast setting​
    Requires Permission: autosave.broadcast​
    /save debug {on|off}
    Sets or gets the debug setting​
    Requires Permission: autosave.debug​
    /save warn {seconds[,seconds]...}
    Sets or gets the warning time setting in seconds (warns users of an upcoming save n seconds before it happens)​
    Requires Permission: autosave.warn​
    /save version
    Prints AutoSave version​
    Requires Permission: autosave.version​


    AutoSave reports minimal anonymous data to provide general usage tracking. No personal or server information is ever transmitted. The following data is provided:
    • Plugin Name (this will always be AutoSave)
    • Plugin Version
    • Bukkit Version (the full Bukkit version string)
    • Operating System
      • Name
      • Version
      • Architecture
    • Java Version
    This data helps me understand the environments in which AutoSave is used within, however you are more than welcome to disable it, either via "" in the configuration file, or "save report [off|on]" from console.

    Known Issues:
    • During upgrade messages no longer are colored
      • Solution: Delete config file or add colors manually

    Permissions can be disabled by manually editing the config file and setting "permissions" to false. That will completely disable Permissions. Running AutoSave without Permissions with the value to true (default) will cause the plugin to unload itself.

    Here are the permission settings, either do 'autosave.*' or use the granular permissions below: Allows the ability to save at any time​
    autosave.toggle: Allows the ability to stop and start AutoSave​
    autosave.status: Allows the ability to see status of AutoSave​
    autosave.interval: Allows the ability to see and change interval setting​
    autosave.broadcast: Allows the ability to see and change broadcast setting​
    autosave.version: Allows the ability to see the version of AutoSave​
    autosave.debug: Allows the ability to change the debug setting​
    autosave.warn: Allows the ability to see and change the warning time setting​ Allows the ability to view the world save list​ Allows the ability to add to the world save list​ Allows the ability to remove from the world save list​
    bobacadodl, iKeirNez, Joe12o and 12 others like this.
  2. Offline


    My world got totally griefed. How can i rollback ?
  3. Offline


    I would say get BackupPlugin if you want to restore a backup. This doesn't keep copies.
  4. Offline


    Is bigbrother better than Backup?
  5. Offline


    AutoSave doesn't perform backups as per the description. As such it doesn't stop griefers since it'll just save what they did anyhow. Depending on how big your server is and how experienced you are would probably lend you to doing different solutions. You can manually copy the world folder every once in a while, or write a batch/bash/perl/whatever script to do it for you, use a plugin, or even use BigBrother (using a fancy pants database).

    As far as what is the best solution, you might want to try IRC or even starting a topic specifically about that!

    Also, I decided that I wanted to make a change so that saves only happen when players are actually on the server so I'm feeling like I'll implement that soon -- should be simple and useful.
  6. Offline


    @cereal - Does AutoSave support colour codes for the warning message? I'd like to standardize various 'server related tools' using the same colour, if possible. I tried using the § and the & characters but in both instances the warning message never showed.
  7. Offline


    I'll look into supporting it...though I would imagine it SHOULD have worked. I suspect shenanigans! I should have time tonight -- been needing to finish up some other idea's too.
  8. Offline


    Cheers, thanks. It's such a minor thing, so honestly don't go nuts in putting effort towards the feature -- I'd rather not monopolize your time for visuals, heh.

    (This is the entry I am using:

    <entry key="message.warning">&d[Server Notice] World AutoSave will commence in 30 seconds.</entry>

    so you have something to test against.)
  9. Offline


    I ended up getting the value to finally pass by using &amp;d but it didn't change the color. I'll probably just make a color variable, would probably be easiest.
  10. Offline


    That would be awesome, as I said it's totally cosmetic, so don't let this eat up any huge amount of time. I know you devs get really busy at times :)
  11. Offline

    Moo Master

    Whenver it saved for us, we'd crash. Even if it was at 60 seconds, 90 seconds. 180. or 30 minutes. The server would crash every time.
  12. Offline


    That doesn't sound very enjoyable. Could you provide more details?
    • A full server log from the start to end of this happening would be necessary to even begin troubleshooting.
    • Also can you type the command "save" into the console and does it crash when that happens?
    • What version of CraftBukkit are you using (use the "version" command)?
    • What version of AutoSave are you using (use the "save version" command)?
    That is the minimum information I would need to help.
  13. Offline

    Moo Master

    Well, there were no errors in server.log when it would crash. And the save in console is perfectly fine. I was using v531 of craftbukkit and the latest version of autosave
  14. Offline


    Well the only way I can really see whats going on is by turning debugging on, performing a manual save, and then letting the server crash and providing in entirety the server logs.
    • save debug on
    • save
    • -- now you wait for it to crash
    • provide logs here
  15. Offline


    Good work Cereal :)

    It was running on my main minecraft server but today I tried to update your plugin and test it into a test server, and so I got this error when using "/save help" =>

    16:54:26 [INFO] [AuthMe] Player WolwX logged in!
    17:02:41 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'save' in plugin AutoSave v1.1.5
    at org.bukkit.command.PluginCommand.execute(
    at org.bukkit.command.SimpleCommandMap.dispatch(
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
    at net.minecraft.server.NetServerHandler.c(
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.Packet3Chat.a(SourceFile:24)
    at net.minecraft.server.NetworkManager.a(SourceFile:230)
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
    at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.NullPointerException
    at sh.cereal.bukkit.plugin.AutoSave.AutoSave.onCommand(Unknown Source)
    at org.bukkit.command.PluginCommand.execute(
    ... 12 more
    EDIT : Ok that's corrected about the fact it work now :)
    But I still with error when trying tu use /save help :s

    Debug informations are really fine :)
  16. Offline


    Do you have the Permissions plugin as well? I recently wound some interesting code (aka...not so awesome) code regarding permissions that may be causing that specifically. I've been slowly working on the next version which should fix that, maybe in another few days I'll have it ready. Anyhow, if you don't have Permissions that would confirm my thoughts and the temporary fix could be to just try it with said Permissions. You should also be able to try it from the Console (not as a player)? That might work.
  17. Offline


    same error here !
  18. Offline


    Hello, Just to let you know recommended is now 602 of this post :)

    I have 0 complaints about this plugin saves are instant it runs wonders.

    @cereal Forgot to ping you haha :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 8, 2016
  19. Offline


    [WARNING] [AutoSave] UNKNOWN SERVER VERSION: It has NOT been tested and AutoSave MAY NOT function properly: git-Bukkit-0.0.0-609-g39996e1-b612jnks (MC: 1.4)
    Other than this, there seems to be no errors. But I just thought I'd let you know :p
  20. Offline


    I hope its really saving though haha :)

    cereal was last seen:
    Tuesday at 1:26 AM

  21. Offline


    No more bugs with the last version, and yes using Permissions plugin and EssentialsGroupManager both.

    But, there is a way to tweak your plugin ?
    When I have 50+ players online and the plugin do a save, that's result by a big freeze (between 10 and 30 sec at less) :(
  22. Offline


    Was kind of wondering if it would be possible to make the plugin send a message as the save started and as it ended? I like knowing how long the save takes.
  23. Offline


    Yup its still saving ;) Thats just there to let you know I haven't personally tested that Build on the version of AutoSave your using. Though I've been watching the changes and none of the changes since 493 and up would have caused AutoSave to not work (yet).

    I'm probably going to add the pre/post messages and calculate the time difference so you can say how long it takes which would be pretty nifty. That and I'm going to remove a ton of the administrative messages from the configuration file since it only adds to the confusion.

    I've been meaning to dive into Notch code and save per region slowly over a period of time, but its very time consuming. For now I would just use the warning message and reduce how often it runs. For now it simply saves all of your worlds (which you could possibly remove some if you have a few bigger worlds).

    Also I'm always on the IRC server if you need to get in contact with me and chat about anything.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 8, 2016
    Kane likes this.
  24. Offline


    Is it compatable with the latest stable verson 617?
  25. Offline


    You check, no spam!​
    I check, it's work on CB 617+!!!!
  26. Offline


    That's what I must do :(

    Another tips to add some little better things to your plugin :)

    Can you add multiple line to avert before the automatic save ?
    <entry key="var.warntime">60,30,5,4,3,2,1</entry>
    For exemple

    And can you add a system of cron save ?
    <entry key="">00h00,6h,12h,18h</entry>
  27. Offline


    Is there a fix for this on 617?
  28. Offline


    Just leting people know, This works with 617,

    It might say the following but doesn't mean it wont work, I am running it now on my server that has Craftbukkit 617

  29. Offline


    I love your plugin, i know this works with 617 but is there anyway u can finish updating it so it dose not give errors
  30. Offline


    As far as the warn time, yea...that is incredibly simple. Just didn't occur to me that you might want multiple times there. I'll add it to the list!

    As far as the cron save, could you elaborate? Thats not in cron format so its a bit misleading anyways. Are you asking for a way to save at arbitrary hours of the day such as in your example it would save at 00:00, 06:00, 12:00, and 18:00 (in real person time?)?

    And yes, I've been busy with school projects but I should be able to mush a minor update quickly to address that for you guys!

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 8, 2016
  31. Offline


    After a server restart /save help - is sending an internal error ^^^ not sure if thats the same message as before

    Also if its tested and works for 617 - please update the first page stating so to not have anymore confusion :)
Thread Status:
Not open for further replies.

Share This Page