I bought this way back in 2017. I am not experiencing the slowdown and errors that the others are experiencing, even on a project in Unity 2023.3. Unlike Rainbow Hierarchy 2, this has the advantage of not needing an extra GameObject in the scene, and it works in Prefab Mode. It also has a handy button to quickly lock any GameObject (turns the Inspector read-only for that GameObject), useful when you make a GameObject that you don't want other people in your team to accidentally edit. When debugging, it has this feature that shows error icons on GameObjects that logged any warning/error messages, and the tooltip shows the actual message and stack trace. No other hierarchy plugin I've tried has those features in the same price range. My only actual complaint is that the settings are saved in EditorPrefs, which means I can't share my settings with others working on the same project. Compare that to other plugins that save its settings into the project folder instead (so it could actually be included in version control).

The page states that it supports 2023, but that is misleading. Yes it does change the hierarchy, but you will face several DrawTexture errors and warnings popping non-stop. I'm almost sure the same happens with 2022. Furthermore, it will noticeably affect the Editor's performance.

These are really good features, and I think it really does improve the Hierarchy a lot. Unfortunately, when this asset is in a project, I see a major dip in game performance. This can be as much as halving my game's FPS due to the editor calls this asset makes. This basically makes the addon unusable for me, as I would like to keep a close eye on game performance, and having an outside variable like that really gets in the way.

Seriously. It makes the inspector easier to read, having enable/disable buttons and lock buttons is great (and standard with most other creative software), and being able to see tags and layers has helped me debug more than once. Totally worth the $15. Bring yourself joy - add it to your cart.

Very good tool, tons of options, very well presented. Works really well with rainbow hierarchy to enable custom icons.

Enhanced Hierarchy 2.0 has almost all what I need except: 1. Option to add custom object colour tint highlight and icons to game objects 2. Option to change tint colour if you pick an object from Scene (at the moment Unity selects tint from scene is very bad visible! in hierarchy…) Looking forward to the next update with those 2 things added because then it will become Unity Hierarchy Holy Grail!!!

I would have like to add my own icons to gameobjects so that I can easily identify them. The closest thing to this is adding my gameobjects to a layer and giving it a color. Also I feel like adjusting the font size should be a standard feature. It's really not a bad tool. I just don't see it being worth the $15 I paid for it. Maybe $5 or max $10.

The asset definitely holds up to its promises, but pretty much the same functionality can be achieved using free assets, so i don't really see a reason to spend money for this now. I switched to an open source variant some time ago since i can customize it

I've bought this asset last week and love it ever since I installed it in my project. Definitely helps with the visual appearance of the hierarchy to make it easier to identify separate items. It has a little script-popout window in the hierarchy which can be very helpful if you want to glance over a gameobjects properties fast. The error/warning icon turns out helpful when identifying scripts that have problems. Ofcourse you can also just read what's in the console, but this definitely speeds up the workflow. You can re-color all the labels, which is nice if you're like me and just like certain color palettes. The color-background can only be a faded one from one side to the other. Would be great if there was also an option to just make it semi-transparant but without a gradient over the line. Very nice asset overall, definitely recommend. Maybe some of the features of this asset should be included in unity in the first place. But until then, this will do :)

It is not that big of an issue, but can it be changed to be imported in the packages folder instead of the assets folder? Since it is not part of the project I'm working on and is not ment to be added in scene it could fit better in the packages folder