1. A locomotion system for controlling animation of a character in a three-dimensional (3D) virtual environment comprising: a rendering engine; a core system logic communicatively coupled to the rendering engine for executing core game logic of the virtual environment …

This is basically a description of a game engine that supports movement and animation. Descent (1994) would be the earliest production use of such an engine.

2. The locomotion system of claim 1, wherein a key identifies one or more variables of the blackboard, the key comprising a human readable name associated with the variables to provide the selection criteria.

Congratulations, you just described “variables”, a concept at least as old as ENIAC (1945).

3. The locomotion system of claim 1, wherein the core game logic defines one or more desired physical movements to sequence the motion type objects blocks.

Yes, that’s one way to describe “animation”

4. The locomotion system of claim 1, wherein a selected archetype block defines a fallback archetype block, the fallback archetype block defining at least one new motion animation block or motion type block not present in the selected archetype block and inheriting any remaining motion type blocks and motion animation blocks from the selected archetype block.

Variables having a default value is the default behavior of most programming languages and software systems.

5. The locomotion system of claim 1, wherein a selected archetype block defines the character’s default animation.

Yea, we’re talking about animation here. Default value of animation description = default animation.

6. The locomotion system of claim 1, wherein a selected archetype block of the character is unique from a second archetype block of a second character and at least one motion type block is common across the character and the second character.

Inheritance, a property of most software designs since the 1980s.

7. The locomotion system of claim 1, wherein at least one of the motion animation blocks, the motion type blocks, and the archetype blocks is defined by a series of extensible markup language (XML)-based meta files.

Storing configuration in a data file. You’d be hard pressed to find an alternative. Maybe some genius will come along and find some way to represent it in JSON…

8. The locomotion system of claim 1, wherein a selected attribute of a selected motion animation block includes at least one of a clip set that is used by a selected motion of the character, an overloadable animation blend tree to be used for the selected motion, named additional clips within specific clip sets, parametric blends from sets that can be named, a Boolean that specifies whether play speed of the selected motion can be modified, a minimum speed, and a maximum speed.

This seems to be the main claim of the patent, but seems to have a huge amount of prior art (see links). “Parametric blends” and other terms are just jargon.

9. The locomotion system of claim 1, wherein the attributes of the motion animation block are custom float values.

Oh my god. Really? Shall we also include “doubles”, “halfs”, or maybe “rationals”?

10. The locomotion system of claim 1, further comprising one or more transition tables to control a relationship between motion animation blocks.

“Translation table” seems to just be referring to the graph topology of the system. Yes, graphs are the most common way to represent arbitrary N:M relationships.

11. The locomotion system of claim 1, further comprising an in-game graphical user interface for real-time modification of at least one of the motion animation blocks, the motion type blocks, and the archetype blocks.

Node-based editing; standard practice in all 3D modeling.

12. A computer-implemented method for controlling animation of a character in a three-dimensional (3D) virtual environment comprising: executing core game logic to render the virtual environment using a core system logic communicatively coupled to a rendering engine …

Yes, you already described what a game engine is and an animation system is. Game engines certainly do have animation systems…

13. The computer-implemented method of claim 12, wherein said animating the character further comprises identifying a second archetype block, the common set of motion type blocks and the motion animation blocks of the second archetype block altering the animation of the character as a game story defined by the core game logic develops.

Picking animation keys based on game logic. What else would you base it on exactly?

14. The computer-implemented method of claim 12, wherein said animating the character further comprises identifying a fallback archetype block of the archetype block, the fallback archetype block defining at least one new motion animation block or motion type block not present in the selected archetype block and inheriting any remaining motion type blocks and motion animation blocks from the selected archetype block.

Yes, default values do be defaultin’.

15. A computer program product for controlling animation of a character in a three-dimensional (3D) virtual environment, the computer program product including a non-transitory computer readable storage medium having program instructions embodied therewith, the program instructions executable by a device to cause the device to perform a method comprising: executing core game logic to render the virtual environment using a core system logic communicatively coupled to a rendering engine …

Yep, software sure does run on computers. Computers are neat. And they have storage.

16. The computer program product of claim 15, wherein said animating the character further comprises identifying a second archetype block, the common set of motion type objects blocks and the motion animation blocks of the second archetype block altering the animation of the character as a game story defined by the core game logic develops.

Are we really going to enumerate all the permutations of engine + animation + defaults claims?

17. The computer program product of claim 15, wherein said animating the character further comprises identifying a fallback archetype block of the archetype block, the fallback archetype block defining at least one new motion animation block or motion type block not present in the selected archetype block and inheriting any remaining motion type objects blocks and motion animation blocks from the selected archetype block.

I guess we are…