By: James Keats | 09 February 2018
Another week, another re[Mod] technical update!
One of the issues we were running into as re[Mod] has expanded more and more is that the BaseWeapon class had grown a little out of control. BaseWeapon handled combining all of the stats from its component WeaponParts, handling the logic for things like shooting, reloading, aiming down sights, serializing all of the necessary data across the network, and presenting the player with a visual response to their actions (such as switching the model pieces when changing weapon parts, activating particle effects while shooting, etc). The result was a file that was over 1,000 lines long. It was split up into #regions, but I still always dreaded it a bit when going into that file.
The first step in the solution to this problem was extracting out all of the “view” code out of this script. This included all of the code that handled VFX and animation, model switching, and any other visual code. In effect, it became similar to an MVC architecture, where the Model and Controller were combined in the BaseWeapon script and all of the view logic became the WeaponView script. Through this, we managed to significantly reduce the amount of code in the BaseWeapon script down to a mostly-manageable level, and the separation of concerns allows both scripts to be reasoned about more easily. Going forward, a potential next step would be to further implement the MVC architecture, pulling the Controller and Model for the Weapon out into two different classes.
Another major improvement I made this week for “game feel” was the addition and tweaking of inertia in the movement of the weapon. This was something that we had been planning for a while, and the refactor of the WeaponView made it significantly easier. The subtle but important effect is demonstrated in the video below made by our designer Charlie Carucci, who is showing off some new weapon parts he made (with placeholder art):
This system works by accumulating the player’s “look” rotation over several frames, sampling them with a bias towards the recent ones to establish a rotational velocity, and then setting its own rotation to the current look rotation with the velocity added and a slight smoothing factor. Working on this gave me a renewed appreciation for Quaternions, because doing this with Euler angles would’ve been a nightmare. Here’s a look at the code that achieves this effect:
That’s it for this week so far, but there’s a lot coming up! Weapon/head bob while walking, a UI overhaul, and a first-person hand viewmodel are all on the docket for this sprint, so look forward to the next blog post!