Writing synthetic and comprehensive technical documents to ensure the team uses the same vocabulary and has a document to refer to. Here is the technical document we wrote on the throw & aim mechanic.
Using Google Slides allows for easier teamwork
Overview of the feature before going in-depth into details
Illustrating clearly each situation with a diagram creates documents that are easier to read
Coherent symbols in every diagram make for a more readable document
I am able to design mathematical models that are adapted to our intentions
Detailing meaningful tweakable parameters to facilitate work with programmers
Detailing our design intentions ensure each member can take the right decisions
To ensure everyone is up to date with the latest design decisions, we arrange presentations that explain design intentions, why solutions were accepted or rejected and what we decided.
Presenting mechanics to the team
Reference technical documentation to explain how it works and give it more exposure
Seeing the system through the user eyes to highlight what's important
Explaining what are the standard solutions for this problem
Explaining design intentions to give an idea of why solutions were rejected/accepted
Giving an overview of the inner workings of the system
A link to technical documentation is available in every slide
Giving intentions also help User Researchers to know what to test
Reusing the same diagrams as in technical documentation to foster readability
We built our enemies in regards to the character's moveset we made. Each enemy challenges specific skills and all skills are covered by our enemy set.
We suggested simple & functional character designs to the art team as a basis to iterate upon and to be able to meet deadlines. For example, the spike catcher design matches its behaviour without the need to add hard-to-animate hands.
I worked inside the engine using Unity's animator and used a custom finite state machine tool
to implement enemies into the game.
I worked hand-in-hand with the AI programmer to be able to do faster
refinements on the enemies.
To balance the game, I used internal feedback from the team combined with mathematical balancing based on the target player behaviours we wanted to have.
To be able to get a better grasp on our 3Cs as soon as possible, I prototyped some parts of our character controller and added gamefeel elements such as animations.
To test our 3Cs and gamefeel early on, we prototyped toys such as breakable objects that are shown in the adjacent gif.
