VoogaSalad

Names of all people who worked on the project:

• Josh Medway (jwm58)
• Ben Lawrence (bcl19)
• Justin Havas (jah135)
• Erie Seong Ho Han (eh174)
• Junyu Liang (jl751)
• Kyle Hong (sh394)

Date you started, date you finished, and an estimate of the number of hours worked on the project each person's role in developing the project

• Joshua Medway (jwm58) started: 10/29/19 finished: 12/11/19 Hours worked: ~15 hours per week
• Ben Lawrence (bcl19): Started on 10/29/2019, finished 12/11/2019, 15 hours/week
• Justin Havas (jah135): Started: 10/29/19, finished: 12/11/19, 12 hour/week
• Erie Seong Ho Han (eh174): Started on 10/29/2019, finished 12/11/2019, 15 hours/week
• Junyu Liang (jl751): Started on 10/29/2019, finished 12/11/2019, 13 hours/week
• Diane Lin(dl257): Started on 10/29/2019, finished 12/11/2019, 13 hours a week
• Kyle Hong(sh394): Started on 10/29/2019, finished 12/11/2019, 15 Hours/Week

Any books, papers, online, or human resources that you used in developing the project

• https://stackoverflow.com/questions/21083945/how-to-avoid-not-on-fx-application-thread-currentthread-javafx-application-th
• https://www.tutorialspoint.com/java/java_networking.htm
• https://www.tutorialspoint.com/java/java_networking.htm
• https://www.geeksforgeeks.org/singleton-class-java/
• https://docs.oracle.com/javase/8/javafx/

Files used to start the project (the class(es) containing main)

• The main class is in src/voogasalad/Main.java.
• Since this project uses xstream, the program must be compiled to a .jar file and the JAR file run instead of just running the main java file.

Files used to test the project and errors you expect your program to handle without crashing

• We created a number of sample games to test the project.
• There are JUnit tests in the src/testing/ package except for tests for data which are within the src/voogasalad/data/test package.

Any data or resource files required by the project (including format of non-standard files)

• Games must be stored in the data/games directory.

Any information about using the program (i.e., required resource files, key inputs, interesting example data files, or easter eggs)

• Games must be stored in the data/games/ directory. They also must be built with the latest version of the authoring environment to run.
• All other images, files, and resources are contained within the jar file itself.

Any decisions, assumptions, or simplifications you made to handle vague, ambiguous, or conflicting requirements

• We assumed that we were only making tower defense games. This means that the only options for characters are attackers, defenders, and obstacles.
• We assumed that only one game would be played at a time to keep from instantiating a new game engine for every game being played.

Any known bugs, crashes, or problems with the project's functionality

• Playing the games too much will cause it to crash because of poor memory management (not due to a bug per se, just no memory management implemented)
• The social center requires quitting and restarting the program to update with the newest game high scores
• Game icon is not loaded back into the authoring environment when loading a game XML file
• If a game map is REALLY complex (as in more than 8 or 9 spawn points and the map size is 35 by 35 cells and all the spawn and end points are connected to each other), the xml file will not be made properly sometimes and the game will not load because the xml file will be too large.
• To play the game that has been saved, the user must go out of the game and go into that game again through the game selecting screen.

Any extra features included in the project

• Live Game editing
• AI
• Social Center

Your impressions of the assignment to help improve it in the future

• Pretty fun assignment. Lot of work but worth it if you have a good team, which I think we did
• Great experience working on a big team. Really showed the importantance of communication and making sure APIs are planned correctly.