Skip to content
BlogStart for free

Files and history

Inspect and edit project files

The project editor lets you inspect generated source and make manual changes. You need owner or editor access to save changes; viewers can inspect the project.

  1. Open the File explorer.
  2. Expand the relevant folder or use Search files.
  3. Select a file to open it in the editor.
  4. Check the path and tab name before editing.

For a plugin, start with metadata, configuration, and the class implementing your feature. For a datapack, inspect pack.mcmeta, the namespace, and the function or data file associated with the requested behavior.

Use Ctrl + F on Windows/Linux or Cmd + F on macOS while the editor is focused. Enter a command name, configuration key, permission, or other text to find its occurrences.

File-explorer search locates files by name. Editor search locates content inside the active file. If the browser’s page search opens, click inside the editor and try again.

  1. Wait for active generation to finish and resolve any pending review that affects your file.
  2. Open the file and make the change.
  3. Save using Ctrl + S or Cmd + S while the editor is focused.
  4. Wait for the save confirmation and check that the unsaved indicator clears.
  5. Build the project to package the new saved content.

After saving source, build and deploy again to test the edit in Minecraft. A running server keeps its earlier artifact.

An editor tab can contain content you have not saved. Do not assume that leaving the tab, changing projects, or starting a build preserves that content. Save first, or copy it somewhere safe if you are unsure.

Each saved file has a version. If another member or the AI changes it after you open it, Buildryn can reject your save to protect the newer content.

  1. Copy any unsaved text you need to retain.
  2. Reopen or refresh the current file.
  3. Compare your intended edit with the stored version.
  4. Apply the required change to the current content and save again.
  5. Coordinate with collaborators if both edits touch the same logic.
  1. Open the file’s actions in the explorer.
  2. Choose Rename.
  3. Enter the new base name; the existing extension is preserved by the rename control.
  4. Confirm the rename and check the new path/name in the explorer and editor.
  5. Update any code references or declarations that depend on the old name, then build.

Renaming a Java file may also require changing its public class name and references. Renaming a datapack function may require changing calls and tags. Ask Buildryn to make the related changes if you are not comfortable editing them manually.

Choose Reference in chat from the file actions, or type @ in the prompt and select the file. Explain the task, such as checking an error, updating one behavior, or comparing it with another file.

Save your manual changes first so the request uses the stored content you intended.

Open a changed file from the review list to compare its before/after content. Additions and deletions help identify the scope of generation. A diff is a comparison view; return to the normal file tab for a manual edit.

Open Markdown preview to read the rendered content. Use the editor’s download control to save a copy of the active file on your device. Downloading an individual source file is different from downloading a packaged project artifact.

Request new files or removals through a Build prompt and inspect the resulting change set. Use the file explorer to work with existing files.

For example: “Add a configuration helper and update the existing command to use it. Remove the unused old helper only if nothing references it.” Review all linked changes together.

See reviewing changes and builds for the next steps.

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