Home / Projects / HITZ: Merge Tactics

Independent project, published on Fab

HITZ: Merge Tactics

A server-authoritative auto-battler framework for Unreal Engine 5.8, designed so a complete game can be built on it without writing C++.

Engine
Unreal Engine 5.8
Language
C++
Structure
3 modules and a sample game
Type
Solo project
Source
Public on GitHub
Distribution
Fab
Overview of the HITZ framework: board layouts, shop, traits, combat, 3D viewer and material painter

Overview

Merge Tactics is a complete, playable auto-battler framework: board, shop, traits, combat and the full multiplayer round loop. It is aimed at Unreal developers who want to build an auto-battler and extend it without touching C++.

My role

I designed, built, documented and published all of it myself, including the listing and the documentation site.

Main responsibilities

  • Architecture: three reusable modules (HMT_Core, HMT_CoreEditor, HMT_GASBridge) and a separate sample game.
  • Server-authoritative combat and the multiplayer round loop.
  • Four Blueprint extension interfaces and the GAS bridge.
  • Editor tooling: a click-to-paint board layout editor, a unit definition editor with live 3D preview and montage playback, and a save-time validator across seven data-asset types.

Technical challenges

  • Keep match results cheat-proof, so clients must not compute outcomes.
  • Keep the core independent of GAS while still supporting GAS projects.
  • Make every extension point usable from Blueprint.
  • Support hex and square grids from one board asset, with the grid maths separate from board state.

Implementation

The server locks board snapshots, simulates combat and replicates one compact event log, which clients replay for animation.

Merge Tactics server-authoritative combat flow On the server, board snapshots are locked, combat is simulated, an event log is built and results are applied. Clients receive the event log once and replay it visually. SERVERCLIENTS Lock board snapshotsend of prep phase Simulate combattargeting, abilities, traits Build event logcompact, ordered events Apply resultsHP, gold, pairing Receive event logreplicated once Replay visuallyanimation, VFX, UI
Clients only receive the server's event log and replay it for animation. They never compute a match outcome.

The four extension interfaces are the stat provider, the targeting strategy, the trait effect and the ability executor. The GAS bridge maps the stat interface onto an existing AttributeSet per unit, so a GAS project swaps its stat backend with no changes to any other system.

// Source/HMT_Core/Public/Units/IHMT_TargetingStrategy.h
UINTERFACE(BlueprintType, MinimalAPI)
class UHMT_TargetingStrategy : public UInterface { GENERATED_BODY() };

class HMT_CORE_API IHMT_TargetingStrategy
{
    GENERATED_BODY()
public:
    UFUNCTION(BlueprintNativeEvent, BlueprintCallable,
              Category = "HitzMergeTactics|Combat")
    AActor* SelectTarget(AActor* SelfActor,
                         const TArray<AActor*>& Candidates,
                         UHMT_CombatContext* Context);
};
// Source/HMT_Core/Public/Stats/IHMT_StatProvider.h (excerpt)
class HMT_CORE_API IHMT_StatProvider
{
    GENERATED_BODY()
public:
    UFUNCTION(BlueprintNativeEvent, BlueprintCallable)
    float GetFinalStatValue(FGameplayTag StatTag);

    UFUNCTION(BlueprintNativeEvent, BlueprintCallable)
    void ApplyStatModifier(FGameplayTag StatTag,
        EHMT_StatModOp ModOp, float Magnitude,
        EHMT_ModifierDuration Duration, ...);
};

The round loop covers prep, combat and results phases, recency-weighted pairing, ghost boards for odd lobbies, PvE rounds, spectating and late join, on standard Unreal replication.

Results

Clients never compute outcomes, which closes the cheat surface on match results. The framework drops into an existing project by copying three source folders. I have no sales or player figures to report here.

Links and media

Combat and prep phases on a hex grid
Board layout data asset and material painter in the editor
Unit definition editor with live 3D preview
Board layout options in the framework