Corona-cation (Day 9)

Git Commit: None


    Still nothing finished yet for the Plague Doctor. It is proving to be much harder than I originally thought it would be. The only difference between this enemy and the others I have worked on is that this one has multiple attacks. That one difference has taken up two full days of work and it has yet to be fully figured out. 
    From the last time I worked on it I changed a few things. The first being the random attack generator. I had this in a service before but now it is a task. I realized that a service is not what I would want because it ticks and that would change the attack type rapidly, confusing the hell out of the AI. But with that figured out, I went back to figuring out how to have the attacks cycle. This was the part I was stuck on for the majority of my time today. 
    The problem was, once an attack was chosen it would do that attack (as expected) but then it wouldn't return to the state where it would choose a new attack. I experimented with multiple solutions, none of which fully worked. The first attempt was to have an empty attack state that would signal the BT to choose a new attack. This didn't work though as when it chose an attack the BT would lock up because now it had an attack type but the decorator that would reset the attack tree would close. 
    The next attempt was to make a custom decorator that would only abort when the AttackType was set to none. This didn't work, partially because I don't really know how the custom decorators work (because I didn't look for documentation) and because of that I didn't put too much time into it. As I write this retrospectively though I think that this approach might actually have some merit if I looked more into it.
    The third and final approach for today was to have a boolean Attacking that would dictate when to reset. This kind of worked, but with a new problem. Now the BT cycles too quickly. When it is supposed to move toward the player to do a slash attack it only tries for one tick until it picks a new AttackType. I don't quite know why yet but I will look more into it tomorrow.
    This is the current state of the attack branch of the BT:


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