Difference between revisions of "Cutscene Framework"
(Initial page) |
(added category) |
||
| Line 16: | Line 16: | ||
*[[CutsceneCmdTranslate]] | *[[CutsceneCmdTranslate]] | ||
*[[CutsceneCmdWaitForMessage]] | *[[CutsceneCmdWaitForMessage]] | ||
| + | |||
| + | [[Category:Cutscene Framework]] | ||
Revision as of 22:15, 10 April 2013
The cutscene framework allows the game designer to implement a sequence of actions, driven by script. Each cutscene implements a particular interface for starting and stopping the cutscene, and the cutscene instance is responsible for handling those events (in Software Engineering this is called the Command pattern). In addition, the Cutscene object itself implements delegate functions to decouple the interface of calling into this interface with the actual acts that are performed (this is called the Observer pattern). In addition, there is a special type of Cutscene called the CompoundCutscene that adheres to the cutscene interface, but has an entire list of cutscenes it manages itself (this is the Composite pattern).
From a practical standpoint, this means that there is one Cutscene script and different Cutscene commands that implement different things you may want a cutscene to do, such as translate, rotate or scale an object, play a sound, delay for some time, etc... There is a CutsceneDirector script that kicks the whole thing off. Usually, a CompoundCutscene is attached to the CutsceneDirector to drive a sequence of commands.
This page has links to documentation for each script in the Cutscene Framework:
These are the commands (actions) currently supported by the framework:
