Generating and Applying Code
Export
Use /gen for a concrete implementation request. Name the product, object type, expected behavior, dependencies, and what should happen when a reference is missing or the work is interrupted.
/gen Create a GameObject Action for Behavior Designer Pro that calls DoorController.Open. Use the existing DoorController API, fail when the reference is missing, and do not control character movement.
Attach the existing API when Atlas needs to call your code. Atlas prefers existing built-ins and project APIs; a request may produce an explanation that an existing object already does the job.
Review the result
Check the source, target product, class and file names, lifecycle methods, references, and output destination. Structural validation happens before the preview, while Unity compilation happens after a file is saved. Neither check verifies the complete gameplay behavior.
| Action | Use it to |
|---|---|
| Apply or the file’s save action | Write the reviewed result to its intended destination, following the current access policy |
| Save as… | Choose a different project filename or destination |
| Copy | Copy source for manual use |
| Discard | Dismiss a proposed result; this is not an undo of an already saved file |
| Apply all | Apply a complete multi-file result after reviewing its destinations |
Save generated C# under Assets/.... Do not target installed package or Opsive vendor source. For a modification, Atlas maps the result back to the selected original source path. A plan build instead asks for a package root and preserves its planned subfolders.
File-access settings
Open Settings > Access, or type /access:
| Setting | Confirmation behavior |
|---|---|
| Ask for approval | Confirm every file write |
| Approve for me | Confirm overwrites of existing files |
| Full access | Apply supported file actions without confirmation |
These choices control confirmation for generated files and preserve destination validation. They are separate from Allow Unity scene edits on explicit requests, which controls bounded scene tools for local Codex. See Optional scene editing. Start with Ask for approval while learning the file workflow.
Compilation and correction
After saving, wait for Unity to compile. If a generated file fails, Atlas collects the real compiler diagnostics and can offer correction. Under the approval policy it asks before starting a correction request. Correction consumes provider resources just like other generation work, and automatic attempts are bounded.
Review the corrected result and the original diagnostic. If an unrelated project error is the cause, fix that error rather than repeatedly regenerating the task. If compilation succeeds, test required assignments, success/failure paths, interruption, and cleanup in Play Mode.
See Modify, review, and test, Planning, and the relevant product guide for the next step.