UQL.BY DEADBEAK
Release plans

UNIVERSAL QUERY LANGUAGE / UNITY

Ask your project.
Get evidence back.

Explore your game’s data. Save checks you can run again.
Use UQL directly or connect your development agent to Unity.

Explore the workflows Read the documentation
ONE LANGUAGE, CONNECTED WORKFLOWSExploreCheckTraceReview

01 / FROM A QUESTION TO A WORKFLOW

Write it once.
Run it again.

See how a few commands can help you find a value, check a change, or follow its history.

WORKFLOW NOTEBOOKIllustrative examples
SCAN / DISCOVERYUQL
BUCKET $hits; VALUE $report = null;
SCAN FIELD health IN SCENE INTO $hits REPORT $report;
RECORD $report.Text; REGISTER health_scan;

Command excerpt. Assumes a field named health exists; no matches is a valid result. Scan limits can leave partial coverage.

WHAT THIS WORKFLOW DOES

Start with the field. Keep the report.

Search the loaded scene for health fields and retain a report of what was found. Follow a result into the values that matter.

  1. 01
    Choose the scope

    Search a scene, object, or supported static scope.

  2. 02
    Inspect the matches

    Review discovered paths and the report’s coverage.

  3. 03
    Keep useful evidence

    Save the report for the next step in your investigation.

OBSERVE / CHECKUQL
VALUE $before = null; VALUE $after = null; VALUE $check = null;
BLOCK Test {
    OBSERVE FIELDS hp = $boss.health INTO $before PHASE Before;
    CALL PerformAction;
    OBSERVE FIELDS hp = $boss.health INTO $after PHASE After;
    CHECK health_changed: $after["hp"] != $before["hp"] INTO $check;
}

Script excerpt. The surrounding script supplies $boss and a PerformAction block. CHECK reports an outcome; it does not stop the process automatically.

WHAT THIS WORKFLOW DOES

Capture before. Compare after.

Freeze selected values at two points in a workflow, then check what changed. Get a Pass, Fail, or Inconclusive outcome that can be reviewed.

  1. 01
    Observe selected values

    Freeze the fields relevant to this question.

  2. 02
    Perform the action

    Run the action you defined in your script.

  3. 03
    Read the check outcome

    A completed run alone does not mean the check passed.

TRACE / MANUAL SAMPLEUQL
UQLSCRIPT PositionEvidence;
ALIAS $character = [SCENE:Character];
TRACEOPT manual = true;
VALUE $positionTrace = null;
BLOCK Begin {
    TRACE $character.transform.position INTO $positionTrace;
    UPDATE TRACE $positionTrace PHASE BeforeMovement;
}

Assumes an object named Character. Run Begin in the UQL host. This example samples once; it does not move the object or schedule movement.

WHAT THIS WORKFLOW DOES

Record a value at the point you choose.

Trace a scene object’s position, then take an explicit sample at a named point. Add later samples to compare changes through the same captured path.

  1. 01
    Bind the target

    Use a path rooted in the intended scene object.

  2. 02
    Sample explicitly

    Manual TRACE records at your chosen execution points.

  3. 03
    Follow the history

    Changes between samples can still be missed.

Documentation-based examples · Development previewThese snippets do not execute on this website.

02 / BUILT AROUND THE INVESTIGATION

Find. Test.
Understand.

Find the data behind a bug, try a change, and keep the checks that help you catch it next time.

01 / DISCOVER

Find the right starting point.

Look up scene objects, inspect members, scan data, and narrow the target before making a change.

SELECT · SCAN · METHODS
02 / REPEAT

Keep the useful check.

Save a question as a script with named blocks. Capture selected values before and after an action, then compare them.

BLOCK · OBSERVE · CHECK
03 / FOLLOW

Give changes context.

Record selected value changes with TRACE. Take explicit samples at meaningful points, including supported hook workflows.

TRACE · UPDATE TRACE · HOOK
04 / CONNECT

Give your agent a way in.

Connect a compatible development agent through the local MCP integration. It can find your Unity host, look up commands, run scripts, and read the results.

LOCAL MCP · UNITY HOST
05 / CONTROL

Choose what may run.

Choose which scripts can run, edit values, capture images, or use events. Review the permissions before running a workflow.

PER-SOURCE GRANTS
06 / REVIEW

Keep a record of the results.

Collect logs, named reports, and supported PNG captures alongside your checks. Review the outcome and the limits of its evidence.

LOG · REGISTER · CAPTURE

03 / WORK WITH YOUR AGENT

A shared workflow
for you and your agent.

Choose what to investigate, define the steps in UQL, and review the results with your agent.

Explore the guides and commands
01Choose the Unity host

Confirm the intended project and a ready session.

02Discover, then run

Use the host’s help and the grants needed by the workflow.

03Read the evidence

Inspect reports and check outcomes, not just completion.

Requires a local UQL host and MCP setup. No Unity project is connected to this website.

04 / A FIRST WORKFLOW

Start small.
Make it explicit.

Your first workflow in four steps. For command details and more examples, open the UQL documentation ↗.

  1. 01

    Choose an entry point.

    Use UQL’s Editor tools for interactive work, or a connected local agent through MCP. Confirm the project and session before running a command.

  2. 02

    Discover the target.

    Read command help, then locate the object and member you actually need. Start with a small search, then expand it if you need more detail.

  3. 03

    Save and run the workflow.

    Put repeatable work in a .uql script with named BLOCK entry points. Enable the required grants, compile the group, and run the intended block.

  4. 04

    Read the result.

    Review logs, reports, and each check’s Pass, Fail, or Inconclusive outcome. Close permissions that are no longer needed.

A few useful boundaries.

Observations freeze selected values, not a whole object graph. Traces can miss changes between samples. Reading getters may execute code, and grants are operational controls rather than a security sandbox. Writes are not automatically rolled back.

05 / TWO TOOLS. ONE CONNECTED WORKFLOW.

Choose how you
want to work.

UDB gives you the visual browser. UQL gives you queries and repeatable workflows.

UQL.Standalone · Planned

The query workflow,
on its own.

For developers who want scripted investigation, reusable checks, and an agent connection to Unity.

  • UQL query and workflow tools
  • Repeatable observations and checks
  • Local agent workflows through MCP
Ask about UQL Release date and pricing are not announced.
UDB + UQLFull package · Planned

Visual exploration.
Repeatable execution.

Move between UDB’s visual inspection and UQL’s explicit workflows as the investigation changes.

  • UDB’s visual browser and advanced tools
  • UQL planned for a future full-package update
  • One connected family of Unity tools
Explore Universal Data Browser The current Asset Store package contains UDB. UQL is not included yet.

A FEW USEFUL DETAILS

Before you
try the workflow.

Ask DeadBeak
Can I download UQL now?

This page is a development preview. UQL’s standalone release and its inclusion in the full UDB package are planned; download and purchase links will be added when available.

Do I need UDB or an AI agent?

UQL is designed to work independently and is planned as a standalone product. An AI agent is optional: UQL also provides Editor workflows for direct use. Agent integration requires a compatible MCP client and a connected local host.

Are the examples running against my project?

No. These are documentation-based examples, shown to explain the workflow. This website has no connection to your Unity project. Replace example targets and supply the required script context in your own UQL host.

Does “Completed” mean my test passed?

No. It means the process finished. Read the individual CHECK outcomes and their reasons; a workflow can complete with a failed or inconclusive check.

FROM A QUESTION TO EVIDENCE.

Give the next
investigation a script.

Explore the examples Prefer a visual browser? Meet UDB