Difference between revisions of "Debugging"
imported>Dev akm |
imported>P.lo m ("getdistance player >0" CHANGED TO "getdistance player > 0") |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__TOC__When something just isn't working right, look here for possible causes and ways to track down the bug. | |||
== Comma Instead of Period == | == Comma Instead of Period == | ||
| Line 41: | Line 39: | ||
When called in a scripteffect spell, the statement sometimes evaluates true for the player. The easiest solution is to add another condition to double-check it, such as: | When called in a scripteffect spell, the statement sometimes evaluates true for the player. The easiest solution is to add another condition to double-check it, such as: | ||
getdistance player >0 | getdistance player > 0 | ||
However, [[getDistance]] is unreliable if the player is swimming. | However, [[getDistance]] is unreliable if the player is swimming. | ||
| Line 49: | Line 47: | ||
set refVar to getSelf | set refVar to getSelf | ||
if ( refVar.getIsReference player == 0 ) | if ( refVar.getIsReference player == 0 ) | ||
== Using PlaceAtMe's referenced item in the same frame == | |||
If you use the referenced item of a PlaceAtMe call in the same frame | |||
<pre>set pItem to (player.PlaceAtMe IronBow 1, 0, 0) | |||
pItem.Activate player ;this adds the bow to the player</pre> | |||
the script on the object may not run. | |||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
Latest revision as of 11:47, 17 December 2008
When something just isn't working right, look here for possible causes and ways to track down the bug.
Comma Instead of Period[edit | edit source]
This can cause severe headaches for the scripter: The compiler will accept a comma in place of a period in reference syntax, but the script will silently fail in the game when the line is encountered.
player.modAV health 200 <- Fine player,modAV health 200 <- Suddenly your script is no longer running and you're wondering why
Easy to miss when you're looking for logic errors.
Numerals[edit | edit source]
Don't start an ID or variable with a numeral.
short 5forFighting; BAD long benFolds5; GOOD! myGuy.moveTo 0marker; BAD
Mismatched If/Endif[edit | edit source]
The compiler will ignore extra endifs when you save your script, but they can cause the script to stop running when encountered during gameplay. Make sure each if in your script is paired with exactly one endif:
if ( something == happened ) do something endif ; GOOD endif ; BAD, extra endif may cause errors in the game
The best way to avoid this problem is to use proper indentation of if-blocks.
Quest Topic Scripts[edit | edit source]
The Scripting section in the Quest/Topic editor seems to be for very generic scripting like setting global variables and doing things like setstage. Be aware that while some things may compile clean here and seem perfectly fine, they just don't work in-game.
Getself != player[edit | edit source]
Be careful if you use:
Getself != player
When called in a scripteffect spell, the statement sometimes evaluates true for the player. The easiest solution is to add another condition to double-check it, such as:
getdistance player > 0
However, getDistance is unreliable if the player is swimming. The best solution is to use:
ref refVar set refVar to getSelf if ( refVar.getIsReference player == 0 )
Using PlaceAtMe's referenced item in the same frame[edit | edit source]
If you use the referenced item of a PlaceAtMe call in the same frame
set pItem to (player.PlaceAtMe IronBow 1, 0, 0) pItem.Activate player ;this adds the bow to the player
the script on the object may not run.