View source for STL:Formatting

*[Brackets] for actions
:*Anything enclosed within brackets is meant to be something the speaker(s) does, be it movement, a sound, or...an action. This is something the listener would directly be able to observe.

*{Braces} for implications
:*Anything enclosed within braces, on the other hand, are implied to have happened or be important, but might not necessarily be indicated through speech or noises. Usually, this manifests as something the listener might be doing or reacting. 

*<arrows> for sound FX
:*Pretty much what you think it is. Sound effects. Finding ones that work well for what the script asks for is up to you. I personally tend to find most sound effects pretty distracting, so their use is intended to be quite minimal or optional.

*Line breaks should direct cadence/pauses, but specifics are up to you
:*I don't like dictating the flow of how people talk that much. One of the most interesting parts of listening to script fills (for me) is how different VAs approach the same lines in terms of cadence and spacing. For my scripts, flow is generally more decided in paragraph form, rather than sentence to sentence. Ideas and topics tend to bunch together like cloves of garlic—you can peel em any which way you want, but they still all need to form the same end result.

<small>Another note while I have your attention: These scripts are often written with pretty clear intentions, details, and delivery in mind. For that reason, I ask that you do not make major changes to any of these scripts found on this site. The omission of specific phrases, words, or word order may jeopardize small details to make a script feel complete, or to make narrative sense at all. Small, rare adjustments to help spoken delivery or the occasional gender flip are acceptable, but please do try to read these as they are presented.</small>

[[Category:Policy]]