0 Members and 1 Guest are viewing this topic.
Quote from: lookitsan00b on November 11, 2010, 11:30:50 pmOh and one more, am I asking too many questions? Nah, it's cool. The more questions you ask, the more everyone learns.
Oh and one more, am I asking too many questions?
{====______}
{=========_}
Block type 10 is having major problems...
I really need some answers.Is !If X-56 also an optimisation?
What if I have compound If statements? I know splitting them up saves speed, but what about space?
Lastly, should I be using DelVar in my save routine? I do have to overwrite the appvar every time I save...
Quote from: Builderboy on November 11, 2010, 07:07:10 pmWe observe the mentality of pushing you in the right direction and then letting you gain some experience yourself Of course if you are totally lost or if we can give a few more pointers, we'll be happy No thanks. My program uses too many already
We observe the mentality of pushing you in the right direction and then letting you gain some experience yourself Of course if you are totally lost or if we can give a few more pointers, we'll be happy
I spent about half an hour in endless mode.A few limits might help to keep the game challenging and interesting.1) Paddle width--after a while it was wider than the screen, so you could just leave it and/or watch the score increase 2) # of balls limit--there were about 20 by the time I got tired of it3) some way to keep track of the score if it goes over 65535. It looped six or seven times Code: [Select]Disp <Score>,i,"65535 times ",<Var> With <var> incrementing by 1 each 65535 or something.
Disp <Score>,i,"65535 times ",<Var>
yup. it just crashes my calc when it tries to return...
Quote from: DJ Omnimaga on November 12, 2010, 03:54:01 amOk so when score reaches 10000 it increases the second variable? Sounds interesting. I wonder how do you display them? I think I tried such thing before and failed. File size seems pretty nice so far. Keep up the good work and I hope you can solve the issues you are having. Well thats why it increases the second variable when it hits 10000 instead of 65535 or 60000.Code: [Select]:Output(4,0,S>Dec):If Q:Output(0,0,Q>Dec):End
Ok so when score reaches 10000 it increases the second variable? Sounds interesting. I wonder how do you display them? I think I tried such thing before and failed. File size seems pretty nice so far. Keep up the good work and I hope you can solve the issues you are having.
:Output(4,0,S>Dec):If Q:Output(0,0,Q>Dec):End
Quote from: lookitsan00b on November 12, 2010, 11:02:12 amQuote from: DJ Omnimaga on November 12, 2010, 03:54:01 amOk so when score reaches 10000 it increases the second variable? Sounds interesting. I wonder how do you display them? I think I tried such thing before and failed. File size seems pretty nice so far. Keep up the good work and I hope you can solve the issues you are having. Well thats why it increases the second variable when it hits 10000 instead of 65535 or 60000.Code: [Select]:Output(4,0,S>Dec):If Q:Output(0,0,Q>Dec):EndThat's a great idea! I've been wondering how to do this. Thanks.
1 10
:Output(4,0,Q=/=0*10000+S>Dec):If Q:Output(0,0,Q>Dec):End
Glad to hear it's working. @Darl181 I think he means test mode blue screen. The one that can damage the screen if left like that for a minute.