Inspector Visibility Tool

Analyzing Unity inspector visibility patterns is a common source of editor confusion and serialization mistakes. This tool targets Unity developers who want consistent in-editor behavior across projects. By analyzing fields and attributes, it identifies when a field is hidden or shown due to attributes such as [HideInInspector], SerializeField usage, or custom property drawers. It focuses on patterns that developers frequently struggle with, offering concrete, code-first guidance rather than UI tweaks. The analysis is heuristic and respects Unity version differences to avoid suggesting incompatible approaches.
Conceptually, the tool treats visibility as a domain rule: if a field is serialized but not shown, ensure a clear reason, such as a private backing field with a public property, or replace with a dedicated drawer. For each detected pattern, it outputs a concise rationale, a recommended approach (for example, replacing direct field visibility with a custom PropertyDrawer or ShowIf-like attribute), and a ready-to-use snippet. It can also flag ambiguous cases where runtime reflection or plugin behavior could alter visibility, guiding the developer to review before committing.
Use cases include simplifying inspector UIs for large data models, preparing assets for QA, and reducing inconsistency in team projects. The tool's unique value lies in domain-aware recommendations that reflect Unity's serialization rules and common editor extensions. It differentiates between standard Unity attributes and third-party patterns, helping teams adopt maintainable patterns quickly.