So my directory module has been "corrupted" god knows why, I haven't touched it today, yet it worked earlier in the week.
I was reading threads etc, downloaded the module checker and removed anything which indicates its "maybe corrupted".
And yet it still hasn't fixed it. I even found it funny that the check_module.exe might be corrupted.
It's odd, because it's giving temp1temp1, not just once but twice.
Is there anything else I can use or do?
what's toolset error message, when you Open directory
No error message, but after everything loads, it gives me the temp1temp1.
If I try to load it again, it loads all the areas then goes to a blank module, temp2temp2.
I bet one of the module type files is bad. The module.ifo or similar.
I bet one of the module type files is bad. The module.ifo or similar.
How would I go around fixing that? Removing it?
I tried removing the module.ifo and .jrl, and still no luck.
what happens if you open a different module, or create a new one (save, close it & reopen it)?
My other 2 modules work perfectly fine.
It's just this one :/
it's not a magic solution, but if i were you
I'd create a new directory (not with the toolset, just with explorer). And create a new directory module w/ the toolset, to refer to as a template.
Then start brushing up on NwN2 filetypes. Start by transfering into the new directory those files you think are needed to get your startup area up & running. Also try using copies of things like the .ifo & .jrl from the template directory if you really got to.
just try to get something up and running,
Luckily I always keep an an extra, but the modules old, hence why I wouldn't want to start again and lose my progress of 2 weeks work 
I tried exporting 3.utcs (3 armours) and it worked fine by dropping them into my other modules.
Though the toolset crashed twice when I tried to click them, 3rd time it didn't crash.
Was hoping that I wouldn't have to do this :/ but I have no choice lol
you can narrow the problem down by using a program like WinMerge to compare your current version with your backup version. The problem must be with one of the files that is different.
Retour en haut