I host a Unix-based Minecraft server whose population is those people who like to be on the most up2date version of Minecraft as soon as it's released. I have a WebUI that updates the server jar based on the old URI scheme:
http://s3.amazonaws.com/MinecraftDownload/launcher/minecraft_server.jar
This allowed for easy, 1 click updates without me having to futz around on the filesystem. It was also easily automated using a cron script.
With the new URI structure, this is no longer feasible, as now the directory changes and so I have to go in and manually change my script. It's also no longer feasible to automate updates.
Please consider re-creating a symlink on AWS to the latest MC jar file. It would make my life (and other server admins lives) a little easier 🙂
Linked issues
Comments 3
@anon Sorry about that, but to be honest that answer is unacceptable. Where are we to post issues about the minecraft.net website? This is a pain point amongst anyone running any kind of sophisticated server backend.
Duplicate of MC-24185, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.