Disclaimer:

• Some content in showcase is not included in asset, but will provide free samples and tutorials

For unknown reasons, I can't reply on the product page, if you have any questions, please send email or ask in the discrod

(Free Sample) Showcase: Youtube - Playable Demo: GoogleDrive

(Free Sample) Paragon(Wraith) - Showcase : Youtube - Tutorial (Youtube)

[Tutorial] Locomotion System + Riding System - Showcase: Youtube - Playable Demo(GoogleDrive)

(Tutorial) Showcase - Metahuman: Youtube

(Tutorial) Kubold Sword & Shield - Demo GoogleDrive - Tutorial (Youtube)

Tutorials and samples will provide more in the future

Support & Tutorial & Docs & Samples: Discord

Locomotion Component - Compatible with most Animsets in the marketplace & Pragon

Usage introduction Youtube

Main Features:

1. It can be integrated into any existing project.
2. No need to inherit from a parent character class, just add component in the character blueprint and it's done.
3. Support for both UE4 and UE5 skeletons.
4. Adding and modifying animations, as well as changing character speeds, can all be done simply through the use of DataTables, making it easy to manage a large number of animations.
5. The logic of animation states no longer needs to be done in ABP. Simply configure the animations for each state, and switch states as needed in any BP.
6. Other animsets from the marketplace are also supported, with assets such as Kubold, GhostSamurai_Bow, and Paragon already tested [Youtube] (more animsets will be tested in the future, and related tutorials will be created).
7. Very flexible animation configuration that can meet most requirements. All animations in the showcase project are completed through configuration.
8. You can adjust the animation of each pose by adding Anim Override.
9. Anim Override allows you to create different movement animations using fewer animations.

This asset includes lightweight combat components, it is built on an Event-driven architecture(Wiki) (Blueprint Only).

Usage introduction Youtube

Features:

1. Using components and events instead of interfaces and parent classes can lead to better decoupling
2. No need to know the specific type of the Actor anymore, as everything is treated as an Actor type, completely avoiding the use of type conversions (Cast to XXX).
3. When a value or state changes, all listeners are notified through an event dispatch mechanism to avoid using Event Tick

Components included:

• QuickBar：Used to manage weapon switching
• Health：manages character's health, damage taken, and death
• HUD：used to create and remove widget and dispatch events to widget
• AbilitiesManager：registers, unregisters, and get abilities
• Ability：manages ability cooldowns and triggers
• Bow：a universal bow solution that manages the state of the bow.
• Event：used for communication between BP
• Montage：used to play replicated montage and receive animation notify in any place.
• Team：used to assign teams to characters
• Weapon：Used for melee attack trace and management of some basic properties.

All of the above components implement the most basic functions and are not coupled to each other. Therefore, you are free to usd and extend them as you wish.