Ok so I can preload haks using my patch folder or my using the custom content tab in the toolset.
I have started playing around with the patch folder and so far I kinda like using haks this way.
Which is better to use and why?
Edit: Oh and is there still a limit with haks when using the patch folder?
The patch folder method is for patches and overrides. If you are using new content, you have to assign it to your module instead of putting it in the patch directory. If you don't do that, other people will not be able to play your module and won't even know which haks are missing to play it.Ok so I can preload haks using my patch folder or my using the custom content tab in the toolset.
I have started playing around with the patch folder and so far I kinda like using haks this way.
Which is better to use and why?
Edit: Oh and is there still a limit with haks when using the patch folder?
Ok I think I get it now.
If I use the patch folder then the person who wants to play my module will need to have their patch folder set up to match mine? Which will effect other games they play as well.
However if I use module CC Tab then it will just use the haks in their hak folder and they can still have what files they want in their patch folder. So they can use their own overrides if they so wish as well.
Or
Will it still work if they just have the haks in there hak folder, but when they try to log into the module it will not tell them what they are missing?
Patch HAKs should only contain resources that override default/Bioware resources. You can put resources which extend the game in Patch HAKs but its not recommended. For that stuff you should associate the HAKs with your module.
In short, Patch HAKs are for players only because a player can put whatever they want in their own Patch HAKs.
Module HAKs are for builders.
Retour en haut