User Tools

Site Tools


Sidebar

projects

wcp1 (due 20240828)
btt0 (due 20240904)
wcp2 (due 20240904)
pct0 (bonus; due 20240905)
pct1 (bonus; due 20240905)
pct2 (due 20240905)
abc0 (due 20240906)
msi0 (due 20240911)
pct3 (bonus; due 20240911)
wcp3 (due 20240911)
msi1 (due 20240918)
pct4 (due 20240918)
wcp4 (due 20240918)
dsr0 (due 20240926)
pct5 (bonus; due 20240926)
wcp5 (due 20240926)
gfo0 (due 20241002)
pct6 (due 20241002)
pnc0 (due 20241002)
wcp6 (due 20241002)
dsr1 (due 20241009)
pct7 (bonus; due 20241009)
wcp7 (due 20241009)
bwp1 (bonus; due 20241016)
pct8 (due 20241016)
pnc1 (due 20241016)
wcp8 (due 20241016)
pct9 (bonus; due 20241023)
pnc2 (due 20241023)
wcp9 (due 20241023)
gfo1 (due 20241030)
mag0 (due 20241030)
pctA (due 20241030)
wcpA (due 20241030)
mag1 (due 20241106)
pctB (bonus; due 20241106)
wcpB (due 20241106)
mag2 (due 20241113)
pctC (due 20241113)
wcpC (due 20241113)
pctD (bonus; due 20241120)
wcpD (bonus; due 20241120)
pctE (bonus; due 20241204)
wcpE (bonus; due 20241204)
haas:fall2024:discrete:projects:mag0

Corning Community College

CSCS2330 Discrete Structures

PROJECT: Make A Game (MAG0)

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 1 of 3. You do not have to finish the game this week, instead, aim to complete about a third, submitting your current snapshot.

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 here to edit and fill in the various sections of the document:

MAGX

the game

The game criteria is intentionally very open-ended. The goal is to make a game that incorporates logic into a fun challenge. Thus far, many students are opting to adapt a game that already exists, but one could design a game from scratch if they so desired.

Game ideas

Game ideas one could make are Dr.Mario where the colors are logic gates and you have to modify the pills so that when a certain number are together they disappear.

One could also make the hit Commodore 64 game Number Builder but instead of numbers it is bits. Where each “tile” color is a different logical operation that affects your current number until you can get to the target number.

One could also make a tower defense game where you place towers that relate to each kind of logic and that shoot a certain number to an “enemy” number that then changes that enemy's “value.” And you keep shooting at that enemy until they become a certain number, probably zero would be the easiest.

One could also do a shooting game where you and the enemies have bullets and you shoot their bullets with different logic to turn their bullets into zero's so that they can't hurt you.

One could do a rhythm game where you have to press the right key (logic) for the right note (some number) to make it zero.

Logic

For refresher, there are seven logic operations one will want to make use of. This includes:

AND OR XOR

NOT

NAND NOR XNOR

AND

 A B | Y
 ----|--
 0 0 | 0
 1 0 | 0
 0 1 | 0
 1 1 | 1
 

OR

 A B | Y
 ----|--
 0 0 | 0
 1 0 | 1
 0 1 | 1
 1 1 | 1
 

XOR

 A B | Y
 ----|--
 0 0 | 0
 1 0 | 1
 0 1 | 1
 1 1 | 0
 

NOT

 A | Y
 --|--
 0 | 1
 1 | 0
 

NAND

 A B | Y
 ----|--
 0 0 | 1
 1 0 | 1
 0 1 | 1
 1 1 | 0
 

NOR

 A B | Y
 ----|--
 0 0 | 1
 1 0 | 0
 0 1 | 0
 1 1 | 0
 

XNOR

 A B | Y
 ----|--
 0 0 | 1
 1 0 | 0
 0 1 | 0
 1 1 | 1
 

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:

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

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:

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

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
haas/fall2024/discrete/projects/mag0.txt · Last modified: 2024/10/16 17:57 by wedge