Skip to content

Getting Started

Welcome to the Quick Start Guide! In this tutorial, you will learn how to install the plugin into your project and spawn your first damage number using the built-in example assets in under 5 minutes.


Engine versionsUnreal Engine 5.5, 5.6, 5.7, 5.8
PlatformsWindows, Mac, Linux
Project typeBlueprint-only or C++
Engine pluginsNiagara (enabled automatically)

If you downloaded the plugin from FAB, follow these steps to add it to your project:

  1. Close your Unreal Engine Editor.
  2. Navigate to your project’s root folder (where your .uproject file is located).
  3. Create a new folder named Plugins (if it doesn’t already exist).
  4. Extract the downloaded MageItCombatText folder into the Plugins directory.
  5. Launch your project.
  6. In the Editor, go to Edit > Plugins, search for “MageIt Combat Text”, and ensure the checkbox is enabled.

To test the system immediately, we will use the ready-made example assets shipped with the plugin. By default, Unreal Engine hides plugin content in the Content Browser.

  1. Open the Content Drawer (Ctrl + Space).
  2. Click the Settings gear icon in the top right corner of the Content Drawer.
  3. Check the box for Show Plugin Content.
  4. In the folder tree on the left, scroll down until you find the MageItCombatText Content folder, then open Examples/Blueprints. You’ll find four ready-made renderer Blueprints:
    • BP_MCT_ExampleUMGRenderer
    • BP_MCT_ExampleUMGHealRenderer (UMG, using the WBP_MCT_AccumulatedHeal widget)
    • BP_MCT_ExampleNiagaraRenderer
    • BP_MCT_ExampleSlateRenderer
Content Browser with Show Plugin Content enabled, showing the MageIt Combat Text plugin folder and its Core/Examples/UI subfolders

🏷️ Step 3: Register a Renderer Against a GameplayTag

Section titled “🏷️ Step 3: Register a Renderer Against a GameplayTag”

Combat text is routed by FGameplayTag, so we need at least one tag and one renderer registered against it before anything can render.

  1. If your project doesn’t have any gameplay tags yet, go to Edit > Project Settings > Project > GameplayTags and add a tag, e.g. Damage.
  2. Go to Edit > Project Settings > Plugins > Combat Text.
  3. Under Renderer Registry, add a new entry:
    • Key: Damage
    • Renderer Class: BP_MCT_ExampleUMGRenderer
    • b Initialize At Begin Play: leave unchecked for this example (see Configuring Renderers for when to enable it)
Project Settings > Plugins > Combat Text showing three Renderer Registry entries — Damage.Niagara, Damage.Slate, and Damage.UMG — each mapped to a renderer Blueprint

The demo project above registers one tag per renderer (Damage.Niagara, Damage.Slate, Damage.UMG) so it can showcase all three side by side — for this guide, a single Damage entry is all you need.


Now let’s trigger the renderer from Blueprint.

  1. Open any Blueprint that has access to a PlayerController or Pawn (e.g. your character Blueprint, or Level Blueprint for a quick test).
  2. Right-click in the Event Graph and search for Get MageItCombatTextSubsystem.
  3. Drag off the return value and search for Add Damage Event.
  4. Build a Make MageItCombatTextEvent struct (or break it out as individual pins) and fill in:
    • Location: A world position, e.g. the target actor’s location plus some height offset.
    • DamageAmount: Any float, e.g. 42.0.
    • DamageTag: Damage (the tag you registered in Step 3).
    • TargetActor: (Optional) the actor the number should track, required by the UMG renderer.
  5. Wire this up to any event you like for testing — a key press, Event BeginPlay, or a custom “Take Damage” event.

  1. Hit the Play (PIE) button in the editor.
  2. Trigger the event you wired up in Step 4.
  3. You should see a damage number pop, animate, and fade near the location or actor you specified.
Play-in-editor screenshot showing stacked white damage numbers and a larger orange CRIT! callout floating above a hit target

What’s Next? Now that you know the plugin works, continue to Your First Damage Event for a full walkthrough of wiring damage from a real gameplay event, or read Configuring Renderers to understand when to reach for UMG, Niagara, or Slate. You can also explore the full Blueprint API Reference!