{"id":1556,"date":"2025-05-12T14:56:22","date_gmt":"2025-05-12T14:56:22","guid":{"rendered":"https:\/\/sites.wsagames.com\/et4g23\/?p=1556"},"modified":"2025-05-14T22:40:39","modified_gmt":"2025-05-14T22:40:39","slug":"understanding-my-role","status":"publish","type":"post","link":"https:\/\/sites.wsagames.com\/et4g23\/2025\/05\/12\/understanding-my-role\/","title":{"rendered":"Understanding my role"},"content":{"rendered":"\n

A major part of this project is being able to understand and reflect real roles in industry, knowing what my responsibilities are and the responsibilities of real industry professionals with the same role is essential for that.<\/p>\n\n\n\n

Technical Designer<\/h2>\n\n\n\n
\"\"<\/figure>\n\n\n\n

When our teams were announced and shown to us, I found out that I was the team’s Technical Designer<\/strong>. In terms of the project overall, Sophie told me that my role was the one who would be communicating with the “higher-ups” the most (Being the course-leaders Vanissa and Sophie). However in terms of the group, it meant that I would be the one who would mostly communicate with everyone – merging different ideas and processes between the design side (Aysa and Josh) and the art side (Xane and Riya).<\/p>\n\n\n\n

Technical Designers in Industry<\/h3>\n\n\n\n

However, in order to this I needed to know what responsibilities and tasks I had to deal with myself. A perfect way to do this was to research what they were for real industry professionals who were Technical Designers.
From researching Technical Designers, I found that their main responsibilities were:<\/p>\n\n\n\n

Industry Responsibility<\/th><\/tr><\/thead>
Translating design into systems<\/td><\/tr>
Prototyping mechanics<\/td><\/tr>
Tool and workflow support<\/td><\/tr>
System scalability<\/td><\/tr>
Interdisciplinary collaboration<\/td><\/tr>
Documentation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

How does this translate to my role?<\/h3>\n\n\n\n

After using academic resources to research the responsibilities of a Technical Designer, it is key to evaluate them and understand how they should apply to me in this project. Furthermore, I will provide links to posts that showcase how I have understood and fulfilled my role:<\/p>\n\n\n\n

Industry Responsibility<\/th>Translation to my role<\/th><\/tr><\/thead>
Translating design into systems<\/td>Taking Lament’s GDD and implementing mechanics in Unity<\/td><\/tr>
Prototyping mechanics<\/td>Testing core mechanics (e.g. movement, combat, Tree of Sorrow)<\/td><\/tr>
Tool and workflow support<\/td>Creating robust systems in Unity for my teammates<\/td><\/tr>
System scalability<\/td>Structuring code for maintainability and reuse across scenes and features<\/td><\/tr>
Interdisciplinary collaboration<\/td>Communicating with my groups designers and artists to ensure everything works well together<\/td><\/tr>
Documentation<\/td>Website developer logs and explaining systems and code that I wrote<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

How have I fulfilled these responsibilities?<\/h3>\n\n\n\n
Industry Responsibility<\/th>What I’ve done<\/th><\/tr><\/thead>
Translating design into systems<\/td>Developed a Procedural Room Generation System<\/a>
Created a fully-functional Skill Tree<\/a>
Developed various enemy types<\/a>
Developed a Player movement and combat<\/a>
[All of which were heavily influenced by the GDD or with informed decisions from researching existing games]<\/td><\/tr>
Prototyping mechanics<\/td>Constantly tested Player movement and combat feel<\/a>
[Which resulted in an entire redo of the player’s attack]<\/a>
Tested prototypes of the skill tree step-by-step<\/a><\/td><\/tr>
Tool and workflow support<\/td>For the Procedural Room Generation, I created arrays of rooms that could spawn in the dungeon in a ‘RoomTemplates’ script<\/a><\/em><\/strong>, which our level designer could simply drag and drop in new rooms that they had designed.
Created animator bools and floats that Xane used to implement enemy animations<\/a> and player animations<\/a><\/td><\/tr>
System scalability<\/td>For the Procedural Room Generation, I created arrays of rooms that could spawn in the dungeon in a ‘RoomTemplates’ script<\/a><\/em><\/strong>, which could be infinitely scaled with the development of new room prefabs.
The Skill Tree uses SkillSO scriptable objects<\/a> that I used to quickly and efficiently scale the Tree of Sorrow<\/a><\/td><\/tr>
Interdisciplinary collaboration<\/td>Explaining to our Mechanics Designer about how animations would translate and be used in Unity<\/a>
When explaining that we should redo the player entirely<\/a>, I brought up how the old player had 8 attack directions. While we had 4 attack animations<\/td><\/tr>
Documentation<\/td>The Development section<\/a> of this website documents all of the scripts and systems I made and explains them fully<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Evaluating my performance<\/h2>\n\n\n\n

As I am writing this as the project comes to an end, It is an essential part of the Learning Outcomes that I am able to evaluate my teamwork role in its professional context:<\/p>\n\n\n\n