A Safer, Faster, and More Intuitive Way to Build

GameCatalyst is built around three core principles: safety, speed, and intuition.

Safety:

• Dry-run mode by default — All file write operations simulate changes first. You see what would happen before it happens.
• Protected paths — Critical directories (.git, Library, Temp, Logs) are permanently shielded from AI access.
• Permission gates — You control which commands the AI can use. Disable dangerous operations entirely if you want.
• Plan approval — For multi-step operations, the AI presents a full plan and waits for your approval before executing.
• Verification gates — The AI verifies each step before moving to the next, catching errors early.

Speed:

• Batch operations — Create 50 scripts in one recompile cycle instead of 50 separate recompiles.
• Recompile-resistant architecture — When Unity recompiles, your AI session stays active. No lost context.
• Structured commands — Commands execute in milliseconds with validated parameters.
• Workspace intelligence — AI uses workspace.find and workspace.index to locate files instantly instead of guessing paths.

Intuition:

• Natural language — You talk to the AI normally. No special syntax or command memorization.
• Self-healing errors — When the AI uses a command incorrectly, GameCatalyst automatically provides the correct usage. The AI self-corrects without your intervention.
• Guided onboarding — Vex introduces itself and explains how to work together effectively.
• Built-in documentation — The WhatIs system provides instant command reference for both you and the AI.

GameCatalyst makes AI assistance practical, not just theoretical. It’s designed for real game development workflows, not demos.

Safety in practice:

Here is what safety looks like during a real session. You ask Vex to reorganize your Scripts folder. Vex first calls workspace.find to discover the current folder structure. Then it creates a plan showing every file that would be moved and where. If plan approval is enabled, Vex waits for your okay before touching anything. Each file move defaults to dry-run mode, so you see what would happen first. Only after you confirm does Vex execute the moves for real. At every step, you have visibility and control.

Speed in practice:

Creating 10 scripts normally triggers 10 separate Unity recompilations — potentially 2-3 minutes of waiting. With batch operations, Vex freezes recompilation, creates all 10 scripts, then triggers one single recompile. Total wait time: a few seconds instead of minutes. This speed advantage grows with project size.

Intuition in practice:

You say “make the player bounce higher” and Vex knows to find the player object, locate the jump force variable in the movement script, increase its value, and report what was changed. You do not need to specify which component, which property, or what value. Vex understands your intent and translates it into precise technical actions.