P.A.I.N.T. Logo

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!

Trailer

Project Details

Websitepaint-game.com
EngineUnreal Engine 4
Development Time40 weeks
Team Size25 people
My RoleTech Lead
QA Lead
Programmer
TechnologiesC++, Blueprints, C#, Python, Batch
Target PlatformsWindows
PlayStation 4

My contributions

Tech Lead

During the second half of the project, I took the role of tech lead. This included some of the following tasks;

  • Having meetings with the other leads and individual teammembers.
  • Setting goals for every Sprint for the programmers in the team.
  • Giving updates in the form of a presentation to the stakeholders (school teaching staff).
  • Organising Stand downs at the end of the day with the programmers to give each other progress updates.
  • Making sure everyone in the team is happy.

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.

Arthur Kuylaars - teammember on this project

Quality Assurance Lead

Throughout the entirety of the project, I've been responsible for the technical side of Quality Assurance. I've been keeping myself busy 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.

Here are some things I've worked on that fall under my role as Quality Assurance Lead;

Continuous Integration

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.

Crash Reporting

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.

Sentry Logo
Swarm Reviews

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.

Analytics

TODO