Build numerous systems, including player movement, HUD elements, skill trees, checkpoint systems, inventory systems, and game state serialization.

Consult with enemy designers and programmers to determine workflows, technical limitations, and studio planning.

Advise designers on technical limitations and restrictions of proposed ideas.

Assist artists and sound designers with integration of their assets using Adobe Illustrator and FMOD.

Reusable components allowed cut work to be used on future projects

The online UI prototyping tools allowed for quick iteration and clear specifications from designers

Regular meetings allowed for close collaboration between designers and programmers

Clear documentation and tutorials for FMOD allowed for easy integration of sound effects.

Skill Tree integration with abilities was not planned from the start, leading to “spaghetti-like” code architecture when integrated with player abilities.

Overscoping with player abilities led to an unexpected cut to the skill tree. The tight coupling of player abilities and the skill tree made the cut much harder than expected.

Last minute feature additions created numerous bugs and led to additional production delays

Use online prototyping tools to quickly iterate and clarify expectations

Regularly meet with teammates to ensure close collaboration between different disciplines

Avoid tight coupling of systems through design patterns, event systems, and careful planning

Avoid last minute feature additions and late scope cuts