FIT3094 : AI for Gaming

Assignment Submission the fine print Semester 1, 2015

The assignments are due at the times specified in the course outline.

You will need to exactly follow the provided template for your assignment submission. This will allow other students in the class to play against your AI controller and it will allow the lecturer to assess your work.

The compulsory demo games using your controller will occur during the scheduled lab sessions before the code submission time. If you miss the demo. and do not have a valid medical certificate or other documentation, you will receive a mark of 0N for the assignment as it will not be assessed.

Your code is checked during the demo. to be certain that:

• Your code does not have any of its own global variables or enumerated types – put all of these within your controller class.

• Your code does not have any of its own #defined variables.

• Your code does not seed the random number generator - this is done once in the main() method of the framework.

• Your code does not define any static variables – these would allow multiple ships to communicate, (e.g. by sharing a map) and this is against the rules!

• All your classes are kept in a single pair of .h and .cpp files called AIController##.h and AIController##.cpp where ## are your two code digits.

• All your C++ classes must have a name followed by your code number digits ##.

• The #ifndef variable at the top of your AIController.h file must end with your code digits ##.

• After doing a "make clean", when you compile your code using "make" there must be no compiler warnings generated by your code

• Using these parameters:

100 gold units
40 sea grid size
250 rocks

Your code must be able to run 3 games of 1000 time steps each:
- without crashing
- without printing any of your own text to the screen

After your demo, and before the submission deadline, you have to build an archive of your code and submit it as follows...

1. As you complete the two parts of the assignment make a tar or zip archive of the source code (not the executable) and any written text file documentation (in PDF format or plain text only).
   
   
2. Before the code submission deadline, email the lecturer alan.dorin-at-monash.edu the archive file in an email exactly like this:

   email subject:
   FIT3094 assignment <your ID number> submission

   email body:
   <your full name>
   <your student ID>
   ----- REMEMBER to attach the archive file -----

Each file of your source code must contain the following at the top:

 /* 
  * This software is the original work of <Your Full Name>. ID: <Your ID> 
  * This software is submitted in partial fulfillment of the 
  * requirements for the degree of <Your Degree>, 
  * Monash University
  */ 

You are encouraged to consult reference material as widely as possible, but remember the code you write MUST be your own work. Make sure you think about, and understand, the processes involved rather than blindly copying the work of others.

Please be realistic about what you can achieve given the time constraints.

Late assignments will incur mark penalties according to the Fibonacci sequence. An assignment that is one day late will receive a one mark penalty. Assignments two days late will receive a 2 mark penalty, three days late, 3 marks. The sequence is [1],1,2,3,5,8,13,21. This applies for all days including public holidays and weekends so please submit your assignments punctually!