Hi, I have started some days ago programming Tetris in grammer! Some of you may have noticed me talking about it on chat. Well, for those who don't: I have already pretty much done, I think I'll have the beta up soon!
What I have already done:
 - all blocks, you can rotate them
 - checks that you can't go to far left/right
 - checks that you cant go through other blocks
 - checks whether the block hits the bottom or a other block
 - the possibility for fast down (pressing down-button)
 - automatic go down

Things I have to add for the beta:
 - check whether a line is complete
 - make that line go away
 - check whether you lost
 - put in that it is random what figure appears (easy, just one line of code! )
 - take out the possibility to change the figure by pressing 2ND

Things I then STILL have to do for the full version:
 - score
 - make it go down faster after some time
 - menu
 - high-score list
 - display the next block
( - some other cool features!)

Sorry, I don't have any screenies yet. I don't know if I will even make any before the betta. Please tell what you think about it!

So you have a way to make sure the block doesn't go through another block? Then you can probably use a series of pxl-Test( in a for loop to test if a line is complete. If the shape was 2 blocks tall, you only need to test those two rows.

Use the same idea for checking if you lose

As for shifting blocks down, I am not sure how that will work I know I could whip up some code in Grammer, but it would be a little complicated and use several buffers.

EDIT: Okay, here is the complicated piece code I was talking about It took some thought, but I figured it out
Send(768,"VGBuf→K
37696→J
Lbl "SD→I

<<code>>

.SD
Disp K
ClrDraw
Line(X,Y,H-4,W,1
Fill(10,J
Fill(13,J
Tangent(4,1
Fill(13,J
Disp J
Line(X,Y,H,W,0
Fill(9,K
End
The shifting code is at .SD
The inputs to that subroutine are:

X and Y are the upper left coordinates of the place to begin shifting at
H and W are the height and width of the region to shift down
K points to a 768-byte buffer
J points to the main buffer (usually the graph buffer)
I hope that helps!

So you have a way to make sure the block doesn't go through another block? Then you can probably use a series of pxl-Test( in a for loop to test if a line is complete. If the shape was 2 blocks tall, you only need to test those two rows.

Use the same idea for checking if you lose

As for shifting blocks down, I am not sure how that will work Undecided I know I could whip up some code in Grammer, but it would be a little complicated and use several buffers.

I was already going to make the check weather a line is complete with pixel checks.
And If you lose I wanted to check the y-variable, if it is to small you lose.
And to the shifting: I draw all figures twice: once it leaves the loop where it waits for a keypress/shifting down it draws the figure in white pixels, I change the position of the figure and then I draw it in black ones! xD

Good luck!

I don't know why, but it throughs an error when it shall shift everything down if a line is complete.....
Well, this is the responsible code::For(O,1,26
:0→H
:For(A,1,10
:H +pxl-Test(65535+O*4,1+4*A)
:→H
:End
:If H=10
:Then
:O-1→O
:For(P,0,O)
:For(Q,1,10)
:O-P→R
:pxl-Test(4*R,4*Q)→K
:If K=1
:Then
:Line(4*Q,4*R,4,4,0
:Line(4*Q,4*1+R,4,4,1
:End
:If K=0
:Line(4*Q,4*1+R,4,4,0
:DispGraph
:End
:End
:
:EndPlease help me!

Ok, cool, thanks. I think I'll have beta up soon!
All I need to do now is a check whether you die!

Just tried. Nice!
It gives me syntax error if I die

Thanks both of you!
Yeong: I don't know why it throughs a syntax error, to me it doesn't... :S