Extensions

Extension 1: Programming Contest (2 points):

A TA will demo and sign off on this ONLY if he or she thinks your entry
is worthy of consideration.

To be worthy, you must have implemented some extra features for which you
will receive other extension credit. See the other extensions for this module
for more detail.

Be sure that any pictures, sound, or other files you use in your game
are in your repository and committed. Do not reference files outside your
repository, as they will not be available to the TAs for demo.

This is your chance to show off your great work on our Lab.
If a TA agrees that your work merits consideration for the contest, then take
the following steps to enter the contest and to earn the extra extension points.

Your code most be committed and working, and each of the steps below must be
observed. Failure to follow these instructions will exempt you from the contest
and from earning these extension points.

You must choose one of your team member's repositories to hold the code we
will consider for the contest. Let's call that person P.

In P's repository, in the lab10 folder, create a
README text file:

This
file can be a plain text file that you can create and edit using eclipse.
Right-click on the lab10 package, and select New...Untitled Text File.

Write a few sentences to explain why your entry is special and merits
consideration.

If your entry is not the official class game, then explain what you did instead.

Be sure to note any extra features you have implemented.

List each team member and a brief sentence or two about that person's
contribution to the game entry.

Be sure all of your code (and sound or image files) are self-contained in
P's
repository and committed.

Complete the
box below with all of the names (and wustl keys as usual) of the contestants in your
group.

You will each earn extension points for entering the contest.

You must check the propgate box on the repo that contains your contest
entry code. You should progagate from P's repo.

When you done with this extension, you must be cleared by the TA to receive credit.

Commit all your work to your repository

Fill in the form below with the relevant information

Have a TA check your work

The TA should check your work and then fill in his or her name

Click OK while the TA watches

If you request propagation, it does not happen immediately,
but should be posted in the next day or so

End of extension 1

Extension 2: Game Extra Features 1 (5 points):

To receive credit for this extension, you must show a TA that you have
implemented all of the following described features in your game.

These features are independent of other extension credit you may
receive for the game. Thus, you are free to implement these with, or
without, the other features described in other extensions.

The Blob will on conditions of your choosing vomit
some of its Food. The only requirement for this is that the
Blob looses mass, and there is some indication in the game that
vomiting has taken place. The rest is up to you:

Under what conditions does the Blob vomit?

Perhaps it
eats something that doesn't agree with it.

Perhaps it just happens randomly
on infrequent occasions.

Perhaps you have something else in mind.

What happens to the vomited Food?

Maybe it reappears on the screen and can be subquently eaten again.

Maybe it disappears from the game entirely.

Some sound is emitted when Food is eaten.

Some different sound is emitted when Food is vomited.

When you done with this extension, you must be cleared by the TA to receive credit.

Commit all your work to your repository

Fill in the form below with the relevant information

Have a TA check your work

The TA should check your work and then fill in his or her name

Click OK while the TA watches

If you request propagation, it does not happen immediately,
but should be posted in the next day or so