Corona-cation (Day 5)

Git Commit: afb9a0e

"Added ScarabSwarm enemy"


Added ScarabSwarm enemy:

    What I thought would be a simple enemy turned out to take up all my time today. The basic idea was that it would be an enemy that would just be a hitbox that once overlapped would do damage every interval of time. That part wasn't so bad, it was the movement that took the longest.
    I started off thinking that the actor itself would be static and the actual swarm would be a particle effect that would give the illusion of movement. Turns out I was wrong and the designers said that the entire thing "moves in erratic patterns". So I had to convert the actor to a pawn then add an AI controller, blackboard, behavior tree, etc. then tell it to pick a random point close to around it and move there. The problem was, it didn't move. I struggled for a while until I noticed that I had forgotten the most important thing that I had always taken for granted when making human type enemies. The pawn didn't have a movement component. I basically told it to move somewhere without giving it legs. 
    Once I figured that out I decided that a behavior tree and whatnot was too complex for something that only moved around randomly. Because of this I deleted all that in favor of doing all the movement on the pawn itself by using "AIMoveTo" nodes. With this done I showed a designer for approval and was told it looked as intended. Success! The only feedback was that the swarm should move more in a straight path and not double back on itself so much. This was expected as the random points were random and so the swarm was a little too erratic. 
    To fix this I did a check to see if the point it had found was more or less in front of the swarm. This made it look much better but resulted in a new problem: the swarm would run itself into a wall or corner and get completely stuck. To remedy this I added a condition that if too many points in a row were found out of range, the swarm would just go with any point it found.
    This is the final BP:
TestForValidPoint

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