Unofficialcrusaderpatch: Seperated AIV-Patch

Created on 15 Apr 2019 · 1Comment · Source: Sh0wdown/UnofficialCrusaderPatch

Hey,
since I had seen now many new people presenting their own castles for AI and we already have some in the patch I wondered if we could maybe outsource the AIV patches to another patch program. I would would be glad if we could add things like

preview pictures of the castles
option to mix up the AIV: Sometimes I do not want every AIV of someone. So e. g. if I want Evrey's Frederick, PitchNeeded's Pig, Tathas Wazir, original Saladin, historical Nazir, ... it would be much easier for me to mix that up if we would have an option for that (like "just install emir castles")
an option to include my own small castle creations into the downloaded program so I can switch easier between them and others. Would also be more useful since we now got the AI creator and I myself am also switching around castles for my own AI
AI got a castle preference (e. g. wolf often likes to build his small castle with 2 Towers but I nearly never see some of his other castles). If that is connected to the name of a castle: an option to switch names of the castles (sultan1 to sultan2, ... sultan8 to sultan1) so we can see other castles more often

I thought because of the mass of new castles an extra AIV-patch would be nice so the original patch stays clear and doesn't get too huge. The small description for every AIV that we also have right now in the patch should stay of course.

Source

Halbarad1

👍5 ❤2 🚀1 🎉1

Most helpful comment

Pure AIV patches, pure AIC patches, and new lords. Yes, in the long run, it would be good to have a separate "community content" tool that acts as a package manager. Ideally it would be able to:

... easily add more community content via a config listing on GitHub where modders can file merge requests to add their stuff.
... detect Git dependencies (GitHub for my mods, for example) and automatically update git submodules if used. But better just fire up a git client on the user's machine to pull the master branch.
... never allow unencrypted or weakly encrypted network connections, no opt-out.
... select only parts of distinct mods. Like "grab the castles from Evrey, except for Marshall, who's grabbed from Tatha, and the Abbot, who is Firefly vanilla", or "take the AIC from Kimberly, but override the Sultan with Evrey's AIC mod", etc.
... override and back-up other assets like TGX and GM1 files for new lords.
... use a local directory as a non-public mod for private experimentation.
... remember all changes done.
... allow to have multiple different remembered change sets. I.e. don't hard-code config file paths.
... update all files based on the remembered changes.
... most importantly: Be written in a language and using APIs that are easy to compile on Linux, pretty please.

Evrey on 16 Apr 2019

👍3

>All comments

Pure AIV patches, pure AIC patches, and new lords. Yes, in the long run, it would be good to have a separate "community content" tool that acts as a package manager. Ideally it would be able to:

... easily add more community content via a config listing on GitHub where modders can file merge requests to add their stuff.
... detect Git dependencies (GitHub for my mods, for example) and automatically update git submodules if used. But better just fire up a git client on the user's machine to pull the master branch.
... never allow unencrypted or weakly encrypted network connections, no opt-out.
... select only parts of distinct mods. Like "grab the castles from Evrey, except for Marshall, who's grabbed from Tatha, and the Abbot, who is Firefly vanilla", or "take the AIC from Kimberly, but override the Sultan with Evrey's AIC mod", etc.
... override and back-up other assets like TGX and GM1 files for new lords.
... use a local directory as a non-public mod for private experimentation.
... remember all changes done.
... allow to have multiple different remembered change sets. I.e. don't hard-code config file paths.
... update all files based on the remembered changes.
... most importantly: Be written in a language and using APIs that are easy to compile on Linux, pretty please.