MoveExplanation

Remarks

⚠ "Why did it pick that clip" is otherwise unanswerable, and that is the single most valuable thing in the move set editor. A scored query is a good design and an opaque one: an author looking at the wrong animation has no way back from the result to the reason without this, and the alternative they reach for is a pairwise table they can read.

Fields and properties (7)

• public MoveKey Key

  Which move.

• public string Name

  What it is called.

• public bool Eligible

  Whether it passed the required facets.

• public Facet Missing

  The first required facet it does not say, when it did not.

• public float Score

  What it scored.

• public IReadOnlyList<ScoreTerm> Terms

  Every term that made up that score.

• public float PlaybackRate

  What it would have been retimed to.

Methods (2)

• public MoveExplanation(MoveKey Key, string Name, bool Eligible, Facet Missing, float Score, IReadOnlyList<ScoreTerm> Terms, float PlaybackRate)

  Why one move scored what it did, and whether it was eligible at all.

• public override string ToString()

  Returns the fully qualified type name of this instance.

Used by (4)

• AuthoringTestsVixen.Animation.Tests
• MoveExplanationsVixen.Animation
• MoveSetTestsVixen.Editor.AssetEditors.Tests
• MoveSetViewVixen.Editor.AssetEditors