Connect your game.
Make combat readable.

Start here

What this kit does

Targeting & Combat provides target selection, character frames, overhead nameplates, cast bars, effect icons, floating numbers, a combat log and threat information. Think of it as the display and connection layer around your combat system.

What your game supplies

Your game controls ability rules, animations and multiplayer authority. The kit can display results from your existing health system. Alternatively, use its optional combat-stat and damage components. Choose one health owner: showing a number does not apply damage, and applying damage twice will double the hit.

Choose your route

Use the supplied demonstration to explore the controls. When connecting your own game, start with Player connection below. You do not need another BIS product to use these hooks. The editable Blueprint examples are teaching examples; placing one in a level alone does not connect your game.

This build

This guide targets Unreal Engine 5.8 on Windows. The Blueprint images are actual complete native editor graph views. The examples demonstrate local integration; they do not establish automatic multiplayer replication.

Install and find the examples

1. Keep a backup

Before adding the kit to your game, save your project and keep a recoverable copy. Use the plugin build that matches your Unreal version.

2. Add the plugin

For a manual installation, put the TargetingSystemKit folder inside your project's Plugins folder. Keep Content, Source, Resources and the descriptor together. Enable Targeting & Combat Information and its engine-bundled Text3D, Niagara, Enhanced Input, Control Rig and Animation Compression Library dependencies. Restart when requested. A source rebuild requires Unreal-compatible C++ build tools; the Blueprint hooks do not require writing C++.

3. Find the saved examples

In the Content Drawer, enable Show Plugin Content, select All and clear asset-type filters. Search BP_BIS_TC_IntegrationExamples for BIS01-BIS14 or BP_BIS_TC_CombatExtensions for BIS15-BIS26. Both are under TargetingSystemKit Content > TargetingCombat > Integration > Blueprints. Open the Blueprint, then use Ctrl+F with the individual BIS number, or select its full graph name in My Blueprint.

4. Work on your copy

Duplicate the example into your game Content before adapting it. Open it and choose a numbered graph from My Blueprint. Each tab contains one complete example. Ctrl+F searches the Blueprint: BIS01 takes you to player binding; BIS03 takes you to the ability-request receiver. Double-click a result to jump there.

5. Understand the red starting node

The red node is an event you call from your own game. It does not run automatically. Its inputs supply the objects and values used by the blue function node. White wires decide what runs next. Colored wires carry values. A Provider input means the particular object that owns that function; it is not a new asset you must buy.

Connect your player first

1. Give characters a targetable component

Open your player character Blueprint. Add a TSK Targetable Component. Do the same for enemies or friendly characters you want to select. Set their display name, level, disposition and maximum health. Turn on a resource display only when that character uses it. Flag bosses explicitly; a large health pool does not make an actor a boss.

2. Resolve the correct local player

From the PlayerController that owns the player, get the TSK Targeting HUD Subsystem for that local player. A subsystem is simply the kit's manager for one local player. Keep that reference for the examples that need the HUD Provider. Resolve CIE Combat Subsystem from the same local player for the combat log and meter. Avoid a global player-zero lookup when supporting more than one local player.

3. Bind the possessed character

Once the controller possesses its pawn, call Bind Host Player with that pawn's Targetable component. BIS01 shows the connection. Bind Host Player must receive your possessed local pawn, not an enemy or a different player. Its direct node returns true when binding succeeds. In your own graph, check this return value before continuing.

4. Copy your real values

When your game changes health, call Set Health on the matching Targetable component with the new current value. Set maxima before current values. Use Set Mana or Set Fury when applicable. For a simple check, set maximum health to 100 and current health to 75; the associated health display should read three quarters full.

5. Keep ownership clear

Binding enables host-game mode: the temporary demonstration bar and its combat simulation stop owning your player. Your ability system is still responsible for damage, costs and death. For your own targeting inputs, use TSK Targeting Component or the HUD selection hooks. Consume interface clicks before processing a world-selection click.

6. Reconnect after respawn

When your game replaces the pawn, bind the new pawn's Targetable component. A stale pawn is not accepted as the current player. Passing an empty player reference unbinds while keeping host-game mode on; it does not quietly restore demo health.

Explore the demonstration

The temporary bar

The demonstration has Auto Attack, Unbreakable, Ironhide and Kick. Kick plays the included kick animation and can be spent even when it interrupts nothing. It can interrupt eligible healer and mage casts; the Juggernaut's Gravefist and Gravebound Roar stay protected. The Juggernaut keeps its punch-only attack animation.

The Draugr and boss

Open L_Training under TargetingSystemKit Content > TargetingCombat > Demo > Maps. It includes Juggernaut, Gravebinder, Runecaller and the larger Ashen Warden boss. The healer and mage use mana; the Juggernaut uses its own resource. Select a placed actor to edit its combat stats, abilities, movement and respawn settings.

Death and restart

Defeated demo enemies remain dead for their configured Respawn Delay before recovering. The player stays down after death; Enter restarts the level. These demonstration rules do not take ownership of death in a game connected through Bind Host Player.

Choose a target

Use the configured targeting controls or click a targetable character. The player frame can select yourself. Right-click the selected-target frame for supported focus and marking actions. Friendly selection uses green. Choosing a target is separate from permission to attack it.

Preview versus gameplay

Settings previews help arrange an otherwise hidden panel. A visible preview is not proof that a real cast, threat event or boss encounter is connected. Test with events from your own game before relying on a panel.

Switch the training character

Press N to switch between Quinn and Manny while alive. Your health, cooldowns, target and position remain unchanged. The shortcut is disabled while a settings panel, menu or text-entry control owns input. It is a training-map convenience; your own game retains control of its player character.

Make the display suit your game

Open the settings

Use the Targeting & Combat launcher. The targeting pages include Targeting, Global Appearance, Player Frame, Target Frame, Party Frames, Nameplate Layout, Nameplate Text, Nameplate Bars, Selection Ring, Buff / Debuff Icons, Layout & Profiles, Ability Catalog, Combat Text and Text Colors.

Change the right control

Global appearance affects the overall style; a frame page adjusts that particular surface. Use Nameplate settings for floating enemy labels, not the fixed target frame. Keep the thin resource bars distinct from health. Use Buff / Debuff Icons for effect sizes. Combat Text adjusts the floating-number presentation; Text Colors changes its palette.

Arrange hidden panels

Use the combat panel controls and Idle Panels preview when arranging cast bars and other normally inactive panels. Turn the preview off to judge ordinary behavior. Enable or disable the relevant panel separately; hiding a panel should not change gameplay.

Save deliberately

Use Layout & Profiles for targeting profiles. Existing saved choices can take precedence over new project defaults. Combat presentation stores its own layout choices. Use the relevant Save or Reset control and read its scope. Reset appearance, reset positions and reset everything serve different purposes. Do not delete the project's Saved folder just to change a layout.

Set project defaults

Stop Play, then inspect Edit > Project Settings > Plugins for the Targeting and Combat pages. These are the starting choices for your project. When checking a new default, account for existing saved profiles; do not overwrite player data accidentally.

A reliable order for your own combat

Request

Your button asks to use an ability, identified by a stable name such as Game.Fireball. The request event tells your game which ability and selected actor were requested. It does not guarantee success.

Validate

Your game checks that the player can act, that the target and range are valid, and that enough resources and cooldown time are available. In multiplayer, your authoritative server makes the gameplay decision.

Cast and resolve

Start the actual cast and feed its state to the kit. When your game delivers the ability, apply damage or healing once. If it is cancelled or interrupted, stop any pending delivery in your own system.

Display

Copy the new health/resources, update cooldowns and effects, show the actual damage or healing number, and send the resolved combat event to the log/meter. Add threat separately if your rules call for it. These are distinct jobs; a floating number must not apply damage a second time.

COMPLETE BLUEPRINT EXAMPLE 01

Connect your player

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS01_ConnectPlayer_Example
Function: Bind Host Player

What to connect

1. Get the TSK Targeting HUD Subsystem from the owning local player. Connect it to Provider.
2. Connect the currently possessed pawn's TSK Targetable Component to Player State.
3. Call this example after possession. For your production graph, inspect Bind Host Player's return value and handle a failed binding.

COMPLETE BLUEPRINT EXAMPLE 02

Ask to use an ability

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS02_RequestAbility_Example
Function: Request Host Ability

What to connect

1. Connect the same local HUD manager to Provider.
2. Supply a stable Ability Id, for example Game.Fireball. Use the same ID in your own catalog, button and handler.
3. Call from your button or input. Connect BIS03 first. Your handler checks whether the requested ability may run.

COMPLETE BLUEPRINT EXAMPLE 03

Receive the request in your game

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS03_ReceiveAbilityRequest_Example
Function: On Host Ability Requested

What to connect

1. Call BIS03 Bind Ability Requests once with the correct HUD Provider.
2. The red delegate connection points to BIS03 Ability Requested. This example records Ability Id and Target Actor in Last Requested Ability and Last Requested Target.
3. Extend that receiver into your own ability logic. Validate eligibility and route server-owned gameplay through your own networking. Remove old bindings when replacing a listener.

COMPLETE BLUEPRINT EXAMPLE 04

Show a cooldown

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS04_UpdateCooldown_Example
Function: Set Host Ability Cooldown

What to connect

1. After your game accepts an ability, supply its stable Ability Id and the correct HUD Provider.
2. Set Duration Seconds to the full cooldown and Remaining Seconds to the current time left.
3. Send zero remaining time to clear the display. Keep this in step with your real cooldown system.

COMPLETE BLUEPRINT EXAMPLE 05

Read the time left

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS05_ReadCooldown_Example
Function: Get Host Ability Cooldown Remaining

What to connect

1. Provide the local HUD manager and the same Ability Id used when updating the cooldown.
2. Call the example. Its green data wire carries the seconds remaining into Last Cooldown Remaining.
3. Read that variable for a custom display, or use the getter directly in your own widget.

COMPLETE BLUEPRINT EXAMPLE 06

Show current buffs and debuffs

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS06_UpdateBuffsAndDebuffs_Example
Function: Set Host Effect Presentation

What to connect

1. Provide the local HUD manager and the Recipient actor whose effects you are showing.
2. Build the complete Effects list. Each entry needs a stable Effect Id, name, description, icon, stack count, remaining time and whether it is beneficial.
3. Send the full list when it changes; an empty list clears it. Use current durations from your game.

COMPLETE BLUEPRINT EXAMPLE 07

Start a cast display

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS07_StartCast_Example
Function: Begin Cast

What to connect

1. Provider is the caster's Targetable component, not the HUD manager.
2. Supply the ability name, duration in seconds and whether this particular cast can be interrupted.
3. Call when your actual cast starts. Use the same caster state for overhead, target and focus presentation.

COMPLETE BLUEPRINT EXAMPLE 08

Finish a successful cast

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS08_FinishCast_Example
Function: Complete Cast

What to connect

1. Keep a reference to the same caster component used by Begin Cast.
2. Let your own ability finish its accepted gameplay delivery once.
3. Call Complete Cast on that component to end its cast state.

COMPLETE BLUEPRINT EXAMPLE 09

Cancel a cast

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS09_CancelCast_Example
Function: Cancel Cast

What to connect

1. Provide the active caster's Targetable component.
2. Call Cancel Cast when your gameplay cancels the ability.
3. In your game, also cancel pending timers, projectiles or other delivery. Use On Cast Finished to handle unsuccessful completion consistently.

COMPLETE BLUEPRINT EXAMPLE 10

Interrupt an eligible cast

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS10_InterruptCast_Example
Function: Interrupt Cast

What to connect

1. Your game first checks the interrupt's target, range and rules.
2. Provide the target caster's Targetable component and call Interrupt Cast.
3. Inspect the direct node's boolean result in your own graph. Stop pending delivery when interruption succeeds; protected or absent casts are not successful interrupts.

COMPLETE BLUEPRINT EXAMPLE 11

Show a damage number

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS11_ShowDamage_Example
Function: Show Resolved Damage Number

What to connect

1. Apply damage once in your own system and obtain the actual amount dealt.
2. Supply the local HUD Provider, the Recipient actor and Actual Damage.
3. Choose the actual hit Kind: Normal, Critical or Crippling. Call once for that result.

COMPLETE BLUEPRINT EXAMPLE 12

Show a healing number

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS12_ShowHealing_Example
Function: Show Healing Number

What to connect

1. Heal once in your own system and calculate the health actually restored.
2. Provide the local HUD manager and healed Recipient.
3. Send Actual Restored without overheal. For a target at 90 of 100, a 25-point heal restores 10; display 10.

COMPLETE BLUEPRINT EXAMPLE 13

Update the log and meter

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS13_RecordCombatEvent_Example
Function: Record Combat Event

What to connect

1. Provider is the CIE Combat Subsystem for this local player.
2. Build the Event with stable Source Id, readable source/target/ability labels, resolved amount and the correct damage/healing/critical flags.
3. Call once after resolving the event. Begin Encounter when starting a measurement window and end it when your encounter ends.

COMPLETE BLUEPRINT EXAMPLE 14

Add a real threat contribution

Blueprint: BP_BIS_TC_IntegrationExamples
Graph tab: BIS14_AddThreat_Example
Function: Add Threat

What to connect

1. Provider is the threatened enemy's Targetable component.
2. Source is the actor that generated the threat. Supply the accepted Amount from your game's threat rules.
3. Add other real contributors in the same way. Clear threat when your encounter/reset policy requires it.

COMPLETE BLUEPRINT EXAMPLE 15

Configure a character's combat stats

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS15_ConfigureCombatStats_Example
Function: Configure Combat Stats

What to connect

1. Use the character's TSK Targetable Component as Provider. Call this when setting up that character, not every frame.
2. Supply maximum health, armor and strength. Restore Health chooses whether current health is refilled. Configure Damage Per Strength in the component defaults; zero leaves outgoing base damage unchanged.
3. Keep your authoritative stat system responsible for deciding these values. Changing a display label does not change armor or damage.

COMPLETE BLUEPRINT EXAMPLE 16

Apply damage through the optional health component

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS16_ApplyCombatDamage_Example
Function: Apply Combat Damage

What to connect

1. Provider is the victim's Targetable component. Supply nonnegative incoming Damage and the actual Source actor.
2. Call once after your authoritative game accepts a hit. The component applies its armor calculation and updates health.
3. Read Result BIS16 for health actually lost. Send that result to display/log hooks once. If your own health system already applied the hit, mirror health with BIS22 instead.

COMPLETE BLUEPRINT EXAMPLE 17

Resolve block, dodge or parry

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS17_ResolveMeleeDefense_Example
Function: Resolve Melee Defense

What to connect

1. Supply the actual attacker and defender positions and defender forward direction, plus your chosen defense settings.
2. Supply one random roll from your authoritative combat logic. This example stores the returned outcome in Result BIS17.
3. Use that outcome consistently for damage and presentation. Rear attacks cannot be blocked, dodged or parried. Resolving the outcome alone does not damage anyone.

COMPLETE BLUEPRINT EXAMPLE 18

Display a hit or avoidance result

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS18_ShowResolvedHit_Example
Function: Show Resolved Hit

What to connect

1. Connect the owning local player's TSK Targeting HUD Subsystem to Provider.
2. Connect a complete Hit result, carrying Source, Target, Ability, Kind, Applied Damage and Defense. Existing result events can supply this structure. For a simple amount from your own system, use Show Resolved Damage Number instead.
3. Call once after resolution. Apply damage through your chosen health owner and record the combat event separately when required.

COMPLETE BLUEPRINT EXAMPLE 19

Select or clear a target

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS19_SetCurrentTarget_Example
Function: Set Current Target

What to connect

1. Connect the correct local HUD manager to Provider.
2. Supply the target actor's Targetable component. A null component clears selection.
3. Call from your own selection UI. Continue to validate hostility, range, facing and obstruction when resolving an action.

COMPLETE BLUEPRINT EXAMPLE 20

Set a focus target

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS20_SetFocusTarget_Example
Function: Set Focus Target

What to connect

1. Provide the local HUD manager and the desired actor's Targetable component.
2. Call the example and check Result BIS20 rather than assuming the requested focus was accepted.
3. Use Clear Focus Target on the same HUD manager when dismissing focus or cleaning up your encounter.

COMPLETE BLUEPRINT EXAMPLE 21

Assign an overhead marker

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS21_SetTargetMarker_Example
Function: Set Target Marker

What to connect

1. Use the marked character's Targetable component as Provider.
2. Choose the marker enum value. Use None to remove an existing mark.
3. Call when your game accepts the mark change. Keep any multiplayer ownership and replication in your game.

COMPLETE BLUEPRINT EXAMPLE 22

Mirror health from your existing game

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS22_SetHealth_Example
Function: Set Health

What to connect

1. Set the character's Max Health first and use its Targetable component as Provider.
2. Supply the current health value after your existing system has processed damage or healing.
3. Call when health changes. Do not additionally apply the same hit through BIS16.

COMPLETE BLUEPRINT EXAMPLE 23

Mirror mana from your existing game

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS23_SetMana_Example
Function: Set Mana

What to connect

1. Configure Uses Mana and Max Mana on the character's Targetable component.
2. Supply that component as Provider and the actual current mana after spending or regenerating it.
3. Disable Uses Mana for characters that do not use this resource. Do not fake a mana bar for the Juggernaut.

COMPLETE BLUEPRINT EXAMPLE 24

Add custom target information

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS24_SetTargetAdornment_Example
Function: Set Target Adornment

What to connect

1. Use the owning local player's HUD manager as Provider.
2. Connect the character's Targetable component to Target. Make a TSK Target Adornment structure with your Texture, Height and Gap, then connect it to Adornment. Fixed Screen Pixels is optional; leave Visible Bottom UV at 1 unless accounting for transparent padding.
3. Call Clear Target Adornment during cleanup so information from a previous target is not left behind.

COMPLETE BLUEPRINT EXAMPLE 25

Use the resolved defense result

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS25_DefenseDamageMultiplier_Example
Function: Defense Damage Multiplier

What to connect

1. Supply the defense outcome resolved by BIS17 and the same defense settings.
2. Read Result BIS25 and multiply the incoming damage by this value once.
3. Pass the resulting damage to your chosen health owner. Keep avoidance, mitigation and floating feedback consistent.

COMPLETE BLUEPRINT EXAMPLE 26

Reset an encounter's threat

Blueprint: BP_BIS_TC_CombatExtensions
Graph tab: BIS26_ClearThreat_Example
Function: Clear Threat

What to connect

1. Supply the encounter target's Targetable component as Provider.
2. Call during your encounter reset or cleanup when its contributor ledger should be cleared.
3. Synchronize your own authoritative threat data separately in a networked game.

If something does not work

I cannot find the Blueprint

Enable Show Plugin Content, select All, clear filters and search BP_BIS_TC_IntegrationExamples. The function Bind Host Player is not a Content Drawer asset. Once inside the example, use Ctrl+F with BIS01 or open its named graph tab.

The player frame shows the wrong health

Confirm that Bind Host Player received the currently possessed pawn's Targetable component. Copy current health after your own system changes it. Rebind when replacing the pawn. The Provider must belong to the same local player.

An ability request does nothing

Bind your receiver before requesting the ability. The included BIS03 receiver only records the requested ID and actor, so you can inspect them. Replace or extend it with your own validated ability router. A request without a listener is not an executed ability.

The cast bar finishes but nothing happens

The kit shows casting state; your game performs delivery. Call Complete Cast after successful delivery. Bind On Cast Finished to stop your own pending delivery when the cast fails or is interrupted. The component also completes its display automatically when its duration expires. A successful On Cast Finished notification confirms that display lifecycle, not server-approved spell delivery. Do not apply damage merely because a bar reached the end.

Numbers or totals are doubled

Check that your game applies health changes once, that Show Resolved Damage Number is called once for display, and that Record Combat Event is called once for the log/meter. Remove duplicate listeners and duplicate input routes.

Old effects remain after respawn

Send the complete current effect list, clear it when appropriate, and bind the replacement pawn. Do not carry a dead actor's effect list into the new life.

My changes disappear or do not appear

Check whether you changed project defaults or a saved profile. Confirm the relevant panel is enabled and that preview visibility is not masking live behavior. Compile and save your own Blueprint copy.

Before using this in your game

A useful first check

Connect your own pawn, change its health and resource values, request one ability through your own button, show its cast and cooldown, then cancel it. Replace the pawn and confirm the new binding works. Check target changes, effect expiry and one damage event without duplicate totals.

Networked games

These examples show local presentation and event routing. They do not provide automatic replication or a server-authoritative combat framework. Send accepted results from your game's networking to the correct local player's presentation.

Your own action bar

Use stable ability IDs in your buttons and drag/drop receiver. The preview catalog supplies a reusable payload, but a compatible receiver still needs to connect it to your game. Full integration with an arbitrary action-bar product is not implied.

Packaging

Keep the plugin dependencies enabled and make sure your own meshes, textures, animations, abilities and reference assets are included in your packaged game. A successful editor graph compile is not a packaged-game test.

Support

Contact support.blackironspine@proton.me with your Unreal version, the graph you used, what you expected and what actually happened. Include a readable full-graph screenshot where useful. Keep secrets and account credentials out of your report.