So a week or two ago I had a question about this travel package because my actor was going to the wrong spot. Now he is not traveling at all. Blerg.

This might be hard for you all to answer unless there are common pitfalls that might explain my trouble.

I am writing a quest with an actor who has to run somewhere at a certain point after being talked to. I have a package set up and an EvaluatePackage() script set up in the Stage fragment. He was even following this package before, but it was being triggered off of me setting the stage via console command. I got the actor dialogue set up to set the stage which should fire the EvaluatePackage() command, but it's not happening anymore (not even by setting the stage with console commands). I can tell that the stage is being set because another command (SetObjectiveDisplayed) is evident at that stage, but the actor's travel package is not kicking in. I have set up this stage with the kmyquest option pointing to a script that has the actor's reference alias and the quest as properties. The only condition for the package is that the quest is at a stage above zero (stage it's supposed to be called at is 20). Navmesh is okay and finalized. Strange thing is that this package worked before and I don't know what I did that made it stop.

I have a feeling it could be an issue with Aliases, as they seem to be finicky and prone to causing problems for reasons that I don't comprehend. Is this a possibility? On the surface, everything seems to be correct.

Any help or insight into the problem would be appreciated. Thanks in advance