This is the same effect I created for the landing feedback of the ray in RayRunaway (the second project in the portfolio). In this case because I had also foliage in the scene I needed to create another material function that operates only for them (third slide). My main inspiration was the amazing Dragon's Dogma 2 impacts and roar effects , of course I'm very far from that result because the limitation of my approach is that the wiggle stops when exiting the circle width. In the future I would love to dive deeper into landscape interaction with render targets and/or Niagara 2d grids, but for now this was good enough for my application.

In this project I used a lot of data asset, they were the easiest way that came to mind for creating multiple attacks, items and skills. Each Data Asset is implemented in C++ because I needed to easily reference them in player and enemy attacks sequences (for damage, animation montages to play, etc.). I also used a Data Table to color code items effects (for example the percentage of health gain is green and the enemy debuff red).

In this section it's showed an example on how I managed inputs actions in the project. At every state of the turn (for state I refer to when you see the action menu or the items menu, the skills menu, when in focus mode, when targeting, etc.) corrisponds an Input Mapping Context that is added after removing the previous ones (through a bp function library call as showed in the slides).

We can divide all widgets used in two categories: the combat HUD and the Player widgets. The only widget that use canvas panel is the HUD, all the others are created inside it or put into widget components on the player. In the slide there are some widgets constructions examples, in particular it is shown how the menus (items and skills operate in the same way) are created modularly, you can put either one, two or 3 skills/items. It is also shown how I display widgets attached to the player. Every UI element was made in GIMP.

As can be seen in the first slide the qte widget animation handles also the parameter from the material parameter collection for the progression. I used this method so I could easily access the same parameter from the battle manager (third slide) and check if the player should get a damage buff. Damage Calculation is done with the c++ function shown in the final image that takes into account all buffs and debuffs that can be present.

In this section we can see every animation notify that I used for managing attacks movement, it is also shown the player function that determines an hit, a parry or a dodge. My first approach to enemy and player animations was to use only montages for everything except camera movement, this method didn't function as I could have expected because it lacked control on the sequence and they were hard to debug, for those reason I discarded the animation notifies for changing the play rate to simulate time dilation.