lionz's Forum Posts

  • The object is in a different layout so it wouldn't work. You can store the animation you want for the player as a global variable, then in game layout - on start of layout, set player animation skin to global variable.

  • But what is the issue you are having? Maybe I can assist in a more general way. If the problem is that the object does not retain its skin between layouts then you can set a global variable string to the animation name and set it later.

  • You can put them on a layer which you don't need to edit and then lock the layer

  • That's not for anyone else to answer but yourself, you design the game and where the player saves their progress.

  • You described well what you did but I don't think you said what the problem is although I am translating. If you cannot set the skin for the player and are using instance variables that do not go between layouts try using a global variable for the player.

  • Save game is what you're after, it saves the state of the game including the many objects you have. Not sure I can explain it any other way.

  • So you have it triggering how? Share the event or describe it.

  • The persist behaviour itself saves the sprite's status when you go between layouts, that's what it is for. If you want to save the sprite after you close the game and load it again then you use system save/load.

  • Not got time to check the file but in general terms you would say if ns greater than 40, set ns to 40.

  • What specific data are you trying to save?

  • Probably the sound is set to play on 'key is down' ? This keep running constantly, you can use 'On jump' from the platform behaviour to play the sound.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • If you use 'system : save' this will save the game, and you can use 'system : load' action later to load it.

  • Yeah I didn't see anywhere you set the variable to true but with that event disabled it all works fine for some reason. Not really sure on what the deal is with that UI layout tbh but since the event is 'every tick' it has a change of going wrong without you noticing, to me it looks like it could get stuck in a loop going from UI back to the main layout, or it is going to the same layout continuously.

  • The cause is that condition XHas UI on Game Sheet. Looks like it is caught in a loop going between one layout and the UI layout or something.

  • Heya, by default it works with the arrow keys, but you can change these later on to WASD or something custom.