lionz's Forum Posts

  • They are the same

  • On the bullet behaviour tick the box 'Set Angle', then they will run towards the player. Seems fine then. Also disable the 8-direction behaviour as it seems to be causing a bug.

  • Yeah I was referring to when you tap down to make them smaller then it cycles round so they appear huge, I still have nightmares.

  • You do not have permission to view this post

  • System compare two values : family1.count is equal to 0

  • Family1.count = 0 and player is overlapping flag, go to layout 2

  • I like it ^^

  • With either 8-direction or tile, you would compare the x and y of the enemy to the player and based on this side 'simulate control' toward the player. Because you're using 4-direction only it's not really clear what you want the movement focus to be on, if it should just run left across the screen and then down or down and meet the player y and then left towards the player, but you can order the logic so it chooses one direction first. That seems the most suitable for what you are trying to describe.

    Pathfinding may also be suitable, you do enemy find path to player, on path found move along path and disable diagonal movement.

    With the bullet behaviour you would use set enemy angle toward player but it would move at diagonals toward the player.

  • If you are designing it so it's a high score per level then yes it's a variable per level as you would need to show the high score for each level, right?

  • You would only need 2 global variables, a level score and a total score.

    When you finish level 1, level score = 50, total score = 50

    finish level 2, level score = 100, total score = total score + level score, so 100 + 50 = 150

    finish level 3, level score = 150, total score = total score + level score, so 150 + 150 = 300

    You just add the level score to total at the end of each level.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I don't think it matters too much although it's more difficult to track what's going on with 'time' than if you assigned a timer behaviour to the bomb. You are basically saying on it becoming activated calculate some time from that point, well you can do this with a timer behaviour and track it on each bomb. I can't think of a more obvious use for a timer behaviour than a bomb :D Also I should note the timer is affected by timescale so when you are trying to pause the game it will stop the timer and resolve that issue for you.

  • Yes it's object.timer.currenttime("timer name")

  • You alter the idle timer in the device settings. It's possible to override the idle timer if you are coding an application from scratch but generally people advise against it.

  • There is a timer behaviour. You assign it to the bomb and say when bomb is activated, trigger once, start timer. construct.net/en/make-games/manuals/construct-3/behavior-reference/timer

  • Keep pressing the down key if you want to have a panic attack.