The B stands for BASIC, since I know very little asm. :p

You might be asking "Why BASIC? We already have TetricA, and it's awesome."

And I will agree with you on that, it is awesome.

This is actually my first forays into building a tetris game. I've been trying to expand myself into other things beyond that of RPGs, and since I've never done this before, I figured this could be a fun learning experience.

As it stands right now,

I have the pieces to where they fall to the bottom

Full rotation on all 7 pieces and their varying forms

The pieces do not rotate past the right side boundary

The program is 1870 bytes in size



And the DCS8 icon:

Thoughts so far?

Not really, is just me trying to follow the rules. Tetris is generally created on a 10w x 20h board. Since Pt-On( doesn't have colors when choosing options 2 and 3, I went with option 1 which puts 3x3 squares up. It sadly makes the playing area a bit smaller. It also gives me the ability to minimize code and make things more efficient.

Got a bit more working this evening:



And right after I stopped that screenshot, I decided to see how it handled rotating the piece and seeing if that stacked properly:



So, what do you guys think so far?

I'm going to try throwing it at my calc and 'play' as it stands right now. I know I still have to do the line fill checking, but that can wait until I'm sure every piece fits in properly and all the checking is done correctly.

I can make it a little bigger and ignore the set rules of Tetris, without overly affecting the size of the program, just the size of the matrix. I've thought about doubling the size of the sprites into 6x6 blocks.. The only thing that would add would be.. 4 times the amount of Pt-On( commands, and would slow down drawing and erasing of the blocks. I might look into that once I have a fully working version going. Kind of up in the air, I really want to keep this below 3kb if at all possible.

I also fixed all collision detection and hid code off in boolean blocks to speed up the loops, so it goes a bit faster now.

Thanks at least for the partial compliment. lol

I haven't looked into the asm bit, honestly not even sure where to get it.

As to using the Line(s, I'd have to modify how the pieces are stored, which is currently a list in a format of {how far right, how far down, how far right, how far down, how far right, how far down, how far right, how far down} which is in values of 0,3,6,9, since Pt-On( with option 1 is 3x3 pixels.

did you also check for collision above your piece when turning, so that if you put the piece inside a 'cave' it could get higher when turning...(do you know what i mean?)

Looks kinda good for BASIC. I assume that it would be best to not play this for too long at once, though, else your eyes will get tired from the small screen.

so tiny

But still nice!