⚠️Limitations

Better Delete improves project cleanup, but it has some limitations you should understand.

1️⃣ Dynamic Script References Are Not Detected

The Dependency Map tracks assets referenced through Unity’s standard asset system.

However, it cannot detect assets that are:

• Loaded via Resources.Load

• Loaded using Addressables at runtime

• Instantiated dynamically through script paths

• Referenced by string-based loading

These assets may not appear in the map, even if they are used in your final build.

Always double-check assets that are loaded dynamically.

2️⃣ Deleted Assets Go to Trash

When you delete assets using Better Delete:

• Files are moved to your system’s Trash / Recycle Bin

• You can usually recover them from there

However:

• It is always recommended to backup your project

• Use version control if possible (Git, Plastic, etc.)

• Be extra careful in production projects

🔒 Important Reminder

Better Delete helps automate cleanup, but final responsibility remains with the user.

Always review what you are deleting before confirming.