Computer Science Canada Can you beat 60? |
Author: | upthescale [ Sat Apr 01, 2006 10:50 pm ] |
Post subject: | Can you beat 60? |
I can't upload music, so just take out the music files in the code thanks give me hate also cuz u always do it ps. the program will be glitchy it is because u dont have the music, so take it out and it will b fine |
Author: | cool dude [ Sun Apr 02, 2006 9:38 am ] |
Post subject: | |
thats pretty hard to beat. has some flickering even when i take out the mucsic and your instructions go off the screen. also if i hold my mouse over the button but not click it will select that button. overall good game! ![]() |
Author: | Delos [ Sun Apr 02, 2006 10:17 am ] |
Post subject: | |
Why must you use processes? Really, your code would be so much more efficient if you used procedures and functions instead. As it stands, it really needs a lot of work. You'll notice that in segments like "money2" you have a lot of repetitive code. This could easily be fixed by using procedures. Read the tuts and improve on what you already have. Your collision detection is buggy. I had several blocks move right through the paddle despite them aligning perfectly. Also, why does one lose a life for going off the screen? Why don't you just restrict the movement of the paddle if you don't want people moving it there? Again, using breaks. This leads on from the processes comment. Once you get yourself some procedures in there, you won't need breaks anymore and things will look far prettier. |
Author: | MysticVegeta [ Sun Apr 02, 2006 2:49 pm ] | ||
Post subject: | |||
Here is a really simple version of your game using procs and fcns and records instead of using processes, as yuo can see, it is clearly more efficient in several ways, study the code and implement the methods in further projects that you do, because running smoothly is a really important focus of a programming game project. I have named the procs and vars long so that you could understand whats going on inside of them, again, this is a really simple version, I am sure other people here can come up with a highly detailed and 100X better version that this.
Just increase the goDownRate in the randAll Procedure to increase their speed of going down ![]() |