Currently working a game like this right now, you really helped me with the collision mask of the paddle, now the ball bounces in different directions, thanks! 😁
That's a good idea the assets actually has some graphics for it. It would be easy to do when a brick is destroyed I would assign a variable a random number and then have sub conditions in the brick death of creating pick ups. The bigger the range you make the random number the less often the pick ups would appear.
Thank you for the step by step walkthrough on this, helped me a lot!! I ve got a question, when the ball hits 2 bricks simultaneously, score adds 10 instead of 20 (it shows on 30:35), why is this happening and is there a way to fix it? Thanks again for sharing this!
Oh yeah I hadn't noticed that. I made a simpler version to see if I could reproduce it and yep the same thing happened. I thought it might be the order of the events so if you added the score first but it still happens. I tried it with the collision not being a sub condition but it still happened. I tried hiding the brick then detecting if a brick was hidden adding to the score and deleting it. I tried adding a sprite variable to the brick changing that to one with a collision and then when that variable is changed to 1 deleting the brick and adding to the score. Every method produced the same result when the ball collides with two bricks you only get the score for one... Sorry let me know if you figure it out.
@@markrotondella4689 Thank you for taking the time to search for a solution! Maybe if after every hit there is a counter that counts the bricks and then according to the number it gives you get the score variable instead of getting the score from the collision?
@@giorgoschr79 that would work when the level starts you could set a variable to how many bricks are on the screen then after you delete bricks you check the current number of bricks to the starting amount. Annoying to make such a clumsy solution but it would work fine and wouldn't slow anything down.
@@markrotondella4689 Fixed it, made a variable for all the bricks on the screen. When ball collision's with brick, it deletes the brick as before and then I put 2 sub events, one for each of the two cases. a) if the number of bricks on screen are var -1 , add 10 to the score b) if it's var -2 add 20 to score. Just tested it, it works. Yes a little clumsy 😕. Thank you again for your time and answers!!
@@giorgoschr79 I glad I'm aware of the issue. It's no biggie here because you just lose some points but there would be a many situations where this could cause problems in a game. I hope it gets fixed in future versions of Gdevelop.
Currently working a game like this right now, you really helped me with the collision mask of the paddle, now the ball bounces in different directions, thanks! 😁
Nice glad it helped. :D :D
Could you make a tutorial on how to spawn upgrades/pickups after destroying a few bricks? 😁
That's a good idea the assets actually has some graphics for it. It would be easy to do when a brick is destroyed I would assign a variable a random number and then have sub conditions in the brick death of creating pick ups. The bigger the range you make the random number the less often the pick ups would appear.
Thank you for the step by step walkthrough on this, helped me a lot!! I ve got a question, when the ball hits 2 bricks simultaneously, score adds 10 instead of 20 (it shows on 30:35), why is this happening and is there a way to fix it? Thanks again for sharing this!
Oh yeah I hadn't noticed that. I made a simpler version to see if I could reproduce it and yep the same thing happened.
I thought it might be the order of the events so if you added the score first but it still happens. I tried it with the collision not being a sub condition but it still happened.
I tried hiding the brick then detecting if a brick was hidden adding to the score and deleting it. I tried adding a sprite variable to the brick changing that to one with a collision and then when that variable is changed to 1 deleting the brick and adding to the score. Every method produced the same result when the ball collides with two bricks you only get the score for one...
Sorry let me know if you figure it out.
@@markrotondella4689 Thank you for taking the time to search for a solution!
Maybe if after every hit there is a counter that counts the bricks and then according to the number it gives you get the score variable instead of getting the score from the collision?
@@giorgoschr79 that would work when the level starts you could set a variable to how many bricks are on the screen then after you delete bricks you check the current number of bricks to the starting amount. Annoying to make such a clumsy solution but it would work fine and wouldn't slow anything down.
@@markrotondella4689 Fixed it, made a variable for all the bricks on the screen. When ball collision's with brick, it deletes the brick as before and then I put 2 sub events, one for each of the two cases. a) if the number of bricks on screen are var -1 , add 10 to the score
b) if it's var -2 add 20 to score.
Just tested it, it works. Yes a little clumsy 😕.
Thank you again for your time and answers!!
@@giorgoschr79 I glad I'm aware of the issue. It's no biggie here because you just lose some points but there would be a many situations where this could cause problems in a game. I hope it gets fixed in future versions of Gdevelop.
🎉🎉🎉💪💪💪
🤖🤖🤖¡¡¡Thanks!!!👾👾👾
Thank you!
No worries :D