Currently, the server resourcepack is handled by letting the server owner upload a resourcepack to a third-party site like Dropbox and letting him point the resource-pack url to the Dropbox url. This system usually works, but also causes problems:

• It is some effort
• Webcaches can be annoying
• I don't like relying on third parties
• It is impossible to update the resourcepack without a server restart
• This won't work for servers where people can join with different minecraft client versions (since each client would need a different resourcepack...)

We could improve this by using the Bukkit API to send resourcepacks to players rather than relying on server.properties. But, the hardest part is that we still need to upload the resourcepack to some public url. For this, I have a dirty solution in mind: we could finish my work-in-progress https://github.com/knokko/Multi-Purpose-Server to use the server itself as the resourcepack host. This will require quite some experimentation and is generally a big change of flow, so it won't be quick or easy.

Alternatively, I could buy a VPS and write an application that acts as resourcepack host. I would also write an additional plug-in that integrates with this resourcepack host. This plug-in would simply pick the resourcepack from its data folder, so installation would be much less annoying for users.

Wait, I just realized that this is becoming a duplicate of #74 , so I will close this issue.