Skip to content

E-Jay Tripoli

A documentation of my work for Year 2 – Studying Games Design and Art at the University of Southampton

Menu
  • Lament
    • Development
      • Procedural Room Generation
        • PRG – Pt 1
        • PRG – Pt 2
        • PRG – Pt 3
        • PRG – Pt 4
        • PRG – Pt 5
      • Dungeon
        • Stalagmites
        • Pitfalls
        • Health Potion
        • Dungeon Bug Fixing
      • Player
        • Player – Pt 1
        • Player – Pt 2
        • Player – Pt 3
        • Player – Pt 4
        • Player – Pt 5
      • UI/HUD
        • Start Menu – Pt 1
        • General UI
        • Skill Tree – Pt 1
        • Skill Tree – Pt 2
        • Skill Tree – Pt 3
        • Skill Tree – Pt 4
        • Skill Tree – Pt 5
        • Skill Tree – Pt 6
      • Enemies
        • Whispers – Pt 1
        • Whispers – Pt 2
        • Wrought – Pt 1
        • Wrought – Pt 2
        • Boss
      • Scenes
        • Tutorial
        • Hub
        • Depression Gate
        • Gateway Scenes
    • Logs
      • Initial Plan
      • Teamwork
        • GitHub
        • Discord
      • Weekly Logs
        • User Analysis
        • Accessibility
        • Testing
        • Marketing
        • Formative Feedback
      • Playtests
        • Playtest 1
        • Playtest 2
        • Playtest 3
      • Showcase Event
      • Post-Project Reflection
    • Research
      • Understanding Learning Outcomes
      • Understanding my role
      • Researching Tools
      • Researching Pipelines
      • GDD Breakdown
      • Researching Procedural Generation
      • Existing Games
  • Arcadia GDD
    • Weekly Logs
      • Week 1 – What is a GDD?
      • Week 2 – Game Worlds
      • Week 3 – Concept Art
      • Week 4 – Character Design
      • Week 5 – Narratives
      • Week 6 – Gameplay and Game Systems
      • Week 7 – Feedback week
      • Week 8 – Audio
    • Research
      • Analysing Existing Games
      • Genre Research
      • Research into Psychological Abuse
      • Character Research/Moodboards
      • Environment/Map Research
      • Researching Medieval Knights
      • Researching Enemies
      • UI Research
    • Ideation & Development
      • Initial Development
        • The Essential Experience
        • Initial Game Ideas
        • Choosing a Game Genre
        • Choosing the Game’s Title
      • Game Play
        • Gameplay Loops
        • Mechanics/Tech
      • Story/Narrative
        • Twine
        • Summary of Narrative and Story
      • Game Art
    • GDD
      • Game Overview
      • Game’s Vision
        • Game Pillars
        • Project Focuses
      • Gameplay
        • Mechanics
        • Skills
        • Enemy Behaviour
      • Story & Narrative
        • Twine Prototype
        • Story
        • Narrative
      • Character & NPC Profiles
      • Map/ Level Design
      • UI & HUD
        • Creating the logo
      • Prototype/ Proof of Concept
      • Sound
      • Target Audience
      • Controls & Platform Specs
Menu

Playtest 2

Posted on May 13, 2025May 13, 2025 by et4g23

After developing our game further, we had a second playtest on the 27th of March, in which we recorded all of the feedback we got verbally from our playtesters and sent them surveys that they could answer regarding our game.

With all of the feedback we garnered, we created a google doc in order to track all of the feedback and cross them off as we went:

We also decided to add these tasks to Trello, maintaining our Priority categorization and labelling each task with what team member was assigned to the task:

Some tasks were never accomplished as we decided that they were too low priority with too little impact, or we had found another way around them. For example, implementing i-Frames to the pitfall was never completed because we changed the pitfall fundamentally and it was no longer able to deal damage.

Of the tasks we had assigned ourselves after the playtest, these were the ones I completed:

Player

  • Bug where player was unable to move ~ Bug Fixing – Pt 2
  • Player turns invisible when walking into Pitfall
    • This was a bug in the tutorial where the playerRespawn transform was located outside of the bounds of the room
  • Player collider is too big ~ Quality of Life Changes
  • Hitbox should be lower body ~ Quality of Life Changes
  • Pitfall dash problem ~ Pitfall Interaction – Pt 2

Enemies

  • Enemies pick up health potion bug ~ Bug Fixing – Pt 2
  • Items should spawn in after death animation
    • This bug was due to the Terra Shard instantiating too quickly, I simply created a coroutine to wait before it was instantiated

Tutorial

  • Whisper doesn’t die no matter what its HP is ~ Bug Fixing
  • Whisper is able to shoot at the player through walls ~ Bug Fixing

Obstacles

  • Rearrange pitfalls
    • This was due to the playerRespawn transform being in awkward locations in some of the room prefabs
  • Spike hitbox needs to be fixed
    • Players felt the hitbox was too big, so I reduced them in the stalagmite prefab

UI/UX

  • Main menu freezes
    • This bug was due to the Time.timeScale not being set back to 0 when the player would press the main menu button in the pause menu or the game over menu

Hub/Dungeon

  • Invisible walls in the depression gate scene ~ Playtest Changes
  • Closed room is offset
    • This was simply a matter of changing the transform values of the closedRoom prefab
  • Players and enemies were able to walk through walls ~ BIG PATCH
  • Rooms would overlap slightly ~ BIG PATCH

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

©2025 E-Jay Tripoli | Built using WordPress and Responsive Blogily theme by Superb