Week #2

Week #2 #

Detailed Requirements Elaboration #

Functional requirements #

  • Core Gameplay
    • the game should include puzzles that will help the player to advance through levels
    • core mechanics should be based on manipulating with the light bulbs
    • central concept: insert the light bulbs into the npcs to interact with them
    • the game should include basic tutorial elements in the beginning
    • the game location should be set in a tower, with respective level design
    • 15-20 minutes of gameplay with several levels should be implemented
  • Storyline
    • the story should be presented through the dialogues with npcs and text plates
    • the game should include characters with distint personalities and background
    • the plot should be concluded and have a logical end
    • two choices should be provided at the end to lead to two different endings
    • the story should be complex enough and carry valuable thoughts
    • the story should explain the setting and location logically
  • Visual design
    • the art style should use a mix of traditional and digital art and resemble paper
    • the game should include original character and location designs
    • the environmental design should support the storytelling
    • the style should be based on two color pallete
  • Sound design
    • the game should include several original soundtracks
    • the sound effects should be added for the atmosphere

Non-functional requirements #

  • the game should be intuitive enough and don’t get players stuck indeffinitely
  • the game should be appropriate for all ages both gameplay and story-wise
  • the interface should be easy to get used to
  • the game should run smootly on the supported platform
  • no critical bugs should be present
  • the text should be visible and easily readable
  • the environmental objects should be distinct enough (important since only two main colors are used)

Target users #

Even though our dedicated target audience is casual players without some prerequisite field-specific skills or background, we also aim to make our game satisfiable for more picky indie game lovers. Thus, we will follow two main routes:

  • the game should be enjoyable for gamers of any age, the included puzzles should require some critical thinking but be solvable in an adequate time nevertheless, the story should bring both kids and adults thoughts and ideas for light contemplation. We consider our users’ primary needs to be spending their pastime with a considerable amount of intellectual stimulation and aesthetic pleasure;

  • the needs of our more sophisticated players include inventive mechanics and original storyline. Level design should be thoroughly thought through and aid to the gaming process, mechanics should be diverse enough to be fascinating for experienced users, and the storyline must include logical (and probably not open) end, possibly with several endings. The conflict in the game should also be complex enough to keep the players invested.

Elaborated user stories #

(stories from report 1)

  • As a casual player, I want to solve puzzles on my own and in adequate time, so I can enjoy the game and move forward.
  • As a busy person, I want to play for a short time session, so my mind is relaxed after a long day.
  • As a reader, I want to see the interesting plot and ideas, so I have something to think about.
  • As an experienced player, I want see new problems and design choices, so my game process is not repetative and boring.
  • As a visual content consumer, I want to see a beautiful art style, so I am aesthetically satisfied.

(elaborated)

  • As a player, I want my gaming process to be bugless and smooth, so I don’t get unnerved and disappointed.
  • As a kid, I want to see bright and memorisible characters, so I learn to empathise.
  • As an adult, I want to see the story with complex characters, so I can relate to them.
  • As a indie game enjoer, I want the game to be authentic, so I feel a disctinctive atmosphere when I play.
  • As a parent, I want the game to have interesting puzzles, so my kid’s brain is stimulated.
  • As a listener, I want the game to have memorable soundtracks, so I get immersed into the game universe more.

Scope (slightly elaborated from the report 1) #

  • Core mechanics
    • platformer with a puzzles-based advancement through the world
    • manipulation with light bulbs to interact with the world and solve logical problems
  • Art style
    • the arts resemble paper, probably with mixed digital and traditional works
    • the main location is set inside the tower
  • Narrative and world setting
    • fantastic world with cyberpunk and fairytale elements
    • solid story with some logical conclusion
    • two endings depending on the user’s decision
    • dialogues with npcs and text plates
  • Level design
    • 15-20 minutes of gameplay
    • three levels with several screens in each
    • quick introduction to the mechanics
  • Sound design
    • several original soundtracks
    • sound effects

Prioritized backlog #

prioritized tasks

Project specific progress #

Code #

  • The movement of the character is implemented
  • The libraries for setting up the light, dialogue system, and text animation render are imported
  • The lighting is almost fully configured

Visual Design #

  • The designs for the main character, a light bulb, sockets, and dialogue windows are done
  • Several background designs are done

Narrative #

  • The core plot is finalised
  • The prologue for the level 1 and the main character description are drafted

Sound design #

  • The demo for the first soundtrack is done

Weekly commitments #

Individual contribution of each participant #

Plan for Next Week #

Things to code #

  • the light bulb and the port for it
  • the sliding bridge
  • the dialogue system

Narrative and level design #

  • finalise the prologue and the first level dialogues
  • finish design for the first level

Visual Design #

  • work on background locations and details
  • draw some of the npcs

Sound design #

  • finalise the first soundtrack

Organisation #

  • group call to discuss the process
  • keep consistent chat communication

Confirmation of the code’s operability #

We confirm that the code in the main branch:

  • In working condition.
  • Run via docker-compose (or another alternative described in the README.md).