PixelPAD game
I enjoyed learning how to program for the first time, programming an app for a beginner might be boring but programming a game is much more entertaining.
One of the things that I am kind of familiar with is the screen scale and how pixels are used to locate specific objects on the screen, I was able to connect to my math classes that I had recently even though, I suffer math.
I am familiar with counting pixel scales because I play video games and sometimes I have to tweak the setting from default to lower or hight based on the system specs, one of the things that play a big role in making the game run smoother is pixels...
One of the things that I am kind of familiar with is the screen scale and how pixels are used to locate specific objects on the screen, I was able to connect to my math classes that I had recently even though, I suffer math.
I am familiar with counting pixel scales because I play video games and sometimes I have to tweak the setting from default to lower or hight based on the system specs, one of the things that play a big role in making the game run smoother is pixels...
One complicated thing I got to know about specifically from video #3 is Object oriented programming, I did not fully understand it but I was able to connect to it which helped me better understand it.
In the video it says that objects can't create themselves which means that someone has to create them, in this case us using the Game class but objects can set their own speed, sprites, and size by writing the code with in their class/room section. Objects can also check for collisions between themselves and other objects. This leads to a bigger idea that we automatically think of or connect to...
In the video it says that objects can't create themselves which means that someone has to create them, in this case us using the Game class but objects can set their own speed, sprites, and size by writing the code with in their class/room section. Objects can also check for collisions between themselves and other objects. This leads to a bigger idea that we automatically think of or connect to...
I learned that when bullets don't automatically get deleted when they leave the game screen, we actually have to make a code using an if statement to delete them and if they're not deleted then the game will get laggy.
Using what I learned from video #3, I wrote a code with an if statement saying that if the bullet leaves the screen border then the bullet will destroy itself, I used the y scale to measure where the bullet would destroy itself.
Using what I learned from video #3, I wrote a code with an if statement saying that if the bullet leaves the screen border then the bullet will destroy itself, I used the y scale to measure where the bullet would destroy itself.
I felt that video #5 was the hardest for it containing unknown concepts, I still don't know how words make sense in programming, I don't know how grammar works in programming, and I don't know exactly how functions and variables work in a program. I wouldn't bother saying this if I was programming an app but because it is a game, I felt like I was just copying the tutorial without it making much sense.