Melee+ (AI+FP/TP+Two Hands)

Melee+ is based on a flexible foundation: any weapon can be equipped on any hand. That rule anchors a blueprint framework that handles melee combat across two view modes, and it means editing a combat project starts with how you want characters to carry weapons rather than what the animation cycle permits. It has grown through updates that refocused the codebase around a single melee actor component, so it can be brought into a character blueprint without copy-pasting dozens of functions around the asset.

Any item on any hand, with a melee rule that stays consistent

The asset calls this Two Handed Combat. Rather than setting one weapon slot to a rigid left- or right-hand grip, Melee+ lets characters freely equip any item in any hand. That makes it easy to put a player's primary weapon where it feels right, or to change an enemy loadout by swapping the item that the melee actor is holding on a given side. The included animations are fully compatible and scaled to Epic's skeleton, so the movement set does not fight the standard UE character proportions.

Combat states also have room to breathe outside of combat. The first update added sheathe and unsheathe animations. When characters enter or leave an interaction area, they can put the weapon away and return to a neutral stance. The same update improved dodge rolling animation and introduced input buffering, so players can chain commands even if the exact frame timing was early or late on the preceding action.

Switching between first-person and third-person without a camera on the neck

Melee+ supports both first-person and third-person view modes. Switching between them is part of the core control scheme, not an added feature layered on top. One important detail about the first-person camera: it is not attached to the third-person mesh. In a typical melee system, switching to first-person means the camera sits inside or directly follows the same skeleton that handles dodges, impacts, and locomotion. In Melee+, the first-person camera is separate, so it doesn't inherit every head or bone rotation from the third-person character. This is a deliberate choice, as the asset states it exists to avoid motion sickness.

That difference matters in a fight full of dodges, strafes, and directional hit reactions. A detached first-person camera remains stable while the third-person body shifts, avoiding the disorienting roll or drift that many third-to-first person swaps introduce.

Damage is a physical contact test, not an animation timer

The combat feature list uses the phrase True Damage Hit Tracing with the warning: no smoke and mirrors. A weapon deals damage by physically hitting a surface in the game world. The system does not fake a hit when an animation reaches a particular frame, nor does it grant damage from a simple line-of-sight check. It checks the weapon's own trace and requires that trace to cross a surface. This has direct battlefield consequences: swings that pass wide, hit a wall, or land on another object will not damage a target standing behind that geometry.

Once contact happens, the reactions are not static either. The asset supports dynamic hit and death reactions. Characters can react authentically to the location and direction of the hit, and death forces include realistic bone impulses so bodies fall as physics pushes them. That makes the actual moment of impact feel like a consequence of the contact trace rather than a triggered animation.

AI combatants share the same melee rules

Melee combat systems often split into a fully designed player experience and a simpler simulation for enemies. Melee+ treats AI pawns as part of the same combat space. AI combatants are included, with team detection and four example classes for a head start. Team detection allows characters to be set on different sides, so allied and hostile guards can respond differently to surrounding actors. The four example classes provide skeleton AI setups that can be reskinned, rebuilt, or used to test player loadouts, rather than starting an AI controller from empty.

This is not a separate cutscene AI mode. The AI fighters use the same melee component architecture, and because the blueprint nodes are well structured and commented, it is possible to read through the flow and adjust behavior without migrating systems.

Update 2: integration moves into a single component

The update history marks a major shift in how Melee+ is meant to be installed. Update 2 is a complete code rewrite. The melee functionality is now neatly housed inside a melee actor component. Instead of connecting attack traces and hit events to several different blueprint interfaces or copy-pasting logic into each character, developers can add the component to an actor and wire the weapon into it. That plug-and-play setup is listed as the asset's easy integration path.

For a typical production workflow, this means the setup can be understood by reading a single component. A pick-up prompt system is tagged as removable, and feature examples are provided in commented blueprint nodes for teams that want to extend rather than inspect. The asset also includes a video tutorial for basic integration and a playable demo, which show how the component is meant to be applied before you open the graph.

A low-poly arena and a performance-first structure make testing direct

Practical validation is handled by a low-poly arena map included with the asset. Because the map is already there, combat testing does not depend on another level being complete. You can place an AI character, give them a weapon, and observe the first-person or third-person systems in a neutral environment.

The code's runtime behavior also supports heavy testing across multiple characters. The system is lightweight and performant, with performance as the top priority. Ticks are reserved for cosmetic elements, short duration tracing, and removable features such as pick-up prompts. The melee traces run for a short enough time that the system is not emitting collision checks on every actor for the entire swing. This keeps the generated combat loop easier on the frame budget than an always-on scan.

For projects that need restraint, optional features like dodge rolling and input buffering show the intended pattern: add only what the combat needs. Responsive combat is the stated priority; it emphasizes gameplay responsiveness over animation fidelity. The asset is labeled as universally adaptable, tailored to suit the melee combat needs of most projects and crafted to leave room for creative concepts. For gameplay programmers and blueprint tinkerers, Melee+ is a base that handles the dry fundamentals of grip, view, damage contact, and AI response so the first custom feature can be about the combat idea rather than the hit detection behind it.

Explore Similar Assets

• Hand to Hand set
• One Hand Sword Attacks And Finishers
• Stylized Fantasy Human NPC Pack
• Melee Weapon Stealth Finishers
• Hand to Hand finishers Volume 1