lionz's Forum Posts

  • Add a system > trigger once while true condition

  • Your second layout can have a separate event sheet linked to it which does different things and only applies to that layout.

  • Yes try it

  • Give the object 'Persist' behaviour, it stays destroyed.

  • Great :)

  • I kind of see what you're doing but it's highly convoluted for showing some lives. I would do the following, use a global variable for lives as mentioned above. To relate it to the lives object on screen, put an instance variable for lives, and give them the values 1, 2 , 3 etc. Then you just need a couple events, when you get hit, subtract 1 from the lives global variable, and to display lives you say choose lives object where instance variable is greater than lives global variable, set invisible. So if your lives is 1, it will hide the jet for 2 and 3 etc.

  • Another way to do it is just use system "save" and it will save the game at the current state, so you could save every time you hit the main menu and it would also load from there.

  • And how does jetlivesdisplay object relate to the lives variable?

  • Assuming that all works, this isn't the event to display the lives, let's see that.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Yes the size of the array is number of levels. You have 5 levels but levels variable is set to 4. Problem is also you have to clear local storage because it will keep loading the old array of 4 when you've saved already. Changing levels variable won't fix it unless local storage is cleared first.

  • Well it's a problem with your events but can't see them. There is no need to use instance variables and global variables for the same thing so don't do that.

  • You do not have permission to view this post

  • I mean you're asking me if a line that doesn't exist is still true, not sure how I can help with that. All I can see is the manual and I cannot see this line about user event not required for NW.js.

  • Then it's resolved. I guess the request is too early for the browser if it's the very first event

  • From the manual : Note the browser may ignore this request unless the action is in a user-initiated event, such as a mouse click, key press, touch event or button press.