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 it
3) 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. 

...Whoa.  I never really expected it to be possible to make it loop... I'll probably think of something. (like using one variable for the lower 4 digits and another for the upper, max 655,359,990)  I thought the paddle-size power-downs would make up for the lack of a cap... they seem far more common than their happy counterparts to me.

Lol I just found a bug that existed since v.50(and before)
 Whenever I deleted something, I just copy the last item in the list over the one that got deleted.
 I just realized that the item that gets copied doesn't get hittested, etc. (whatever the loop is for)
 Just 3 more increments in the whole thing, probably amounts to, at most, 9 bytes
 (I've been having really big problems with size recently... can't fit both the source and the program in ram at the same time)

capping it at 9 would be fine, although I guess you could maybe change the control scheme and have people just select the block they want to insert. By the way what will be the max rows of blocks in a level?

For the max paddle movement: I chose 5.
Max rows: 14.

Wow looks great! I'll download the new version now.

EDIT: Awesome game! However, I was bored and this is what happened

lol that should be much easier on you now

Btw question: why does the paddle move this fast when there are many balls at once? Or is it just in 15 MHz mode (like I added to create this screenshot)

Actually, neither.  I figured with many balls on the screen it'd be harder to keep them all on, so I made paddle_speed = 1 + Number_of_balls to compensate.  Now that I think about it, a cap would be nice.

*bookmarks* Looks great! "Bomb" blocks (that destroy blocks near them, even if they're normally unbreakable) shouldn't be too hard to implement...haven't seen your code tho, so I don't know. We're all behind you!

The first time I read this I was almost laughing... then I realized that it really wouldn't be that hard...
It's certainly a possibility.
The question is: I have blocks 0-7. Should I cap it at 9, or find more keys/another control scheme for the editor?

okay the point system works as follows:

every time you grab a power up, 10*M+S->S

Every time you hit a block, 10*M+S->S

M is 1 + combo_multiplier + 2*Multiplier_power_ups_recently

combo multiplier is either 0 or 1.  every time you hit a block, T+20->T, and every frame, T-(T=/=1)->T.
  The multiplier is active if T gets above 40 and has not since hit 0.

The power-ups just last 300 frames, and reset the timer every time you grab another, however, the multipliers do add together.
  Note: they share a timer with the pass-through-ball. This means that grabbing one will set your multiplier timer to 100.

I won't keep you waiting

done already:
  paddle length reworked, no longer dependant on # of balls
  power-up framework: done.
  paddle length power-ups fully functional

I said it'd be done by tomorrow, didn't I? Time to catch some zzz's, though

EDIT: actually, i haven't limited the max paddle length yet...

Quote from: lookitsan00b on November 07, 2010, 09:17:00 pm

Hmmm... what would the score be based on?

Something like 10 a hit would work nicely.

And as for powerups, it'd be cool to have features like temporarily making the ball go really fast and hit for twice as much damage. I have seen Breakout games with powerups dropping from the hit block, and that sometimes adds a lot to the game because you have to catch it...

Yes, it really does (the power-ups dropping down), but it'd be really interesting to code, I think. 10 a hit might do well. 2x damage... well that could work, but certainly not easy.

maybe have it create random levels?

Actually in one of my earlier versions (I'd say v.40) it did that. But I think for the sake of testing, one constant level works better... also the random levels were 8x8 blocks of blocks, and that lagged with only 1 ball... imagine 2 or 3

EDIT:

This looks really nice! ^^

Quote from: lookitsan00b on November 07, 2010, 09:17:00 pm

Actually having the powerups drop down from the hit block on-screen?... you're kidding, right?

Yea, I'm not sure how else you would do it. That's how the break clones that have power ups work. A couple of power-ups I've seen are mulitball, longer paddle, shorter power, or gun(gives you a couple of shots that fire directly upwards and destroy a block on impact)

As for score, different style blocks usually give a different amount of points.

I guess that'd work... but the score counter would look like... what?

Wow that,s nice. I especially like the multi-ball support. Will there be a faster mode with fewer balls too?

I'm not sure what you mean there.  It's running at max speed as is.  If I only allowed for one ball, yes, it would run faster. Or are you saying actually make the ball move twice as fast?

weapons? how would I do that? like a laser shot upwards from the center of the paddle? that would be cool, but game-breaking.  
something that catches the ball the next time it hits the paddle? easy, and useful.
Something that makes the paddle wider? would require a bit of work, especially the timer...

Actually having the powerups drop down from the hit block on-screen?... you're kidding, right?

EDIT: that's common? I have it actually set 1->Yv when it hits the bottom of the block. it's somehow just passing through the bottom. the zig-zagging is because I have it set so in the middle of the block, it negates Xv

Hmmm... what would the score be based on?

I need ideas.

I have noticed these bugs:
  Occasionally, the ball will pass through a block vertically instead of bouncing off of it.
  The C4 block is somewhat unreliable, and it lags a little.

If you have any idea why this is happening, please tell me.

See readme for version history