Are there tool to manipulate variables inside saves?

Hi Everyone.
Recentely, I was playing a module that got stuck. I couldn't talk to anyone, clicking on them wouldn't bring the dialogue window, locking me. I tought it is something about the scripts, I wished to try to understand if some varible got stuck.
But, alas of the dm_dumplocals/modulelocals/arealocals, it is really difficult to understand which variables are set...
Is there a simple tool to open a save file, that let you navigate every variable (module, objects, characters) and edit it? Think like a spreadsheet similar to Excel. It seems incredible that this kind of tool, if exists, is pratically unkown, it would help recover a lot of saves and debug modules.
Thanks!
Alberto
Recentely, I was playing a module that got stuck. I couldn't talk to anyone, clicking on them wouldn't bring the dialogue window, locking me. I tought it is something about the scripts, I wished to try to understand if some varible got stuck.
But, alas of the dm_dumplocals/modulelocals/arealocals, it is really difficult to understand which variables are set...
Is there a simple tool to open a save file, that let you navigate every variable (module, objects, characters) and edit it? Think like a spreadsheet similar to Excel. It seems incredible that this kind of tool, if exists, is pratically unkown, it would help recover a lot of saves and debug modules.
Thanks!
Alberto
0
Comments
But your problem is unlikely to be related to variables and is more likely to be related to a "stuck" shift or something like that. If that's what it is, you can usually cure it by hitting and then releasing shift, or alt, or ctrl, or whichever key might be stuck, in order to "unstick" it. I'm not talking about it being physically stuck down, either. There are some software conditions in NWN which can cause the game to "think" that one of those three keys is still pressed when it isn't.
You can also try the old trick of "turn it off and on again" for your computer and see if that fixes the problem. Otherwise, I'm afraid the only solution would be to go back to an earlier save-game before the problem, or start over.