Tuesday, 27 October 2015

Post 19 - Trade Show and Course Reflection - Week 13

Trade Show:

Today was the trade show contact session and I can't believe we are almost finished this course. I was thoroughly amazed at the assignments that were displayed on the day. The two that I loved the most was the 'Cluedo' inspired app and the web app that utilised oranges as hardware buzzers.

Our game did attract some attention whereby onlookers would watch the player and laugh if they ended up at a dead end. It was great to see that our product inspires the audience to laugh and enjoy themselves.

The tutor said that our web app was working great and that he was impressed with our graphics which is nice to here.

Course Reflection:

As a whole I did enjoy this course, it improved my team work skills and communication. Refreshed me of HTML and CSS code and improved my Javascript skills. I also learnt a new program called GameMaker which also encouraged me to improve my general coding skills. Our team worked in such a way that each member was the 'specialist' in a specific area such as media generation, writing, coding and game development and this course improved my skills in regards to communicating with a team like this.

I did however think the course could be improved upon which I will also mention in the course surveys. Here is some ways in which I believe the course can be improved:

  • Clearly outline where the rubric is and specifically outline the marks for each section, I honestly had no idea where the rubric was and because there was a course website as well as Blackboard, this made it even more confusing as there was often conflicting information given. 
  • I didn't really like the workshops as none of my group members were in my session. A lot of my workshop members were in the same class as their team members so they were able to get things done together but I just felt that the workshop session was of no benefit to me unless I had a question for the tutor. I don't see the need for the workshop session to be compulsory because after the third or forth week there is nothing really taught that will help us with our project. 
Thats just my thoughts on my experiences with the DECO1800 course. I did enjoy it. 

Wednesday, 21 October 2015

Post 18 - Week 12

Following the user testing and prototyping feedback/observations, we have been working hard on completing Labyrinth for the submission next week. We have been finding it difficult in getting Trove to work and also finding it difficult to get the timer to stay in the correct spot.

Due to the way GameMaker implements its draw function it is very hard to specifically align gui text. This means we will have to work quite hard in order to get it to work before next week.

Stay tuned for more updates.

Wednesday, 7 October 2015

Post 17 - Week 11 - Experiences with Prototyping and User Testing

Today Theseus presented the Labyrinth prototype to our peers and we learnt a fair few things in regards to our current functionality. As with the paper prototyping session, users stated that they were a little confused when they started the game but because the controls are quite intuitive they were able to understand how to play. Unfortunately our prototype was extremely basic and didn't offer very much interactivity for the user which meant that we didn't achieve a lot of feedback on our product.

However I was thoroughly impressed with my peers prototypes. They did show a lot of potential and honestly it has made me nervous as I am starting to think our game will not be able to compare to the such good quality products of the other teams.

We definitely need to work very hard on improving our product in order to provide greater user satisfaction with our game. I'm looking forward to the coming weeks. 

Thursday, 1 October 2015

Post 16 - Week 10

Since the male sprites have been finished, I have worked hard at implementing them into the game. I have managed to also get a timer to work and have also added the grass background into the game which has helped the aesthetics.

It's taken me a long time in learning GameMaker code syntax/language but I'm starting to get a hold of it.


Here is a video of what I have managed to get working: 

Wednesday, 23 September 2015

Post 15 - Week 9 - Male spites are now finished

Thanks to Craig Johnson our Labyrinth male sprite character has now been implemented into the game, animated and all. I have also half finished the character selection menu prototype. However there is an issue with this where it would create another character appear in a different room. I am not sure how this has happened but after some more debugging it should be fixed and working.

We are still EXTREMELY concerned about how we will incorporate the trove API into our game. Because we are using a third-party software which isn't exactly catering to added javascript, css or html I am sure we will find it quite frustrating in trying to incorporate the trove API into the game.

After completing our progress report presentation we were told that we should include more HTML/web based elements on the game play page so it doesn't look so bare.

Wednesday, 16 September 2015

Post 14 - Week 8 - Revised Maze Concept

After a discussion with the design team, we all collectively decided that we need to can the fog of war concept and revisit our original plan which was to go with the grid/room style maze. We originally thought this style of maze would be too hard to implement but after some thinking we worked out it is actually much more simple to implement than the traditional maze concept.

In order to create the entire maze design we first started by drawing it out on a piece of paper. This enabled us to visualise what to create for our web program. Implementation isn't all that hard in regards to creating this as all that is needed is a collision detection object which changes the room if hit.



Friday, 11 September 2015

post 13 - Paper Prototyping Reflection

Last Tuesday we undertook a paper prototyping session whereby Craig Johnson and I took our peers through our Labyrinth concept in order to understand the limitations of our interface or designs.
We found that many of our peers were confused as to how to start the game, outlining that a how to wizard would be incredibly important to implement in the game. We also had to explain how we were using Trove in the game as it wasn't that obvious.

Ultimately the paper prototyping session was successful in enlightening us on the importance of a how to play function. I wish we were able to have a look at the other designs, that would've been fun. Oh well. Stay tuned for more updates.