Dr. Lugo's weapons

Author: Daniel Jackson


            The final boss dubbed 'Dr. Lugo' has the ability to use any of the weapons in the game and use them to a better degree than the player is able to. The additional functionality changes based on the weapon and in phase one he will take and use the weapon the player had equipped. I was charged with adapting the original weapon code with the new boss variation.


    To start with the boss uses the base weapon values just like the player, from there I broke out into each weapon to modify them individually. First was the pistol, in addition to firing normally it fired explosive rounds, the bullets themselves were larger than normal, and the boss can fire the weapon in a cone pattern. Second was the shotgun, I created a second shotgun in addition to the first one and offset them so he can fire two shotguns at once. Then the rocket launcher, when the rocket launcher is fired an additional one is fire straight backwards, instead of normal explosions cluster bombs drop instead, and the rockets have a heat-seeking capability. The sniper fires additional bullets as it travels, the swordgun will apply a bleed effect to the player and heal the boss, the shots ricochet off of walls, and the swords will eventually explode. Finally, the last weapon I was able to work on was the assault weapon. This weapon fires two bullets at the same that travel in a sine wave like pattern. This last pattern was the most challenging out of all of them and took the longest to implement out of the listed weapons.




(Example of how the boss' assault weapon starts its bullet construction)



Comments

Post a Comment

Popular posts from this blog

Adding assets to every enemy -- Owen Meyers

Image
      As with every game, it is very important to have assets to denote which enemy is which. Being able to tell at a glance what enemy you are encountering before receiving a face full of buckshot is incredibly important. The issue for Project [REDACTED] is that we didn't have any artists working full time to deliver assets for the enemies. Thus, it fell upon me, the designer of the asset pipeline, to acquire assets for every enemy. This led to having to fix models and integrate animations, with each problem being subtly different.     Take, for example, the shotgunner model. His original model was designed for an OpenGL renderer, and was flipped 180 degrees for that very reason. In addition to this, he was also placed halfway in the ground, likely due to something required for that game's collision to function. Fixing this model to function for our renderer required that it be re-rigged and most of the animations acquired from Mixamo. With the help of Kris, and several hours
Read more

Sphere to AABB collision

       I had a problem today when trying to detect sphere to AABB collision. For some reason the collision check that I made was never turning true even though I could clearly see the sphere hitting the AABB. This was a big problem as we needed this collision to detect whether any entities are hitting walls.     I discovered that the problem with this bug was that I was improperly getting the closest point in the AABB to the sphere. The way I fixed this problem this problem was by getting the max vertex that the circle center could be and using that to get the closest point on the AABB to then determine the minimum vertex between the sphere's max vertex and the max of the AABB.  Once I found this point, I could properly compare the distance of that point to the center of the sphere. This solution will allow detection between walls and any sphere collider such as the player collider, and enemy collider. This is very important to make sure they both stay within the level bounds.
Read more