Ding! Level 75.

Unfortunately I was not able to hit level 80 as planned due to other work. After finishing my Rail Nation Review (it should be posted on OnRPG soon, I will make a post about it when it goes live) and my school work, I logged on to at least hit level 75.


I still get blown away by the graphics in this game. They are definitely not as detailed as newer games but this game always reminds me that art style is always better than having realistic graphics.



I revisited the same dungeons again after failing to hand in the quests on Saturday. I love the dungeon designs.

After hitting level 75, I decided to skip over the quests in Borean Tundra and Dragonblight and move on to Grizzy Hills to speed up leveling. It seems like this zone doesn’t have as much snow as others in Northrend.

I hope to gain some levels over the week but due to school I do not expect big jumps in progress until the weekend.

Share on FacebookShare on RedditTweet about this on TwitterShare on Google+Email this to someone

Moving onto The Lich King

I progressed further in the Wrath of the Lich King expansion by completing some quests and dungeons. A lot of the stories were related to the Lich King, can’t wait to be able to fight him! Although, I think I will wait until 90 before moving onto raids and stick with dungeons for now.



Seems like I was able to find Lich and Pudge! Great to see the Warcraft roots when also playing Dota 2.

This was an interesting boss battle. The entire group was turned into skeletons and all our abilities were changed. It was good to be able to use some new abilities once in a while.

After finishing this dungeon quest, it turns out this guy betrayed us. He used what we gave him to aid The Lich King! My party member danced around him during the cut scene taunting him, “I defeated you on my Warlock main!”

I concluded the day with this quest where another minion of the Lich King had to be defeated.

So far I am really enjoying The Wrath of the Lich King content. The areas look beautiful and the quests and dungeons are very enjoyable. My aim is to hit level 80 before heading back to school, at this point it does not seem possible due to having other work to complete but we’ll see…

I am also working on a review for a game called Rail-Nation. It is currently in beta and it lets players run their own train company. Look out for my first impressions article to be posted on OnRPG in the near future.

Share on FacebookShare on RedditTweet about this on TwitterShare on Google+Email this to someone

WoW Update: New Dungeon and onto Northrend

Since I already post my screenshots to the SS thread on OnRPG, I might as well mirror it here. The blog posts will contain more details about what is going on while the thread simply has a one liner.




We tried out a new dungeon today. Dungeons do give EXP a lot faster than quests at this point. However, we were all new to this dungeon so it went slowly. In the end we did finish, with one wipe when our healer got stuck, and a good chunk of EXP was gained. The dungeon looked gorgeous.

Hoping to hit level 90 soon and get through a lot of the content before the next expansion hits. It is going slower than I want due to school but since it is enjoyable, there are no complaints.

Now I move onto the Wrath of the Lich King continent, Northrend. Looking forward to this continent and its content.

Share on FacebookShare on RedditTweet about this on TwitterShare on Google+Email this to someone

Transformers Universe First Impressions: Too Slow and Easy

Transformers Universe seemed like a game I’d enjoy. I love playing shooters and like the Transformers. However, the game was made much too simple and slow to enjoy. You kill very slowly and it is very easy to run away and heal. The game forces you to play defensively and slowly. I’d stay away from this game.

Click the image above for my full review.

Share on FacebookShare on RedditTweet about this on TwitterShare on Google+Email this to someone

Why do I bother with all this planning?

As a computer science student or even as a professional programmer, you can get annoyed with requirements to plan for even the simplest of things. We could be working on a simple problem where teachers can store grades for students but the requirement for the assignment would make us create UML diagrams, CRC cards, and so on. You just think, “This is pointless. It’s much simpler to just begin programming, there is no need to do all this planning and documenting.”

After taking a software design course, I’ve come to appreciate the documentation of code a lot more. I’ve always been a programmer that follows good style with good comments but I would never plan my projects. I would begin coding and add on features and make changes as necessary. This was working great for me but this could not continue when the project was done with a group.

Our term project was a simple Android application where nurses and physicians can add patients and store their vital sign and other medical information. It was by no means anything complicated and could have easily been done without creating any documentation. Being a software design course, you were forced to work in a group of four.

The project consisted of many phases such as planning, programming, and updating requirements due to client changes. With this project I could easily see the benefits of UML diagrams. Since we were working with a group, we decided to create UML diagrams to clearly see what each class and its methods should do. By simply taking a look at the UML diagrams you could see what other methods would return in the exact form with its type. There was no need to wait around for other group members to finish their part so you can take a look at their code and build your portion that uses their code. Look at the diagram, know what it will return, and get coding.

This group project really helped to teach me the benefits of planning and documentation. You could say that the benefits are only helpful when you’re working with a team. I do agree that it is much more useful to create diagrams when working with a team but it is still very useful when working alone.

For example, at one point in the project, the requirements changed to simulate clients changing their minds. Because we had all the UML diagrams and tasks split up efficiently due to planning, the change was as simple as extending a class. If these plans had not been made a lot more code would have to be changed.

Even if you find the creation of diagrams, planning and other documentation troublesome or pointless, keep at it as it will be beneficial. If these techniques were truly pointless, why would professionals keep using and teaching them?

Share on FacebookShare on RedditTweet about this on TwitterShare on Google+Email this to someone