Skip to content

NPC interaction testing results sprint3

Kai9613 edited this page Oct 4, 2022 · 1 revision

Purpose

The primary purpose of this user test was to survey and assess user perceptions and feelings about the current implementation of NPC interactions. This user test was very important for our project because our team's final design might have some flaws. Therefore, the test results will be used to improve the system.

Process

Due to the current COVID-19 situation, user testing will be done by an online zoom meeting. Testers will experience the system through the remote control of zoom functionality.

image

This is the window screen that the user will see talking to the NPC during the test. 1、The tester will look carefully and use the dialog box to gather clues. 2、Write down some important observations. 3、After experiencing the overall interaction, we asked the testers some key open-ended questions about the dialog box.

Key Questions Asked

  1. Do you think this dialog box can make you understand the relevant plot content clearly?
  2. Do you skip points on content and finish it quickly?
  3. Do you have any suggestions for improvement?

Results

Q1. Do you think this dialog box can make you understand the relevant plot content clearly?

Overall, the user can understand the overall story development through the specific text content and mouse click, but because it is not combined with the scene, the user does not understand why to do so

Q2. Do you skip points on content and finish it quickly?

In addition, because we have a large amount of text content, users will habitually ignore and close, so they will ignore important information, but we do not have an entrance for users to see the previous information.

Q3. Do you have any suggestions for improvement?

First of all, users feel that they can't get back to the previous content because of a quick click, which is a hindrance to completing the game. In addition, the user cannot restart the dialog after closing the dialog box, which is also unacceptable to them. Third, there is no guidance on what to do if they make a wrong choice, so they need to communicate with the team responsible for the game design.

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally