User:Nightmareci

Definitions

In this page, the very top row is row number 0, the row below the top row is row number 1, and so on, until 20 (TGM1 has 20 visible rows + 1 vanish zone row).

Tetris The Grand Master

Some of the following information may not be consistent with other wiki pages; where this applies, simply ignore the information elsewhere in the wiki. Corrections to this information by others are only accepted if supported by examples. Information here is still work in progress.

Gravity

Directly from Tetris The Grand Master, here is the gravity curve:

Internal Gravity[1]

Level	Interal Gravity (1/256 G)	Level	Internal Gravity (1/256 G)
0	4	220	32
30	6	230	64
35	8	233	96
40	10	236	128
50	12	239	160
60	16	243	192
70	32	247	224
80	48	251	256 (1G)
90	64	300	512 (2G)
100	80	330	768 (3G)
120	96	360	1024 (4G)
140	112	400	1280 (5G)
160	128	420	1024 (4G)
170	144	450	768 (3G)
200	4	500	5120 (20G)

This is also based on a timings table in Tetris The Grand Master, but is modified to better fit observations I've made:

Delays

Level	DAS (frames)	Lock (frames)	Lock flash (frames)	Line clear (frames)	ARE (frames)
000 - 999	14	30	4	41	27

The different ordering is chosen such that it somewhat represents the order in which each delay happens, left being first, right being last, although DAS charging can occur during ARE.

In the following, "gravity_count" is the current Gravity Count; "gravity" is the current Gravity Speed, and is equal to one of the Internal Gravity entries in the above table; das_counter is the current count of DAS charge frames. A % is used to represent a "remainder of division" operator (commonly known as "modulo", i.e. 13 % 5 == 3). All division has the fractional part truncated, as in ISO C (60/256 == 0, 252/256 == 0, 260/256 == 1).

When I say uninteractive, I mean that any input the player sends results in no observable behavioral changes with the game. ARE is technically an interactive period of the game, as you can charge DAS. IRS is not processed in ARE, but on the very first frame of piece display.

TGM1 only accepts 1 rotation input per frame; if multiple rotation inputs are pressed down on the same frame, then no rotation input is registered. The only way to send a rotation input with no empty frames between inputs is to alternate between separate rotation buttons, be it A/B or A/C.

At the start of a game, there is a single "READY, GO" sequence; it is a special case, in this description:

1. Begin "READY, GO" sequence:
   • 170 frames of uninteractive display until the first pieces' first frame TODO: Expand this after more observations (how long "READY" displays, etc.)

After the "READY, GO" sequence, every frame the following is processed from top to bottom, until the game ends:

1. Interactive gameplay (piece is in field and in control):
   • If this is the first frame of this piece:
     • If placing the piece in row number 1 causes stack intersection:
       • Game over
     • Else:
       • Place the piece in row number 1
       • While the piece is in a row number < (gravity % 256 + 1):
         • If placing the piece 1 row down would cause stack intersection:
           • Break out of this loop
         • Else:
           • Place the piece in the next row
     • If a single rotation input is pressed down this frame:
       • TGM Rotation
       • Play the IRS sound
     • Skip to frame render
   • If a single rotation input is pressed down this frame:
     • TGM Rotation
   • If left/right shift is read this frame:
     • If das_counter == 0 or das_counter == 14:
       • Shift left/right 1 column
     • Else if das_counter < 14:
       • Increment das_counter by 1
   • Else:
     • das_counter = 0
2. Uninteractive delays (lock flash, line clear, ARE):
   • TODO: Fill this up (have enough data currently, just sort it out)

VERY BIG TODO: Create a ton of examples showing specific points of behavior, i.e. interaction of gravity/soft drop.