@henesuz....I am aware of this, but on a mod you are actively creating, any patch could affect pre-existing work when recompiled as development continues as the includes then become a part of the compiled ncs file. This is to what I was alluding to. Any existing compiled work would be unaffected. The catch occurs if you should ever recompile using the patched version of NWN. This in not to say that there will be any problems, just to say that there CAN be problems and that they may not be readily found, just a possible head ache.
Yes, I mentioned this. But as I said earlier all you have to do is recompile after uninstalling the patch. Uninstalling the patch is trivial, and recompiling is trivial. So if you don't want to bother dealing with the rare thing that you might find causing a problem, then you can solve it in a minute or two by reinstalling the 1.69 thingamabob.
Debugging does take an indeterminate amount of time, but that is only stressful if you can't just restore your module with a click of a button. Since the patch files can be swapped in and out so easily however, you always have this option.
And why is this? Because the patch doesn't break your module. It doesn't do anything to your module. It impacts the context in which your module operates. And it is trivially simple to restore to the 1,69 state and the data in your module is unimpacted.
Which also means that the CPP is less intrusive than importing an erf with scripts into your module.
It boggles my mind that this simple fact alone doesn't dispel the "scary patch" nonsense. Because even if the patch was poorly put together you could easily solve your problem. The thing is however its well put together which even further renders these concerns utterly bogus. Not only is it easy to test for yourself, and pose no threat what so ever to your work, but when you do test it you can see that its easy to work with. And on top of that ShadoOoW will actually work with you.
Retour en haut
