Project Description

This will be a race among all programming languages. War of the languages!!! The human player will be the Assembly Mobile, and the other AI routines will be named C-Mobile, Fortran Mobile, Basic Mobile, etc. There will be point and time bonuses. Running over (picking up) certain items like a RAM chip, resistors, capacitors, intel symbol, etc. can be used for point bonuses. Time bonuses are possible only through the pick-up of a clock symbol. Obstacles are included in this game also. Such obstacles include undefined variable , mismatch arguments, char-to-int warnings, etc. This will result in points taken away. Objective: be the first to terminate successfully. i.e. Don`t: lose to another (AI) player, or run over an infinite loop symbol or segmentation fault.

Main Game Control

GameMain By Charlinda Catchings

Purpose: Control/maintain game flow

Initialize registers to correct segment

Initialze for correct mode (video, text, etc.)

Set up and maintain music

Set up Introduction Screen

Set up Selection Screen

Respond to player's keyboard input:

when making a choice from Selection Screen

when player makes a decision on the movement of the car(R,L,Up)

Continuous updates of:

screen

player's time and/or score

player and AI position

player and AI speed

If player wins/crashes, set up Win/Lose Screen

Inputs:

Keyboard controls

Outputs:

JICE's Run-Time Racers game

AI

Variables:

PlayerMaxSpeed - used by UpdateMaxSpeed
Next_X_Coord – used by EnemyAI
Next_Y_Coord – used by EnemyAI
Next_Speed – used by EnemyAI

Procedures:

EnemyAI: Written by Il-Sun Park

Purpose: EnemyAI will be called for every computer challenger in JICE’s racers. The AI, which will have varying degrees of intelligence for each computer challenger, will determine through a number of factors what the next x-y coordinate and speed the computer challenger will have. The top computer challenger will be at 94% of the players maximum speed reached- this will offset the fact that the computer maneuvers more skillfully than a human player. As the intelligence of the AI player goes down, so does its top speed. The AI will be able to bump opponents, by sensing if anyone is near, then changing direction and speed accordingly. It will be able to dodge obstacles in the same fashion. This will be a c-style procedure.
Inputs:

Prev_X_Coord – computer challenger’s previous x-position

Prev_Y_Coord – computer challenger’s previous y-position

Prev_Speed – computer challenger’s previous speed

Outputs:

Next_X_Coord – computer challenger’s next x-position

Next_Y_Position – computer challenger’s next y-position

Next_Speed – computer challenger’s next speed

UpdateMaxSpeed: Written by Il-Sun Park

Purpose: UpdateMaxSpeed takes previous PlayerMaxSpeed, checks whether current speed is faster, if so, updates PlayerMaxSpeed. C- style procedure. Called by EnemyAI.
Inputs:

PlayerMaxSpeed

Outputs:

PlayerMaxSpeed

CheckEnemy: Written by Il-Sun Park

Purpose: CheckEnemy checks a 20x20 grid in front of the computer challenger to see if any enemy cars are there. If so, tells EnemyAI to maneuver towards them. C-Style procedure called by EnemyAI.
Inputs:

Prev_X_Coord – computer challenger’s previous x-position

Prev_Y_Coord – computer challenger’s previous y-position

Prev_Speed – computer challenger’s previous speed

Outputs:

Next_X_Coord – computer challenger’s next x-position

Next_Y_Position – computer challenger’s next y-position

Next_Speed – computer challenger’s next speed

CheckCourse: Written by Il-Sun Park

Purpose: CheckCourse checks a 30x30 grid in front of the computer challegner to see if any obstacles, powerups, etc. are there. If so, tells EnemyAI to maneuver away/towards them, depending on what it is. C-Style procedure called by EnemyAI.
Inputs:

Prev_X_Coord – computer challenger’s previous x-position

Prev_Y_Coord – computer challenger’s previous y-position

Prev_Speed – computer challenger’s previous speed

Outputs:

Next_X_Coord – computer challenger’s next x-position

Next_Y_Position – computer challenger’s next y-position

Next_Speed – computer challenger’s next speed

User Interface

Purpose: This portion of the project deals with the user of the game. It takes all the inputs given by the user and outputs to the proper screens or playing of the actual game. The screens that will be used will be an Introduction Screen, Options Screen, Instruction Screen, Player Screen, and Win/Lose Screens. This portion will also deal with the user moves. It takes the variables of his direction, acceleration, and so on.

Variables:

Accelerator: Up_Arrow or A_key
Brake: Down_Arrow or B_key
Right: Right_Arrow
Left: Left_Arrow
Enter_Key: Enter Key
Exit_Key: Esc Key
Introduction Screen: Sets Screen to Introduction
OptionsScreen: Screen used to display options
DriverScreen: Screen used to select player
InstructionScreen: Screen used to view instructions
CreditScreen: Screen used to display credits
Win Screen: Screen used to show if user won
Lose Screen: Screen used to show if user lost
OldKeyV, OldTimerV: Hold pointers to the default timer and keyboard interrupt.
TimerCount: Incremented by the timer interrupt every time it is called.
OptionState: Gives player options to play, view instructions, or exit game.
LangDriver: Lets the user choose which language they want to compile with.
PlayDir: Variable that tells which direction player is going in
PlayerSpeed: Variable that increases speed based upon if Accelerator or Brake is pressed

Procedures:

Introduction: By Eilleen Berganos

Purpose: Introduction of Game to User
Inputs: Enter_Key
Outputs:

Implements Introduction Screen to User

Brings Player to Options Screen

Notes: LoadPCX is used

OptionsScreen: By Eilleen Berganos

Purpose:

User can select driver

User can view instructions

User can exit game

Inputs:

Right: Right_Arrow

Left: Left_Arrow

Enter_Key: Enter Key

Exit_Key: Exit Key

Outputs:

If OptionState =1

Calls SelectLanguage procedure and Driver Screen

OptionState=2

Calls Instructions procedure and Instruction Screen

OptionState=3

Exits Game and calls Credits Screen

SelectLanguage: By Eilleen Berganos

Purpose:

User selects which language in which they will compile.

Inputs:

Right: Right_Arrow
Left: Left_Arrow
Enter_Key: Enter Key

Outputs:

If LangDriver =1
Selects Assembly as Driver
LangDriver = 2
Selects Visual C++ as Driver
LangDriver = 3
Selects Fortran as Driver
LangDriver = 4
Selects Scheme as Driver

Instructions: By Eilleen Berganos

Purpose:

Lets user view instructions for game.

Inputs: None

Outputs:

Instruction Screen

Plays Music

WinScreen: By Eilleen Berganos

Purpose:

Displays Win Screen

Inputs: None
Outputs:

Win Screen

Plays Music

LoseScreen: By Eilleen Berganos

Purpose:

Displays Lose Screen

Inputs: None
Outputs:

Lose Screen

Plays Music

CreditsScreen: By Eilleen Berganos

Purpose:

Displays Credit Screen

Inputs: None
Outputs:

Credit Screen

Plays Music

InstTimer, DeInstTimer, MyTimerHandler: By E. Berganos

Purpose: Controls pace of the game similar to what was used in MP3 but with some modifications for our game.

InstTimer:

Saves default interrupt vector in OldTimerV

DeInstTimer:

Restores OldTimerV as default timer routine

MyTimerHandler:

TimerCount is incremented every time called.

Sends ACK and end-of-interrupt

Inputs:

InstTimer: None

DeInstTimer: OldTimerV

MyTimerHandler: TimerCount

Outputs:

InstTimer: OldTimerV

DeInstTimer: None

MyTimerHandler: TimerCount

InstKey, DeInstKey, MyKeyHandler: By Eilleen Berganos

Purpose: Sets game controls when key is pressed. Similar to what was used in MP3 but with large variation because of the number of variables that is controlled.

InstKey:

Saves default vector for OldKeyV

DeInstKey:

Restores default interrupt vector for OldKeyV

MyKeyHandler:

Sets Exit_Game to one if the Esc key is pressed.

Sets PlayDir to either left or right depending if left or right is pressed.

Sets PlayerSpeed to slow or speed up depending if Brake or Accelerator is pressed.

Sends ACK and end-of interrupt.

Inputs:

InstKey: None

DeInstKey: OldKeyV

MyKeyHandler: None

Outputs:

InstKey: OldKeyV

DeInstKey: None

MyKeyHandler: Exit_Game, PlayDir, PlayerSpeed

Graphics and Sound

Variables:

ImageSeg: a segment that contains the currently useful 320x200 image
FontSeg: a segment that contains a 320x200 font map
Letters: a variable whose offsets contain offsets into the font map for each ASCII character
ScreenBuffer: a segment containing the 320x200 pixels that are to be mapped to the CRT
ZBuffer: a segment containing values that correspond to images on the 320x200 screen. For example, player 1 is represented by a 9 in ZBuffer, but by a complex image in ScreenBuffer. This data will be used to determine collisions, and to assist in AI.
FontFile: the null-terminated filename string of the PCX file containing the font map
ScratchPad: a temporary buffer used by LoadPCX for decompression
"Various" null-terminated strings: represent filenames of the various files used as splash screens, sound files, etc.

Procedures:

LoadPCX by John Smolen

Purpose: This function takes a 320x200 PCX file and decompresses it into a buffer for later use.
Inputs:

AX: offset of the buffer to write into

DX: offset of the filename string

Outputs:

ImageFile: 320x200 decompressed PCX file

Splash by John Smolen

Purpose: This function takes a segment containing a 320x200 image, and puts it into the ScreenBuffer
Inputs:

ImageFile

Outputs:

ScreenBuffer

InitBuf by John Smolen

Purpose: This function initializes ScreenBuffer and ZBuffer to default values
Inputs:

None

Outputs:

ScreenBuffer

ZBuffer

ModeText from MP4 - See MP4

ModeGraph from MP4 - See MP4

PlaySound by John Smolen

Purpose: This function takes a sound file, loads it, initializes the sound card, plays the sound, then cleans up.
Inputs:

DX: offset of filename string

Outputs:

A .wav sound

Notes: Will call helper functions that have not yet been defined.

DrawScreen by John Smolen

Purpose: This function takes the values in ScreenBuffer and ZBuffer to create a completed image on the user's screen
Inputs:

ScreenBuffer

ZBuffer

Outputs:

Image on CRT

DrawPoint by John Smolen

Purpose: This function (C-style) places a point into the ScreenBuffer and ZBuffer at the given coordinates with the given color and type.
Inputs:

X: X position of pixel

Y: Y position of pixel

Z: Image value (see Variables)

Color: The color of the pixel

Outputs:

ScreenBuffer

PutBkGd by John Smolen

Purpose: This function (C-style) draws the background image based on a 320xN-sized image. It will repeatedly place the image, so that the background looks continuous. It will begin placing the image at any specified line, to allow the background to "shift" up or down, giving the appearance of motion.
Inputs:

StartLine: The line within the image to start at. Must be <= TileSize

TileSize: the value N, as seen in the Purpose, specifying the vertical height of the image to be repeated as the background.

BackGrnd: an offset to the upper-left corner of the background tile, within ImageFile

Outputs:

ScreenBuffer

PutImage by John Smolen

Purpose: This function (C-style) places a square image at X,Y within ScreenBuffer and ZBuffer.
Inputs:

X: The X position ( 0 <= X < 320)

Y: The Y-position (0 <= Y < 200)

ImageOffset: The offset of the upper-left corner of the image within ImageFile

ImageSize: The dimensions of the square image

ImageValue: The value to be used in ZBuffer

Outputs:

ScreenBuffer

ZBuffer

DrawStatus by John Smolen

Purpose: This function draws the status bar (the area of the screen containing the score, speed, etc. of the player).
Inputs:

Speed: The speed of the player

Time: The elapsed time

...

Output:

ScreenBuffer

DrawText by John Smolen

Purpose: This function (C-Style) draws text starting at X,Y
Inputs:

FontSeg: The segement containing the font file

X: The X position to start from

Y: The Y position to start from

Register SI: offset to the '$'-terminated string

Color: The color to draw the text in

Outputs:

ScreenBuffer