Skip to content
BlogStart for free

Files and history

Review generated changes

Buildryn applies generated changes before showing the review controls. Inspect the changed files, then keep the result or undo it to restore the affected content.

Wait for the run to finish. Read its response and note the requested behavior, assumptions, new configuration, and any errors. Save or discard unsaved manual edits before a review action that changes those files.

Owners and editors can review; viewers cannot resolve changes. If the interface says it is waiting for review, coordinate with an authorized member rather than starting a competing edit.

  1. Expand Total changes beneath the generated result.
  2. Check the list of affected files and addition/deletion counts.
  3. Select each relevant file to open its diff.
  4. Compare the previous and current content.
  5. Check the complete behavior, including metadata and configuration that accompany the source.

New files appear as additions and removed files as deletions. For a large change, check whether Buildryn also changed content unrelated to your request.

Question What to inspect
Is the trigger correct? Command, event, function, recipe, or other entry point.
Are access rules correct? Permissions, player-only handling, and administrator restrictions.
Are names consistent? Source identifiers, metadata declarations, function paths, and configuration keys.
Are failure paths defined? Invalid input, missing dependency, full inventory, unavailable world, or absent configuration.
Is stored data preserved? Existing data format and restart behavior.
Is the version correct? Target APIs and version-specific datapack layout.
Can I test it? Concrete commands and observable expected results.
  1. Finish inspecting the related changes.
  2. Choose Keep all.
  3. Wait for confirmation and for the review banner to resolve.
  4. Build and test the resulting source.
  1. Confirm that you want to restore the files affected by this generated change set.
  2. Copy any current content you need to keep.
  3. Choose Undo all.
  4. Wait for restoration and check the affected files.
  5. Plan another approach or submit a revised request.

Undoing a generated result changes project files. It does not refund already performed AI work or replace an artifact already running on a server.

The review interface presents the feature as a whole. If part of a result needs correction, you can keep the changes and request that correction after review. Avoid removing one linked file while leaving command declarations or other references inconsistent.

Buildryn can reject a review decision if someone changes the affected files or change set after you load it.

  1. Stop making additional edits to the affected paths.
  2. Save or copy your unsaved work.
  3. Reload the current review and inspect the latest source.
  4. Coordinate with the member who changed the project, if applicable.
  5. Resolve the current review or choose the appropriate historical recovery action.

Check the latest files before retrying a review decision. Buildryn rejects decisions based on an older revision to protect newer content.

If the composer is disabled because review is pending, resolve that review first. Check the files you kept or restored before submitting the next request.

For a later rollback, see history and recovery. To inspect compilation or packaging, see build and download.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.