2 réponses à ce sujet

[dan_upright]

It's been a long time since I did anything with the toolset and I know I've had this problem before but I can't for the life of me remember how to fix it.

I've got an m2da file and an ncs file, which work perfectly in "packages/core/override" but not in "addins/mymod/core/override". The addin is visible and enabled in the downloadable content menu but has absolutely no effect when I start or load a game. Anyone know what I've done wrong? I'd guess it's something in the module properties but I'm not sure.

[Proleric]

Well, we know this normally works.

Are you extending the OC or a custom campaign? The add-in module properties need to specify which module it's extending.

For example, if you've set up the add-in as a standalone campaign, it will have no impact on the OC.

Incidentally, the module override folder is normally used, unless there's a compelling reason to use core override.

Modifié par Proleric1, 01 octobre 2010 - 10:11 .

[dan_upright]

I was trying to make a change to the core rules that would apply to any campaign. In any case, I started a new module in the toolset and it's working this time, so who knows what I did wrong before.



Thanks for the help anyway