In this cooperative third-person shooter, you take control of the P.U.N.K.’s. Rebels that shoot their way through an evil factory with high-powered paint blasters. Sabotage the tyrannical corporation and fight your way through their factory to achieve the highest chaos score!
|Engine||Unreal Engine 4|
|Development Time||40 weeks|
|Team Size||25 people|
|My Role||Tech Lead|
|Technologies||C++, Blueprints, C#, Python, Batch|
Throughout the entirety of the project, I've been responsible for the technical side of quality assurance. I've been responsible for setting up our processes such as Helix Swarm reviews, setting up continuous integration using Jenkins, continuous delivery to Steam and in general, making sure we keep the build stable as much as possible.
All quality assurance pipelines are described in a single, easy to read document so that everyone in the team is able to read up on it should they need to.
Here are some things I've worked on that fall under my role as quality assurance lead;
For continuous integration, we are using Jenkins, which periodically checks for changes in our Perforce depot, and if there are any, it triggers a build for the different platforms we support. (Windows and PlayStation 4) This is done for both the development and shipping configurations. When a build succeeds or fails, a message is sent in Discord to notify the team about this.
Through the approach of continuous delivery, Jenkins automatically uploads successful Windows shipping and development builds to Steam and push these to separate branches. This ensures we always have the latest build available on our machines with Steam keeping it updated automatically.
I've been responsible for setting up the Unreal Engine crash reporter to post crash reports to my Sentry server. This allows us to see when and why the game crashes and aids us in improving the game.
I've been responsible for setting up the Swarm review processes that the team follows. The process is set up in a way that allows us to enforce continuous delivery, by always having a stable build ready to deploy to Steam.
During the second half of the project, I took the role of tech lead. This included some of the following tasks;
You have picked up the role as lead programmer very well. Honestly you are the best tech lead I have come across. You take your role very seriously and are actively involved in many sections of the project, not only tech. Your behavior and communication is very professional.