diff --git a/content/docs/2025/evening-jam/_index.md b/content/docs/2025/evening-jam/_index.md new file mode 100644 index 000000000..da46dd550 --- /dev/null +++ b/content/docs/2025/evening-jam/_index.md @@ -0,0 +1,4 @@ +--- +bookCollapseSection: true +title: "Light Lethargy" +--- diff --git a/content/docs/2025/evening-jam/week1.md b/content/docs/2025/evening-jam/week1.md new file mode 100644 index 000000000..422245302 --- /dev/null +++ b/content/docs/2025/evening-jam/week1.md @@ -0,0 +1,171 @@ +--- +title: "Week #1" +--- + +# Week #1 + +## Project description + +### Project name: Light Lethargy + +**Code repository**: https://github.com/fantom73d/evening-jam + +A puzzle-platformer game with a fairytale setting, mixed with cyberpunk elements. Involves the paper-like artstyle, simple but intriguing mechanics, and a touch of light phylosophy. Lamps are significant and playable objects: player advances through the levels and interacts with the world by manipulating them. + +Problem statement: create a game that provides an enjoyable and fascinating way to spend time with a creative but not overwlelming brain training and an easy-to-follow storyline. + +### **Team Members** + +| Team Member | Telegram Alias | Email Address | Track | Responsibilities | +|-------------------------|------------------|-------------------------------------|----------------------------------------|--------------------| +| (Lead) Dmitry Korletynu | @fantom_73d | d.korletyanu@innopolis.university | Art design, Game design | Team organization, art design, game and sound design | +| Lev Ivanov | @Evolutionleo | i.ivanov@innopolis.university | System architecture, Code, Game Design | Coding, making game design choices | +| Ulyana Yanovskaya | @polsha_byaka | u.yanovitskaya@innopolis.university | Narrative design, Game design | Writing plot and dialogues, working on game and sound design | +| Veronika Levashseva | @fountainer | v.levasheva@innopolis.university | Narrative design, Documentation | Reports, writing plot and dialogues, sound design | +| Bulat Shigapov | @blt326Ray | b.shigapov@innopolis.university | Art Design | Visual art design | + +## Brainstorming + +### Ideas during brainstorming + +Main concept ideas (from fittest to less fittest ranked in descending order) + +| Name | Short description | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Light bulbs in the fantastic world | The setting is focused on the idea of the manipulation with the light to solve problems: interesting and gives freedom for plot choices | +| Character is a robot | Can integrate interesting mechanics involving the player himself +| Character is a human | People more readily sympathise with other people | +| Gamification of Innopolis Bootcamp (totally different setting) | Interesting but hard to implement everything + members of the team wanted to focus on the full game +| Light affects colors | The world is monochrome, which can be interestingly explained by some plot: in the usual world, the oblects reflect light and we see colors, in this, it doesn't work | +| A tower like a playground | Helps to see the progress with visual representation | +| Main character is the outsider | A natural scientist suddently gets into the fairytale-like world and firstly very sceptical about it; idea is okay but not really matches the cyberpunk setting with the lamps | | + +Game Mechanics Ideas + +| Name | Short description | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Incandescent light bulb | Light up the paper sheet that will burn out with time | +| Broken fragments of a bulb | Player torns himself if he steps on the fragments (because the character is made of paper) | +| Bulbs of different powers | Example: one lamp can power the lift but cannot turn on the drawbridge | +| De-energised world | The whole world is freezed but the player can give life to its objects/inhabitants only temporarily by using lamps as accumulators | +| Screwed in light bulb | Npc can become "revived"/active by putting a lamp in him/her | +| Broken lamp influence 1 | If the lamp is broken it leaks the energy and cannot be used forever | +| Geometry changes | If you insert the light bulb into yourself your hitbox is increased and you cannot get into small passages | +| Broken lamp influence 2 | A broken lamp inserted into a mechanism will activate it abruptly, with repeated ons and offs. Example: an elevating platform becomes a trampoline | +| Light mechanics | Player can light his/her way up with a light bulb | + + + +### Brief market research / problem validation + +Puzzle-platformers are distinguished and widely played, as well as loved by the players for their authenticity and simple cognitive training. They also provide a solid ground for the indie developers with small teams and give the opportunity to focus on story telling and interesting mechanics. + +Examples in the market + +Renowned platformers: + +- Limbo by Playdead: very atmospheric with subtle but prominent social shadowing, interesting mechanics involved +- Badland by HypeHype Inc: more dynamic due to its sidescrolling game process, puzzles with the world objects +- Machinarium by Amanita Design: beautiful design with cyberpunk style, puzzles based on the mechanisms manipulations, similar to our project and also has paper-based arts + +Games that also used light as a base for game mechanics: + +- Closure by Eyebrow Interactive: based on manipulation of light and shadows: player can use the object only if it is visible. Was innovative with this concept at its time and gained wide recognition +- Candleman by Spotlightor Interactive: a player has to use light from a candle to pass the level, but it extinguishes after the time is up. Similar to our idea with a broken lamp and adds a possibility for timer-based quests + +## Basic requirements + +### Target users and their primary needs + +Our target users are casual players without any specific background. We want our game to be fascinating for any ages: the puzzles should be understandable but not dumbed-down, and the story should be enjoable and provide the ground for light contemplation both for kids and adults. Our aim is to give our players a way to spend time with some intellectual stimulation and aesthetic pleasure. + +As a side consideration, we want our game to be suitable for for avid indie games players through its inventive mechanics and original storyline. The users who seek something innovative and authentic should also enjoy the gaming process. + +### User stories + +- 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. + + +### Initial scope + +- 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 +- Narrative and world setting + - Fantastic world with cyberpunk and fairytale elements + - Solid story with some logical conclusion (but with a possibility for further development) + - Dialogues with npcs and text plates +- Level design + - Initially intended 15-20 minutes of gameplay + - Several levels + - Quick introduction to the mechanics + +## Tech-stack + +- Code/engine: Gamemaker +- Art: Aseprite, Photoshop, Krita +- Docs: Google Docs +- Presentations: Figma +- Version control: git +- Narrative: Google Docs +- Team communication: Telegram + +## *Something else you want to add* + +If it possible, we would like to provide a new name for the project in Week 2. +Also, we did not setup the Docker Compose since it is not suitable for our project specification. + +# Weekly commitments + +## Individual contribution of each participant + +- Dmitry Korletynu: + - team organization + - [art style sketches](https://docs.google.com/document/d/1-2NGqt-iOFekyaZ3wNFKYwu0CocmT8kTIUd0YJfZL1M/edit?usp=sharing) + - [game mechanics ideas](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing) + - organized team github and added [description](https://github.com/fantom73d/evening-jam/commit/3d027d4282cde69200504226683c1ef7c6b09ff4) +- Lev Ivanov: + - [game mechanics ideas](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing) + - [initial repo for the project files](https://github.com/evolutionleo/Capstone-2025) +- Ulyana Yanovskaya: + - [game mechanics ideas](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing) + - [plot ideas](https://docs.google.com/document/d/1X3O8aEoBbfwByd1n85P7moEmHtmtGIArqPp-ZDOn_1s/edit?usp=sharing) +- Veronika Levasheva: + - report writing, market research, requirements formulation and project description + - [plot ideas](https://docs.google.com/document/d/1hWIcZBvNxBm6T2rokU6OvqqILAwzmeWg26bmX7wfSDw/edit?usp=sharing) + - fixed the directory for [_index.md](https://github.com/fantom73d/evening-jam/commit/ba2f8eea9d3b1b8ba53b61983ab8855968584e72) +- Bulat Shigapov: + - [art style sketches](https://docs.google.com/document/d/1XaA9Zpr1JE7QGSfo9WQFBLV58CPPrVcmso8HinUmkkA/edit?usp=sharing) + +## Confirmation of the code's operability + +We confirm that the code in the main branch: +- [x] In working condition. +- [ ] Run via docker-compose (or another alternative described in the `README.md`). + +# Plans for the Week 2 sprint + +## Things to code +- the light bulb and the port for it +- the basic movement +- the sliding bridge +- the dialogue system + +## Narrative and level design +- Write dialogues for the first level +- Make up puzzles for the first level + +## Art +- Draw the main character and npcs +- Draw the dialogue window +- Draw the basic location elements + +## Organisation +- Video call to brainshtorm and agree on the first level content +- Write report for week 2 diff --git a/content/docs/2025/evening-jam/week2.md b/content/docs/2025/evening-jam/week2.md new file mode 100644 index 000000000..304a90e85 --- /dev/null +++ b/content/docs/2025/evening-jam/week2.md @@ -0,0 +1,172 @@ +--- +title: "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](https://github.com/user-attachments/assets/d7b61bf7-ae9d-4cf2-9bcf-2eb9ce04aab5) + +## 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 + +- Dmitry Korletynu: + - team organization + - [art designs](https://docs.google.com/document/d/13QO-JjkJXl1LKpEI9iTTEW-dIfMBKsB1IMP66PQc_S0/edit?usp=sharing) + - [sprites commit 1](https://github.com/evolutionleo/Capstone-2025/commit/5ea5c47031c3b67325d69d16ba5ce944a626e960) + - [sprites commit 2](https://github.com/evolutionleo/Capstone-2025/commit/de13d21abc9643dc9f855f4d7cf85a9a92469f0b) +- Lev Ivanov: + - [player movement implementation](https://github.com/evolutionleo/Capstone-2025/commit/5f6086e6404e2770ca8f2a2779c2fc9453e620cd) + - [imported libraries](https://github.com/evolutionleo/Capstone-2025/commit/921121b51624ca7f65f559ee0802afa75726cd84) +- Ulyana Yanovitskaya: + - [prologue ("пролог" section)](https://docs.google.com/document/d/1Ul-d97mPKF-ZTrO-CHl08b0JdEY6rSsgcE8PJKCeIiA/edit?usp=sharing) + - [core plot ("нарратив" section)](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing) +- Veronika Levasheva: + - this report + - [demo for the first soundtrack](https://drive.google.com/file/d/1j_lxH5Jn6wQWqhvHfidEOMMCKEOHEVcc/view?usp=sharing) + - [core plot ("нарратив" section)](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing) +- Bulat Shigapov: + - [art designs](https://docs.google.com/document/d/1hlbU7bBaP0luV-S_qWmShMu2GZVDvdzh_Kt1rzFqdpI/edit?usp=sharing) + +## 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: +- [x] In working condition. +- [ ] Run via docker-compose (or another alternative described in the `README.md`). diff --git a/content/docs/2025/evening-jam/week3.md b/content/docs/2025/evening-jam/week3.md new file mode 100644 index 000000000..4fd9f8a20 --- /dev/null +++ b/content/docs/2025/evening-jam/week3.md @@ -0,0 +1,130 @@ +--- +title: "Week #3" +--- + +# **Week #3** + +## Implemented MVP features + +Our MVP includes core mechanics implementation as a base for the developing gameplay. Right now, we have: + +- the [movement](https://github.com/evolutionleo/Capstone-2025/commit/240ccae0369598a1a325bd159815cc488674264e) of the player is implemented + +- a starting set of empty [levels](https://github.com/evolutionleo/Capstone-2025/commit/ea8649c54e851f08ec1a17e079e312ddde290510) with designed [backgrounds](https://github.com/evolutionleo/Capstone-2025/commit/a47ab97d76e9545cde6638aa1e28576505701782) + +- implemented [lamp mechanics](https://github.com/evolutionleo/Capstone-2025/commit/1c18e0b88c2564f7cc4d017136531a35d670034e): the player can pick them up, place into designated sockets and activate mechanisms (for example, a bridge) + +- the [interaction with the npcs](https://github.com/evolutionleo/Capstone-2025/commit/1c18e0b88c2564f7cc4d017136531a35d670034e) and [dialogue window](https://github.com/evolutionleo/Capstone-2025/commit/c0892f44dac87e79c8824b6ed0d18ddd11f07f6f) are implemented + +- some mechanisms are now present in the form of placeholders to display the future functionality + +This MVP forms a base for the future detailed development in the following weeks. + +### The user journey + +Movement and world exploration + +- The player can control the movement of the character using W, A, S, D and Space for jumping + +Interaction with the lamps and mechanisms + +- The player can pick up and put down a lamp by pressing E +- The player can activate the mechanism by putting a lamp into it + +NPC interaction + +- If NPC are present, pressing F will trigger a dialogue + +Navigation shortcuts + +- F4 to go to the previous level + +- F5 to restart the current level + +- F6 to skip to the next level + +- Ctrl + F5 to restart the whole game + +## Demonstration of the working MVP + +[The repository with implementation](https://github.com/evolutionleo/Capstone-2025) + +[Video demo](https://youtu.be/HfcIS501ZTU) + + +## Internal demo + +### Strong sides + +- Movement is responsive and goes without lagging +- Core lamp mechanics are done and work smoothly +- The shortcuts help with debugging +- The designs are harmonious and look good + +### Functional weaknesses + +- no animation makes the gameplay look too static +- placeholders should be replaced asap +- npcs should be added for storytelling opportunities +- no music is added yet, though is in progress + +### Team organisation + +- since two members are not able to be present at discussions physically, the group meetings are harder to organise, we should take it into account more and find means of easier communication + +# Weekly commitments + +## Individual contribution of each participant + +- Dmitry Korletynu: + - team organization + - added an [npc sprite](https://github.com/evolutionleo/Capstone-2025/commit/0204721bdab40da21d7e5ba7a4a979881ce1bb75) + - [level design](https://docs.google.com/document/d/1LlTyt_cxw3sljkO4-UPljxDbiX3mdZn26JJxUg8c63Q/edit?usp=sharing) +- Lev Ivanov: + - [a sequence of empty levels](https://github.com/evolutionleo/Capstone-2025/commit/ea8649c54e851f08ec1a17e079e312ddde290510) + - [lighbulbs and npcs](https://github.com/evolutionleo/Capstone-2025/commit/1c18e0b88c2564f7cc4d017136531a35d670034e) and [dialogue box](https://github.com/evolutionleo/Capstone-2025/commit/c0892f44dac87e79c8824b6ed0d18ddd11f07f6f) + - [energy system](https://github.com/evolutionleo/Capstone-2025/commit/91dee58a636d3ecb0f4405ad550ec76d77ce6cfd) + - [level transition](https://github.com/evolutionleo/Capstone-2025/commit/1d3e90fd503edebc46616547b8938ea049b779d6) and [debug cheatcodes](https://github.com/evolutionleo/Capstone-2025/commit/b976c9c382fcb4eb44e4023e4b5410a1effe65cf) + - [player controls improved](https://github.com/evolutionleo/Capstone-2025/commit/240ccae0369598a1a325bd159815cc488674264e) + - [initializer room + lighting test](https://github.com/evolutionleo/Capstone-2025/commit/fbcd671a48caa658d0ac0bcd6ae531458679e1f3) + - [level design](https://docs.google.com/document/d/1LlTyt_cxw3sljkO4-UPljxDbiX3mdZn26JJxUg8c63Q/edit?usp=sharing) +- Ulyana Yanovitskaya: + - [level design](https://docs.google.com/document/d/1LlTyt_cxw3sljkO4-UPljxDbiX3mdZn26JJxUg8c63Q/edit?usp=sharing) +- Veronika Levasheva: + - this report + - [extended version of the first track](https://drive.google.com/file/d/1KFaNlOjRa3GvwmQFbs7H60GLHEDfS87o/view?usp=sharing) +- Bulat Shigapov: + - [designed backgrounds](https://docs.google.com/document/d/1Atrx-hVSO6tmEkwe1dREJji7B9UFaqKRLlV8gW07qBw/edit?usp=sharing) + - [updated previous sprites](https://github.com/evolutionleo/Capstone-2025/commit/a36ab70cbb441e57c10807e9a730526df42bdf1e) + +## Plan for Next Week + +### Things to code + +- code the jump pad +- put the second level together + +### Narrative and level design + +- formulate the level design for the second level +- write the second level dialogues + +### Visual Design + +- make backgrounds for the second level +- animate objects for interaction + +### Sound design + +- write the second 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: +- [x] In working condition. +- [ ] Run via docker-compose (or another alternative described in the `README.md`). diff --git a/content/docs/2025/evening-jam/week4.md b/content/docs/2025/evening-jam/week4.md new file mode 100644 index 000000000..4fc4faa55 --- /dev/null +++ b/content/docs/2025/evening-jam/week4.md @@ -0,0 +1,91 @@ +--- +title: "Week #4" +--- + +# **Week #4** + +## Testing and QA + +For the quality assurance, we made an automated build for our project that is activated on each push. + +### Evidence of test execution + +![The pipeline](https://github.com/user-attachments/assets/0d783799-d895-420f-ada2-b781d4883194) + +## CI/CD + +### Tools we used + +- [setup](https://github.com/bscotch/igor-setup) +- [build](https://github.com/bscotch/igor-build) + +### Challanges + +- Making an automated build for the Gamemaker project was quite hard and demanded a lot of time + +### Links to CI/CD configuration files + +- [yml file](https://github.com/evolutionleo/Capstone-2025/blob/main/.github/workflows/ci.yml) + +## Deployment + +### Staging + +Each push is going through the build pipeline, so if is not successful, we would not authorise the merge requests. + +### Production + +Release builds meant for publishing are compiled on our developer's machine locally for now. This is to ensure optimal build settings. + +## Vibe Check + +- We still have some problems with organisation and the general mood of the team +- Some people are not satisfied with their roles and the need to make something creative under the deadlines, so we need to create a more comfortable environment +- Some members are still not present with a legal reason, so the communication is not as good as it could have been + + +# Weekly commitments + +## Individual contribution of each participant + +- Dmitry Korletynu: + - team organization +- Lev Ivanov: + - [implemented the jump pad](https://github.com/evolutionleo/Capstone-2025/commit/f87ae6975b138383e6859962171e3fbec4c26794) + - [implemented death handling](https://github.com/evolutionleo/Capstone-2025/commit/92561e12d49579750ca4c13ae5b398e4827aff13) + - [automated build](https://github.com/evolutionleo/Capstone-2025/commit/122a3e6749c0c37610680dd2484872aecd67874b) +- Ulyana Yanovitskaya: + - [worked on characters ("персонажи" field)](https://docs.google.com/document/d/1Ul-d97mPKF-ZTrO-CHl08b0JdEY6rSsgcE8PJKCeIiA/edit?tab=t.fepdcfwihw9p#heading=h.jrms3cqlaruf) +- Veronika Levasheva: + - this report + - [wrote all dialogues for the first level and for the start of the second one (lvl1 and lvl2 fields)](https://docs.google.com/document/d/1Ul-d97mPKF-ZTrO-CHl08b0JdEY6rSsgcE8PJKCeIiA/edit?tab=t.5t03903ai246) +- Bulat Shigapov: + - [made new backgrounds](https://docs.google.com/document/d/18_2sXF0mWBhaDnU7dNCTDwzn7qXZSNZqnLJ529hH1vs/edit?usp=sharing) + +## Plan for Next Week + +### Things to code + +- put the second level together + +### Narrative and level design + +- formulate the level design for the second level +- finish writing the second level dialogues + +### Visual Design + +- make the backgrounds for the next scenes +- design objects for interaction +- animate objects for interaction + +### 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: +- [x] In working condition. +- [ ] Run via docker-compose (or another alternative described in the `README.md`). diff --git a/content/docs/2025/evening-jam/week5.md b/content/docs/2025/evening-jam/week5.md new file mode 100644 index 000000000..3ab65d7e7 --- /dev/null +++ b/content/docs/2025/evening-jam/week5.md @@ -0,0 +1,117 @@ +--- +title: "Week #5" +--- + +# **Week #5** + +## Feedback + +### Sessions + +We conducted three sessions with our potential users and gained the following insight: + +| Participant| Pros | Cons | Suggestion | +| ------------------------------------- | --------- | -------------------------------------------------------- | ------- | +| Maxim - an experienced gamer who mostly plays on PC | Quickly understood the controls, liked the idea of using lamps | Graphics felt "unfinished", didn’t understand the purpose of the NPC | Make the lamps more noticeable and "interactable" | +| Artyom - a game designer interested in philosophy and indie games | Found the setting intriguing, liked the atmospheric lamps | Gameplay felt too short and overly simple | Add more interactive objects and expand on the idea of light as a symbolic element | +| Andrey - a hobbyist developer | Appreciated the bridge and energy mechanics | Lacked feedback during interactions (no sounds or visual effects) | Add visual and audio effects to enhance interaction feedback | + +### Analyze + +| Problem | Priority | Comment | +| ------------------------------------- | --------- | -------------------------------------------------------- | +| Underdeveloped graphics | High | Affects first impressions and overall atmosphere | +| Short and simple gameplay | Medium | Needs at least 2–3 levels or some form of progression | +| Lamps are not clearly key elements | High | Should be visually and narratively emphasized | +| Lack of interaction feedback | Medium | Enhancing it will improve immersion | +| NPC lacks narrative purpose | Medium | Add dialogue, a quest, or some hint of a storyline | + +## Iteration & Refinement + +### Implemented features based on feedback + +In progress: + +- NPC dialogue: Dialogue with light philosophical undertones is written and ready, but not yet added to the build + +- Graphics enhancement: We've started reworking the background and interactive objects, focusing on a "paper-like" visual style + +Will be added in the next runs: + +- Visual and sound effects: We're planning to add animations for lamp activation and other mechanisms + +- Level expansion: We plan to add 1–2 more scenes with new puzzles and interactions + + +### Performance & Stability + +| Metric | Current Value | Improvement Potential | +|-----------------------|-----------------------------------------|------------------------------------------------------| +| FPS on standard PC | 60+ FPS | Stable, but not tested on low-end devices | +| Level loading time | < 1 second | Acceptable, though resource optimization is possible | +| Stability | No crashes | Stability level is acceptable | +| Number of bugs | 0 found | — | + + +### Documentation + +We have multiple documentation documents for various parts of our project: + +- Technical documentation + - [Game Design Document](https://docs.google.com/document/d/1Vo9ULr0iiDlRrvzsPDKi_QGgH3iBMy6o6v2Kx9lyGMw/edit?usp=sharing). Contains general description, team information, the main mechanics ideas and plot summarisation. This document is the main reference for all game components + - [Level design in Figma](https://www.figma.com/design/ug2Id0lJdqkA6U6IL1Cmds/Untitled?node-id=592-3&t=SLnBhW5YGFaIlANR-1). We had to keep the clean and consise workspace with a collaborative opportunities for the level design formulation and we chose to do it in Figma + +- [Detailed plot with all dialogues](https://docs.google.com/document/d/1Ul-d97mPKF-ZTrO-CHl08b0JdEY6rSsgcE8PJKCeIiA/edit?usp=sharing). The document is up to date with all relevant changes and provides an opportunity for quick reviews, feedback and sharing + +- [README with the project description](https://github.com/evolutionleo/Capstone-2025/blob/main/README.md). The DEADME currently only contains the descriptions but will be elaborated with the game local setup instructions in the next runs + +# Weekly commitments + +## Individual contribution of each participant + +- Dmitry Korletynu: + - team organization + - organised the sessions with the potential users and assessed the metrics + - [worked on the level 2 design](https://docs.google.com/document/d/1W190nFbnwszOzWxLTKID2sHAAxvsDKtxP2FoA8v9g0U/edit?usp=sharing) +- Lev Ivanov: + - code revision +- Ulyana Yanovitskaya: + - [worked on the level 2 design](https://docs.google.com/document/d/1W190nFbnwszOzWxLTKID2sHAAxvsDKtxP2FoA8v9g0U/edit?usp=sharing) +- Veronika Levasheva: + - put the report together + - [worked on the dialogues for the second level](https://docs.google.com/document/d/1Ul-d97mPKF-ZTrO-CHl08b0JdEY6rSsgcE8PJKCeIiA/edit?usp=sharing) +- Bulat Shigapov: + - worked on backgrounds and overall style + +## Plan for Next Week + +### Things to code + +- code the shutters (doors and platforms) +- put the second level together + +### Narrative and level design + +- finalise dialogues + +### Visual Design + +- animate walking +- make the backgrounds for the next scenes +- refine and animate objects for interaction +- lamp animation + +### Sound design + +- add sound feedbacks + +### 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: +- [x] In working condition. +- [ ] Run via docker-compose (or another alternative described in the `README.md`). \ No newline at end of file