I have been working on this game called Space Dodgers its not for the calculator its for Windows. (I am pretty shure it won't work on Macs )
I made it in Visual Basic and have been working on it for a few months. MegaSasquatch has been doing an exceptional job with the graphics. I wanted to post this on the forum to see if you guys had any suggestions.
Space Dodgers is a spaceship game where as of now the enemy missles do not follow a specific pattern. You get powerups and you have a lifebar. I might also want to put in some bosses.
The web site is http://www.freewebs.com/dwarrior333 there you can find new updates and betas. The controls are also on the beta section of the site accesible with a password and a username for beta testers. There is also a guestbook there for suggestions. If anyone would like to be a beta tester post it here and then we will pm you if we would like you to beta test.
I really did not want to make any vids but I did do the screenshot.
Note: The powerup is not messed up it only looks like that.
The green bar is your life and the blue is how long you have your powerup.
This is awesome!! I hope it runs pretty fast. I guess I shouldn't underestimate VB, but then again, the only VB programs I've seen up til now were applications.
This is awesome!! I hope it runs pretty fast. I guess I shouldn't underestimate VB, but then again, the only VB programs I've seen up til now were applications.
Keep up the good work!!
If you look closely at the falling health powerup you can kinda see it looks like there is two sprites, but it is because I took a screenshot in the middle of the draw/erase process.
Why? It's OO, which makes game programming a lot easier ... plus it has powerfull .net libraries. (They even have some really nice game programming tutorials for vb.net and c# .net on msdn)
Ah well, as long as it "works", I guess I can't complain Nice to see you're still programming
Why? It's OO, which makes game programming a lot easier ... plus it has powerfull .net libraries. (They even have some really nice game programming tutorials for vb.net and c# .net on msdn)
Ah well, as long as it "works", I guess I can't complain Nice to see you're still programming
Visual Basic 6 is OO and I dont like VB.net because there is no control arrays mainly
Dragonwarrior333 wrote:
Its VB6, i really don't like Vb.net
Why? It's OO, which makes game programming a lot easier ... plus it has powerfull .net libraries. (They even have some really nice game programming tutorials for vb.net and c# .net on msdn)
Ah well, as long as it "works", I guess I can't complain Nice to see you're still programming
Visual Basic 6 is OO and I dont like VB.net because there is no control arrays mainly
Last time I check VB6 was not OO. (It ain't. Or when was the last time you did an inheritt in VB6?)
Wiki wrote:Visual Basic versions 5 and 6 are not quite object oriented languages as they do not include implementation inheritance.
and for what do you need a "control array" (which should be in VB.net aswell) anyway in a game?
kv83 wrote:Why? It's OO, which makes game programming a lot easier ... plus it has powerfull .net libraries. (They even have some really nice game programming tutorials for vb.net and c# .net on msdn)
Ah well, as long as it "works", I guess I can't complain Nice to see you're still programming
Visual Basic 6 is OO and I dont like VB.net because there is no control arrays mainly
Last time I check VB6 was not OO. (It ain't. Or when was the last time you did an inheritt in VB6?)
Wiki wrote:Visual Basic versions 5 and 6 are not quite object oriented languages as they do not include implementation inheritance.
and for what do you need a "control array" (which should be in VB.net aswell) anyway in a game?
Inheritance
Inheritance comes in two forms. Interface and Implementation inheritance. Interface inheritance is available in Visual Basic since VB6's introduction of the Implements keyword. Implementation inheritance is available as of VB.NET with the Inherits keyword.
The main difference between the two inheritances is that interface inheritance should specify only a contract of desired behavior. It should not allow any corresponding implementation code. It is up to other classes, which realize that interface, to provide the implementation.
Implementation inheritance lets subclasses share common code and attributes (properties). Also, implementation inheritance's ability to declare an operation abstract enables it to act similar to interface inheritance and force subclasses to implement the operation instead.
A VB.NET class can only enter into an implementation inheritance relationship with one superclass (also called base or ancestor class). However, VB.NET, like VB6, lets that same class enter into as many interface inheritance relationships as it chooses.
)
.
jk
