RUNDOWN:
(Note: At the beginning of the game <font color=blue>numScenarios</font> is set to the width of the <font color=red>QA array</font> to keep track of how many questions there are.)
What I expect to happen:
The while loop begins, it prints the first scenario, the user has a chance to touch/click which door has the correlating, correct answer - they move along a path to the door they touched, once they arrive to the touch coordinates: if they are right (if the <font color=green>door.doorOption</font>/<font color=orange>doorText.specificDoorText</font> = <font color=magenta>scenario.scenarioAnswer</font>), I take the scenario they got right out of the <font color=red>QA array</font> and subtract one from <font color=blue>numScenarios</font>//if they are wrong, points get added to delay time, the scenario stays in the <font color=red>QA array</font>, and <font color=blue>numScenarios</font> stays the same. This process happens until <font color=blue>numScenarios</font> = 0. Then the game is over and it takes you to the summary page.
However, I am not sure what part of my while loop is causing the page to get hung up.. and hoping that another pair of eyes can catch it, or suggest another way to go about doing things.
Thank you all very much. <img src="smileys/smiley1.gif" border="0" align="middle" />
C2 event sheets are evaluated as whole every tick. So if you have a while loop, you should also break out of it somehow, otherwise the tick will never complete. You don't need 'game loop' as you'd have in traditional programming. :) I don't see any need for the while in there at all. You should adjust your thought process more towards 'trigger based', so think what should happen when player clicks a door, what should happen when a layout starts etc. It will help you a lot in getting best out of construct 2!