❔FAQ

Will my Custom Inspector break if I rename the class / property?

When you rename a class, next time you select a component, Vibe will try to match properties saved in the config to the selected component. If there's a match, it will automatically use that config file for the new class.

When you rename a property, Vibe will look for FormerlySerializedAsAttribute to try to match the Inspector Elements with the property's new name.

Good practice: When refactoring, don't rename the class and its properties at the same time.

Rename the class, let Unity recompile, select the component in the inspector to trigger the cleanup. Afterwards, continue refactoring the properties. Remeber to add the FormerlySerializedAsAttribute to properties you rename!

How does Vibe differ from Odin Inspector / other Custom Inspector assets?

Vibe is a visual, no-code solution. This means you can build efficient, attractive, and usable inspectors much faster, with no guesswork.

As you drag and drop different inspector elements, you'll see the changes you make in real-time, without waiting to recompile.

Because Vibe's custom inspectors are stored as separate files, you can freely share your own code without worrying about compatibility issues or breaching EULAs. This also reduces dependencies and lets you keep your code clean and concise.

When working in a multidisciplinary team, coders can now focus on writing code, while designers can easily build editor tools for themselves.

Can Vibe work alongside Odin or other Custom Inspector assets ?

See: Compatibility