Persistence question

[dizietemblesssma]

When putting refs into aliases in a quest in the CK, the resulting esp shows in xedit that the plugin now marks those refs as persistent if they weren't before.  Does this mean, that being set persistent in the CK, those refs won't become unpersistent when the aliases are cleared?

If I remove those edits of persistence in xedit, just leaving the quest records, will some of the refs fail to fill because they are not persistent when the quest starts?

 

diziet

[SKKmods]

The quest will only be able to fill aliases with ObjectReferences if they are either:

(a) Non persistent but in the active uGridsToLoad around the player when the quest alias tries to fill, or

(b) Has a LocationRefType keyword associated with a Location and the Alias is configured to use it, or

(c) Is persistent.

If (a) is not guaranteed, you have not used (b) and you remove the persistent flag from the ObjectReference the alias will fail to fil. If its not an optional alias the quest will fail to start.

[LarannKiar]

10 hours ago, dizietemblesssma said:

When putting refs into aliases in a quest in the CK, the resulting esp shows in xedit that the plugin now marks those refs as persistent if they weren't before.  Does this mean, that being set persistent in the CK, those refs won't become unpersistent when the aliases are cleared?

Yes, if the Persistent flag is set in the record header the reference "won't become unpersistent when the aliases are cleared".

Quest Alias >> Fill Type >> Forced Reference >> automatically sets the Persistent flag.

Quest Alias >> Fill Type >> Find Matching Reference >> doesn't set the Persistent flag but the Story Manager may not be able to find the reference. 

[dizietemblesssma]

Thanks to both, this is what I feared, it seems that to make quests that add markers to 'collectibles' requires either persistence of those items, or editing the vanilla items to add a LocationRefType keyword?

What if anything happens if there are multiple items with the same LocationRefType keyword near each other, does the CK prompt to use this alias method rather than the forced reference method still allow for, say, 3 alias refs for 3 things all on the same shelf that have the same LocationRefType keyword?  When selecting a reference in the render window to fill an alias in the CK I'm often prompted with a 'this looks like a job for a location ref' dialogue.  Given that I want items to show up on the map even if that area of the world hasn't been visited before is there any way to do this without forcing persistence?

 

diziet

[SKKmods]

If there are multiple matches on any condition fill whether its LocRefType, Keyword, GetisID or whatever a ReferenceAlias will just fill the first one.

If you cant guarantee one result, redesign to use a RefCollectionAlias and set Initial fill to 0 to collect 'em all.

If you totally want to avoid persistence redesign to start/stop a finder quest with a dynamic search/fill every Player.OnLocationChange or Player.OnDistanceGreaterThan a moveable datum object and put the found results in the persistent owning quest to mark.

[LarannKiar]

13 hours ago, dizietemblesssma said:

Thanks to both, this is what I feared, it seems that to make quests that add markers to 'collectibles' requires either persistence of those items, or editing the vanilla items to add a LocationRefType keyword?

What if anything happens if there are multiple items with the same LocationRefType keyword near each other, does the CK prompt to use this alias method rather than the forced reference method still allow for, say, 3 alias refs for 3 things all on the same shelf that have the same LocationRefType keyword?  When selecting a reference in the render window to fill an alias in the CK I'm often prompted with a 'this looks like a job for a location ref' dialogue.  Given that I want items to show up on the map even if that area of the world hasn't been visited before is there any way to do this without forcing persistence?

 

diziet

If you wouldn't like to add support for mod added collectibles, you can export the coordinates of nearby vanilla persistent references and place "dummy" object references at their coordinates with PlaceAtMe() and fill the dummy references into the RefColls. It may work if all cells the vanilla collectibles can be found have a persistent reference that you can use as origo but probably it's not worth the effort.