Difference between revisions of "Category:Troubleshooting"
→Common MessageBox Mistakes
imported>Haama (More meaningful "Activating a Container" title) |
imported>Haama |
||
| Line 217: | Line 217: | ||
== Common MessageBox Mistakes == | == Common MessageBox Mistakes == | ||
#The script has to run every frame to catch the button press. For persistent objects (activators, containers, tokens, etc.) this means the object needs to be loaded in memory (i.e., in the same cell as the player). For quests, this means you have to set fQuestDelayTime to a low number, like .001. | #The script has to run every frame to catch the button press. For persistent objects (activators, containers, tokens, etc.) this means the object needs to be loaded in memory (i.e., in the same cell as the player). For quests, this means you have to set fQuestDelayTime to a low number, like .001. For all of them, you also have to place the code inside a blocktype that runs every frame (i.e., [[GameMode]], [[MenuMode]]) | ||
#If you plan on having multiple menus displayed from one script, you need to use a governing variable to tell which menu you're currently displaying. For instance, make a [b]short MenuShowing[/b] variable and set it to 1 to display your first menu, and 2 to display the second menu. | #If you plan on having multiple menus displayed from one script, you need to use a governing variable to tell which menu you're currently displaying. For instance, make a [b]short MenuShowing[/b] variable and set it to 1 to display your first menu, and 2 to display the second menu. | ||
#If any part of your code after the button catch (that is, after [b]if (Button > -1)[/b]) requires more than one frame to process, and you've set up your code to set the button variable every frame, such as: | #If any part of your code after the button catch (that is, after [b]if (Button > -1)[/b]) requires more than one frame to process, and you've set up your code to set the button variable every frame, such as: | ||