Door with spoken password. Where is that word kept?

ngc7293

I would say my Toolset-Fu is around a white belt maybe a little better. I can make things and I read how to make conversations and and transition. I do not make my own modules. I get stuck in them.

So I am stuck in a module where there is a door that has a password. You click on the door and you are told to type it on the talk line. But the module isn't so great or I'm not so great with puzzles. So I go into the toolset. I figure the answer is in a script having to do with the door. But I'm not sure.

In the area there are supposed to be clues.

To make this less obscure, the module is "The Nature of the Beast" and it's the third level of the Abandoned Tower.

thanks

Proleric

The talk line is processed in the OnPlayerChat event script in module properties, so the password will be there.

ngc7293

Thanks for the reply.
I looked in Module Properties and that script section is blank. If the module was important, I would edit this guy's module just to get beyond that door, but it really isn't. But I am curious. But OnPlayerChat is the only place or script the password would be put?

Katzerchen

The password itself which is a string variable could be stored anywhere.
You could check the door properties: Properties->Advanced->Variables for a string variable.

Would be logical to store it there, but it also could be stored in the module, in the area or anywhere.
You could check OnModuleLoad, OnClientEnter or the script in OnEnter of the area for
SetLocalString or
SetCampaignString

What does the OnFailToOpen script of the door do, exactly?

I can't open the module or got the wrong one (says it needs CEP 2.6 but in fact uses another version of CEP, and I really don't want to bother with it too much just to check something).

Proleric

There is an obsolete technique that the module might be using. If you open a script, then search all scripts in the module for SetListenPattern, that might reveal the password.

ngc7293

Under Door properties there was one thing that said something like "thebutlerknows"
I tried that and it didn't work. I looked under all the Module properties and didn't see anything that fit the two clues. "A gnomish bar room joke you don't get." and "Something you do at least once a day."

I did the script search for SetListenPattern and found: Inventory, Pick, and Trap. Non of those seem to fit the clues but I will give them a shot.

Given the idea that this could be almost anywhere, I tried to go slowly through the scripts searching for ones that seemed likely. I went through the Module scripts scripts firsts. Nothing stood out.

Maybe I WILL edit that door to just a plain old door just to get beyond it. This is getting annoying. [grrr]

Proleric

SPOILER ALERT

Seems this is a red herring. According to a player review from 2007 on the old IGN Vault

Regarding the door, I kept thinking I had to type in some unfathomable word to open the door, but it turns out that once the PC picks up the diary she is scripted to "read" an underlined passage in the book

ngc7293

Well that answers that.
However, I have NWNEE.
Nothing happened when I picked up the book. Nothing happened when I went to the door other than what happened when I dropped the book and clicked on the door. (asking for a password)
This seems like a 1.69 friendly module. It has worked fine otherwise so I find it strange.

I guess I will look up the book and see what I can find out about it.

ngc7293

Maybe one last thing.
I did a bunch of things to change that door (even delete it all together) and when I opened a saved game It was the same old door.

It feels like the Save games are keeping me from seeing any changes I do to the module itself.

I would have to start a new game. Is this correct?

Proleric

Changing the module doesn't affect saved games, as you discovered.

There are lots of ways to alter a saved game. By far the simplest in this case is to write a script that destroys the door (or whatever).

For example

void main()
{
  DestroyObject(GetObjectByTag("####"));
}

where #### is the tag of the door.

You can run this as a script chunk in ctrl-shift-f12 mode, or put it in override, then dm_runscript in debug mode.

As always, back up the save before trying to change it!

TarotRedhand

I'm late to the party (again) but could I humbly suggest that @ngc7293 goes and looks in my Fun Doors package for some ideas. All the door scripts are in the included demo module and there is an erf that contains all the scripts, 3 conversations and blueprints for any pre-fab creatures/doors/etc. I included in the package. There is also a table that details which scripts need anything other than the actual script to work so you can copy and paste just a single door script if you want. In other words the scripts are to an extent "plug 'n play".

Hope this is helpful.

TR

ngc7293

Thanks for the help. My knowledge of programming is BASIC from the 80's. PERL was forced on me at a job. In any case I ran the above script on my Mac. It kept on giving me error messages and then I did something right and the door was gone. I hate it when I do something right but not what it is! But the module is over and I am happy. Thanks for everyone's help.