End of week 12: Bouncing all over the place

--Originally published at TC3045 – Quality and Software Testing

23984384901_e598c1c077_z
“Bounces” flickr photo by David Goehring shared under a Creative Commons (BY) license

This week, I created the fourth level which has a lot of those new obstacles we implemented last week. This level focuses on the use of the walls that makes the player to bounce; actually, almost everything is one of those obstacles. The actual purpose of this level is to make the player to get used to this type of object. It is actually kind of hard but also challenging because you have to avoid some enemies while bouncing around the level.

Week 12: Harder levels

--Originally published at TC3045 – Quality and Software Testing

For this week, we are going to implement new levels using the new type of objects that were implemented last week. With these new obstacles we can create harder levels and make them more challenging for the user.

40664942044_c8166d2436_z
“#Design These surreal stairs” flickr photo by junaidrao shared under a Creative Commons (BY) license

We are also going to internationalize every string we used on the project as a suggestion of our teacher, such as, every word in the main menu and those from the first level that tells you how to move.

End of Week 11: End of sprint

--Originally published at TC3045 – Quality and Software Testing

This week, Andres and I finished the implementation of the new types of obstacles. We had trouble with the one that makes the player to bounce because of the physics, especially when the player touched the object from the sides. We did not have much trouble with the ice object, we just gradually decreased the current speed of the player when it stops moving instead of setting it to zero.

Week 11: The levels are getting colder

--Originally published at TC3045 – Quality and Software Testing

This week, I am going to fix those bugs from the bouncing object and start the implementation of the ice-like object.

4296909311_664632590a_z
“Ice!” flickr photo by Sergio Morchon shared under a Creative Commons (BY) license

I think this will be easier than the obstacle implemented last week because we will not have the problem with the level schema again. This means that, adding this new obstacle to levels will be straight forward and what is going to be left will be only the simulation of reduced friction when the player touches the ice.

End of Week 10: Bouncing problems

--Originally published at TC3045 – Quality and Software Testing

Andres Barro and I worked on the implementation of a new type of object, the one that makes the player to bounce. We have not finished yet because we found some bugs when the player bounces in midair when going in one direction, the bouncing effects looks really weird, so we need to fix that.

We had some problems adding this new type of obstacle, those objects did not want to appear on new levels; but after asking Miguel, our teammate that manages the database, we were able to solve the problem. We missed to add this new type of object inside the level schema.

Week 10: A new feature for game-play

--Originally published at TC3045 – Quality and Software Testing

This week, I am going to work on the obstacle that makes the player to bounce. It will be an indestructible object that it can either help or obstruct the player in his way to the goal.

To make the player bounce, maybe a will take the current velocity of the player and launch it to the opposite direction; I this does not work, I will do some testing to find out the right formula for the bouncing effect.

End of Week 9: new issues

--Originally published at TC3045 – Quality and Software Testing

This week, we planned what we are going to do for this sprint and assigned each of them to every member of our team. We decided to postpone the visual elements such a sprites and textures for later because none of us have experience with that; so we decided to add new features to further increase the user experience and gameplay.

Week 9: A simple start

--Originally published at TC3045 – Quality and Software Testing

Second partials start on this week, so we are going to start with small features or, at least, start with some of those that were planned last week.

However, before we start working, we first need to assign the issues to each member of the team.

39929189955_e58bc7190e_z
“Quick & slow” flickr photo by gerlos shared under a Creative Commons (BY) license

We actually choose which issue we wanted to do, but we did not write anything on paper, and that is the first thing we are going to do to prevent ambiguity on the assignment of the tasks.