Creating comprehensive design documents that can be understood by all facets of the team.

Balancing the game in the form of: economy, mission quests, character power, progression speed.

Designing the game to be player friendly; UX and accesibility is a large priority in my design.

Continually improving systems to reduce player friction and ensure enjoyment.

Creating greybox environments for new levels, and populating them with vital objects / obstacles.

Making internal tools to help coalesce information in a more digestible and automated way (spreadsheets).

Creating 'tutorial' documents and wiki pages to help other designers and team members to understand internal tools and systems.

Playtesting the game to discern where bugs and causes for concern are.

Generating new ideas for characters, levels, events, and systems.

Coding and prototyping; due to my comfort in Unity and doing C# coding, I handled the bulk of coding the systems and logic for the game.

Aiding with some asset hunting.

Playtesting and ensuring that the game is working properly.

Handling version control and any issues that arise with multiple people working on it.

Truthfully, the whole project. I took up the mantle of coding / prototyping, alongside designing (levels, mechanics, etc.), and doing art.

Research into resources to use for the game that are copyright free or offer a license (such as the Corgi Engine which was used here).

Comment your code. Even when revisiting the project years later, having everything very neatly commented helped a lot to understand the function of everything.

Feedback from other non-design team members is paramount. Although the team was small, there was an artist working on a different project who would often playtest and give feedback from a different perspective.

External feedback is just as important; there was no way for us to know that when putting out an alpha to test, the resolution on itch.io's built in player messed up completely.

(Thanks to Cyberwolf Games for trying it out and making a video review for it.)

UX not being taken into account alongside accessibility. There is no option to adjust the post processing effects to reduce eye strain. This is in part just due to lack of knowledge how to go about it, but it also wasn't taken into design account.

A lack of documenting. There was very little documentation made for this game outside of concept art and level design sketches which were all on paper; although we were working with an engine that had a robust system of mechanics, these were never written down how they worked for our game.

Revisiting tutorials and easily accessible tutorials help a lot in info retention, especially for players who may have not played in a long while; putting tutorials in just the game itself and not somewhere static can hurt.

Coding and playtesting; I am the most familiar with Unity and C# coding among my team members, so doing interactions and coding was my primary task to ensure the game was working properly.

Design work, designing was a team effort in sitting down and brainstorming the mechanics we wanted to have, and I worked on implementing and refining with the Unity XR Kit system.