Modding:Dependencies: Difference between revisions

== What is a Dependency? ==

A dependency when it comes to the game or modding is to tell the game that your pak depends on something from the referenced pak. So when we want to reference an asset from a defined pak say from the SharedDev.pak and we make our pak and the asset doesn't show, well if we were to make our mod have the dependency of the SharedDev.pak it will tell the game that is where some of the assets referenced are coming from.

== Why do we want to use Dependencies? ==

So if we make a head mod that references a vanilla ID and the head shows up checkered we can fix that "bug" by making our mod dependent on the pak that material comes from.  

So breaking this down using heads if we want to use vanilla assets for our heads and were to use the dependency of the pak our textures and materials are in. This would mean we can reference their ID's without having to include MaterialBanks/TextureBanks. So when wanting to use vanilla materials/textures we only need our VisualBank entries.

Or if we want to make a class mod and want to add an ability from another mod, after getting permission we would make our mod dependent on that mod. That way when both are installed our class mod would be able to use that ability without having to actually include it in our mod itself.

In this extract from the games GustavDev meta this is saying the GustavDev pak is dependent on the SharedDev pak and the Gustav pak

So using the example above the image below expands upon that and shows what lines are used from the original pak to make the dependencies section. You may need to open the image to see it in its full size.