Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>CSCS2320 Data Structures</fs></WRAP>
</WRAP>

======PROJECT: Make A Game (MAG2)======

=====OBJECTIVE=====
Implement a puzzle game that uses doubly-linked queues and during gameplay applies the use of bitwise or set logic to progress or succeed in the game.

This is part 3 of 3. You are expected to finish the game this week, fully functional with polish.

=====TASK=====
Implement program in Vircon32 C, that:

  * implements a block-based puzzle game, in the vein of Dr. Mario or Tetris, that:
    * incorporates some direct gameplay application of bitwise logic or set logic in the game progression and success.
    * game should (eventually) be polished, with intuitive controls, sound effects, music, and a functional, consistent gameplay.

=====EDIT=====
You will want to go [[/notes/fall2024/projects/magX|here]] to edit and fill in the various sections of the document:

  * [[/notes/fall2024/projects/magX|https://lab46.g7n.org/notes/fall2024/projects/magX]]

{{page>notes:fall2024:projects:magX&nouser&nodate&nomdate&editbtn}}

=====SUBMISSION=====
To be successful in this project, the following criteria (or their equivalent) must be met:

  * Project must be submit on time, by the deadline.
    * Late submissions will lose 33%  credit per day, with the submission window closing on the 3rd day following the deadline.
  * Executed programs must display in a manner similar to provided output
    * output  formatted,  where applicable,  must match  that of  project requirements
  * Processing must be correct based on input given and output requested
  * Output, if applicable, must be correct based on values input
  * Code must be nicely and consistently indented
  * Code must be consistently written, to strive for readability from having a consistent style throughout
  * Code must be commented
    * Any "to be implemented" comments **MUST** be removed
      * these   "to  be  implemented"   comments,  if  still  present  at evaluation time, will result in points being deducted.
      * Sufficient  comments  explaining  the point  of  provided   logic **MUST** be present
  * No global variables (without instructor approval), no goto statements, no calling of main()!
  * Track/version the source code in your lab46 semester repository
  * Submit  a copy of  your source code to  me using the  **submit** tool by the deadline.

====Submit Tool Usage====
Let's  say you  have completed  work  on the  project, and  are ready  to
submit, you  would do the following:

<cli>
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
</cli>

You should get some sort of confirmation indicating successful submission
if all went according to plan. If  not, check for typos and or locational
mismatches.

=====RUBRIC=====
I'll be evaluating the project based on the following criteria:

<code>
624:mag2:final tally of results (624/624)
*:mag2:code, XML, build script, and cartridge submitted [104/104]
*:mag2:implements and functionally utilizes doubly linked queues [104/104]
*:mag2:some aspect of progress captured on our way toward mag2 [104/104]
*:mag2:screenshots, video produced showing aspects of game runtime [104/104]
*:mag2:screenshots, video posted to discord channel [104/104]
*:mag2:committed to lab46 semester repo [104/104]
</code>

===Pertaining to the collaborative authoring of project documentation===

  * each class member is to participate in the contribution of relevant information and formatting of the documentation
    * minimal member contributions consist of:
      * near the class average edits (a value of at least four productive edits)
      * near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
      * no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
    * adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
    * content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
      * no contributions, co-efficient is 0.50
      * less than minimum contributions is 0.75
      * met minimum contribution threshold is 1.00

===Additionally===

  * Solutions not abiding  by spirit of project will be  subject to a 50% overall deduction
  * Solutions  not  utilizing descriptive  why and  how comments  will be subject to a 25% overall deduction
  * Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
  * Solutions not organized and easy to  read (assume a terminal at least 90 characters wide, 40 characters tall)  are subject to a 25% overall deduction
Lab46 Wiki

User Tools

Site Tools

Page Tools
