WK8_Design Process

In previous few week, we have modified our project idea several times according to feedbacks from testers and now we are really working on making it.

As for our project – a web game, we have separated our works into 3 parts to implement our game.

The clues design part, the technical part and the user interface part.

Clues design

Clues design is the hardest part of the design stage, which is the key factor to impact the difficulty and interestingness of the game. For designing clues, we don’t only need to consider the clue itself, but we also have to check whether it can be found from Trove website and how we should get it from Trove. So far, we have designed a draft version of clues, which are all selected elaborately for our game story and all clues material are retrieved by Trove API. The major form of clues are images with captions, which include the actual pictures, screenshots of books, digital newspapers and so on.

Technical part

The database has been divided into 4 tables -- user, chapter, user-chapter, and question. The user class inherits all the attributes from auth.user table and expands three attributes (avatar, current play status, and history play status).

Database Scheme

User Interface

•  Character design

We have two characters, the detective, and the thief. For each character, we designed an image to represent the specific emotion of him. Creating the variety of character images can increase the engagement and invite students to enjoy the story.

Character design

• Main page

Main page 1

Main page 2

• Gameplay interfaces

Gameplay interfaces