Week 7 Weekly Contribution

Our team met up on Friday to work on refining our prototype and design document.

We created design questions to ask our participants in our user study. We decided to create two versions of our game to test whether user prefer their character to land on co-ordination platforms or go through them. Over the weekend, all of us worked on different parts of the game:

Michael worked on coding the game and fixing glitches for our prototype.

Dan worked on the level design with Michael and also the design documentation.

Wilson, Tim, Dan and I conducted user tests after the prototype has been completed and worked on refining our design documentation and our combining our user test results online on Sunday.

After the lecture, we discussed what we wanted to include in our level design and what is more important to complete and decided that the level design should be done first along with enemies and platform placements. This was from the guest speakers feedback that we need to focus on our level design and character control first before pushing further in our game development.



Week 6 Weekly Contribution

We met on Friday during the reading break and found some issues that we need to address.

1.) Graphics:

We have issues with using RageSpline graphics, and dicussed that it didn’t no have anything to do with OnCollision or OnTrigger in the script. Michael found that it is probable the 3D / 2D plane of the objects that we created using RageSpline in Unity.

Dan decides to research more on RageSpline

Wilson is almost done with the enemies graphics

Tim and I will continue to work with the level design and the graphics (we plan to find alternatives to implementing graphics through Maya or Illustrator

Michael will continue to work on the programming, now including checkpoints, enemies, and energy.

2.) Endurance/Energy Bar

We wanted to decrease the players energy bar as the move, jump, …etc but we found through internal testing that it is to hard to accomplish a stage with the limited energy that we provide. We decide that the player should collect energy as they explore the terrain instead of decrease their energy because this is an explorational type of game. We plan to decrease some energy when they use their powers collected from the artifacts.

3.) Artifacts

For the artifacts, we decide instead of just having them be placed in hard to reach places is to give them the artifacts as an accomplishment for exploring the terrain. We have to decide the checkpoints where they receive these artifacts.

This week, we were unable to meet today after class because of personal issues(sick, other projects due..etc), but we have communicated online to continue with our tasks beforehand and meet on our usual Fridays.


Week 5 Reading Break Contribution

We all split the work done on our own:

Wilson: works on animation of character: walking, running, jumping and creating enemies.

Dan: narrative, video pre-story

Michael: works on the programming adding endurance bar, and collecting artifacts.

Tim and I: met up to work on the level design of the game because we found that that learning curve is quite high (exponentially).

We had some difficulties with using Unity because we are new and there was some problem with the collision.

-when we form just rectangles, there is collision with the sprite and the sprite animation works (legs moving while walking,running and jumping)

-but when we try to create our graphics with mesh using the plugin “Ragespline”, the sprite animation does not work and the sprite is gliding on the mesh block create.

-We found some answer about OnTrigger and OnCollision and found that we need to code it, so we plan to ask Michael for help on that.

We plan to meet up this week before the end of the reading break.

Week 4 Game Critique 3: Tetris DS- Marathon

The original Tetris came out dozens of years ago, countless spin-offs and re-imaginings have since been released with varying degrees of success. Now it’s Nintendo’s turn to add their magical touch to Tetris with Tetris DS for the Nintendo DS.

There are six main modes in Tetris DS, and each of them has their own theme. The standard Tetris mode is your most simple. Differently shaped blocks fall down from the top of the screen one at a time, and the goal is to create a line of shapes in a given row. Clear a row, and your score increases. Clear two or more lines, and you score even more points.

Push is a unique take on the Tetris formula. It uses a Donkey Kong theme as its background. Opponents try to push each other’s blocks into their opponent’s area by clearing two or more lines. So while your blocks are falling downward, your opponent’s blocks are falling upward. Hence how you’re pushing one another by clearing lines. Once the bundle of blocks has infiltrated the danger line of a given player, the push battle is over and a victor is crowned.

Game Level Fun: High Concepts

Ergonomics is used in the game in a way where the AI opponent is away for the player’s comfort level and the difficulty level increases as the player pushes the opponent to win the game.

The flow of the game is based on the difficulty level, it gets more intense as player hold on longer and continues to push/battle the opponent. It begins rather simple, but the opponent picks up their pace in clearing lines, the difficulty is rather linear and gradually increase the difficulty. This would keep the players hooked because they want to win and beat their opponent. There isn’t much wow factor, with impressive graphics but rather the competitiveness that motivates the players to play. The more challenging, the more the player gets hooked into the game; hence they become hooked even without the impressive graphics. The game focuses more on skills and the players to respond and react to situations that they are put on the spot as well as strategy of how to win quickly or not lose so fast.

Week 4 Contribution

With our weekly Friday meeting, we were able to conduct our user testing after Michael created a prototype for testing our color changing mechanic. We all tried to play with the prototype and found new findings of the responsiveness of the controls and getting use to idea of color switching in the game.

Dan, Tim and I found participants to test our game prototype after we have create a few challenging obstacles. Dan guided the users if there were questions they wanted to ask during the test, Tim observed participants reactions, and I took pictures for our report. Tim guided the post game interview and we helped with asking questions as well.

After, we set up a time to meet on the weekend online to finish the report. Everyone contributed on the google doc.