This topic is for the purpose of discussing #6631: Fraplatek's NES Tengen Tetris "30 lines" in 00:53.63

I'm just pointing it out, it has pretty much the same submission text as the published movie's (obvious omissions are obvious). Another thing to point out to everyone else is we should probably look at the other submission cause well... that time yo (also cause I can't be bothered spiking something already spiked). (inb4 Judge updates the file and deletes the other submission) Or I'll just write three frame improvement at the very start of the gameplay. (over the proper truncated submission obviously) Tengen Tetris is a special case of set seeds. If the correct seed can be found well an improvement can be found as well like this one did... --- Adjusting PikachuMan's input towards the end to not be slow beats this movie out by 80 frames. It raised questions when it was a: Pik: 3, 1, 1, 2, 2, 2, 4, 4, 2, 3, 4, 2. versus a You: 2, 3, 1, 3, 4, 4, 2, 1, 2, 1, 1, 1, 1, 4. Meaning that yours should've been slower for going for those singles. The only reason you were 10 frames faster was due to the fact that the ending input on the published TAS was bad.

I watched the old Tengen Tetris TAS just yesterday or so, oddly enough. And I did notice that it seemed like it had a low amount of Tetrises, since the animation for a line clear is the same length no matter how many lines. Spikestuff offered me to help him try and get a high-Tetris/Triple run after I expressed interest, and it sounded fun enough. At the moment, with a very horrible ending, I have 1604 frames (26.689 seconds, vs. this one's 28.919): http://tasvideos.org/userfiles/info/61514363070078918 So obviously this movie isn't optimized, and neither is mine, but I think it would be interesting if a little frame war starts here... Anyone else interested? This feels like there may be a more Lua-centric way to figure out the best possible starting RNG and setup, but I wouldn't even know where to begin with that. Something that would be very useful is a Lua script that shows the next few pieces, however. So far I've found: 0034 and 0035 seem to seed the RNG (change every frame) 005C and 005D are the in-game RNG (only change when a new piece is pulled) Spikestuff found 0066 is the next piece: 1 - I 2 - T 3 - O 4 - J 5 - L 6 - S 7 - Z Trying to debug, instruction 9930 is where 0066 is written, and 9A08 seems to be where 005C is written afterwards.

Well, rather than a disassembly approach, I decided to take a brute force approach and simply simulate what the upcoming 80 blocks will be. Here's a Lua script that will show you 7 extra upcoming pieces (designed for 2x window size) https://pastebin.com/4H75aayN Although technically, this is off-topic, so I'll move any further optimization talk to the game thread for Tengen Tetris: http://tasvideos.org/forum/viewtopic.php?t=3761 As for Fraplatek's (two) submission(s), well, the main time save in this game is minimizing the number of separate line clears, and this run certainly doesn't do that.

om, nom, nom... blech, salty!