Connect Argus to an Existing Combat AI

The connection pattern

1. Keep your combat controller on the same guard prefab.
2. Implement IArgusGuardReactions on a small bridge component beside ArgusGuard.
3. Enable the combat controller on OnEnterCombat and disable it on OnExitCombat.
4. Use the other callbacks for barks, animation triggers, search presentation, or mission logic.

Minimal adapter

using UnityEngine;
using Argus.Actors;

public sealed class ExistingCombatBridge : MonoBehaviour, IArgusGuardReactions
{
    [SerializeField] private Behaviour combatController;

    private void Awake()
    {
        if (combatController != null) combatController.enabled = false;
    }

    public void OnEnterCombat()
    {
        if (combatController != null) combatController.enabled = true;
    }

    public void OnExitCombat()
    {
        if (combatController != null) combatController.enabled = false;
    }

    public void OnAlerted() { }
    public void OnReachedLastKnown() { }
    public void OnStartedSearching() { }
    public void OnReturnedToPatrol() { }
}

Why this seam stays stable

ArgusGuard discovers IArgusGuardReactions components on the same GameObject and invokes them alongside its inspector UnityEvents. There is no package edit and no hard reference from Argus to your controller.

If your project does not use ArgusGuard, subscribe directly to StealthAgent.LadderChanged or FsmStateChanged. The observer contract stays the same: Argus publishes what the enemy knows, and your code chooses the reaction.