PROJECT: Fun With Games (FWG2)
- OBJECTIVE
- EDIT
  - FWGX
- SUBMISSION
  - Submit Tool Usage
- RUBRIC

Corning Community College

CSCS1320 C/C++ Programming

PROJECT: Fun With Games (FWG2)

OBJECTIVE

Continuing to incorporate programming concepts learned through the semester, in conjunction with functions from the Vircon32 API, implement on-screen opponents, collision detection, projectiles (as appropriate), points/score/progress indicator.

If you are having trouble creating a scenario to shoot for, try something like:

Warlords (Atari game)

EDIT

You will want to go here to edit and fill in the various sections of the document:

https://lab46.g7n.org/notes/cprog/fall2024/projects/fwgX

FWGX

URLs

Vircon32 API

displaying text

processing textures and regions

displaying a region at location

gamepad

To get inputs from a gamepad you can include the input.h header file.

Most functions return a integer value that represents whether a button is being pressed or not

int buttonA;
buttonA = gamepad_button_a()

if(buttonA == 1)
{
  print_at(0, 0, "Button A pressed");
}

if(gamepad_button_a() == 1)
{
  print_at(0, 0, "Button A pressed");
}

Some functions require an adress input: such as gamepad_direction()

int directionX;
int directionY;

gamepad_direction(&directionX, &directionY);

if(directionX == 1)
{
  print_at(0, 0, "Right pressed");
}
else if(directionX == -1)
{
  print_at(0, 0, "Left pressed");
}

if(directionY == 1)
{
  print_at(0, 18, "Up pressed");
}
else if(directionY == -1)
{
  print_at(0, 18, "Down pressed");
}

structures

bounds checking

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:fwg2:final tally of results (260/260)
*:fwg2:all files needed to build cartridge are submitted [32/32]
*:fwg2:code compiles, cartridge builds with no warning or error [32/32]
*:fwg2:game incorporates onscreen assets other than player [32/32]
*:fwg2:interaction between onscreen assets is present [32/32]
*:fwg2:collision detection between onscreen assets [36/36]
*:fwg2:structs continue to be used for organizing data [32/32]
*:fwg2:tracking of game information done and displayed [32/32]
*:fwg2:committed project related changes to semester repo [32/32]

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 1kiB 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

Table of Contents