linking modules script problem

Greetings,

I have a minor problem with some selfmade modules that are not linked to Aenea at all. Let me explain, what i want to do and what my problem is.

I am building multiple different modules. One Module is supposed to be a big hub to enter into different modules. In this hub you can get a quest to go clean op a goblininfested cave. That cave is another module. So far so good. Now in that cave i have to aquire an item that i have to bring to the questgiver in the hub to get my reward. When i got it, i can go back to the hub.

Now the problem: If i reenter the hubmodule, the questitem i aquired before simply vanishes from my inventory making it impossible to complete the quest. Can you tell me what might cause the item to vanish? I know i can simply make one module for this but i want it to be different modules.

best wishes,
margolloxx

At what point specifically is the item being removed?  As you exit the goblin cave module, or as you are re-entering the hub module?

Are you using any haks?  If so, do both the goblin cave module AND the hub have the same haks instaled?

no haks and its removed on entering the hubmodule

Check your module events to make sure none of them are set accidentally to your script for removing that item (oncliententer, onmoduleload, onacquiereitem), and do the same check for the start area's onenter event.  Beyond your item removal script being called outside of the quest-giver's converation, I can't think of any reason why the item would get removed from your inventory on entering the hub module.

Are you saving the player between module loads ?.... I've never done any inter-module linking stuff in NWN before, I have no idea how it works. But, I'm almost certain that the main campaign (and Aenea) has some kind of "export/save PC" function between chapters (per log out).... ...

Is the item actually being removed (the log says Lost item: xxxx) or are you just not carrying it correctly...

StartNewModule("bla"); will carry all playercharacters over to the new module as they are. There is no need to manually save them, though it might be wise to do so anyway.

The problem here was the onModuleLoad event. The tagbased itemscript stuff was messing things up. I removed it completely and its fine now.

Thanks for your input.

Good! Glad you got it figured out.