Corona-cation (Day 0)

Git Commit: 9e45555

"Enabled plugins, Added enemy health bar, Finalized cleric"

Enabled plugins:

    I just enabled the SmoothSync plugin for later use as well as the SurfaceFootstepSystem plugin. I also disabled the VR plugins because it was annoying having SteamVR open every time I opened the editor. 


Added enemy health bar:

    More substantial than enabling plugins was the health bar that I made for the enemies. This health bar is connected to a socket on the mesh so hopefully it will look better by moving relative to the animating mesh. The major feature of the bar though was that it would only show when the player is looking at the enemy (I still have yet to disable this through walls) and will rotate to always face the individual players.











Finalized cleric:

    After I made the health bar I decided now would be a good time to make sure that the players can do damage and kill the enemies correctly. I started out with the sharpshooter and everything went according to plan. The only thing I changed with him was that if you kill an enemy that is caught in the lasso the game would throw errors. To fix this I just removed that enemy from the array of lassoed enemies if it was killed. I then moved on to the cleric.
    There were two things that I hadn't implemented yet. From the design doc these were, "[Mana] bar will gradually refill over time but at a very slow rate (10% refilled after 30s)" and "Pray over corpses refills the [mana] bar (1 corpse = 10%)". The mana refill was relatively easy, just running off tick.


    The corpse feature was the easiest as I basically just did the same thing as from the creative jam project. When the enemy died they would spawn a torus on the ground that, if stepped on, would add to the cleric's mana.
    Now, when I had finished this I tested the heal spell just to make sure it hadn't broken. It all went fine until it came to the part where if mana is depleted, the cleric can use health to cast the spell. What actually happened was that the mana would go to 0 but the health just would not go down, no matter what I did. I just need to vent a little here about how incredibly stupid the solution was. I cannot express the frustration and anger I felt when trying to debug this. I had watched every value, changed execution flows, and prayed to every god imaginable but it refused to work. After just over two hours I said "screw it" and just deleted the Health variable, replacing it with a fresh one. AND THAT @!$*& WORKED!!! I was even more confused after that. So apparently that old health variable had decided to just straight up ignore my set calls meaning that the health would never deplete. Now it works though and I am so relieved.

Comments

Post a Comment

Popular posts from this blog

Polishing the Foundation

Image
     This sprint was relatively uneventful; mainly cleaning up the existing foundational elements of the game (the first person character and spell component) and continuing to improve the necessary elements of the game like the pause screen. Player Character & Spells      The improvements to the player character come in two parts; the ability to have, use, and change spells, as well as interaction via an interface. Both of theses are as simple as I could make them. Utilizing inheritance from USpellBase using the spells is only really a single line, and changing out the spells we can use the NewObject factory to make a new spell very simply. FirstPersonCharacter.h FirstPersonCharacter.cpp      As for the interaction interface, it only consists of two functions right now, one to fire an interaction event and one to check if the object can be interacted with. This second function is used mainly to show UI on the player's screen like...
Read more

Progress Update #13

Image
  Niagara Asteroids in UE4     These past few days I have continued work on asteroids. Only that now I have ditched instanced static meshes in favor of getting my hands on the new-ish Niagara particle system.  Learning Niagara     I have decided that since this is an entirely new subsystem of the engine I would do everything in blueprint first, then transition everything to C++ when I knew it was working reliably. Additionally, because Niagara is still relatively new, the official documentation is sparse if existent at all. So with most tutorials at this time geared towards blueprint implementation, starting in blueprint will give me the highest likelihood of finding a solution to any problems I may come across. The Niagara Workflow     The first thing I learned about Niagara is that the workflow has changed significantly from what cascade was. Where in cascade (to my limited knowledge) you worked in one particle system where e...
Read more

A New Chapter

Image
     This week has presented the biggest change probably since the release of Mini Solar System; I was offered a full-time position as a junior programmer at Studio 369 which I was happy to accept. I start on Monday and I couldn't be more excited to work with the team there! However, this did mean though that my priorities shifted quite instantaneously. I went from working full-time on "RPG_Game" to preparing for this new job. This mainly meant getting up to speed on networking as that is the one area of Unreal Engine I feel I have a lack of knowledge in (I'm already proficient in UI, AI, gameplay, materials, and general backend work), and since 369's specialty is networking I figured I would come prepared. I did do a little work on "RPG_Game" but it was minimal just to tie up some loose ends. Unreal's Multiplayer Framework      As explained by the Unreal Engine documentation, "multiplayer programming [is] inherently more complex than programmin...
Read more