Being prepared

-



As this is my second blog post on the topic of play testing, I will rather focus on preparing for playtesting, than the value of playtesting itself. If you want to read about that instead, check out this post. When working on a game it is very important to be prepared for things as Alpha and Beta presentations, but also for events like playtesting sessions.

This was unfortunately not the case when we had our first playtesting at university. Motivated, proud and confident about our product we went to show off our game and get opinions, but we were not really prepared for the playtesting session itself. We just thought bringing the game on a laptop would be enough, but we were proven wrong. As we only finished some of the assets, mechanics and game elements the day before, we did not really have the time to test the game ourselves. This seems a bit redundant, as the playtesting session is there for finding those issues, but there were some crucial problems that we did not fix before and that influenced how our game was perceived. Fixing up those obvious major issues would have allowed the playtesters to focus on certain design decisions, rather than big bugs in the game. Additionally, we just prepared a small survey right before the session on the same day, so it was not really thought out to well and just covered some basic questions.




The second time, we tried to do it better. We brought two laptops that the game can be played on, prepared headphones for the playtesters to have the proper gaming experience and our survey was well thought out, too. Unfortunately, there were still some bugs and issues in the code, but we got some valuable feedback from our testers.

All in all we realised how important it is to be well prepared when you want to show off a game, even if it is just for an audience of playtesters. You should have a playable version ready in advance. Even if it does not include all the recent features, a stable earlier version is way better than a broken recent one. Also take some time to write a proper survey that is tailored to your design decisions as well as the overall impression of the game. Bring some laptops for the testers to play and have fun with them enjoying your product!

Comments

Post a Comment

Popular posts from this blog

The importance of playtesting

-
Image
Testing game play in the Unity editor Recently I realized how important it is to play test your game. I always thought of play testing as a thing a developer has to do every once in a while, but did not take play testing and all of its facets too serious. However, a play testing session that we had at university on Monday proved me wrong. I didn't expect  a lot from the play testing. We prepared a few questions about our game, that we could ask the testers about. Some of the questions were about the play feeling of the game, others were about specific mechanics, music or the art style. Nevertheless, I was actually really confident with our game and did not really expect too much useful feedback, but more response on issues that we already know of. However, when the play testing started, we already faced our first issues. As we never build our Unity project as an actual .exe file, there were a few things we have not tested out. When our testers started playing in full scre
Read more

Programming a centered bee swarm

-
Image
Finished version of the centered bee swarm following the player The bee swarm in “Game of Beelonging” is one of the main parts of the game concept. Whilst playing the game, there is a bee swarm constantly chasing the player, helping you out when enemies come to close and assigning a new player on death of the main bee. The swarm is supposed to always be vertically centered in a compact swarm, even if one of the bees die, which makes programming the swarm quite difficult. As I was aware that setting up the bee swarm was the most difficult part of creating “Game of Beelonging” I started off with it right away. I began creating ten empty game objects called “slots” representing  all the positions, each of the non playable bees could go to and added a script to each of the slots containing a pointer to their current bee, a pointer to the next slot and a boolean that tells if the slot is occupied or if it is not. The idea was that each bee will constantly check
Read more

More Bees, Less Bugs

-
Image
Even though we are creating a game about bees, wasps and beetles, I only want bugs to appear on screen and not in my code. Unfortunately, fixing bugs is a major part of your work as a programmer and can get extremely frustrating when you can not seem to find out what is wrong. Especially after the last playtesting session there were a lot of things that needed to be fixed. For some reason, our main character or his companions occasionally decided to leave the screen, the pause menu did not work, dead things still managed to kill you, bees were hiding behind each other, random pieces of air killed you during the boss fight, the Game Over Screen popped up when you were not actually dead and the Win Screen refused to show up at all. Me seeing my stupid code not working As there was a huge amount of things to fix up, I tried to figure out the best way to debugging in Unity and figured out that there is a lot of approaches that might work depending on the situation. 1. The Conso
Read more