Story Manager and Multiple Quests in Parallel

[Ashenfire]

Short version:

 

1. How do you start a new quest from another quest?

2. How important is it to use the correct node category (change location, remove item)?

3. Why are parts of my quests 'lagging', is it because of not using correct story manager types?

For instance : Player would complete a task and player gets the reward and it is no problem.

But then on the same NPC, when player comes back to get a new reward, the

ObjectiveDisplayed, Stage advancement, add item will take up to 30 seconds.

 

 

LONG version:

 

I was using creationkit.com and I have finally reworked my entire quest line to rid itself of the 'dialogue bug'.

No quest that I make will ever 'start enabled'.

 

So now the NEW problem is that I can't make several of my quest nodes run at the same time.

I have a main Story Manager Node that I want to keep track of all my other quests.

So that would allow me to have a MAIN side quest inside the parent node and around 15 'mini' quests.

 

The main Story Manager Node would keep track of the 15 mini quests and decide when to reward the character

or when to make the story advance, give relationship options;etc. When those mini quests are done, then the

ObjectiveDisplayed for the starting story line, will complete and the main quest will be completed.

 

Not all of my 'mini quests' are stacked inside my parent node.

 

For example: Using a node (not the one I actually am using).

 

AshenfireParentNode type of node is 'changelocationevent' / branch

condition: when player reaches Angis Camp Location

 

Ashenfire child node1 type of node is 'changelocationevent/ questnode

condition when player reaches Angis Camp and is over 6th level

 

The above node works great for me, but I can't get it to start a new quest called VapormistSQ.

The vapormistsq quest does not rely on change location (player is not going anywhere so the event must happen differently).

So in the quest that was from the PARENT NODE, I added an amulet that was scripted to change the stage of the parent

and that worked just fine. In the same script, I added a change container script to start the VapormistSQ and it won't fire up.

 

I of course had added another node in the Story Manager at the same level that the parent node is. So when you

unexpand the branch nodes, AshenfireParentNode and VapormistSQNode are shown at same time.

 

 

The VapormistSQ node is a 'removeitem' event and the quest it starts 'the yellow quest name where you make dialogue' has the

drop down selected for 'remove item' event.

 

Whew...taking breath. Have more to say but maybe we chew on this first.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[Ashenfire]

Well, this sucks. All this time. An entire world of people and no leads?