Today we need to agree on all the details of the game and then we can make a TA for people. In our team we have two Game Designers, one technical and one narrative. The narrative game designer is responsible for the idea and its development, and the technical one is responsible for its implementation in Unity.

It all starts with the narrative game designer: he writes down what mechanics there will be, decomposes pictures and audio (in simple terms, he writes a complete list of animations and sounds in the game) here is an example:

- Character

- Character walking animation

- Character hitting animation

- Character walking sound

- Character hitting sound, etc.

This is a very important point because thanks to decomposition, we divide one big task "make a Game" into many small tasks. This allows you to look at the amount of work as a whole and discuss it with other team members.

We are writing the mechanics in great detail, since according to the idea we have a resource "Stamina" in the game and it is spent all the time, the whole gameplay will be built on it. It is also planned to add character Stats that can be pumped up. All these mechanics are very closely intertwined with each other, so these relationships should also be taken into account when writing TA for the programmer.

Since we did not have time to agree on everything on this day and write the TA for the artists, programmer and sound engineer to the end, we will do it tomorrow. As of today, we have the following ready from the game: The concept of the first cutscene, the floor and walls of the first location, the sprite of the main character, the mechanics of walking and a half-finished Beat 'em up combat system, as well as music for the menu.

Some advice:

1. If you are a narrative game designer in the project, then this is the most important moment for you. You need to somehow imagine a picture of the finished game in your head. And then ask yourself how it will be played, boring or fun? And if it's boring, how to diversify the gameplay without increasing the work for your team.

2. If you are a technical gem designer, then this is no less important for you. Already at the stage of the finished idea, you need to think over the architecture of the code in the project, because if this is not done in advance or incorrectly, then as a result, developing the project at later stages will either be very painful or impossible.

06/21/2025