Interactable Animations

Animation Handling - Potential Method

Currently, obstacle sprites are pulled from a singular image, through the TextureRenderComponent class. For animations to work, this must be replaced by an AnimationRenderComponent like the one that is used within the GhostNPC.

A few things are required for this component to be functional, including an atlas file of all the relevant sprites and the names of the specified animations (as defined within the atlas file).

The ObstacleAnimationController class has been created to mimic the GhostAnimationController class, and is set up in such a way that when certain events are triggered, the animations of the object are changed. However, as the current implementation requires naming of animations, the obstacle at;as files must be changed slightly to allow for correct animation handling. The animation controller must also be added as a component of the corresponding entity (upon its creation) for the class to function.

Provided the animations are loops, and do not have complex conditions, simply triggering one of the events declared in the animation controller file will change the animation.