--Originally published at TC3045 – "Site Title"

For this week, I was expected to create a new method to introduce a nickname for the player. The task was completed. For this feature, I had to learn to change between what the program calls scenes. A scene is like a different program to have multiple display logic programs separately.

The biggest challenge was to be able to communicate between scenes. Since the logic between them is isolated, I needed to find a better way to get a message across. Currently I fixed it with a global variable but I’ll hopefully change it later.

--Originally published at TC3045 – "Site Title"

A new sprint means we should start with a new set of issues for everyone. All work scheduled for the last milestone is now done.

For the week we will:

• Level creation aid
• Animations
• Projectiles
• Better username handling

--Originally published at TC3045 – "Site Title"

This week is the end of the first partial and with it came the second progress presentation in class. The presentation itself went smoothly. Everything worked as expected and no known bugs were present on the build that was showed.

The progress for the week was all that was expected, except for some errors present on this week’s plans. The previous blog entry lists a projectile and it’s interactions as work for this week, but it was really scheduled for next milestone. All other work expected for the week was successfully completed.

As of right now, I think the project is progressing constantly and has a bright future ahead. So far we haven’t found major roadblocks, so the biggest concern would be what to do in case we find one.

--Originally published at TC3045 – "Site Title"

The second presentation will be this week, we are mostly ready but there are a few more things to be added this week. We will work:

• Leaderboards.
• Projectile.
• Destroy enemies on hit.
• Store scores.

--Originally published at TC3045 – "Site Title"

This week was exams week, which means not much work got done. Personally, I wasn’t expecting to be as busy, so productivity was lower than I would have liked. Still, some progress was made.

Most of this week’s work was done on the back-end side of things. Some of the ways to communicate with the database were changed. Most front-end code wasn’t modified. Some levels were also added to improve the experience.

--Originally published at TC3045 – "Site Title"

For next week, we will look to solve the current issues on github, and decide on what to add next. The current issues are: store user score, add a GUI, and create more levels. Some are halfway done, like the score storing.

Since we are almost done with the current issues, we will also look into what comes next. This may not be a big change, since it’s the same milestone. For example, I started working on a big change on the physics part of the game, so I plan to finish it this week.

--Originally published at TC3045 – "Site Title"

The semester started relatively light on the homework side. For this reason, I had been able to do all that I had planned to do and more, on time. Partial exams start next week, so other project and studying are gaining importance. I was still able to finish all of what was required for the week, but not as early as expected. I was still cleaning up a bit of the code just before writing this blog.

Other than time, this week still contained all that was expected. The server communication has been slightly tweaked to reduce the amount of times it needs to be contacted. We fixed known physics bugs, but are yet to merge it, since more testing is missing.

Since a very basic architecture for the project is done, we have been able to create a new introductory level. This is a kind of milestone for the project, since is one of the first tasks devoted almost fully to design and the user experience. To me, this means progress on other areas so far has been enough, since getting things working is no longer the main driver for the project.

--Originally published at TC3045 – "Site Title"

The date for the first progress presentation finally arrived. As far as goals go, I think we did well to fulfill most of them. The project was working and no major bugs were found on the code that was shown. We even got to create a few tests to check that the server is working correctly.

During this week, the server became a much more relevant part of the project. While past weeks focused mostly on the front-end part of the work, during week 2 we moved the storage of levels to  the server. This step allows us to have more available levels which also helps testing since we can use various levels to test for different behaviors.

Testing also got an initial implementation this week, we made a few server tests, but the framework is now in place to make it easier to test in the future.

Overall, the progress for the first milestone is what we expected and there weren’t any problems that took a large chunk of time.

--Originally published at TC3045 – "Site Title"

After a successful first week, we will continue to add some basic functionality to the game. So far we only wish to add components that we are sure to need in the future.

Testing will also move on to the first stages. We expect to have a few functional tests that allow us to check some key functions.

Progress by other members:

• Montoya: set up a testing framework.
• Arturo: save map to json.
• Barro: improve score and timer.
• Gera: moving obstacles/enemies.

--Originally published at TC3045 – "Site Title"

The progress for the week exceeded expectations. This is mainly due to the step for choosing a framework being done nearly in one day. We expected to spend a few days testing multiple ones, but we quickly decided to use P5play thanks to it being very easy to use. After this decision we created a GitHub repository in the following link: https://github.com/fornesarturo/its-not-raining.

My task during this week consisted mainly on creating a way to end a level and a timer to show the time the user takes. Ending the level ended up being a bit more complex than expected, since I had to ensure logic on other parts of the program stopped. As for the timer, it was mostly dealing with time and dates, which I find to be very stressing from the programming point of view.

Progress by other members:

• Montoya: set up a testing framework.
• Arturo: save map to json.
• Barro: score as timer.
• Gera: moving obstacles/enemies.