Mandatory Playtesting Session
Mandatory Playtesting Session with peers, stafff and other years Students bring a playable build of their games to the session We all go through bug logging in Excel/ google sheets
Contact Time
- Monday (24/2/25) – Improving the first minute of gameplay talk with Jupiter Hadley
- Thursday (27/2/25) – Testing workshop
Description
Thursday’s session: Each team will bring in a build of their games. Students will take it in turn running the tests of their game and testing other students’ games. They will fill out bug reports and update their project management timelines to be able to implement feedback. The class will then discuss the experience together and plan how they will improve before the next playtesting session.
Outcomes
- Students will have tested each other’s prototypes
- Students will have a thorough report of the bugs and feedback for their prototype
- Students will have a list of fixes/ improvements to work on going forward
Reflection :
After this play test, I got questioned some of the players about how they felt about the artwork most saying it looked great and some saying it fit in the setting. I’m happy knowing this.
๐ด – Not implemented
๐ – Working on
๐ข – complete
Current vertical slice idea :
First Realm (Depression) Containing:
- Hub World
- Smaller prologue (3 rooms)๐ข
- 5 different enemies
- The first realm (7 rooms) ๐ข
- Boss fight
( Week 4 : old )
- Finishing Protagonist art /animation ๐ข
- Finishing Enemy animation ๐
Week 5 :
- Finishing Enemy animation (whisper) ๐

After the playtest :

Leave a Reply