TrapModLoader 1.0.5

a tool for modpack makers which allow to change the mod loading order and prevent duplicates mods.

This mod is no longer maintained!

Deprecated since aki 2.3.1


TrapModLoader


Description

Initially, the official ModLoader from spt-aki offers a way to load mods in a certain orders using a loadorder.json inside the mods folder.

Unfortunately, the load order is applied only for the onLoad method, not at js package import.


This mod hijack the official ModLoader api and allow you to setup a proper loadorder.json

Usage

  1. Place TrapModLoader inside user/mods folder
  2. Move all other mods in user/mods/TrapModLoader/mods
  3. Run the server once to generate a default loadorder.json (in user/mods/TrapModLoader/mods)
  4. edit the generated loadorder.json as you want


Be sure to use a version >= 1.0.2

Compatibility with other mods

- For Le Kaiju Advanced modding, change the API.Override part in config.json to:

Code
"Override": {   "enabled": true,   "value": "CoreMod" }
 


Notes

  • mods can be disabled, remove the name of the concerned mod from the loadorder.json file
  • loadorder.json file can be re-generated, delete the file and run the spt-aki server again
  • at each start, some folders prefixed by `TML_DLLS_*` could be generated in your root `user/mods` directory (depends if you have installed some clients mods)


Credits

Thanks to Gave_Over for making the image ;)

  • Version 1.0.5

    • trap
    • 673 Downloads


    Changelog

    update for aki 2.3.0

  • Version 1.0.3

    • trap
    • 458 Downloads


    Changelog

    Fixes

    • prevent server to crash when mods listed in loadorder.json are missing

  • Version 1.0.2

    • trap
    • 42 Downloads

    Changelog

    Fixes

    • client mods dlls are now loaded by TML

  • Version 1.0.1

    • trap
    • 163 Downloads


    Changelog

    Fix

    • integration with AdvancedTraderFramework mod

  • Version 1.0.0

    • trap
    • 18 Downloads

  • By "Deprecated for aki 2.3.1" mean that there will be no version for 2.3.1?

    • For short, it doesn't work with BepInEx mods (included since version 2.3.1)

  • Great mod :)


    Tested:

    1) Removed a mod ONLY from the loadorder.json, NOT from the \mods folder, and it properly did NOT load, GOOD.

    2) Then added a "new" mod to \mods, loadorder.json did NOT get updated to include/load the new mod


    Just verifying that this is the EXPECTED results? Appears the loadorder.json ONLY gets generated ONCE, and then NEEDS to be deleted from and added to exclude and include mods. Any new mods need to be both 1) added to the \mods folder, and 2) manually added to the loadorder.json? Or have the loadorder.json deleted, and the server rerun to regenerate? This is fine, it's just not a "dynamic" process.


    Can the author "trap" confirm??? Thanks

    Thanks 1

    • Exactly, the loadorder.json is generated only when not exist, this is totally expected because we want to be able to disable mods (if you re-generate the file again, you cannot disable a mod via the json file)


      Hope it helps.