Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mod Packaging Guide
04-13-2013, 10:21 AM, (This post was last modified: 04-13-2013, 10:24 AM by Victor.)
#1
Mod Packaging Guide
This is the best way to package your mods, so that people can easily manage and remove them.

Code:
- mods
- (mod name)
  - packages (example)
    - (stuff)
- (mod name).bat

In the .bat file, place:
Code:
Client.bat %* --mod="mods/(mod name)"

Note that you can have multiple --mod flags.

Best regards,
Victor
//victorz.ca
Code:
Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|)
My antithesis compares favorably with _that of_ any high magnitude of pwnage. (|-me| > |-p|, |me| > |p|)
Reply
04-13-2013, 09:56 PM,
#2
RE: Mod Packaging Guide
I didn't understand much of it but ill try to make it work like this

[Image: 3SVsNlV.png]
Reply
04-14-2013, 07:27 AM,
#3
RE: Mod Packaging Guide
I don't know how it exactly work with several --mod flags. I never tried. It probably depend on the order of the flags.

With one --mod flag, when the program look for a file, it try first to find it in the mod folder then, if it doesn't find search in the regular folders.
Reply
01-05-2014, 05:40 PM,
#4
RE: Mod Packaging Guide
Another note. Mods that come first in the order overwrite those that come later.

so if you have
Code:
--mod=mods/moda --mod=mods/modb

moda would overwrite modb, so if you are adding in mods to the latest ACR --mod=acr should be last otherwise it will overwrite your mods.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)