helperkruto.blogg.se

New vegas dlc integration
New vegas dlc integration






new vegas dlc integration

The install directory and the path of the wine prefix (theĬompatadata//pfx folder). The steam_appid is used to look up the application manifest to find # Fallout New Vegas steam_appid = 22380 layers = plugins = Modifications to the game install directory, making modding easy to Modification of the game install, and does to require any Transparent to Steam and SteamPlay, does not require any direct The result of all of this is that mod loading is completely Keeps the base game install vanilla and unmodified. The writable layer is stored separately from the game install, which Worked correctly when on a read-only filesystem, some mods would Earlier layers takeĪ writable layer is then added on top (I found that while New Vegas The mod load order can be controlled by the order which theįilesystems are overlaid on top of each other. This creates theĪppearance of mods being installed manually. Placed back at the path of game install directory. Each mod is layered on top of each other, and then on This tool installs mods over top of the game directory with SteamPlay and found integrating mods and Mod Manager 2 incrediblyĭifficult and frustrating. This project came about as I tried to play Fallout New Vegas through

new vegas dlc integration

This code was thrown together to validate the concept, and hasn't beenĬleaned up or audited for correctness. A proof of concept Linux-first mod manager not intended for general








New vegas dlc integration