At the moment by means of Visual Script Editor it is possible to create scripts which can be established game entity as behavior or as reaction to user input (as task).

The script represents the program which executes set activity (pic.4, [1]). Activity can be executed consistently and in parallel. For script working out it is used Visual Script Editor.

On the right on the panel all possible are presented activity. (pic.4, [4]). By means of drag-and-drop activity are transferred to working area of the editor. Except managing directors activities (wile, if, delay …) and combining activities (parallel, sequence) you can use following two activities:

AnimationActivity

For this activity animation and duration should be defined, if it not looped.

The script using AnimationActivity, can be started as behaviour or on user input.

MoveActivity

For this activity there should be a definite target to which the entity will move. (pic.4, [3]) As the target is possible to use any called entity.

The script using MoveActivity, can be started only as behaviour.

The ready script needs to be compiled, having pressed button "Compile". (pic.4, [2]). If there is a start of not compiled script, the system will try to compile it independently. Compilation is possible during scene simulation. (gameplay-time?) At behaviour restart last compiled script will be used.

The ready script can be started in three ways:

1. By opening context menu, by right clicking onto the entity. (pic. 1)

1. Through the console (pic. 2).

1. In a code or a scene/world script. (See WorkflowScripting.cs method TwoWorkflowDemo) (pic.3)

Use of scripts can be seen in demonstration «Workflow Scripting». As an example scripts are used: MoveDroid and MoveForwardAnimation which are located in a folder \Projects\Demo Assets\Workflow.

MoveDroid and MoveForwardAnimation it is possible to start through the contextual menu or the console. Also MoveForwardAnimation it is established on the left button of the mouse.