Type Designer
The Type Designer simplifies the process of customizing how a given type is presented in the Unity Inspector. It does this without requiring the user to write a single line of code, instead utilizing a drag-and-drop user interface that allows for the rearrangement of fields, properties, groups, and methods within the Inspector. Changes are reflected instantly in real time.

The Type Designer offers a variety of customization options, leveraging APIs similar to Odin Drawers and other familiar APIs where possible. This enables you to further tailor the Type Designer to your team’s workflow and customize how your unique elements are represented and interacted with in the tool.

Additionally, the Type Designer supports a hybrid approach: even if a type is designed using the Designer, it will still respect any additions made in the code.

Each type designed with the Type Designer is saved in its own file within a user-specified directory. These files are human-readable, allowing for easy comparison of different versions in source control. Users can also directly edit these files for quick adjustments, providing flexibility without needing to return to the Designer.

We are currently prioritizing the development of the Type Designer. As we continue working on this tool, we will begin rolling out updates and sneak peeks on our Discord channel.

Nested Prefabs
All attributes and editor utilities will always work in nested prefabs, basic nested prefab compatibility is in release but is deprecated, and you can always use the Odin Serializer to manually serialize individual fields. However, Odin serialized data in Odin's SerializedMonoBehaviour does not support nesting of Odin-serialized prefab modifications beyond one layer of nesting and is currently a deprecated feature, and a warning is currently shown over disabled GUI for nested Odin-serialized prefab values - IE, at any time where several layers of Odin-serialized modifications might be applied.

This is not an easy problem to solve, and it is possible that there is no feasible solution. We would like to bring full nested prefab support to Odin, but we consider this a long-term project with uncertain timelines that may never pan out, as we do not currently see a viable path forward.

We are working on a completely new UI library, read more here.

Odin redistributables
For Odin to be usable in other assets released on the Asset Store, for both for ourselves and others, there are - apart from finding a good and fair financial model - numerous technical problems to solve. We are not currently working on this problem, and don't expect to release this feature for the general use case within the immediate or medium-term future.

We do provide Odin redistributables for special cases (primarily content-generation SDKs, modding frameworks and other tools not meant for general-purpose game development), but these are negotiated on a case-by-case basis to fit the individual case. Please contact us if you are interested in this.

Better package support

Currently, for various reasons, Odin installs into the Asset folder of any project. We plan on removing these roadblocks to create better support for Odin being installed as a project package.