Talk:ForceRefTo - ReferenceAlias

ForceRefTo will makes permanently persistent?

I have a question: Will ForceRefTo makes permament persistent the reference in the same way when you choose "specific reference" in the Quest Alias Tab? --MannyGT (talk) 2015-10-07T06:16:34 (EDT)

Short Answer: NO -> Though objects in aliases are persistent until they are cleared FROM the alias, or the quest ends. --GrandBulwark (talk) 03:48, 22 April 2026 (MST)

I am beginning to question this myself. Mine is reverting back to None after restarting the game which was the default state. --Darkconsole (talk) 2016-05-15T03:36:20 (EDT)

ForceRefTo functions the same way as simply adding a reference to specific reference in the CK. The reference is persistant for as long as it is filled in an alias. Therefore ForceRefto is safe. Now if you are saying that your alias is removed whenever you exit the game instead of starting all over, that is not normal behaviour and something else may be causing that. --Terra Nova2 (talk) 2016-05-21T13:35:06 (EDT)

Notes:

-> ForceRefTo() does not yield and wait for the alias's reference to reflect the that of the new forced value

-> Calling this function means the reference will be forced shortly, not immediately.

-> Repeated calls to the same alias, even with different objectreference criteria will execute in call order, one after another.

-> Can still fail under certain conditions, though it does appear to bypass many if not most CK fill conditions

-> If Called and (AliasRef == YourNewRef) is critical to subsequent local code

method is best coupled with bounded checks for safety

Int Attempts = 0

While ((Alias.GetReference() != YourNewRef) && (Attempts < 10))

Utility.Wait(0.5)

Attempts += 1

EndWhile

If (Alias.GetReference() == YourNewRef)

DoFilledAliasStuff()

Else

FillFailureFallback()

Endif

--GrandBulwark (talk) 04:10, 22 April 2026 (MST)