AutoSave
AutoSave - Automatic World Saves
AutoSave IS NO LONGER UPDATED AND DOES NOT WORK
Yup...time to move on people. Seriously...don't ask. Want to continue AutoSave? Feel free! The source code in all its awesome glory is available on Github so go grab it and no complaining! Or you could just learn how to program and also...no complaining.
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.
How does AutoSave work?
AutoSave works in the background on a server. The plugin ONLY performs a save on all the Worlds and Players on your server. It does not perform backups. Why would you want this? It makes it easier to ensure your world is saved frequently enough that a crash will have only small effects upon your players!
Features
- 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
Reporting
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 "var.report" in the configuration file, or "save report [off|on]" from console.
Problems?
Bug?
If you've found a bug, please report it via a Ticket and provide full details. Any bug reports that are not complete or are not reproducible will be closed. Please provide as much detail as possible!
Suggestions?
Need, want, or desire a feature not currently in AutoSave? If so, please fill out a Ticket and provide full details. Please remember that not all suggestions will be implemented and how they are implemented is up to the developer. Alternatively you can create a fork of AutoSave on Github and submit a Pull Request with your changes!
Need Help?
If your having issues with AutoSave that are not bugs, make a thread in our forum.
Important Links
- Commands
- Performance
- Configuration File
- Frequently Asked Questions
- Changelog
- Github
- Development Builds
@cerea1 http://pastie.org/3446174 Could you please update for the new bukkit R5 build?
Does this plugin need to be/or has it been updated to the new bukkit events system?
Permissions do not seem to work... =/
(Using PermissionsBukkit v1.2)
The "infinite loop fixed", does this refer to something in 2.x or is it an update in 3.0.0 bx? I already have a beta build of 3.0.0, but after like three days of operation. I get "net.minecraft.server.WorldConlictException Failed to check session lock, aborting" and then after a little while "too many files open". Is this related to your plugin?
Can you add a feature, like in older versions, when the last user left the server it saves?
Same thing here, "broadcast: false" doesn't work.
I can't believe... YOU'RE BACK!
@FeedDante
tried having an empty broadcast message, like "" ?
Excellent plugin! thanks
Any way to configure this to output to the console ONLY and not message any players? In the config I set both broadcast and report to false; makes no difference, I still see messages in-game.
@cerea1
Nice to see it is still being updated :) Thank you.
@andune
Awesome ;) If you happen to know of a server that would be willing to run some test builds I'd appreciate it. I don't run a server as of now so it makes experimenting hard!
@cerea1
Yep I've contributed to several github projects and all of mine are hosted there as well. I wasn't sure if you were still around.
Regarding GPL2, the reason I did not offer to release it to other people is exactly that. I maintain enough plugins and didn't want to add another, so before forking and publishing, I was secretly hoping you were still around and would come back to publish a fix. :) (and thank you for doing so!)
GPL2 does allow me to maintain and update my own copy without restriction, for which I am thankful that you chose to publish open source to begin with. Probably wouldn't have been that much extra effort to fork/gitpull request, but as I wasn't sure that you were still around (I see a lot of dead Bukkit projects), I opted to fix it locally since that was easier. Glad you are still around and if I'm ever on the bleeding edge of making a fix for this plugin, I'll be sure to fork/gitpull in the future. :)
Thanks again.
@XeonG8
Yes, it is safe. Tested it prior to release. Please report any issues (not expecting any).
OK so just to confirm that means your 'v3.0.0dev-b26' update is safe to use with cb1783?
I wasn't to sure about it before.
@XeonG8
It was an oops which has been fixed, built and released here (and on our build servers). The phone home (reporting) is well documented but was accidentally omitted from this page when it was created during the move from the forums to Bukkit Dev (here). When I was alerted to this mistake it was promptly corrected. These stats help me understand what the common environments are and they are completely optional, and easily done so. Read the section above titled "Reporting".
Also...hi? Developer reporting?
@andune
Thanks that explains a lot actually.. didn't read it before :) Hopefuly the author gets back as it is a good plugin.
Until then I wouldn't mind your phone-home crippled version that works, stuff like that should be opt in via config anyway or at least opt out :)
@andune
Your source code should be accessible to any whom you distribute the plugin to anyways given that AutoSave is licensed under the General Public License Version 2. Additionally it is good faith to submit a trouble ticket or pull request regarding the issue.
Specifically, everything you just stated was fixed in the most recent commits of AutoSave and also is published here. You can see the commits on GitHub at https://github.com/milkbowl/autosave which is also where trouble tickets and pull requests can be made.
It is always helpful to when developers work together and I would encourage this and have with the use of GitHub. Feel free to join the development, its open!
Folks complaining about this plugin being broken, read my comment a few comments down. Yes, it's broken. Autosave has a phone-home capability and the site went dark, and now the plugin spins in an infinite loop trying to connect, crashing your server. I've fixed it locally and am more than willing to push the update to the author if he asks and wants to put out an update.
EDIT: just noticed original author commented below. Glad you're still around. If you want, I'll make a clone and send you a gitpull request. The changes are pretty simple.
Installed this plugin, reloaded server. It must have conflicted with almost every plugin because my LWC plugin stopped working, and /home didnt work for people. Uninstalled and everything is good.
EDIT: Factions territory locations were also wiped, this is on the 3.0 version. All was easy fixed from backups..but this still serves as a warning.