Assignment 6 a Tetris game written in Ruby.

Overview
This assignment is about a Tetris game written in Ruby. There are four Ruby files involved (provided on
the course website in the zip archive hw6.zip):
1. The Ruby code in hw6provided.rb implements a simple but fully functioning Tetris game (see, for
example, http://en.wikipedia.org/wiki/Tetris#Gameplay).
2. In hw6assignment.rb, you will create a second game that is Tetris with some enhancements, described
below. This is the only file you will submit (other than, as usual, a file you used for testing).
3. The Ruby code in hw6runner.rb is the main starting point. From the command-line (not within irb),
you can run ruby hw6runner.rb to play a Tetris game that includes your enhancements. To use the
original game rather than your code in hw6assignment.rb, run ruby hw6runner.rb original.
4. The Ruby code in hw6graphics.rb provides a simple graphics library, tailored to Tetris. It is
used by the Tetris game in hw6provided.rb. Your code can also use the classes and methods in
hw6graphics.rb (as well as the classes and methods in hw6provided.rb), except for the methods
marked with comments as not to be called by student code. Your code cannot use the Tk graphics
library directly.
You will turn in only hw6assignment.rb, so your solution cannot involve modifying any of the provided
code. Instead, use subclassing (since, after all, this is the OOP portion of the course) to nonetheless reuse
as much of the code as possible. Some code-copying will still be necessary, but you should try to minimize
it. Your solution should also not change any of the provided classes in any way. You will define subclasses
that behave differently. As a result, the provided Tetris game will run without change.
Much of the work in this assignment is understanding the provided code. There are parts you will need to
understand very well and other parts you will not need to understand. Part of the challenge is figuring out
which parts are which. This experience is fairly realistic.
Enhancements
1. In your game, the player can press the ’u’ key to make the piece that is falling rotate 180 degrees.
(Note it is normal for this to make some pieces appear to move slightly.)
2. In your game, instead of the pieces being randomly (and uniformly) chosen from the 7 classic pieces,
the pieces are randomly (and uniformly) chosen from 10 pieces. They are the classic 7 and these 3:
2222
2 22222 222
The initial rotation for each piece is also chosen randomly.
13. In your game, the player can press the ’c’ key to cheat: If the score is less than 100, nothing happens.
Else the player loses 100 points (cheating costs you) and the next piece that appears will be:
2
The piece after is again chosen randomly from the 10 above (unless, of course, the player hits ’c’ while
the \cheat piece" is falling and still has a large enough score). Hitting ’c’ multiple times while a single
piece is falling should behave no differently than hitting it once.
How To Run The Game
We recommend you not use irb to load hw6runner.rb and start a game. We have not had success getting
the graphics library to restart properly more than once inside irb, so you would likely have to exit the REPL
after playing each game anyway. You can use the REPL for testing individual methods and exploring the
program, but to launch a game, go outside irb and run ruby hw6runner.rb (or to make sure the original
unenhanced game still works correctly, run ruby hw6runner.rb original). Make sure the 4 Ruby files are
in the same directory and run the ruby command (or irb when exploring) from that directory.
Requirements
For our testing scripts to work, you must follow these guidelines.
• Your game should have all the features of the original Tetris game, as well as the enhancements.
• The subclasses you create must start with My followed by the name of the original class. For example,
your Tetris class should be called MyTetris. We have provided empty class definitions for you to
complete. You do not need any other classes.
• Do not add to or modify any classes defined in other files or the standard library.
• It is required that your board MyBoard has a next piece method that provides the same functionality
that Board’s next piece provides, which is that it sets @current block to the next piece that will
fall, which might or might not be the cheat piece.
• You must have a MyPiece class and it must define a class constant All My Pieces that contains exactly
the ten \normal" pieces (i.e., the initial seven plus the three additional pieces from enhancement two).
It must not contain your cheat piece. It must be in the same format as the All Pieces array in the
provided code.
• All your new pieces, including your cheat piece, must use the same format as the provided pieces.
• Do not use the Tk library directly in any way. The only use of Tk should occur indirectly by
using instances of classes defined in hw6graphics.rb as needed (only a little is needed). Do not have
require ’tk’ in your hw6assignment.rb file (or any other use of require for that matter).
Advice and Guidance
• For the piece you are adding that has 5 squares in it and is not a line, be sure to add the piece as
pictured and not its mirror image.
• It takes time to understand code you are given. Be patient and work methodically. You might try
changing things to see what happens, but be sure you undo any changes you make to the provided
code.
2• The sample solution is about 85 lines of code. As always, that is just a rough guideline; your solution
might be longer or shorter.
• While you should not copy code unless necessary, some copying will be necessary. After all, the original
game may not have functionality broken down into overridable methods the way you would want and
you are not allowed to change the provided code. This is a fairly realistic situation.
Challenge Problem
First, in hw6assignment.rb, create classes MyTetrisChallenge, MyPieceChallenge, and MyBoardChallenge
that subclass the classes you modified to complete your enhancements. Second, modify hw6runner.rb so
that running ruby hw6runner.rb challenge uses these new classes. Third, in these classes add a fourth
enhancement to your game that is interesting and not similar to the enhancements already required. Fourth,
in a short text file challenge.txt, explain what your enhancement is and how you implemented it. Enhancements that are particularly easy will not necessarily receive credit; aim for something at least as substantial
as the required enhancements and perhaps affecting a different part of the game. Fifth, make sure your main
solution (what runs with ruby hw6runner.rb) is not affected | your fourth enhancement should only be
in your new subclasses.
Your challenge problem may use the Tk graphics library directly if you wish | you are not limited to the
functionality in hw6graphics.rb.
Do not share your enhancement with anyone unless they already have their own. We do not want to see the
same thing twice except by coincidence.
Turn-in Instructions
Turn in hw6assignment.rb and a testing file hw6tests.rb. Follow the link on the course website (homework
section) for the web-form for submitting your files. If you do not do the challenge problem, turn in only
these two files. If you do the challenge problem, also turn in hw6runner.rb and challenge.txt.
3