tool Infinity Auto Packager - automatically generate mod packages when you publish a release

[Jarno Mikkola]

1 hour ago, lefreut said:

I like it better with a lowercase 's'. But it's not a huge deal anyway

To me it is, and YEAH. As in, this is a hill to die on. LOWER CASE EVERY LETTER ! Why, cause there are OS'es that are file case sensitive. You really want to fuck that up with a file tool ?!? WTF !

[Angel]

On 1/4/2021 at 7:45 PM, Jarno Mikkola said:

To me it is, and YEAH. As in, this is a hill to die on. LOWER CASE EVERY LETTER ! Why, cause there are OS'es that are file case sensitive. You really want to fuck that up with a file tool ?!? WTF !

It's not often, but for once Jarno and I agree completely.  MacOS- and Linux users like myself do not like mixed-case filenames at all.  If a mod claims to be MacOS- and Linux compatible, all mod files should be kept in lower case!!

Edited January 5, 2021 by Angel

[AL|EN]

The description was updated to reflect that the zip package always contains the latest official WeiDU version from https://github.com/WeiDUorg/weidu/releases, at the time when it has been created.

Edited April 19, 2021 by AL|EN
typo

[AL|EN]

IAP was updated to fix edge case was a mod has multiline comments with "VERSION x". Now multiline comments are also ignored during getting VERSION value.

Edited June 26, 2021 by AL|EN

[AL|EN]

IAP was updated to fix annoying inconvenience of .iemod package files having no default Linux permissions. This happens only when 'unzip' command was used for extraction, using graphic file manager of popular Linux distribution like Ubuntu didn't face this issue.

No action are required from modders as new mod release will create .iemod packages without above inconvenience. This is not really necessary but If you really want, you could regenerate .iemod packages of your mods that won't have new release in foreseeable future. Go to your GitHub repository, open "Actions" tab, you will see the list of "workflow runs". Then click on the latest workflow run and at the top-right there will be a button called "Re-run jobs" (if you don't see this button, it means that the workflow was expired and cannot be run again). Click on it and choose "Re-run all jobs" from submenu. Packages for the latest release should be regenerated.

Edited July 13, 2021 by AL|EN

[AL|EN]

IAP was updated to remove warnings about deprecated 'node 12' and 'set-output' command . No action are required from modders.

EDIT: When creating a new repository, you might want to check 'Workflow rights' from the first post. No longer needed.

Edited October 4, 2023 by AL|EN

[AL|EN]

IAP was updated to remove requirements of changing setting for "Workflow permission" since too many people face this issue because of GitHub defaults.

No actions are required from modders as long as the latest version of IAP will be used when creating new repositories.

[skellytz]

Would it be preferable to make the package name default to the mod TP2 name (without setup-) rather than the metadata mod name? For example:

sagea4a/sagea4a.ini -> Name=Sage Advice for Adventurers

sagea4a/sagea4a.tp2 -> Version ~v1.0~

sagea4a/setup-sagea4a.exe

Currently, IAP generates a longish "sage-advice-for-adventurers-v1.0.zip" rather than "sagea4a-v1.0.zip"

Or am I the only one who prefers shorter filenames?

[Graion Dilach]

51 minutes ago, skellytz said:

Or am I the only one who prefers shorter filenames?

Nah, I'd prefer this being an option, but after some arguments on it, I just shrugged off years ago.

[jastey]

I prefer the longer filenames.

How would I know which mod c#sodboabri-v5.zip is supposed to be? Or acbre-vx?

Or something completely obscure like "cdtweaks"?

EDIT: Also, unless I misunderstood your suggestion, this would mean that the overall mod package would have the same name like the mod folder (except for the version number), which I think would be unfortunate.

[AL|EN]

After nearly 3 years since the creation of the first version, it's time for a major update. Thanks to recent GitHub improvements, version 2.0.0 switches to a global model: after updating the InfinityAutoPackager.yaml file in the repository, there shouldn't be a need to update it again to use new features and fixes. Multi-threading has also been incorporated to allow packages to be created simultaneously. This enhancement is only noticeable in the case of very large repositories, such as RoT. Additionally, it provides a workaround for the occasional issue where creating a new release doesn't trigger package creation. This problem has been confirmed by GitHub's team but no ETA has been provided.

2.0.0:

- Switched to a global model
- Added multi-threading
- Workaround for skipped runs
 

How to update:

- the installation/update process remains unchanged, simply replace the content of the "InfinityAutoPackager.yaml" file inside your repository with the new version

Thanks to @jastey for reporting skipped runs and @Graion Dilach for testing.

Edited October 6, 2023 by AL|EN
typos

[jastey]

Thanks for this update!

..Now it's our turn to update the repos..

[morpheus562]

Just updated all of my mods. Thank you!

[jastey]

I updated all repos I have cloned currently.

[jastey]

@Austin I updated this for BG1NPCs in SoA&ToB.