Community Patch Project

yes, but it needs some manual work of gettin the 2das from CEP2/Q

also, the result of the process is quite hard to read for human (all spaces replaced by single space) so its very recommended to open and resave each of the processed 2DAs by some 2DA editor.

And I would also recommend to compare result (after resaved by the 2DA editor) with original to make sure the program havent messed it up - which might happen in very rare cases such as new collumns in 2DA (known bug but original author lost source so we couldnt repair it...)

In short. If you are not an experienced user you should not care about 2DA/script merging. Thats not even a player's responsibility but a module builders' or CC packages creators' - you just have to push them to it ;).

I assume you are using 1.72 beta? That would explain bodaks. I will look into into it.

As far as classes concerned. The same problem is with any other CC with prestige classes. If you take prestige class in module A and export your character into module B, you will:

a) lose that prestige class

b) get different prestige class

and get your character bugged.

They are optional in the way that you don't need to take them, and if you won't then there wont be any compatibilty problems.

They had to be there because any custom content reusing the same lines is bugged and gets features of these hidden classes which are hardcoded. Older module-related it wont fix anything sure, but I hope future builders avoid reusing these lines.

checked this issue finally

this was reported long time ago and this is fixed in latest 1.72 beta, however the bug was in vanilla blueprint and I fixed that vanilla blueprint, but any copies made of that blueprint will have tails assigned and since thats a custom content there is no way to fix that.

If thats the case you have to fix your own blueprint copy manually - open blueprint properties go into appearance and select tail = none.

This feature is not automatic but optional and it has to be turned on first.

To do that you need use PC Widget Tool and find module switch called enable inventory of associates (or someting like that) and enable it

Here is explained how to spawn and use PC Widget Tool if you have further quzestions PM me.

There is some misunderstandement here.

First off community patch does not take 10gigabytes on hdd, thats CEP2. Community Patch is barely of size 200mb.

Second if the installer failed (which now happens on win10 as it was created before win10 came and uses librarier win10 no longer has by default) then you did not even installed it and there is nothing to backup.

Third, revert to vanilla can be done via 1.69 critical rebuild or simply by replacing xp2patch.key with the one you can download on this page under uninstall (and installer makes backup of this file as well so you just need to delete xp2patch.key and rename the backup to it). No need to reinstall anything especially if it never installed in first place as you suggest.

The auto2da merger in 1.71 had its issues and wasn't perfect, it was replaced n 1.72 by better tool from leo_x. Note you do not need to run this - thats additional feature for module builders, player doesn't need this at all.

How to fix the issue with installer is explained in first topic in FAQ section linked from this project - posting link again ´here. Or you can install community patch manually by extracting files from archive - just download one of the manual versions and unpack it in NWN folder and confirm overwrite.

CPP is compatible with everything in a way that if there is conflict (ie. file used by CPP and CEP2.6) file from custom content is used (CEP2.6). This by itself should prevent any issues but obviously for a cost of losing some of the CPP fixes/functionalities.

Problem is not on CPP part but on CEP - CEP is the one who should add CPP fixes into their 2das. not the other way around. Unfortunately I don't think that ever happens.

TL'DR: CPP is safe to use with anything including CEP 2.6

It works automatically.

1. fix for equip exploit that allowed player to equip any item into invisible creature slots and get extra bonuses

2. base models replaced with DOA Base Item Model Set

3. Helmet maxrange increased to 100 (this is for custom content)

4. Torch AC type changed from none to dodge (so you can create a offhand item thats not shield that also gives AC bonus)

5. enable to dual wield whip

6. creature skin cost changed to 0

7. in hak version you also get acces to miscleanius items at 10num stack

EDIT: also tower shield basecost increased to 1000 and empty potion and empty scrolls can now be stacked to 10 pieces and whip attack range increased a bit

The one from 1.71 has no settings unless you use linux version in which case the settings is deswcribed on the page you downloaded it.

If you use the development version for 1.72 then HERE is extended info

Short answer: no.

Longer answer: It is a patch. It will automatically fix various bugs and issues. It will work as is with any module without doing anything else than installing it.

However, since the patch takes lowest priority, if there are scripts in your modules that were changed in community patch, yours scripts will take priority. That ensures that you won't lose any functionality of your own (unlike when installing PRC/3.5rules), however that also means that unless you merge the script(s) with changes made in community patch, you might not take effect of the fixes/features/improvements made into this script(s).

Similarly with 2da. If your module uses haks and has 2das in them, unless you merge 2das with changes made in community patch you might not take effect of the fixes made.

So basically, if you want to take full effect of this unofficial patch (and that is optional - I repeat, it will work as is) then you need to do what you should do with NWN:EE -> merge changes in 2das into your 2das (NWN:EE made 2) and merge changes in scripts to your scripts (NWN:EE made none). Within the package there are resources for builders which will make this task easier, check it out. If you have further questions please write on community patch subforum in meantime I will try to prepare comprehesive tutorial for this task.

confirming as very old bug that is not acknowledged by NWN wiki neither fixed in CPP; will be probably added into next release

Hi, first of al, do you use NWN:EE ? If yes then those plugins are not a concern anymore as they don't work with EE (so far).

If you are running old 1.69 (DE) then the answer is this:

- you don't have to run that plugin, it is optional it just adds more fixes, fixed that couldn't be done without it, mostly engine/*hardcoded ones

- if you want to get those extra fixes then you need to download NWNCX package: http://www.neverwinternights.info/nwncx.htm and run game using it (use NWNCX_Loader to run nwn or alternatively patch your game using that patcher and then you just run nwmain.exe as always), if you install 1.72 then it comes with nwncx_patch.dll which you should have in NWN root directory, if so, running NWNCX_Loader will run this plugin with it.

I hope this answered your questions, the stuff around NWNX plugins is confusing and might need better explanation or even rework, however thats the way it is now... If you have further questions, please post on forum, I will be able to reply faster.

NWNX_Patch plugin is much more potent and powerful with 1.69 version and allows to make for example true custom spellcasters.

However if you intent to make a multiplayer module then EE is the only way to go seriously... Because even if nwnx_patch for 1.69 allows more things you would need to make them, there is just one package with spellcasting that uses it and that is it. So it is basically useless for a SP players anyway.