Hi everyone,

I was wondering, whether it is possible to call a function declared in a library-script in Quest B in a dialogue fragment of Quest A. This is the function:

I tried importing it into the Quest-Fragment script attached to Quest A, but that doesn't seem to work. Is there a way to do this?

Thanks!

All the best,

Nicolas

You have two options:

- Create a property with the type set to be the name of the library script

SCRIPTNAME Property VARIABLENAME AutoVARIABLENAME.AddKnowledgePoint()

- Create a quest property and cast the property as the name of the library script

Quest Property VARIABLENAME Auto(VARIABLENAME as SCRIPTNAME).AddKnowledgePoint()

^what he said. Also, if it really is just a library type function, you could create a script that extends quest, and then use that script as the base for both quests. So both quests have access to the additional functions

And if you end up extending quests, then you need to remember that properties carry over from the parent script to the child script.

Okay, so I need to attach that property to the quest script?

No, the property should be added to the dialogue fragment in quest A.

Ah! Fair enough. And I suppose I have do to that through the editor? (Edit Source), don't I? I have never added Script variables.

You can either do it by editing the script itself or by opening the Properties window for the dialogue fragment. If you edit the script itself, then I think you need to add the property at the very bottom of the script as the compiler doesn't like it if you put the declaration somewhere inside the area surrounded by comments stating not to edit anything between them.

Hm! I did exactly what you said, but nothing happens, even though it all compiles fine. He doesn't even call the function - I checked that via Debug-Trace. This is the property I attached:

_00E_NQ02_NewHorizons_Library Property HorizonLibrary Auto

... and this is the code of the fragment:

HorizonLibrary.AddKnowledgePoint()

Like I said, it compiles, but nothing happens. Did I overlook something?

Have you filled the property as well? It should be filled with the quest you have the library script attached to. I suspect CK can find the script and the function or it wouldn't have compiled. However the problem may be that CK doesn't know which instance of the script to use.

Yep, I have filled it. Weird! Does the Library script need to extend anything? This is what it looks like:

You could try making the script extend the Quest script. I've had a few problems in the past with scripts, which didn't extend ReferenceAlias, attached to ReferenceAliases and I had to change it. Might be a similar problem.

Okay, I found the problem. I actually did forget to fill in the value of the property - Once I said it to the quest the dialoge fragment was a part of, it all worked like a charm. Thanks for your help!