top of page

void

Void Trailer

Major Milestones/Accomplishments

  • Pitched and cement the clue system in the core loop, which opens dialogue options for more clues to help solve the mystery​​​

  • Participate in QA sessions and take notes to create iteration plans

  • Get the game published on Alienware's website

Box Summary

Void is a procedurally generated murder mystery in space. As the captain, it's your job to figure out who onboard your ship murdered one of your fellow members. Talk to teammates, gain their trust, and find clues to uncover the truth. Each time you play, a new outcome will come about. Will you save your ship, or will the killer go free?

Project Details

Genre: Mystery / Strategy​

​

Roles: Game Designer, QA Tester

Download the game below for PC or Android

Screenshots

Work Summary

Game Designer:​              

I was a game designer for this project. VOID forced me out of my comfort zone as at the time, I was not familiar with many Whodunnit-style games and hadn't made a game for mobile. I managed documents as well as designed systems for gameplay and the core loop.

What Worked:​

  • Assisted team to design the game loop, lore building, and player interactions

  • Managed documents and helped polish the testimony system

What Could Be Improved:

  • Interactable items on the ship needed more visual clarity or attention called to them

  • The final meeting had the potential to offer more testimony options as well as last-minute clue revelations

2018 Interview

Documentation Excerpts

Testimony System In Game

void game design.gif

QA Tester:​              

I was a QA tester for this project. The RNG nature of the game combined with the mobile platform was interesting but caused many bugs and faults within the game. I and several others participated in bug logging and test sessions to help the team prioritize issues based on the severity

What Worked:​

  • Participated in QA sessions to test and bug log the game 

  • Created surveys and recorded feedback from anonymous testers

  • Created several iterations plans for the team to prioritize fixing based on the amount of feedback and severity of bugs 

What Could Be Improved:

  • Test sessions should have been comprised of more people from the target demographic

  • Better document bugs with videos in addition to pictures

Testing and Iteration Workflow

bottom of page