@Vash and CattleRustler: oh dear
...some people where obviously born l33t and started coding 3 minutes out of the womb, can the attitude guys, I would like to see your first ever attempt at anything code related, we could all do with a good laugh.
The twenty liner is just a bit of fun and as much a test of skill as anything else, and as for bad coding practises, so what!?, if it works with bad code then it`s infinitley better than some OOP .net masterpiece that doesn`t, or is just plain boring, or badly derivative, originality matters more than style IMO, why do you take the trouble to answer a post if you just want to insult somebody?, go join a chat group or something and vent your spleen there.
@rogue the camper: you do realise camping is only gonna work until someone works out where you are
you have made some small mistakes with the code and how it works, a lot of the commands are used in pairs or sets, for-to-next, repeat-until etc, this is not like english where you could make a sentence structured like for-while-until, that would not be allowed in B.A.S.I.C, you could also add some stamina so the the defence reduces the stamina of the opponent or something.
The best way to write your twenty liner is to start off with one command per line, then when you get it all working you can start to condense it down into less lines, goto is usualy frowned upon but in example code like the twenty liners can allow you to do more than an OOP minded person could
.
Ignore the trolls above, for a twenty liner it`s actualy not bad (check my twenty liner..."nice pong" for bad
), all you need to do is check the help and examples to see how they use the commands and what is allowed, sort out the nesting error with the incompatable commands and it will work, oh!, and leave in the blocking and add something to it just to annoy the trolls
Mentor.
PC1: P4 hyperthreading 3ghz, 1gig mem, 2x160gig hd`s, ATI radeon 9800 pro gfx, 6 way surround sound, PC2: AMD 1.2ghz, 512mb ram, FX5200 ultra gfx, stereo 16 bit soundblaster, ups.
