Will do. Thanks.
cep260.tlk is in the correct folder. Will try to open in the toolset.
Sorry, didnāt explain properly.
Well, looks great, really. Would be my choice too!
ignore it
Uh, I should read carefully. Is this module somewhere in the public? Iāll have a look!
The starter tileset module Iām trying to open is in the modules folder in the new CEP download. Kalisterās interior is in the link in the post above.
Brilliant strategy to just ignore the error btw. The module started to open but when I right clicked to view the starter area the toolset crashed.
Btw, I checked and other modules are opening as normal.
Now Iām puzzled. The error message should look like this:
(No red dot in the upper left corner).
The module āCEP - Starter 270 - Extended + Added Tilesetsā opens with this warning but no issue or crash.
Im on a Mac using Crossover 
That might be the difference. Thatās the standard pop up
That explains the different appearance of the error message, but not the crash. By now, Iāve no idea whatās going wrong ā¦ sorry
Tlk folder
No problem. I can redo it and see if it works then. Thanks for your help.
This is not an issue with nwsync. A file with the ā.resā extension is junk and should be permanently removed from the hak. nwsync not allowing junk into a manifest is not a āknown issue with nwsyncā, itās a known issue with this CEP 2.70.
Which hak?
As previously mentioned, cep2_add_tiles3. The file tfa01.res is from the Almraiven tileset, which would have the same issue if used with nwsync. No action required at this time, as nwsync builders can just remove it for now, but it looks like we can safely remove it from the next release.
This isnāt the first time a .res file has caused issues - see for example milorās post here - though I wasnāt aware until today.
In a perfect world, I guess hak authors could do a release check for nwsync unsupported file types, now that we know itās an issue.
Both tileset starter modules work fine for me.
In this example, did you perhaps remove cep260.tlk from the \tlk folder to force the error message?
Let us know if itās still a problem.
I suppose nwsync could just warn and ignore unsupported file types instead of failing. That seems a lot more user friendly to meā¦
2 Likes
True. Digging a bit deeper, though, the problem should be very limited in scope, because nwhak wonāt allow us to add an unsupported file type to a hak (.pdf, for example, is forbidden). For reasons unknown, nwhak accepts .res, but nwsync doesnāt. I imagine there canāt be many other examples?
The thread you linked had a ā.0ā file or something. There are other tools to pack haks than nwhak too. I donāt remember off hand if the erf tool I use complains about unsupported extensions or notā¦
Edit: seems to silently ignore them and not add them to the archive. So yeah, itās not as simple to get unsupported files in there. But still, making it a fatal error seems like overkill.
Ok. Iāve deleted all CEP files ( that I can find). Iām now ready to put the new ones in again from scratch.
From the Readme: āAfter extraction, simply select all subfolders and copy them to the Neverwinter Nights location that contains your \saves subfolder. This will put files in the right place, creating missing subfolders if necessaryā.
Just checking.
Iām on a Mac but that is where my saves are. So, I just drag ambient, docs, erf, hak, modules and tlk folders into my Neverwinter Nights main folder and all these files will be somehow moved into the correct folder? Seems too good to be true. . . .
Yes, the nwsync message always says .0, but in all the examples under discussion, the actual file type is .res. Weāve probably done this to death now!