So this quest I've been constructing is refused to start up. I did the 10, 20, 30, and 40, along with dialogue, alias, and priority to 65. Yet, the quest doesn't seem to start up. It's an old quest that I've had trouble with for sometime. I'm not sure if it's because there's alot of dialogues or has to do with the voice type.

Other than that, I am in need of dire help. I back tracked to my first previous quest that only had 4 dialogues, along with 10, 20, 30, and 40. Is that possibly the reason why it's not starting?

How is this quest started? Is it start game enabled? If so have you generated an SEQ file?

It's started at the Halted Stream camp. I replace some of the NPC's as Haled Stream bandits being attacked by a horde of hired mercenaries. Throughout this three way fight (or sneak in) you come across the same set of NPC's, but have a captive prisoner that is in need of rescuing. After rescuing her, you learn of the BlackWater gang that she was in and how she was disbanded, along with being looked at as a traitor. The player will also learn these mercenaries for hire were also destined to kill her, along with the buyers whom are the bandits at Halted Stream (pretty much a setup with no strings attached or hands being dirty)

Throughout the quest, the player must search for the NPC's sister and save her. After saving her, both NPC's become the players followers if permitted. If not, I want to transport them to the rorikstead inn where they can hangout until the player needs them (so I think a script for this one?)

Other than that, that's pretty much it. started game enabled as in pop up? If so, then yes. As for the SEQ file, I'm not quite sure what you mean.

http://www.darkcreations.org/forums/topic/2677-workaround-skyrim-dialogue-bug-fix/

You need an SEQ file for start game enabled quests.

So when you start the game on a clean save, open the console and type sqv yourquestname. This will tell you the status (running, stopped) and the current quest stage.

Weird. Never recall doing this on my prev quest. Is this sometimes a common bug?

It became a requirement when the 1.6 patch was released, quite a while ago.

Interesting. I'll try this out tomorrow after work and keep posted if whether it works or not. Thanks!

Ok mate