Purchased and on the face of it, I want to say congratulations, looks quite useful and could have been very close to a 5 star review. Alas: Unfortunately, I do regret my purchase as three things made it abandon this asset already in v2019.2.12: - While I could appreciate the inspector enhancement, which did look great, for a while, I had issues with some objects with inspector UI becoming completely corrupted (fixed by removing the asset) - probably has something to do with unfolding fields in the inspector holding custom type list fields - Had an unfortunate severe unity crash with advanced inspector and another asset (ES3), both seemingly interacting negatively combined with serialization process on unity launch that could not recover - lead to two weeks of trying to recover the project with a serialization nightmare. It is possible that an edge case with our project or bad luck was at play, so I do not want to fault this asset with 100% certainty. But remains that removing it did get rid of the problem, which is enough suspicion on my end to step away. - lastly, last release was early 2018... Dashes any hope to dive/invest into the asset. With a heavy heart then as I can see how this asset was cleverly made and its very good potential, perhaps for others in the past, I do regret this purchase and had to write my first ever 1-star review.

It's a great asset but if you are not comfortable fixing some minors bugs that cause errors then I would suggest buying something else. This asset is obviously not supported anymore... I'm using 2019.2.0f1 ... I would have passed if I knew that there were so many errors...

This asset is hugely usefull, I often write Editor scripts when some of my vars are not serialized or when I want to call some specific actions, but it's not necessary anymore ! The documentation is clear. I just had an error with String that has no Constructor that I had to correct in the Advanced Inspector's classes. (2019.1.11)

Really well done. Painless install and immediately noticeable improvements. Better array/list editing is an obvious one but for me the ability to dive into object references and edit them directly inline is what really makes Advanced Inspector an amazing tool. (Using it in 2019.1.3f; no issues)

[Inspect] your function and you have a button on inspector to call that function immediately. Absolutely great for debugging. Various kind of features such as ReadOnly and reorder array/list. Purely awesomeness. However, would like this issue fixed: Those classes that have CustomPropertyDrawer is still drawn by Advanced Inspector (and often does not do what they were supposed to do). Please do not draw by AI for preference "Inspect Default Items" for those with CustomEditor as well as CustomPropertyDrawer.

I absolutely love this! As a programmer, this is just as much effective for me as it is my artist. I will use A.I. in every project I do in Unity!

I REALLY loved this asset and have been using it for the past couple of years. Most of my projects depend on it and I couldn't live without it. Unfortunately, since the last release was in August 2017 (I'm writing this in March 2018), and there are millions of warnings and errors that start to sneak in all over the place, I have come to the conclusion that the developer has abandoned the asset and does not plan to support it any longer. If this would get updated to work with current Unity versions, I would be really glad.

I have worked with this asset since 2015 and I can not imagine working in Unity without it! I have a lot of reusable components of my own that rely on this asset. I hope the publisher continue to update it in the long term :) I want to mention some big advantages in my own workflow: -Reorderable arrays. -Methods can be called in edit mode with buttons. -Inspectable getters and setters (that also can make changes in edit mode). -Polymorphic lists are serialized correctly. -Display options, like colors, different array modes and many other options makes the inspectors so readable and usable for game designers. -Very easy to implement help messages that depend on the state of the components. I just found an issue and would like the publisher to guide me in the process of solving it. I have a MonoBehaviour with a long list of ComponentMonoBehaviour instances with many properties assigned in them (the list has the [CreateDerived] attribute). I want to change the name of the class that I derived from ComponentMonoBehaviour (currently called "GameStateStation") to other name. When I refactor the code and make this change, all the items in the list of the parent MonoBehaviour (the owner) are lost in the inspector and I haven't found a way to recover them. This is a great loss of serialized data that I don't want to have. I have seen that the have the hideFlags property is set to HideFlags.HideInInspector, but I haven't figured out the way to make them visible in the inspector again in order to keep them as normal MonoBehaviours nor I'm sure if this is the solution. Otherwise this component is a must have! Any guidance in this regard would be greatly appreciated!!! Thanks, Juan P.

I'm not programmer, so it is too complicated for me to write CustomInspector script. This realy provides very easy ways to build a good inspector display.

Very fast answer at the forums. Great plugin.