Frequently Asked Questions
Which renderer should I use?
Section titled “Which renderer should I use?”Start with what your game needs most:
- UMG if you want to skin combat text in the Widget Designer. It uses a pre-allocated widget pool, follows the target actor, and the included accumulated damage and heal widgets merge fast hits into one number.
- Niagara SDF for high-volume genres (bullet-hell, MOBA teamfights, horde survivors). All text is drawn by one shared Niagara system from an SDF glyph atlas, and events are batched per tick.
- Pure Slate for the lowest overhead with no widget tree. It is styled through renderer properties and overridable events instead of the Widget Designer.
You can change your mind later: renderers are chosen per Gameplay Tag in Project Settings, so switching needs no gameplay code changes. See Renderer Architecture for a side-by-side comparison.
Can I use more than one renderer at the same time?
Section titled “Can I use more than one renderer at the same time?”Yes. Renderers are mapped per Gameplay Tag in Project Settings → Plugins → Combat Text, so you can route normal damage to Slate, critical hits to Niagara and heals to UMG in the same project, driven by the tag you pass to Add Damage Event.
If a tag has no entry of its own, the plugin falls back to its parent tag (Damage.Fire.Critical, then
Damage.Fire, then Damage), so a few parent tags can cover many child tags. See
Configuring Renderers.
Do I need to write C++ to use this plugin?
Section titled “Do I need to write C++ to use this plugin?”No. AddDamageEvent is BlueprintCallable, and every renderer exposes BlueprintNativeEvent
hooks you can override in a Blueprint child class:
- All renderers:
Initialize,RenderDamage,Shutdown. - Slate: text and color extraction (
ExtractCombatText,ExtractTextColor,ExtractShadowColor), drift direction and animation processing. - Niagara: sprite index, damage style and scale (
FindSpriteIndex,FindDamageStyle,FindScale). - UMG: the widget’s own
FadeIn,UpdateDamageandFadeOutevents onUMageItCombatTextWidget.
C++ is only needed if you want to extend the base renderer classes natively. The Blueprint API Reference lists every node.
Is this networked/replicated?
Section titled “Is this networked/replicated?”No. Combat text is a local, cosmetic UI effect. The plugin has no replication code: it runs in a per-player Local Player subsystem, so each client draws its own numbers.
In multiplayer, replicate the damage as you already do, then call Add Damage Event on each client that should see the number (for example from the same event that updates health or plays hit feedback).
Will this work with my existing damage/gameplay ability system (GAS, custom, etc.)?
Section titled “Will this work with my existing damage/gameplay ability system (GAS, custom, etc.)?”Yes, because the plugin doesn’t depend on any combat framework. Call Add Damage Event (Blueprint) or
UMageItCombatTextSubsystem::AddDamageEvent (C++) from wherever your damage is applied, passing a location, an
amount, a Gameplay Tag and optionally the target actor and hit result.
There is no ready-made integration for Gameplay Ability System or any other framework, so you wire the call into your
own damage or effect code. Your First Damage Event shows the pattern with
Event AnyDamage.
Does it support accumulating multiple hits into one number (e.g. rapid-fire ticks)?
Section titled “Does it support accumulating multiple hits into one number (e.g. rapid-fire ticks)?”Yes. Example accumulated-damage and accumulated-heal widgets are included (WBP_MCT_AccumulatedDamage,
WBP_MCT_AccumulatedHeal) showing the pattern for merging fast successive events into a single rolling number with
its own fade-out timer. See UMageItCombatTextWidget for how the timer works.
What platforms/engine features does this require?
Section titled “What platforms/engine features does this require?”- Engine versions: Unreal Engine 5.5 to 5.8. It also works in Blueprint-only projects.
- Supported platforms: Windows, Mac and Linux.
The plugin requires the Niagara plugin, which is enabled automatically with MageIt Combat Text. The Niagara renderer needs Niagara support on the target platform. The UMG and Slate renderers use only UMG and Slate.
Can I use my own fonts and icons instead of the demo ones?
Section titled “Can I use my own fonts and icons instead of the demo ones?”Yes. The bundled fonts (Anton, Bangers, Creepster, Luckiest Guy, Press Start 2P) and the Font Awesome SDF icon atlas are example content only, and Roboto is the engine’s default font.
- Slate: set your own font in the renderer’s Text Font property.
- UMG: use any font in your widget.
- Niagara: swap the SDF atlas texture and sprite material. See Generating the SDF Atlas.
Is this performant enough for large-scale fights?
Section titled “Is this performant enough for large-scale fights?”The plugin is built to keep per-hit work small, and each renderer does it differently:
- UMG: widgets come from a pre-allocated pool and are reused instead of created per hit. You can cap the pool size.
- Niagara SDF: events are batched per tick and every number is drawn by one shared Niagara system on the GPU.
- Slate: one canvas draws all text with no widget tree, and text measurements are cached per string.
Actual results depend on your project, so check the stress scene in the demo and profile with your own content and target hardware.
Didn’t find your answer? Contact support.