Getting Started

Install and Open

Import Azkar Console from the Unity Asset Store or your release package workflow. After Asset Store import, the product lives at Assets/Azkar Industries/Azkar Console.

Azkar Console depends on com.unity.burst and com.unity.collections. Install them from Unity Package Manager if they are not already present; the release project pins Burst 1.8.25 and Collections 2.6.2 for verification.

After the package is available, open the window from Window > Azkar Console.

First-Run Actions

When the console opens empty, use the built-in quick actions to confirm the UI is working and to start from a useful state.

• Generate demo logs shows categories, tags, aliases, traces, source details, and stack-aware diagnostics immediately.
• Start remote listener prepares the editor to receive logs from development builds.
• Import Azkar Console Database loads a saved .azrecdb session database.

Emit Your First Log

Import the public API namespace, then call AzCon from your script. Passing a Unity object as context makes the log easier to locate later.

using Azkar.Console;
using UnityEngine;

public sealed class ConsoleExample : MonoBehaviour
{
    private void Start()
    {
        AzCon.Log("Player spawned", this);
        AzCon.Debug("Spawn debug details");
        AzCon.LogWarning("Health below threshold", AzCon.Category.Gameplay);
        AzCon.LogError("Spawn failed");
    }
}

Run Play Mode and inspect the rows in Azkar Console.

First Useful Pass

1. Enter Play Mode and reproduce the behavior you want to inspect.
2. Use severity controls or search to narrow the live view.
3. Expand a row to inspect details, callsite or stack information, source preview, and metadata.
4. Bookmark important rows so they stay easy to revisit.
5. Export filtered logs for a focused handoff, or export all logs when the surrounding session context matters.
6. Use .azrecdb when someone should import and inspect the same session inside Azkar Console.

Migrate From Unity Debug

You can use Azkar Console alongside Unity logs, then migrate high-value calls first.

// Before
Debug.LogWarning("Relay RTT spike detected", this);

// After
AzCon.LogWarning("Relay RTT spike detected", AzCon.Category.Network);

Add metadata where it helps filtering and review.

private static readonly LogTagEntry MultiplayerTag = AzCon.Tag.Create("Multiplayer");

var options = new LogOptions(
    category: AzCon.Category.Network,
    tags: AzCon.Tags(MultiplayerTag),
    header: AzCon.Header.Network,
    context: this);

AzCon.LogWarning("Relay RTT spike detected", in options);