DeadBeak.
Get in touch

DEADBEAK / INDEPENDENT GAME DEVELOPMENT

GAMES · UNITY TOOLS · CURIOSITY

A game in
the making.
Tools built
along the way.

I’m the developer behind DeadBeak. I build Unity tools to solve problems in my own game, then share them with other developers.

Explore the tools How it started
DB / INDEPENDENT BY DESIGN
FOLLOW THE CURIOSITY.KEEP BUILDING.
01 INDEPENDENT DEVELOPER02 TOOLS FROM REAL PROJECTS03 MORE IN THE MAKING

01 / TOOLS FOR UNITY

Built to answer
the next question.

Sometimes making a game means making a better way to understand it. These are the tools that grew out of that work.

UQL / REPEATABLE INVESTIGATIONS

A SMALL QUESTION. A CLEAR STARTING POINT.

// Find the data you want to understand.
SCAN → Discover
OBSERVE → Capture the state
CHECK → Compare the outcome

Ask. Inspect. Run it again.
WORKFLOW AT A GLANCE · SEE COMMANDS & EXAMPLES
IN DEVELOPMENT · PUBLIC RELEASE PLANNED

Give your questions a script.

UQL — UNIVERSAL QUERY LANGUAGE

Query your Unity project, save checks you can run again, and give your development agent a way to investigate with you.

A standalone release and inclusion in the full UDB package are planned.

Meet UQL Commands & examples

02 / GAMES

The reason
behind the tools.

There’s a game at the heart of all this. It’s still taking shape, and it hasn’t been revealed yet.

DEADBEAK / GAME PROJECT

Still
under wraps.A GAME IN THE MAKING.

IN DEVELOPMENT

Unannounced game

This is the project I’m building alongside UDB and UQL. The tools help me understand it; the game keeps giving me new questions to answer.

No title reveal just yet.
More to share when it’s ready.

It started with a problem
in my own game.

I needed to see what my game was doing. Its data had grown into a large, complicated structure, and inspecting it meant writing custom editors one after another. After building a few, I wanted a way to explore the data without making a new interface for every structure.

That led me to C# reflection, and eventually to Universal Data Browser. What began as a way to look inside my own game grew into a tool for following nested values, watching changes, and returning to the paths I needed. I decided to share it with other Unity developers facing the same problem.

I’m still building that game, alongside the tools it inspires. UQL is the next part of that work: a way to turn useful questions and checks into scripts I can run again. Different projects, connected by the same curiosity about how things work.

DeadBeakINDEPENDENT DEVELOPER · STILL BUILDING

04 / OPEN THE MANUAL

Less searching.
More understanding.

Start with a walkthrough, look up a feature, or find a command you can put to work.

UDB documentation

Search the field guide for inspection, editing, graphs, scanning, and everyday workflows.

UQL documentation

Browse commands, follow practical guides, and copy examples for your next investigation.

QUESTIONS, FEEDBACK, OR A GOOD IDEA?

There’s a person
behind these tools.

Need help or want to talk about what you’re making? Say hello.

Get in touch