Cold Veins was made using Unreal Engine 5.2.1, during the creation of Cold Veins our team utilised GitHub for our repository and used Git LFS for all of our files too large to be stored in the repository. We also utilised the Git ignore for any unnecessary files that can be regenerated.

​

During my time spent on this project I learnt a lot and was the one to set up our groups repository, due to my previous experience with Unreal Engine I was also elected to be our programmers lead. This helped me reaffirm a lot of my knowledge for unreal whilst helping others and also gave me a better understanding of how long a task should take to complete. 

​

When we began, all code was being done in C++ with blueprints built from those foundations, however towards the end of the projects deadline, time was becoming short so we decided to use blueprints only to maximise our efficiency.

​

My main focus during this was on the weapons. I created a base class and from that branched into children classes for each weapon. I also opened up access to variables in a way that allowed a weapons to be edited but only on the default BP to standardise how a weapon functions and to prevent any accidental or unwanted behaviour for a weapon by accidentally editing one placed in the game world. I also placed maximum and/or minimum values on specific variables to prevent odd behaviour such as negative accuracy.

​

The weapons utilise hit scans using line traces and once fired gives the camera some kickback to emulate weapon recoil. To make cold veins feel nicer to play I also implemented recoil compensation, this returns the reticule back to the amount of degrees adjusted by the recoil and also prevents the players aim from endlessly going up.

​

The weapons were originally designed to be modular, however due to time constraints this ended up being out of scope. To create this there was discussions with the art team on the best way to design this. After which we decided that it would be best to create sockets within the weapons base armature and attach those components accordingly with their attachment point to allow a wide variety of customisations.

​

whilst writing in C++ I used clear naming conventions for variable and functions to ensure that as little notes were required when reading my code, this was to allow other developers to look at what's happening and understand at a glance. If something was temporary and needed to be changed later down the line then there would be a note attached to that line of code or if a line of code seems over complicated I would then use a note to describe it in a much simpler way.

​

I also helped set up all of the menu widgets and created the functionality for them.

​

Click here to play the game: Itch.io

Click here to view source: GitHub

​

​

​

​

​

​

​