Difference between revisions of "Category:Troubleshooting"

No change in size ,  09:53, 13 August 2007
Moved "Activating an object every frame" to "Common Bugs"
imported>Sarkandar
imported>Haama
(Moved "Activating an object every frame" to "Common Bugs")
Line 93: Line 93:
set YourOpenerQuest.rContainerToOpen to YourContainer
set YourOpenerQuest.rContainerToOpen to YourContainer
StartQuest YourOpenQuest</pre>
StartQuest YourOpenQuest</pre>
== Activating an object every frame ==
This didn't cause a CTD with me, but as it causes unpredictable results there is a chance CTD's might occur.
When you have a script that constantly activates a certain object (in my case, to wait for a result that was published inside that object and could be retrieved in this way), other scripts might become unresponsive.
I had several onadd blocks in other scripts that weren't executing anymore.
If you have to do this, build in a timer.


= Common Mistakes =
= Common Mistakes =
Line 309: Line 300:
**In the right situation, you can avoid the problem by changing the [[Scriptname]] of the items
**In the right situation, you can avoid the problem by changing the [[Scriptname]] of the items
*If there is a possibility of the player running into this situation, be sure to test for it
*If there is a possibility of the player running into this situation, be sure to test for it
== Activating an object every frame ==
This didn't cause a CTD with me, but as it causes unpredictable results there is a chance CTD's might occur.
When you have a script that constantly activates a certain object (in my case, to wait for a result that was published inside that object and could be retrieved in this way), other scripts might become unresponsive.
I had several onadd blocks in other scripts that weren't executing anymore.
If you have to do this, build in a timer.


= Debugging =
= Debugging =
Anonymous user