Bug?

Post reply

❤Follow Topic(3)

0 favourites

From the Asset Store

$5 USD

Match same tiles with each other as fast as you can and earn more score during a limited time!

01smile

- PabloDev
- - Joined 2 Nov, 2015
  - 391 topics • 1,545 posts
- 1
- 7 Sep, 2020
- Quote
Hello, is this a bug?

The object is never destroyed.

In this way the object is destroyed.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,388 posts
- 2
- 7 Sep, 2020
- Quote
It's not a bug. Non-static local variables reset their value every tick, so setting their value after a wait doesn't really make any sense. In your case you should make the local variable static so it keeps its value persistently and so changing it after a "wait" makes sense.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- PabloDev
- - Joined 2 Nov, 2015
  - 391 topics • 1,545 posts
- 1
- 11 Sep, 2020
- Quote
But the mode in the second image works fine, so it does make sense, I mean it can be done and it works but it only works for the inner block not for the next block (first image).
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,388 posts
- 1
- 11 Sep, 2020
- Quote
After a wait, it will continue running actions and remaining sub-events. So in the second case you set the variable to 1, then immediately compare it to 1.

In the first case you set the variable to 1 after a wait, then the next tick the variable resets, and it compares it to 1.