This wasn't even an issue really until recently, but with SkywingvL's release of the Advanced Script Compiler , which has some more careful script checking than the old Bioware compiler, I ran into this. A number of the CEP scripts have comment blocks at the end which are un-terminated, i.e. there is an opening "/*" with no closing "*/". For example:

This unclosed comment causes failure to build the including script in the ASC. The ASC may be updated to allow this with a warning, but it would be a good idea to aim for a clean compile of the CEP scripts with this compiler as it's likely a number of PW's may end up using it to circumvent limits in Bioware's compiler. I ran into the too-many-identifiers limit, which compelled me to use the new compiler. I will likely be modifiing the CEP includes locally for this, but if there's a way to get them back into the CEP so the work doesn't have to be repeated that would be great.

Actually, this is much less prevelent than I thought. After taking all the scripts out of CEP 2.4 to recompile them, only that one (zep_inc_1st_rp.nss) has an un-terminated comment. It just got included through zep_inc_phenos and caused a number of warnings. So it should be very little work to clean up. The rest of the CEP scripts built pleasantly cleanly.

I think it's a typo, the second oPC was likely supposed to be oHorse, not sure what it does when it runs. A few minor things: the following files had compiled .ncs files with them, although they produced none on this build. Probably leftovers from testing.

Code:

cut_and_paste.ncstrap_readmecep21.ncszep_cw_inc.ncszep_inc_craft.ncs

crp_inc_language.ncs

The following include is duplicated and is the only script in cep2_build, probably just a stray.

Code:

crp_inc_control.nss

The following Bioware resources are over written by cep2_crp_s, they appear intentional, but should be clearly noted.

Code:

default.nssnw_o2_coninclude.nssx0_i0_treasure.nss

One last thing of note. The CEP has a useful naming convention, i.e. using the zep_ prefix to group the CEP associated functions and help prevent name collisions. It's also useful for working with the CEP products by themselves when mixed with others, such as in temp0. For instance it would be nice to be able to do "ScriptCompiler zep_*.nss" to rebuild the CEP scripts. Quite a few scripts have deviated from this convention over time and it would be nice where possible to try and get them back on course if possible. Here is a list of "non-canon" script names in the 2.4 hak's:

Pstemarie wrote:Just looking at that Advanced Script Compiler you linked above - the post says its for NWN2.

It also works for NWN, and it's used to replace the default compiler if you are using NWNTX (virusman's Neverwinter Nights Toolset Extender).

Thanks for the clarification. I've always used the PRC script compiler when the toolset's compiler couldn't handle things anymore. I don't use NWNTX as its not well documented - at least that I could find - and appears quite intimidating.