1 items
About this mod
A framework file for my current and future Call of Duty (MW19, Vanguard, BOCW, etc) ports containing a master ESP, shared textures, and animations. Made to provide a configurable experience while also keeping file sizes low! Compatible with TTW, CaliberZL, S6S perks, and much more!
- Requirements
- Permissions and credits
- Changelogs
- Donations
One ESP to rule them all...
Say goodbye to bloated ESPs, weapons you don't want, cluttered mod lists, and huge file sizes!
Why a framework system like this?
In my time modding New Vegas and Fallout 4, I've come across two systems people use for handling large amounts of weapons, both with their own benefits and flaws. Method 1 is the more common of the two - individual releases. This style offers two main benefits - greater control over what's added to your game and reduced storage taken since you don't even need assets you don't want. However, it comes with some drawbacks - mainly ESP cluttering and overlapping files (when two mods use the same animations, for example). The former isn't really an issue in F4, but in FNV, where ESLs aren't a thing, those standalones pile up quick. Sure you can merge mods, but that has its own set of issues. The other method, which has been popping up recently, is the concept of a weapon pack. The main benefit here is that you only need to use one esp slot, but its not without issues. On some packs, you're stuck with whatever weapons the pack has, unless you want to break open and edit the mod's scripting (some mods, such as CFWR or 123456's weapon pack, solve this issue by having an ini to configure what spawns). The second issue, however, doesn't have an easy solution - the fact that even if the weapons are disabled, the textures, meshes, and sounds are still taking up space on your disk - and in some mods, they take up a LOT of your space. These factors drove me to find a better solution, which I've used here - the Framework and Addon Program.
How does it work?
When you want to start using my COD ports, you need to do two things. First, install the newest version of this framework mod, along with all of the dependencies. Second, scroll through the "Required By" section and download any of the weapons you want. If you wish, you can also download any patches for other such as GAF, CaliberZL, JSRS, or the upcoming Calibers+. If there's a mod that you'd like to see patched, feel free to leave a comment on the individual weapon that needs patched. After that you're good to go!
I don't plan on doing any Fallout 4 versions, but if enough people want it I can try.
Credits:
Activision: For all the meshes and textures ported from the COD games
Bayrain: For ideas, feedback, and testing
Conzo: For ideas, some light scripting work, and asset work
Diacute: Helping me port some stuff
Eyteen: For aWRP and fixing some assets
Lolwutyyy: For various mesh work
Milenia: For the original assets some of these use
OzzyTheRaven: Helping me with the porting process
PanzerKai: Helping me with the porting process
Say goodbye to bloated ESPs, weapons you don't want, cluttered mod lists, and huge file sizes!
Why a framework system like this?
In my time modding New Vegas and Fallout 4, I've come across two systems people use for handling large amounts of weapons, both with their own benefits and flaws. Method 1 is the more common of the two - individual releases. This style offers two main benefits - greater control over what's added to your game and reduced storage taken since you don't even need assets you don't want. However, it comes with some drawbacks - mainly ESP cluttering and overlapping files (when two mods use the same animations, for example). The former isn't really an issue in F4, but in FNV, where ESLs aren't a thing, those standalones pile up quick. Sure you can merge mods, but that has its own set of issues. The other method, which has been popping up recently, is the concept of a weapon pack. The main benefit here is that you only need to use one esp slot, but its not without issues. On some packs, you're stuck with whatever weapons the pack has, unless you want to break open and edit the mod's scripting (some mods, such as CFWR or 123456's weapon pack, solve this issue by having an ini to configure what spawns). The second issue, however, doesn't have an easy solution - the fact that even if the weapons are disabled, the textures, meshes, and sounds are still taking up space on your disk - and in some mods, they take up a LOT of your space. These factors drove me to find a better solution, which I've used here - the Framework and Addon Program.
How does it work?
When you want to start using my COD ports, you need to do two things. First, install the newest version of this framework mod, along with all of the dependencies. Second, scroll through the "Required By" section and download any of the weapons you want. If you wish, you can also download any patches for other such as GAF, CaliberZL, JSRS, or the upcoming Calibers+. If there's a mod that you'd like to see patched, feel free to leave a comment on the individual weapon that needs patched. After that you're good to go!
I don't plan on doing any Fallout 4 versions, but if enough people want it I can try.
Credits:
Activision: For all the meshes and textures ported from the COD games
Bayrain: For ideas, feedback, and testing
Conzo: For ideas, some light scripting work, and asset work
Diacute: Helping me port some stuff
Eyteen: For aWRP and fixing some assets
Lolwutyyy: For various mesh work
Milenia: For the original assets some of these use
OzzyTheRaven: Helping me with the porting process
PanzerKai: Helping me with the porting process