Workshop CEP not showing up for you? -- Solution

[EdgeCrusher]

Like most of you, I subscribed to CEP in the workshop, only to find out, it was not available in the Toolset (Game Editor), and was nowhere to be seen in the game content folder under "MyDocuments". Most people are going to assume something is wrong, but actually CEP is there and *should* work if you are playing CEP modules obtained from the workshop. That being the current state of things, it's not going to be of much use to those of us who want to develope our own CEP modules. I did some quick research on it, and came up with a quick and easy solution to the problem, which might help others who have experienced this issue...


1. First thing you must do is locate the CEP content from the workshop, typically located at C:\Program Files (x86)\Steam\steamapps\workshop\content\704450\1312882397



2. Once located, copy everything in that folder (You can verify it is correct folder by viewing thumbnail.jpg, It's a picture of the "CEP" shield.)


3. next go to your NWNEE content folder which (in Windows 7) is typically located at;
C:\Users\[YOUR_USERNAME]\Documents\Neverwinter Nights.


4. Paste what you copied earlier, into that location. It will ask you if you want to merge the folders, the answer is yes. You don't have to worry, it will not overwrite anything. the exact size of data copied will be 5.99 GB.


Hope this helps, or points you in the right direction.

[jimbobslimbob]

Good call. I would hope the devs would fix this, as it could be an annoyance for a lot of content creators.

[jimbobslimbob]

Additional: I posted about this on the Beamdog forums to see if the devs can take a look at it, quoting this thread: https://forums.beamdog.com/discussion/69907/workshop-mods-not-being-seen-by-toolset-or-dedicated-server#latest

[Internet Cafe]

What is neat is the game does know it's in there. I tried some override package and the game knows it's in there. No doubt the toolset doesn't do this because it is a different app and I don't think it needs steam at all to run.

I make a link though to the stuff and it shows up in the right folder.

[jimbobslimbob]

Originally posted by Weed Wizard:

What is neat is the game does know it's in there. I tried some override package and the game knows it's in there. No doubt the toolset doesn't do this because it is a different app and I don't think it needs steam at all to run.

I nake a link though to the stuff and it shows up in the right folder.

Indeed. Same thing occurs with the dedicated server client too - it fails to see modules downloaded via the workshop, but like you say, the game itself has no issues with it.

Probably just a case of adding the workshop folder to the list of places that they look in to find the content.

[Estelindis]

It's a bit troublesome that all content should have to be duplicated this way. If the game knows where to look, why can't the toolset do the same?

[Internet Cafe]

I hope the toolset will address that because I don't have alot of space for the Documents folder.

[Ryuu]

Originally posted by Estelindis:

It's a bit troublesome that all content should have to be duplicated this way. If the game knows where to look, why can't the toolset do the same?

Most likely it's because the Toolset is not Steam program(yet?). I mean it's not tied to Steam(does not have steam_api.dll dependency), so does not have access to location where Steam downloads Workshop stuff.
Check yourself: try launching it without Steam running for example, if Steam does not launch together - means it does not have dependency. Same about dedicated client i guess.

[YaoiCatboy]

Thanks for the help you left there over a year ago. :D

I want to add for Part 1.) that it's not in program files every time. It might be the path wherever the user installed steam.

[Paladin]

I followed the above instructions, and still can't find the module. I now see a bunch of CEP test modules, but still no PW

[Star-X]

Protip: save space by using symlinks instead of directly copying. I've been using symlinks on Linux extensively, and it VASTLY improves the amount of space NWN Diamond and NWN:EE together take up. Effectively anything that can be shared between the two installs is shared via symlinks, meaning only one of those two locations actually uses HDD space for anything not unique to that version.

Also, don't use the bloody Workshop. Last time I tried to use it, at least half of the time it would simply not load subscriptions properly. The vault is better for that. If it's something ONLY available on the workshop, I recommend abusing symlinks to ensure the content is actually properly loaded, e.g. symlinking the workshop content to your NWN:EE data folder, and/or Diamond Edition folder if it's not exclusive to NWN:EE.

[Heinz234]

Originally posted by Star-X:

Protip: save space by using symlinks instead of directly copying. I've been using symlinks on Linux extensively, and it VASTLY improves the amount of space NWN Diamond and NWN:EE together take up. Effectively anything that can be shared between the two installs is shared via symlinks, meaning only one of those two locations actually uses HDD space for anything not unique to that version.

No need for any external software.
Editing nwn.ini is all that is needed to share resources between both versions.

Also, don't use the workshop for cep but get it from the neverwinter vault!
https://neverwintervault.org/cep

[Pumpkin]

The bottom line is that if you're going to be doing modding or anything other than casual playing with NWN:EE, you best avoid any and all usage of the workshop, just delete the entire workshop directory for 704450, which is just NWN:EE's steam id.

Anything that the workshop dir loads can be loaded from the documents/nwn dir, it's the conventional way of doing this. Haks go into /hak dir, tlk into /tlk, etc

Basically, the workshop was poorly implemented, or you could say the entire steam integration was, and thank goodness, I don't think any hardcore nwners want any hardline steam functionality, the game is on gog, beamdog client, ios, android, osx, linux, switch. We don't need more platform-specific shenanigans.