| Contents |
|---|
| Random Thumbnail |
|---|
![]() |
| Search |
|---|
| Login |
|---|
| Navigation |
|---|
| Most Recent |
|---|
| Featured Articles |
|---|
| Navigation |
|---|
| Who Is Online? |
|---|
| We have 53 guests online |
| Scripted user variable "None" |
|
| Descent 3 - Descent 3 construction | |||
| Written by Thomas | |||
| Saturday, 14 February 2009 12:19 | |||
|
The Dallas script editor can be quite mean when it comes to user variables which have not be specified. Usually it informs you that some information in an action or a condition is missing. For instance, it comes up with an error if you try to show a HUD message which has not been specified. Not so with user variables. Have a look at this script excerpt:
The script compiles without errors, but no user variable has been given. It goes without saying that the script is not working as intended when the variable in question is queried like inside the above condition. I spent about half an hour on this example to find the culprit. Conclusion: If a script or a script chain isn't working right, check your script flow first, and then check if all conditions and actions for user variables really have variables assigned to them.
I hope this helps you save some time and hassle.
|
|||
| Last Updated on Thursday, 04 March 2010 21:09 |
You need to login or register to post comments.
Discuss this item on the forums. (0 posts)






