#gamepie

[aamirdevloggdt]

Playtesting

Final Conclusions based on results of Playtest - Float Force

What am I trying to accomplish?

The goal is to playtest a prototype as well as get a prototype playtested and draw conclusions from that.

Why would I want to do that?

Both knowing how to give feedback after a playtest and getting feedback on your prototype after its playtested are useful skills.

How do I go about trying to accomplish it?

Watched this Brackey's tutorial on playtesting and basically played the prototype for Hitboy. Filled the form the other team had created, and we had a call with them to discuss our findings.

What is the result?

The final result was a document with the findings of the other team on our prototype and our conclusions on them.

[aamirdevloggdt]

Prototyping in Unity

Playable Prototype - Float Force

What am I trying to accomplish?

The Challenge is to implement the GDD in Unity and come up with a prototype that can be play-tested.

Why would I want to do that?

Having a prototype for play-testing is a great way to prove that your game idea works and figure out at an early stage what works and what doesn't.

How do I go about trying to accomplish it?

We divided our prototype into Level Design and Movement Mechanics and got working on it.

Research Methodologies

Prototyping (Workshop): Making of the prototype in Unity

What is the result?

The final result of this exercise was a playable prototype of an FPS game with Six Degree of Freedom movement system.

How is/will this be helpful?

It was definitely helpful diving into the coding side of things. There's a still a lot to learn, but this was a good start.

What are my next steps?

Get the game play-tested.

[aamirdevloggdt]

Design Challenge & SCRUM

Final Ten Page Design Document - Float Force

What am I trying to accomplish?

Come up with a Design Challenge for Float Force that clearly states the intended desired outcome for the game, and set up SCRUM.

Why would I want to do that?

By coming up with a clear Design Challenge, you are able to come back to it if ever you're unclear about the direction your game should take.

How do I go about trying to accomplish it?

We iterated through various versions of Design Challenges we could come up with by improving on them through the feedback received.

What is the result?

Design Challenge:

Design a fast-paced, space arena FPS game inspired by the Battle Room in the movie Ender's Game and the movement mechanic of Overload and Hardspace: Shipbreaker, where you shoot enemies with laser guns in six-degrees-of-freedom (6DoF) as you attempt to save humanity by utilising your reaction and spatial awareness skills.

Trello Board

User Stories

How did I validate these results?

By getting feedback on each iteration.

[aamirdevloggdt]

Game Concept Design - 2

Final Ten Page Game Design Document - Hitboy

What am I trying to accomplish?

Expand one the One page Game Design Document provided to us.

Why would I want to do that?

To be able to flesh out an idea that is not originally mine by using what I learn from prototyping and other research.

How do I go about trying to accomplish it?

We mainly utilised the interviews we did with the original team and our prototypes to come up with the design document.

Research Methodology:

Prototyping (Workshop): Used the prototypes we made earlier.

Interview (Field): The interview we had with the swap team.

What is the result?

We came up with a Ten Page Design Document.

How did I validate these results?

We shared it with teachers for feedback.

How is/will this be helpful?

Game Design Documents are a staple of the Game Dev Industry, so knowing them is important and I'm certain will be useful when I work on other games.

What are my next steps?

Our group will be presenting this to the original team.

Presentation for 10 Page Game Design Document

[aamirdevloggdt]

Game Analysis

Final Deliverable - Adding an Enemy to DEEP

What am I trying to accomplish?

The Goal of the exercise is to learn to seperate myself from player experience and be able to look at games through the perspective of the designer.

Why would I want to do that?

To be able to build my game design vocabulary, identify existing game elements (mechanics, dynamic, aesthetics) and analyse the reasoning behind the use of these elements. As well as figuring out how changing these elements would affect the player experience.

How do I go about trying to accomplish it?

The assignment provided a structured way of going about this. The task of adding an enemy that fits in with the aesthetics of DEEP but make it more challenging was a decent exercise in Game Analysis.

We analysed enemies in other games like the Cacodemon (DOOM), Evil Eyes (Heroes of Might & Magic), Barnacle (Half Life) etc. Among the things we looked at were what the enemies added to their respective games, how would the game change if they weren't there and how would adding an enemy like that into DEEP make it more challenging.

We also looked at the already existing enemies and features that unified them. It was our consensus that having an enemy as mutated and/or from the sea would make it fit nicely into the aesthetics of DEEP.

Research Methodology:

Available Product Analysis (Library): Looking at enemies in other games.

Problem Analysis (Field): Asking the teachers questions to clarify the task at hand.

Stakeholder Analysis (Field): By considering the experience of players and making sure our solution does not take the immersiveness out of the game.

What is the result?

The enemy we came up with was a mutated version of the Pufferfish. It was our opinion that DEEP lacked enemies that utilised the vertical space and by introducing an enemy that attacked from above would increase the difficulty of the game by forcing the player to pay attention to what was going on above him as well.

Kaloyan designed an enemy based on our feedback and it was presented to the teachers.

How did I validate these results?

Our Group presented our ideas to the teachers in an attempt to validate our solution.

The feedback we got was that we should provide more concrete examples of other similar games that have used a solution similar to ours. This would validate our findings.

Futhermore, our description of the enemy we were suggesting needs to provide details in a way that can be coded e.g. Damage, Movement, Weight of attack and other similar stats. We amended our solution to include those and can be found in the deliverable document at the begining of the post.

How is/will this be helpful?

This exercise was helpful in understanding how helpful a skill it is to be able to analys games from this perspective and I expect it to prove invaluable in the future.

What are my next steps?

Will be pracicing this while playing games.

[aamirdevloggdt]

Final Deliverable - Identifying Game Elements(MDA) in DEEP

Mechanics, Dynamics & Aesthetics (MDA)

What exactly is the MDA framework?

The MDA framework was presented in a paper by Robin Hunicke, Marc LeBlanc and Robert Zubek.

Why would I want to learn about it?

I think understanding these three components and being able to identify them in other games is an invaluable asset. It helps in figuring out what makes a game fun and brings me one step closer to coming up with ideas for making fun games by mixing and matching the many mechanics and dynamics I identify ( I still can't get the idea of mixing the mechanics for Golfing and Tetris out of my head.)

How did I try to learn about MDA?

We were provided links to the paper and blogposts on MDA but I sorta ignored them in the beginning. Got most of my information from the workshop and jumped into practically trying to identify these 3 components in one of the 5 games they told us to pick from.

The game our group chose was Deep and I was horrible at it. I spent way too long trying to reach the end, but that didn't happen. I of course knew that I did not have to finish it, I just couldn't help myself. I guess that tells you a bit about the aesthetics of the game. Or my psyche.  

Research Methodology

I find it a bit difficult to categorize my research methods in a 'technical' way, but here they are:

Literature Study (Library): Went through the MDA paper.

Community Research (Library): Read the blogpost - Mechanics and Dynamics by Ian Schreiber

YouTube Video: Aesthetics of Play - Redefining Genres in Gaming - Extra Credits

Played the games to identify their Mechanics, Dynamics and Aesthetics.

What were the findings? (End Product)

I learnt what MDA were, how to identify them and how useful they can be. Our final product was a document listing out the MDA for Deep.

Link to MDA Findings for Deep

How did I validate these findings?

Mostly by comparing them with the feedback given by instructors to us and other similar findings.

How is/will this be helpful?‌

It will be helpful when coming up with ideas for games. Having starting blocks like a few mechanics and aesthetic you want in a game can be a huge help in kicking the idea generating sessions off.

What are my next steps?‌

I'm never playing games again, I'll be researching the MDAs in games from now on. Sounds way more productive and definitely a better excuse.

Jokes aside, I'm going to try and identify as many MDAs I come across in games I play and jot down ones I think I might enjoy using to come up with game ideas.

[aamirdevloggdt]

Introduction

What is this DevLog?

This is a carefully curated digital representation of the journey I embarked on to learn game development in 2021.....who am I kidding? I gotta do this or I'll fail. We all know how much developers love making documentation.

PROJECTS

[leecammdev]

[Gamepie] #7 Playtesting

GOAL:

How can we figure out which parts need to be improved in our game?

METHODS USED:

Send a peer group a feedback form and let them play our game.

We need to use these methods in order to detect problems that users have and after that, we can fix them before publishing the final version.

PRODUCT:

After sending a peer group a feedback form and let them fill in it, we scheduled a meeting with them in Teams to discuss the problems in our game.

Conclusion:

"As an overall conclusion, the team we swapped with really liked the game we made in these 4 weeks. There were some parts which they thought were difficult at the first try, such as trying to find the correct path (where to go next, what to do next). They said that there were really good parts in the game, like the keys and doors and the final boss fight, however it was pretty difficult for them to beat. They also would like to see some color variation. The amount of health pickups were good, but the ammo boxes around the map as loot and pickups were not the best, because the guns use ammo, and it's pretty hard to fight the bosses without ammo (with the sword). When they die they have to restart the whole level, especially if you are far in the game this is very annoying. They would like to see checkpoints that you can fall back on when they die. Most of them liked the idea of the sword, but some of them had some weird feelings while using it. Some of the pickups, such as the gun loot from one of the enemies were not clear - they didn’t notice that they picked up a gun, however we showed it as a notification on the left side of the screen. They liked the length of the level design, but there were some parts which made them think why are they there."

RESOURCES:

Link to our game:

FPS Micro by Zieheavy (itch.io)

Feedback form link:

Feedback form: ESCAPE - Google Forms