Ok so I've made a perk that gives the player an activation choice, that is supposed to call a function on my quest. I've filled my properties, everything compiles, even swapped my new function for an old function, but for some reason this fragment won't call any functions! Everything compiles fine. I even compared it line for line next to my other fragment, and everything appears in order.

Is there a limit to "valid activation choices"?

Why won't my function call?

A little more information.

This is for my vampire mod. I already have a perk which has two activation entries in it. One is "Drink Blood?", the other is "Carry Body?" Each one calls a function in the PlayerVampireQuestScript. I had originally tried adding a third activation entry to it, but when I hit OK, the dialogue won't close. I tried about 5 times, no matter what, when I add that third entry, the editor will not close the dialogue box so it seems there is no way to add a third entry. So I created a new perk, as described in the original post, called "Give Blood", which calls it's own function called VampireGiveBlood in the playervampirequest script.

So I am wondering, if there is a limit to how many dialogue choices there are to perks? They show up fine, but this new one refuses to call any function I give to it. Here is the code I am using for the fragment:

(PlayerVampireQuest as PlayerVampireQuestScript).VampireGiveBlood(AkTargetRef as Actor)