Difference between revisions of "FAQ: My Script Doesn't Work!"
Jump to navigation
Jump to search
FAQ: My Script Doesn't Work! (edit)
Revision as of 19:09, 10 February 2012
, 19:09, 10 February 2012→I can't get my alias to point to a reference
imported>Jimhsu |
imported>Jimhsu |
||
| Line 72: | Line 72: | ||
**'''The reference doesn't actually exist.''' Did you make sure that a PlaceAtMe command actually generated a reference? Check using Debug.Trace(theReference). | **'''The reference doesn't actually exist.''' Did you make sure that a PlaceAtMe command actually generated a reference? Check using Debug.Trace(theReference). | ||
**'''An alias is pointing to an object in a container.''' Evidently this does not work (creating a persistent reference using PlaceAtMe, and pointing the alias to the persistent reference). Solution: don't put the object in the container, or point to the container and get the object that way (not completely tested). | **'''An alias is pointing to an object in a container.''' Evidently this does not work (creating a persistent reference using PlaceAtMe, and pointing the alias to the persistent reference). Solution: don't put the object in the container, or point to the container and get the object that way (not completely tested). | ||
**'''You created an alias for a quest that is already running (i.e. dirty save)''' - even if you are simply adding an additional alias to an already running quest, you can't get the alias to actually point to anything (despite the fact that Debug.Trace happily shows that it exists). Solution is to make a clean save and remove the quest, then add it back. | **'''You created an alias for a quest that is already running (i.e. dirty save)''' - even if you are simply adding an additional alias to an already running quest, you can't get the alias to actually point to anything (despite the fact that Debug.Trace happily shows that it exists, which is horribly misleading). Solution is to make a clean save and remove the quest, then add it back. | ||