Full error

Assets/Alensia/Core/Locomotion/AnimatedLocomotion.cs(14,46): error CS1644: Feature `expression bodied members' cannot be used because it is not part of the C# 4.0 language specification

One of many errored lines.

        public bool UseRootMotionForRotation => _settings.UseRootMotionForRotation;

How do I make it work with Unity? Can we have How to install/run section in readme.md please.

Currently, all UI resources like themes, icons, or component prefabs reside in a Resources folder, which is considered a discouraged practice by Unity.

We should consider moving them to other locations like an AssetBundle, for instance.

With prototype UI and UMA integration API in place, now we can start implementing necessary features to create and customize characters, with which we can also create a demo scene, similar to what is provided by UMA package.

It's also advisable to make the API as generic as possible, so that we can integrate with other character systems, like Morph3D's, for instance.

Adding a UI component from the editor menu sometimes creates a clone in the root object hierarchy.

IEditorSettings should provide a method to validate its status, which can be invoked from an installer that contains the settings.

Even though Signal supports UniRx by default, it proved to be quite cumbersome to declare them as dependencies, especially when there are more than one instances that use them as events.

So, it seems to be better to provide a unified method for handling events based on UniRx.

Currently, there's a noticeable delay before the main menu shows up for the first time. We need to profile the process to see if there's potential bottleneck and remove the overhead.

In some cases, such methods that perform crucial functionalities (i.e. releasing a resource) are marked as virtual, making extending classes susceptible to introduce unexpected errors.

We need to review such cases, so to make it sure all the classes are extensible without being fragile from such changes.

We need an API documentation, at least for all the major interfaces.

Add TabPanel UI component, to be used in implementing the inventory window(#16).

Even though we already have a prototype implementation for an API wrapper around IMGUI, its future seems to be unclear as it's been superseded by the new, game object based uGUI, which also might be a better choice for building in-game UI elements.

So, we need a new API layer for uGUI, which would provide a tight integration with other parts of the platform.

The current requirements and planned features are:

• It should supports top level windows (popups, draggable windows, and etc).
• UI elements should be skinnable.
• Interactive elements should expose Rx/Signal based events.
• It should provide a streamlined workflow, using both Zenject and prefabs.
• It should be easy to compose more complex components (i.e. tabbed panel) from smaller ones.

We need a set of API that deals with managing inventory, and equippable items. Converting a few standard UMA wardrobes into equippable items could be a good place to start.

As always, the API should not directly rely on, or assume any UMA specific features to function

Write a custom property drawer or an editor for array/list types that can rearrange/insert/delete items. Currently, items in style definition assets are automatically sorted on update to workaround (i.e. rename an item to the last and resize the list to delete it) this limitation, but it's unintuitive and error prone.

Consider using ReorderableList to implement this feature:

• http://va.lent.in/unity-make-your-lists-functional-with-reorderablelist/

We need a common API to handle interactions with in-game objects, like opening a door or picking up an object.

For starters, it might be possible to generalize the existing IHighlightable and IInteratable API so that it can also be used with 3D game objects.

We can use them to implement a prototype interaction API that tracks nearby objects in camera viewport and hightlight them and show proper labels.

Even when the Play Animation option is toggled off, the character moves when adjusting a morph slider.

To make it easier to compose and reuse installer components, we need to replace the current monolithic scene installer class into smaller parts.

This way, it might even be possible to provide ready to use installers as prefabs for commonly used features.

Pressing Reset button resets camera rotation and distance to the character in UMA demo scene, but it does not take into account different default distance of each focus targets, like head, chest, and so on.