Create a clean test instance

Change one variable and preserve the evidence

Use clean profiles to test mods, shaders, packs, and worlds without wrecking your main setup. Troubleshooting works best when the first useful error, exact file names, loader version, and last change are kept intact. Random deletion can hide the cause and make help harder.

Use this guide when the goal is create a clean test instance. Work from a copy or clean instance when the task can affect saves, configs, servers, or account settings.

What to verify first

Before starting, write down the target Minecraft version, loader or platform, and the folder or account area this task changes. That small note makes rollback and support requests much easier.

Reproduce the issue in a clean instance or backup copy, then confirm the fix by reversing only the suspected cause.

How to know you are finished

For create a clean test instance, the work is not finished when a file is merely downloaded. Treat it as finished when you can point to the setup you changed, explain why it matches the intended Minecraft version or platform, and repeat the result in a clean test or copied world.

Use the checklist as the exit test: you know your minecraft version, you are using the correct loader or platform, important worlds are backed up. If one of those checks is still uncertain, stop and verify that detail before moving to a main world, public server, or shared pack.

If the first failure you hit is "Minecraft crashes after the change", start with this fix: Remove the last file you added, relaunch once, then check the latest.log or crash report for the missing dependency or wrong loader. This keeps recovery tied to the guide instead of turning into unrelated guesswork.