Currently the boolean "Loop" metadata isn't being successfully stored on GitHub. This may be due to some metadata being ignored by a .gitignore or something like that.

For now just go through all the clips in the library and check the Loop option for each video file.

Currently Video.js sets and uses a variable called parentScript which points to the parent Avatar.js script. This variable is then used to call getter member functions of Avatar.js. So, at the moment, Video.js asks Avatar.js if the avatar is jumping, firing, etc... and then plays the appropriate video.

Another way to accomplish the same functionality would be for Avatar.js to have reference to Video.js via a variable called childScript and then to call childScript.SetTexture( ... ).

So the two options are:

1. The child asks the parent what to do.
2. The parent tells the child what to do.

Currently it isn't clear which option is best or if there's another better solution altogether.

This issue will remind us of our options and be a place for discussion if we start running into problems with the current "child asks parent" method.

Should the avatars be allowed to turn their back on each other when walking/running left and right? For instance, in Mortal Combat (http://youtu.be/izVZsnCiaWk) when the avatars cross paths they automatically turn to face each other.

So if avatar A is on our left and avatar B is on our right, and B starts walking towards our left, he will be facing left. Once B crosses past A, should B continue to face A (by flipping the animation so B is facing right) and start walking backwards or should B keep facing left after passing A, thus allowing B to turn his back to the enemy?