Skip to content

Village user test

Versprechen080 edited this page Oct 5, 2022 · 2 revisions

Background and Goals

In sprint 3, we were mainly aimed to designing the scenarios of village on the basis of storyline designed before and the gameplay mode.During the design, we also have some middle versions to meet the users' satisfactions.The purpose of this user test was to deplore a more appropriate scene for the village, making the whole game more consistentand improve the design for users' experience and acceptance being taken into account.

Aim

  • to ensure whether the present version of design can be accpeted by users and attain some advice from them for further polishment

Methodology

The user test is designed for collecting effective feedbacks and suggestions to make a balance between user experience and degree of design adaptation with other scenarios.Thus, we use several methods to achieve this goal.

  • Hypothesis:to confirm there is a sufficient number of potential players who are willing to help us finish the test, since it's important to meet their expectations.

  • Design:to evaluate the continuity of the consistency in the game's graphic design when players are moving from one scene to another scene, avoiding too much contrast.Then we make some imporvement by virtue of the feedbacks collected.

  • Evaluation: based on the feedbacks received to change some details and make the design look more comfortable.

Test plan

Our team have had a discussion about the test target and finally determined to conduct internal tests to test the acceptance of users and whether the village design fit with the rest scenarios of the game.

Questionnaire

The general feeling about the village design

Details in design (from aspects like color,scene layout, design style, etc.)

The continuity of the whole game design

Degree of satisfaction with the quality of the picture

Other advice(like adding some components or anything else)

Feedback Collection

Collect feedbacks from the questionnaire above

Results analysis

Analyze the result of questionnaire filled by users and make conclusions

Participation

Test among internal studio students and other random passerby at school

Result and Analysis

Result of the questionnaire

image

Analysis

From the comments and scores we received from questionnaire, it is easy to see that users are basically satisfied with our overall design evalution. However, we still have several aspects to modify.For example, the layout of the whole village, continuity of the whole game design and the quality of the picture, all of which need to be improved. We will discuss about the next step to improve user experience mechanics and game experience.

In addition, we actually had considered whether to design the specific scene of the opera and come to an conclusion that only the exterior is enough because opera just appeared once in the storyline and we would elaborate the design of village cuz players need to stir about it than to spend much time designing the interior details of the opera.

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