Running Minecraft 24/7 at the moment either requires fiddling with things some people shouldn't be fiddling with, losing any console access or setting your machine to automatically log in and run one of the many wrappers around. I wanted Minecraft to run as a Windows service so it was always on, didn't need anyone to log into the machine and kept itself up to date.
So I am making "Yet Another Minecraft Server"
The core features of YAMS are:
- Installer which includes downloading latest Minecraft server
- Runs itself as a Windows service
- Opens firewall ports automatically and closes them again when not needed
- If UPnP router is available, will try and forward ports
- Includes free yams.in dynamic DNS so your players don't need to know your IP
- Detects a Minecraft server crash and automatically restarts
- Runs multiple Minecraft servers within it's service, no need to log on and start manually
- Checks dependencies on install and guides through installing any requirements
- Provides admin web interface for sending console commands and splits chat messages out
- Right-click menu for easily managing players
- Logs everything to a database
- Back up your servers to your own schedule with the job engine
- Map your server on demand and to a schedule with Overviewer
- Generate images of your server with c10t
- Serve the output of renders on a built-in webserver
- Can run Vanilla, Bukkit or the weekly snapshots.
- [DLL] New telnet/terminal interface
- [DLL] Fix bukkit updates failing if server was running
Documentation is being expanded upon as and is contained on the GitHub wiki for the project
See the planned features page for what is nearly, will, may and will never be included in YAMS. Also keep an eye on the version history for what's released and what's upcoming.
There is a setup build on the website, there is a small issue in the dependencies checker where if you don't have Java installed, you can't run the Java installer until you have finished YAMS setup, just click continue and install Java afterwards. This is only because MS's setup packager doesn't seem to allow you to run a program after install, only during. I will repackage the setup with InstallShield when I have time.
TL;DR - Simple way to run your own server and share it with your friends.