Temple of Thorns

The basic spell blueprint was created to be a parent for all other spells. It has a collision sphere set as the default root and projectile movement with no modifications. The sphere is set block all and generate hit events. On component hit, I call a custom event to be overridden by the child blueprints.

Example of creating and customizing a child from base spell and adding custom Niagara effects to be activated.

Example of a blueprint checking for damage type of spell. This was the most modular way to allow my team to create any in game reaction to a spell simply by using this function.

Checks for if the player is on cooldown or has enough mana for the equipped spell.

Checking the current equipped spell and spawning the corresponding actor as well as passing on their individual values.

The vine actor responds to the fire spell and removes collision.

The water reacts to the ice spell creating a bridge to cross over.

The lightning trap reacts to the lightning spell and shuts off.

Showing my folder organization as well as the spell and spell types created.

Input to switch to the next index in the player's spell array. If the index is invalid it resets to 0 being the first spell in the array.

This event is triggered after casting to refill the mana automatically overtime. It calls a function on a looping timer. The timer is promoted to be cleared and invalidated when necessary.

The function being called on a looped timer to recover mana automatically.

This logic gathers the starting overlap values of the stats from the player reference to ensure a successful timeline lerp.

This logic takes the starting overlap values of the stats and recovers them smoothly over the timeline until finished or the player steps off the fountain.

This is a modular level loading script. The blueprint can be placed anywhere in the world and the level to load is instance editable.

This is the damage and death function of the player. If the player takes damage and loses all health, their input is disabled and the respawn at the last checkpoint. The delay in yellow was added by a teammate to allow for the death animation. I originally displayed a game over widget.

This is called when the player takes damage and has more than 0 health after. It causes a visibility blinking effect.

The function called from timer to make the player blink visibility.

This is just fun logic for making a mesh move up, scale down and spin faster when collected.