Took a bit of a hiatus, but came back. MAde some changes to a module and saved. When I run my server the module fails to load and login is disabled. I used to see this from time to time in the past when something weird happened to the module file.
I set the previous version of the module to load on my server and it does just fine. I opened up that version in the toolset and then simply saved. Now it does the same thing, module fails to load.
Unsure what I’ve done here. Any ideas?
This happened to me once over a bad area. I keep each and every area as seperate ERFs as backups now, but try removing the recently-changed area and seeing if it persists. If it does, grab it from the previous version, save, and see if it does.
Thanks. This should be fun. I must have goofed something before I took a several month break and now I need to recall what that was. Removed a few areas I’ve been working with, but same issue after.
Hard to say but here is what I went through to check, when I had my own issue:
For me like I said it was the last area, but it can be other things.
So what’s strange is I have the working build I can run just fine. I can simply open it and resave it without any changes and then it’s corrupted if I try loading it on the server.
Yeah, usually this means a blueprint or area is getting mangled on the save. A full build can sometimes give errors that are indicative of what’s going on, but not always. It’s very frustrating that it doesn’t really give you any direction where the problem is, I’d agree.
So I just took a bare bones module and it does the same thing. as soon as it saves the module is corrupted. Must be something else. I’m going to reinstall - I can’t think of anything else that might cause this.
Very weird indeed. Something borked with the toolset maybe? Let us know if reinstalling helps.
Are you using the Enhanced Edition toolset? It’s happened with me where it messes things up sometimes; i don’t know why. Last time this happened, I renamed the ‘Neverwinter Nights’ folder in the Documents folder to back it up. It gets recreated and then you can add your ‘settings’ and ‘ini’ files etc. back into the new folder and see if it’s still misbehaving.
Yes, EE toolset.
Trying your suggestion next. The reinstall didn’t clean up all the folders, so I’m hoping that’s it.
The issue was with the nwnee-dedicated server exe apparently. Downloaded and dropped in the latest stable build, and it loaded the module right up.
Can’t exactly wrap my head around why not all modules would just load incorrectly and not just recently saved ones… but even all those that failed to load prior now load like they should. What a relief. Thanks for all the help everyone!
I wonder whether this is yet another case of trying to run a module (that’s recently been updated) on an earlier release of EE?
The message in that case is unhelpful, reporting that the module may be corrupt (it goes on to mention the release mismatch, but naturally some people stop reading before that…).
I would definitely be the one who stops reading to early. But where exactly would that message show? At the bottom of the nwnserver window I presume?
edit: I also ensured nwn was up to date in steam and that I was no in any betas. There had been an update since I last worked on my module. But I definitely loaded up my server after that update and played around to check out some of the new features in the last update.
It might be that the Area_List in the module.ifo file lists an area that does not have an actual .are file in the module.