all in title

all in title

Being able to set variables that would normally be hidden to [ShowInInspector], or setting them to [ReadOnly] among other very handy settings alone makes this worth the purchase. I could gush for pages about how this has improved my workflows in ways I did not foresee when I tried this asset out, so i'll just leave a little criticism. 1. I wish it was a bit easier to just get some basic horizontally aligned variables on the same line. Bools have really poorly set default values when it comes to trying to get various inspector loadouts to stack horizontally. 2. Most the examples were edge cases to show off top tier features for big buttons and flashy boxes and stuff. Some examples just showing off bare bones use cases to optimize basic inspector loadouts with some horizontal colums and some clever showIfGruop combined with enum bool checks for hiding away large swathes of your variables at a time would have been really nice to have to learn from. 3. It nukes the bare bones formatting a lot of the time. Headers don't play well with various other features, and the new header functions don't always work well either, they get cut off and the stacking of the variables goes haywire. Kind of a bummer when you spend a long time to get all the variables all set up and clean and tidy and you can't figure out how to get headers in to further organize your inspector. 4. Once you get to using several of the features you end up with huge bracket statements at the start of many of your variables and it gets really messy working with everything. I'd use more of the features but once you start having to create groups and set the proper hidegruopting\groupname\ and organize everything time and again it ends up being more trouble than it's worth just for a bit of variable organization. It would be nice if assigning the "showIf", "hideIf" stuff only have to be declared once, and if we didn't have to create groups and box groups for the nicest GUI features with this bit of code: [ShowIfGroup("NpcTests")] [BoxGroup("NpcTests/NPC")] [HorizontalGroup("NpcTests/NPC/Horizontal")] Like if we just had to say "[horizontalBoxGroup/1, showif "NpcTests"] for a few variables and it auto did the rest

Save a lot of time and make data manage more easier.

No Odin Inspector, No game! No powerful and beautiful editor, No work efficiency and more. It gave me life ! :)

We've tried 4+ inspector assets and this is the best. Most asset just collect every C# type and attributes at the domain reload, but Odin seems to have a mechanism that collect types asynchronosly. Which is difficult to implement, worth more than the price. I am glad this asset exists and thanks for making it.

I can't live without this tool. The single best tool on the asset store.

The best asset to make your own tools. Easy to use, a huge amount of videos and documents to help you learn the attributes. I'm blown away by the quality of this asset.

After 4 years of using this asset, in many different projects, it seems to have diminishing value. The serialization problems cause too much data corruption, are many errors. I used it mainly for Dictionaries, but it's not safe to use. Usage of SerializedMonoBehavour's should be avoided whenever possible. This asset would be a 5/5 if it was stable, but it has caused too much damage over the years. Serialized fields randomly change with no warning exclusively on Odin Serialized game objects, and things in the game start breaking. The concept of custom editors is practical, but all is lost when I am not sure whether the data will randomly change or not. Use vanilla serialization and version control whenever possible if you want to keep your data for large projects.

Awesome set of different tools to make life easier p.s. Thank you for not releasing new packages every year asking for a new purchase each time