Burvey's Forum Posts

  • You do need to provide a capx if you want any reliable help on the issue. Something isn't working right for you and most people won't just throw guesses out.

  • &newline

  • I'm glad I found this thread. Voted. I hope everyone else on here does too. We do a lot of complaining about how bad IE is (rightfully so), now here's a chance to make a difference. Go vote for the changes that you want to see!

  • Thanks korbaach That's the best example I've seen. I'm going to play around with it for a while. I wish I could do it without having to add extra plugins/behaviors though.

  • If it were me I would add the timer behavior. In the same event make a timer called loadwait and set it for 3 seconds and right below it gamewait and set it for 6 seconds. Then just add the triggers on loadwait goto load screen and on gamewait goto gamescreen. I think that should work.

  • I want the the boomerang to end up back in the players hand, even if he jumps etc.

  • Has anyone figured out a good way to make a boomerang effect (throw something and it comes back to you like a boomerang)? I've searched high and low and can't really find anything that I can get to work. I've tried a combination of behaviors like bullet + sine and even pathfinding but my skills just aren't up to par to get the effect to work properly.

    It may or may not be important, but it's for use in a platformer game.

  • Sprite is too close to sprite2. If you move sprite away then it will shake.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Use the timer behavior rather then the wait event. Also, in your specific case, you will need the load screen and game screen to use the same event sheet.

  • It should work the way you describe it. As long as the layer is in the same layout that you are in.

  • There's really no way to know without seeing a capx

  • Just put the key and brick on the same layer, make sure the Z order of the key is behind the brick.

  • It would be nice if the warning would somehow reference which stuff will be deleted. I know I've deleted objects in the past which I forgot were actually used. It can be a pain sometimes.

  • Not sure if it's why or not but the free edition of construct 2 only allows 4 layers.

  • I didn't look through your code with a fine toothed comb but the one thing that jumps out at me is your use of the wait event. I believe that you should be using a timer behavior instead for that.

    Also, since you're using the free version, I think you should be able to save yourself a few events by moving your events (not triggers) in 53 and 54 all up to 52. You will need to make more events for the timer behavior though if you change it out with the wait, which you should.