The project directory in the sources zip.Versions (v1.0.0) in the download url for the release that we would have to change every time, so this wouldn't work.I started thinking maybe we could use releases in Github for this. However, the downside to this was that this was not a good solution for a team working on a resourcepack that needed to be constantly uploaded to the server so that everyone could see the changes live (even though at the moment, we are only in the development stage). This was a quick and easy solution, as you could get the share link from Dropbox, and add it to your server. Anyways, with the addition of Actions to your team's workflow, you can make the process of editing a resourcepack, automatically building it, and shipping it to your live production Minecraft server so very easy.īefore this switch, we (being SupremeObsidian) were using Dropbox to host the resourcepack.
