- Tbh sorting isn't rely needed in my book, the order of variables is controllable by changing there position in code and we can group them using '[ActionSection("A Section")]'. (in action, not Playmaker variables)
- We already have array's in actions and they act just like in unity's inspector. (try "public int[] test;") As for collections, unity inspector doesn't support collections ether and there is a good reason for that. You should avoid using them.
- And yes I mean the collapsible structure. It's not just that it looks cleaner do, it's also the fact that you can make those custom types array's and that makes it allot more flexible. (no more preset size or amount) Link below is a
small example showing how I have it in playmaker and in unity's inspector. Also note that I can change the size in unity, no way to do that in playmaker. I could have made all the variable types array's but that a big "NoNo". It would be impossible to know (100% sure) what string goes on to what key and so on.
(
Click for image)
Sorry if first post coursed some confusion, hope this one clears the air a bit.