{"id":1418,"date":"2026-02-24T13:08:25","date_gmt":"2026-02-24T13:08:25","guid":{"rendered":"https:\/\/sites.wsagames.com\/stw1g24\/?p=1418"},"modified":"2026-05-14T10:17:17","modified_gmt":"2026-05-14T10:17:17","slug":"week-5-log","status":"publish","type":"post","link":"https:\/\/sites.wsagames.com\/stw1g24\/2026\/02\/24\/week-5-log\/","title":{"rendered":"Week 5 Log"},"content":{"rendered":"\n

On Monday before the lesson I photocopied the pieces of the character and emailed them to myself, I then showed the art to my team. They liked the work I had done. <\/p>\n\n\n\n

For the session we had a short lecture on game puzzle tips and tricks and then we spent the rest of the time planning for the playtest. We were encouraged to assign roles for our group when showing our game. Our mechanics designer offered to induct people into the game and give them a brief rundown of it. For the rest of the day the rest of us will take it in shifts<\/strong> to take notes<\/strong> and observe <\/strong>players while the rest of us go and test other peoples games.<\/p>\n\n\n\n

For the rest of the day I worked on animating the character<\/a>.<\/strong><\/p>\n\n\n\n

For our Tuesday meeting I focused on catching up on my organisation and updated the team website. <\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n

This is our to-do list I have been using it to keep track of what I need to do, colour coding my post it notes with a green dot. <\/p>\n\n\n\n

I added some new tasks, design deer and peacock and moved the animation tasks to completed. <\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n

I also worked on the group website ensuring that the navigation menu is up to date and has all of the posts we have made so far.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The last thing I did was update our roadmap to better reflect our progress and I added things we had not previously thought of like sound.<\/p>\n\n\n\n

Thursday Playtesting Session<\/strong><\/p>\n\n\n\n

On Thursday we had our first of two mandatory playtesting sessions. We structured our group so that our Mechanics Designer onboarded players and me and the Technical Designer took turns writing notes and observations on the players. <\/p>\n\n\n\n

This was an extremely helpful session as I wanted to see how my animations translated and were viewed by the players. It was also nice to see where the rest of our peers have gotten to with their games. <\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

The notes from feedback. After the session I took the notes and compiled them into a word document. Using the highlighter tool I sectioned each piece of feedback into groups of similar issues. I then created a list of what we need to improve and suggestions of how we could. On our Friday meeting we will go over this list and decide what tasks we will tackle. <\/p>\n\n\n\n

This the word document. The key is as follows:<\/p>\n\n\n\n