When I try to call a function (one that is defined inside a script that is attached to a quest), it does not work. Now, I've duplicated code from the vampire quest scripts and magic effects, and although THOSE work, MINE do not. Those are far more complicated too.

Basically, the script attached to the magic effect does everything it's supposed to do UNTIL it comes time to call the function, then nothing else happens.

Here's the script attached to the magic effect:

GraniteDevilQuestScript is the script with the function in it. It is attached to the quest GraniteDevilQuest.


Here's the script inside my Quest (the Quest itself is set to Start Game Enabled and its sole purpose is to do exactly what you see here):


GDMsgTwo never, ever shows. Never. But GDMsgOne always shows when the effect triggers. I can't figure out why my function isn't getting called.

I should also point out that if I replace MY script (the one attached to the magic effect) with VampireChangeEffect, the vampire change triggers exactly like it should when the effect occurs. THAT function gets called, but mine doesn't.

So I must be missing something here. Can anybody tell me what I'm doing wrong?

Falling off the first page. I loathe bumping posts, but... I'm really hoping somebody can show me what I'm doing wrong.

Hmm, try defining the function "ForTheLoveOf" as a global function:

Function ForTheLoveOf() global

Then try calling it like this:

GraniteDevilQuestScript.ForTheLoveOf

The property probably wouldn't work, since you'd be calling it on a type, so try adding a Debug.Notification message in there too, just to see if the function is called.

Cipscis

EDIT:

Also, just checking, all your properties are set up correctly in the editor? Including your GraniteDevilQuestScript property?

Cipscis

The other way of doing it would be something like this:

1) In the script attached to the effect, replace

GraniteDevilQuestScript Property GraniteDevilQuest  Auto

with

Quest Property GraniteDevilQuest  Auto

and in the Properties window, set it to your quest.

2) Then change

GraniteDevilQuest.ForTheLoveOf()

to

(GraniteDevilQuest as GraniteDevilQuestScript).ForTheLoveOf()

Cipscis, DreamKing, thanks a lot for the suggestions!

I figured it out though: I had to Fill the properties (who knew? - I did it because I was out of ideas). At first I tried just running the Auto-Fill Properties, and it did its thing, and I ran the game and tried it out but my function still wasn't getting called... so I compiled it from GamePlay menu and tried again... and it worked.

Man, what a learning experience this is. So different from the GECK.

At least you can be satisfied knowing that you had the syntax correct

As far as I know, "Auto-Fill" will only work if your property's name is the same as the editorID of the form that you want it to represent.

Cipscis

I know man. Small victories, right?

First time I've used the Fill thing. Didn't even know I had too. Hopefully, I won't have a problem with *that* next since I have been using the editorID of forms to define properties.