Skip to content

UoB-COMSM0166/2025-group-29

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 

Repository files navigation

2025-group-29

2025 COMSM0166 group 29

**Try Our Latest Beta Version Here! Click here

**Try Our Latest Development Version Here! Click here

Name Email GitHub Username
Weihao Zeng lh24059@bristol.ac.uk Zengweihaooo
Lepeng Zhou wn24588@bristol.ac.uk Lepengz233
Yichen Zhang gd24475@bristol.ac.uk Enderman928
Guojie Liu jy24369@bristol.ac.uk henlandl
Mengqiu Yan zj24391@bristol.ac.uk zj24391
Chen Zhang ov24336@bristol.ac.uk ov24336

image

Project Navigation

Weekly Progress

Week 1: Classic Game Analysis and Initial Ideas


Week 2: Refining Game Selection & p5.js Practice (Drawing App)

Kanban Board

Drawing App


Week 3: Prototype Development

Your Game

Link to your game PLAY HERE

Your game lives in the /docs folder, and is published using Github pages to the link above.

Include a demo video of your game here (you don't have to wait until the end, you can insert a work in progress video)

Your Group

Add a group photo here!

Name Email GitHub Username
Weihao Zeng lh24059@bristol.ac.uk Zengweihaooo
Lepeng Zhou wn24588@bristol.ac.uk Lepengz233
Yichen Zhang gd24475@bristol.ac.uk Enderman928
Guojie Liu jy24369@bristol.ac.uk henlandl
Mengqiu Yan zj24391@bristol.ac.uk zj24391
Chen Zhang ov24336@bristol.ac.uk ov24336

Project Report

Introduction

  • 5% ~250 words
  • Describe your game, what is based on, what makes it novel?

Requirements

  • As a player

    “I want the game to have a skill tree system so that I can choose and upgrade skills according to my playstyle and enhance my character's abilities. “

    “I want the game to have a complete storyline so that I can immerse myself in the game world and enjoy a rich narrative experience. “

    “I want the game to have a skin system so that I can customize the appearance of my character or equipment for a more personalized experience. “

    “I want the game to have multiple playable characters, each with unique traits, so that I can choose the one that best fits my playstyle. “

  • As a developer

    “I want players to enjoy our game.”

    “I want to gain development skills.”

    “I want to plan my time well and participate in quality teamworking.”

    “I want to be a positive role model for the next cohort. “

    “I want players to participate in early access testing for each version so that we can gather feedback and improve game balance patches.”

  • As a marker for this project,

    “I want to experience all core game mechanics in the shortest possible time.”

    “I want to see a game that has something new and innovative, not just a simple copy of an existing game.”

    “ I want to immerse myself in the game as quickly as possible after entering the main interface. “

Design

  • 15% ~750 words
  • System architecture. Class diagrams, behavioural diagrams.

Implementation

  • 15% ~750 words

  • Describe implementation of your game, in particular highlighting the three areas of challenge in developing your game.

Evaluation

  • 15% ~750 words

  • One qualitative evaluation (your choice)

  • One quantitative evaluation (of your choice)

  • Description of how code was tested.

Process

  • 15% ~750 words

  • Teamwork. How did you work together, what tools did you use. Did you have team roles? Reflection on how you worked together.

Conclusion

  • 10% ~500 words

  • Reflect on project as a whole. Lessons learned. Reflect on challenges. Future work.

Contribution Statement

  • Provide a table of everyone's contribution, which may be used to weight individual grades. We expect that the contribution will be split evenly across team-members in most cases. Let us know as soon as possible if there are any issues with teamwork as soon as they are apparent.

Additional Marks

You can delete this section in your own repo, it's just here for information. in addition to the marks above, we will be marking you on the following two points:

  • Quality of report writing, presentation, use of figures and visual material (5%)

    • Please write in a clear concise manner suitable for an interested layperson. Write as if this repo was publicly available.
  • Documentation of code (5%)

    • Is your repo clearly organised?
    • Is code well commented throughout?

About

2025 COMSM0166 group 29

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published