@emraldis Whenever you update, change the version number in the modinfo.json. Then submit the url to the zip as before.
I've moved this thread to Released Mods and stickied it, so it's right next to the PAMM thread. Attention modders: Start including the following parameter in your modinfo.json file: update_description (string): A description of the changes made in the latest version of this mod. PAMM does not support this parameter (it will just ignore it), but PA Hub will utilise it. It lets people see what they're getting when they are updating, without relying on reading the relevant news item. Being re-thought. But watch this space
Interesting. But I don't think I've ever seen a package format with an update in the main manifest. Would it make more sense to read a changelog? We'd need a standard for how to define an 'item'. Or maybe just a link to the changelog, and the application could display it on demand?
That could work too. I could then filter it to show just the changes for the versions between what you currently have, and the latest one. But that might/will get bloated. I'll withdraw the request to modders while this gets pondered some more
Even worse. That would make the manifest: - what it is - how it's changed - the entire history of how it's changed
Thanks for this! It would be helpful to add how to remove your mod from PAMM, and perhaps mention using GitHub releases to make zips for linking rather than the master archive.
Now that news items in PA Hub support tags, I'm adding a "news" link to content (alongside forum, install, etc.), which takes you to the news feed and filters it for just that content. As long as authors add news entries when they release mods, people can see the history of that mod's updates (much like steam).
I'm trying to get a mod published to PAMM but I'm stuck at the part of where I provide a download link to the zip. I've tried a Dropbox link: https://www.dropbox.com/s/03e4e2oam....server.gammacommanderdisplaynamefix.zip?dl=1 And a OneDrive link: https://onedrive.live.com/redir?resid=C3F79EAE94B7E784!148786&authkey=!ADqBhqzKHHjUWPs&ithint=file,zip But the PA Mod Submission page doesn't accept my links, what am I missing ?
What's the error you get? Edit: Also, you have an extra comma after "priority: 100" in your modinfo.json
I go to https://pamm-mereth.rhcloud.com/mod and enter the Dropbox URL and press go, the error says: Your mod must be packaged as a zip archive. Unsupported content type: text/html; charset=utf-8 The OneDrive link generates the same error. It is most definately a .zip file, with the proper .zip file extension, I'm doing this on Windows by the way, not sure what's going wrong.
Yeah, it's DropBox giving you the runaround with their fancy redirecting and stuff. Browsers do that transparently for you, scripts do not. I forget what the right way of doing it for DropBox was though. Maybe change the "?dl=1" to "?dl=0" or just remove it altogether. I can't remember. (By the way, remove the extra comma in your modinfo.json, eh?)
May I request removal of my mod, NavalReduxIcons, from PAMM, upon updating NavalRedux to 1.51< and removing the need for an icon mod.
May I also request... well... Idk, it seems that updating my GitHub in fact updates the mod in PAMM (because it changes the file in the link that is still used). But, it seems that updating my mod in my GitHub, doesn't change the expected version number for PAMM. How do I change the newest version number for PAMM to expect from the mod?
There is separate json on the server that ever pamm downloads on start-up. You need to resubmit for that index to be updated. The server doesn't continuously download all of the mods to check if they are updated fortunately. By the way, you can "unpublish" through the interface as well. It's a bit counter-intuitive, but you do so by submitting the mod again, so it can identify which mod you want to unpublish.
So, I should resubmit NavalReduxIcons... to bring up the screen to disable or republish... And I should resubmit NavalRedux except for version 1.61... to update or disable or replublish... Gotcha... Actually, this isn't that bad at all. Pretty cool system, thanks!
There is another counter-intuitive way to bring a mod in pamm-server to disable it, by using the identifier instead of a download url. And if someone with the appropriate English skills would like to make a more educational "package & publish" chapter, maybe people would stop considering using direct links to the master branch as a sane solution. Because I feel a bit like the guy which had to add in microwave manuals that you should not dry your pet in.
Created a 1v1 map pack and have no idea how to put it on PAMM, Here is the file, you can open it and take the pas files and put them in your systems folder if you wish.