Write a stunt cue sheet
A stunt sheet puts a scene's commands into cues you fire from your own keys.
Running it needs community admin when nobody is directing, or director mode while anyone is directing.
Write the file in a text editor. The Stunts panel loads sheets and edits existing cues, but does not create a new sheet.
Creating the file
Make a plain text file called corridor.cfg in the stunts/ folder inside your StoryForce game
folder.
Create the folder if it is not already there. The shipped sheet is available in game as
example.
Subfolders work too. A file at stunts/mission/corridor.cfg loads with /stunt load mission/corridor.
Use the same naming rules for each folder.
Paste these 4 cues, keeping each cue on one line:
cs Three...; wait 1000; cs Two...; wait 1000; cs One... // Count down
=cs Waiting for Zala // Repeat until the cast is ready
!fade out // Hold the room at black
fade in // Reveal the scene
The file belongs to your copy of the game. Another director needs their own copy to run it.
Writing a cue
One line is one cue.
Put the commands first and an optional description after //.
The description appears on the HUD. Without one, the HUD shows the command instead.
Separate commands on the same line with ;. They run in order when you fire that cue.
wait 1000 waits one second before the next command. Each wait can be up to 60 seconds.
Blank lines and lines starting with // or # are comments. They do not become cues or use cue
numbers. Numbering starts at 1 and follows the remaining lines in order.
Keep
;and//out of message text. They still split commands or start a description inside quotes.
Guarding or holding a cue
Put a marker before the first command:
| Marker | What it does |
|---|---|
! | the first Fire press arms the cue. A second press within 2 seconds runs it |
= | runs without advancing. Fire repeats the cue until you press Next |
!= | combines confirmation and HOLD. =! works too |
In the example, the countdown runs from one press. The second cue stays selected until you press Next. The third needs confirmation before it fades the room out.
Wait for a cue's command chain to finish before firing again. Fire refuses while commands are still waiting to run.
Loading and rehearsing
Load corridor through ESC → Direct → Stunts, or run /stunt load corridor in the console.
Press ~ to open the console.
Turn on dry run before trying the cues:
Fire the cues with your bound keys.
Dry run prints each command instead of performing it.
Run a stunt cue sheet covers the keys, browser and cue selection.
After changing the file, use /stunt reload to read it again.
Things to note
- Keep within the limits. A sheet holds up to 128 cues. Each cue allows 32 commands, 511 characters of command text and a 95-character description.
- Stop a running cue with
/stunt stop. This cancels its pending commands. It does not undo commands that have already run.