Script Filtering

The Script Filter is a dedicated popup window that lets you precisely control which scripts appear inside the main Debug Filter view. Instead of scanning and displaying every file in your project, you can selectively include or hide entire folders, systems, or script groups creating a focused workspace for debugging only the parts of your project that matter.

When you open the Settings Menu (⋮) in the Debug Filter window and choose Script Filter, a new popup appears showing a hierarchical folder tree that mirrors your project’s structure under Assets/ (and optionally Packages/). Each folder and script displays small counters for how many Log, Warning, and Error calls they contain.

From here you can:

• ✅ Toggle visibility for any script or folder to include/exclude its debug lines from the main view.

• 🧩 Collapse or expand folders to manage large projects more easily.

• ⚡ Apply instantly any change is saved immediately and reflected in the main Debug Filter window without reloading.

• 💾 Persist your setup hidden or shown scripts are remembered between sessions and stored automatically in persistent EditorPrefs data.

This makes Script Filter especially useful for large or modular projects where debugging everything at once would be overwhelming. You can isolate a single gameplay system, UI module, or manager folder and review just the relevant logs keeping your debugging workflow clean, fast, and highly focused.

💡 Tip: Combine Script Filter with the Search menu and Log Type filters (Log / Warning / Error / Assert) for an even more targeted workflow.