Connected project · 6 minutes
Review and approve a project change
See what Aura intends to do before any reviewed project action runs.
Use this guide with Aura
Open Aura, then keep this guide beside it while you follow the steps. Aura does not receive the page text, your account, your project, or anything you typed.
If nothing opens, start Aura normally. The written steps still work.
Before you start
- A supported project is connected.
- The project is under your normal source-control or backup practice.
Plan and model funding
Planning and model reasoning use the selected funding source. Local approved file/editor actions do not create a separate Aura charge.
Say this in ordinary language
Make the player move a little faster. Show me exactly what you will change first.
Steps
-
1
Ask for one bounded change in ordinary language.
What you should see: Aura explains the intended result and prepares reviewed actions.
-
2
Read the action list, affected target, and expected outcome.
What you should see: Nothing runs while the approval is waiting.
-
3
Approve only when the list matches your request.
What you should see: Aura executes the approved actions and reports the result.
-
4
Run the game or project check that proves the change.
What you should see: The requested behavior changes and unrelated behavior remains intact.
What Aura may change
Only the files or editor objects listed in the approved action set.
How to verify it worked
Run the real game and compare the behavior before and after.
Undo or recover
Reject before execution, use Aura's rollback when offered, or restore with your source control.
Common problems
- If an action is unclear or broader than requested, cancel it.
- If execution fails, keep the error visible so the automatic support report can capture sanitized diagnostics.