Serious Business – Team of Six
Title: QA Lead / AI Lead
Language: Visual Studios, C++
Source Control: Alienbrain
Direct Input –
- Created a class that modifies a struct that contains values of specific keyboard buttons and mouse input that uses Direct Input
- User can create many different structs and store it so that it can be use at different state of the game
- The class calls its update to check keys every frame to update the struct
- Struct also keep track of a button being double pressed during a set time interval
- Users check for keyboard and mouse inputs by using the data inside the struct
Lua –
- Use to handle game constancy changes and reactions
- Tweaking gameplay such as weapons’ firepower
Weapons Systems -
- Responsible for all projectiles created by the players and the enemies
- Gravity is applied to Cannon shot and the Bomb drop
- Replacing a specific projectile with another after collision
- Indicator will be shown to where the bomb will land as it falling
Collision Reaction –
- Handles the reactions among game objects buy calling a Lua file on collision
- Damages to objects and points are being applied
- To save processing time, collision checks between bullets are skipped
AI programming –
- Responsible for All Enemies Tanks, Turret, and Bombers behavior and movement
- Programmed Navigation Meshes and implemented for path finding for AI
- Navigation Meshes are laid out and exported from Maya
Debugging -
- Spends time on testing for bugs once every few days while working on it
- Rate the Bug’s level to determine the priorities of debugging
- Assigning team members to fix bug depending on the bug type
We manage to get a lot of features into our game and still have time to put more into it. I created a Navigation Mesh before this class started and implement it into our game.
We created two types of games to propose to our instructors to select for us to create, however they selected the one that we less wanted to make.
During the design portion of the class we have planned to have a lot of features in our game. When we showed our list to the instructor he notices that there are too much features that would have taken more than 3 months to code.
We decided to remove and add features to our list so that we can condense it to be small enough to be created in 3 months. While removing features we realize that the game begins to seem like the proposal that didn’t get chosen so we base around that idea as well.
We would create a game with only one type of gameplay mode and check with our Instructor after writing down a few features once in awhile during planning stage.
There was also a part of our code that we ended up passing a String of data instead of an enum of number representing states, next time I would make it an enum so that data can be transfer faster.
Download Document, Game, extra Screenshots, and Source Code used for this game(158.2 Mb):
http://www.mediafire.com/download.php?19b3m6c8pp6vucn
Dropbox: