Corona-cation (Day 1)

Git Commit: 8e3012c

"Fixed players damaging enemies, Added the ability for enemies to damage players, Added SmoothSync to players and enemies"


Fixed players damaging enemies:

    This was a very odd issue that I found today. Yesterday I had only tested the damage system in the DungeonTest level which I did not realize had a different gamemode and therefore an entirely different server-client system. So today when I tested in the Island level the damage system didn't work. I was able to eventually figure out that the problem had to do with the client trying to set the enemy's health which should only be done by the server. To remedy this I added a custom event that would execute essentially the same code just on the server instead. 


Added the ability for enemies to damage players:

    Just a simple recreation of what we did for the creative jam game. When the enemy is close to the player it will wait an amount of time, attack with a given damage value and repeat. The only challenge here was checking the attacked player's health and making the enemy disregard any players that were dead. I think tomorrow I will try to implement this with the revive system. 


Added SmoothSync to players and enemies:

    This was relatively simple. I just followed the documentation for the plugin and in no time all movable characters were less jittery. I did find something interesting though to do with data compression. There is a setting on the SmoothSync component that allows you to compress the position and velocity data. At first glance I thought why would you not enable that, it would make the game take up less bandwidth and you still get smooth movement. But eventually I found why you may not want to enable those settings. Again while testing on the much smaller dungeon map it worked fine, but on the large island level the compression was making the movement exponentially more jittery. So in summary if you are working with small location values then the compression is worthwhile, but if your map is really big you will need the extra resolution that non-compressed values offer.

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