My Flash Game
You can play the game! Just click on the screen and use the arrow keys to move! But watch out for walls, the center of the game piece can't touch them. Enjoy!
Reflection
At the beginning of this project I decided to be an independent flash game maker. Which meant that I worked on one flash game and focused on it the entire length of the project. I knew that I didn't want to do any of the flash game tutorials that Chris Mutter had on his Digital Portfolio. I wanted to do something no one else was doing. So I went on youtube and looked up tutorials. For future reference, there are almost no tutorials for flash games on youtube, helpful ones anyway.
But after awhile I found one and it took me over ten tries to understand what he wanted me to do, saying that I repel technology is an understatement. So, because I was doing a tutorial that no one else in my class or my teacher had done I was on my own when it came to the coding. After about five minutes of the tutorial I decided to completely change what kind of game I was doing. Which seems risky, and it was. I followed the part of tutorial that told me how to code what the moving part of my game did. And then I decided that what the guy in the video wanted me to do, was boring and not at all what I wanted my game to be like. The tutorial was going to make one wall move and then the game would end. That did not sound fun at all to me.
So I decided to make tons of obstacles and have the middle of the game piece not be able to touch any of the walls. When I tested my game there was a major problem, my game piece didn't move. Something was wrong with the code the tutorial had given me. So I looked in the code and fixed the line that had screwed up my entire game, and things only got more complicated from there.
I wanted my game piece to be able to collect things and be timed at how fast the person playing could do it. And after spending multiple hours and almost crying at least five times I can regretfully say that, those things were not accomplished. I looked for more tutorials and tried out three different codes, but none of them worked. Although, a positive outcome was that some of the codes that I did find made my game even better. I was able to add gravity, and change the speeds easier without having to alter the rest of the code.
I feel successful about trying to make a game that no one else was, and making a game that was also more complicated. I also am very proud of myself for spending countless hours outside of school to fix it. I may need to check myself into a mental hospital now but it was worth it. And my game still works, I just have to hold a timer in my hand while someone plays and it works the same way. I know that after the due date of the project I will continue to try and fix my game, hopefully to have it fully function without me.
I think that I deserve an A on this project. Even though a part of my game doesn't work, I tried my best. I worked really hard to find a solution, and found five things that DIDN'T work. That takes major skill. The students that did play my game said that they enjoyed it even though a part of it didn't work. Overall, I had a fun time on this project and so did my classmates, even though we all felt the need to rip our hair out.
But after awhile I found one and it took me over ten tries to understand what he wanted me to do, saying that I repel technology is an understatement. So, because I was doing a tutorial that no one else in my class or my teacher had done I was on my own when it came to the coding. After about five minutes of the tutorial I decided to completely change what kind of game I was doing. Which seems risky, and it was. I followed the part of tutorial that told me how to code what the moving part of my game did. And then I decided that what the guy in the video wanted me to do, was boring and not at all what I wanted my game to be like. The tutorial was going to make one wall move and then the game would end. That did not sound fun at all to me.
So I decided to make tons of obstacles and have the middle of the game piece not be able to touch any of the walls. When I tested my game there was a major problem, my game piece didn't move. Something was wrong with the code the tutorial had given me. So I looked in the code and fixed the line that had screwed up my entire game, and things only got more complicated from there.
I wanted my game piece to be able to collect things and be timed at how fast the person playing could do it. And after spending multiple hours and almost crying at least five times I can regretfully say that, those things were not accomplished. I looked for more tutorials and tried out three different codes, but none of them worked. Although, a positive outcome was that some of the codes that I did find made my game even better. I was able to add gravity, and change the speeds easier without having to alter the rest of the code.
I feel successful about trying to make a game that no one else was, and making a game that was also more complicated. I also am very proud of myself for spending countless hours outside of school to fix it. I may need to check myself into a mental hospital now but it was worth it. And my game still works, I just have to hold a timer in my hand while someone plays and it works the same way. I know that after the due date of the project I will continue to try and fix my game, hopefully to have it fully function without me.
I think that I deserve an A on this project. Even though a part of my game doesn't work, I tried my best. I worked really hard to find a solution, and found five things that DIDN'T work. That takes major skill. The students that did play my game said that they enjoyed it even though a part of it didn't work. Overall, I had a fun time on this project and so did my classmates, even though we all felt the need to rip our hair out.
Code Changes
This is where the problem was with the code, it wouldn't move the game piece when you used the arrow keys. The instance name couldn't be defined for both sets of walls and the "hero".
In simpler terms, this piece of code made sure that my game piece DIDN'T move. So it was deleted and replaced. |
So I changed the if statement by making the "hero" which was the instance name for my game piece true at whatever location it was. Because x and y control location on the stage/screen.
This piece of code allowed my game piece to move WHEREVER the arrows keys moved. |