[LE] What is with this error message?

[RobWed]

So I had a pretty productive day insofar as I learned a lot about Papyrus scripting and quest building. Well, a lot for a noob. Y'all would have found it excruciatingly slow!

 

However, when I tried to add a variable to a quest condition I kept getting the same error:

 

SCRIPTS: Cannot open store for class "blah", missing file?

MASTERFILE: Unable to find variable ::blah_var on any VM scripts for form 'Blah' (050012C5) in TESConditionItem Parameter Init for INFO Form '' (0575EA01): Quest 'Blah' (050012C5), Topic 'blah' (0575EA00), Text "blah blah blah".

This was in the CK log and existed for every single script from the active file and its masters. I was able to select the script from a dropdown list when I set up the VMScript condition but the variable dropdown only contained 'NONE'. For whatever reason the process worked fine for the actual game scripts.

Comments on the interwebs suggested it was because the scripts were not in the right location but they all were. Active and masters.

In the end, I opened up my quest in TESVEdit and added the variable there. And it worked! (Interestingly I'd initially added the gatekeeping conditions to the QEST in TESVEdit and it didn't work and I noticed that the conditions didn't even show up in CK! So I deleted the conditions in TESVEdit, saved, went to CK, added them there, then had the above problem.

Can anyone explain what was going on? What's best practice here? The whole process seems sketchy AF...

cheers

[IsharaMeradin]

The CK is a fickle beast. Often times, especially when scripts are involved, one needs to create the record, close the record and re-open the record before working with the any script related portions. Also, unless creating the script in the CK from scratch, any script you need to attach or access needs to already exist before starting up the CK. Otherwise, it will not find it even if it is literally right there.

[RobWed]

Thanks.

 

I'd already learned the part about closing and opening the record. Thing is though with the scripts, they were all there. I opened and closed CK a few times to no avail before going to TESVEdit out of frustration. Which got the job done so all good.

 

Oh and yes, I've learned that CK is a fickle beast. I reckon I've a lot more to learn in that regard!