Ionix Engine

/ROLE
Informal lead, Engine Architecture team
/TEAM
Whole Games Engines class · Manchester Met
/TECH
C++ · Premake · Box2D · Tiled · ImGui · GitHub
/TIMELINE
6 weeks · Source on GitHub
Overview
Ionix is a 2D game engine written in C++ by the entire Games Engines module class at Manchester Metropolitan University over six weeks. The class split into specialist teams, and I was the informal lead of the Engine Architecture team.
My role
Coordinated the architecture team's GitHub workflow and repository
Resolved merge conflicts as work from across the team came together
Supported teammates on their own engine tasks
Designed the branching strategy described below, which other teams adopted
Challenge: a whole class in one codebase
With an entire class committing to one C++ engine at the same time, merging straight into main quickly led to conflicts and broken builds.
I set up a dedicated Architecture branch that everyone on our team merged into first. Problems were found and fixed there, and only once the branch was stable did it get merged into main. That kept main working for everyone else, and the approach worked so well that the tutors encouraged the other teams to use it too.
Tech
C++, Premake, Box2D, Tiled, ImGui and GitHub, among other libraries.