Jump to content

CustomPacks Suggestion


SethAten

Recommended Posts

As mentioned on IRC, I'ma post my suggestion here on the forum. Seems like the best place soo...

The custompacks should link to a yml, not a zip(though zip could be kept for backwards-compat I suppose) and an example custompack.yml is as follows:

recommended: 1.0.1

latest: 1.0.2

resources: http://mysite.com/modpack/resources/

builds:

    1.0.2:

        minecraft: 1.4.6

        packzip: http://mysite.com/modpack/modpack-1.0.2.zip

        md5: b24db5c8391ec5c5d93cd0ac083acbdf

    1.0.1:

        minecraft: 1.4.5

        packzip: http://mysite.com/modpack/modpack-1.0.1.zip

        md5: 3accddf64b1dd03abeb9b0b3e5a7ba44

Resources would be a link containing the logo and icons, the builds quite obvious, though MD5 could be optional to make it easy on people. Builds would be a single zip file, just as it is now, and the minecraft version is referenced so that techniclauncher can apply the pack to the proper version. In fact, players could also choose [modpack] versions.

Link to comment
Share on other sites

I like this. Another idea (thought maybe even harder to implement): do magnet links to packs. So that when I click a link on a server thread my browser suggests to open it in technic launcher, which then downloads the pack and installs it for the user. Probably works in Windows only, but then again that's about everyone anyways.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...