Guidelines for script writers

Definitions

“Level” - a container of Events

“Sequence” - decides the order of the events.

“Events” - either Story Events, Story Output Events or Story Input events

“Story Input Events” - a type of Story event that allows the player to choose between two options, that in turn will have an effect on a story output event

“Story Output Event” - a type of Story event that is played to the user depending on what Story Input Event selections (maximum 4) the player has made. Thus Story Output event can never have fewer than 2 versions and never have more than 16 versions.

“Story Event” - a type of Story event which does not involve player input or does not depend on player input. It is like a cut-scene.


Event ID structure

The Event ID contains abbreviations for which Frever,  level, sequence and event type that the event belongs to. Below you will find an example of a properly named Level.

GB_L5_A0_S1_ST1_V0

First, you have the abbreviation for your frever, in this case, Gorbi, in short GB. Then you have the Level, in this case, Level 5. The A is irrelevant so you don’t have to pay attention to it. Next, you have the sequence. It always starts at 1. Then you have the Event type, in this case, it’s a Story Event. It is the 1st Story Event in the Level and thus starts at 1. Last you have the version number. This is always 0 for Story and Story Input Events.

GB_L5_A0_S2_ST2_V0

The next event is also a Story Event. So the Frever and Level remain the same. But it’s now Sequence 2. Since it’s the 2nd Story Event in the Level it is now ST2.

GB_L5_A0_S3_SI1_V0

The 3rd event is a Story Input. It´s the 1st Story Input in the Level, so it’s named SI1.

GB_L5_A0_S4_SO1_V1

GB_L5_A0_S4_SO1_V2

These are Story Output Events, where the Level branches out. They both belong to the sequence after GB_L5_A0_S3_SI1_V0. Therefore, they both belong to Sequence 4 and they are both the 1st Story Output in their branch. So they are both called SO1. The key difference is the Version number. V1 is dependent on choice A. V2 is dependent on choice B.

GB_L5_A0_S4_SO2_V1

Choice A has a 2nd event, whereas Choice B only has 1. The second Event remains in the same sequence but is now the 2nd Story Output. And the version is still 1, to show that it belongs to choice A. The Sequence number will remain the same for all Story Outputs until you add a new Event type.

GB_L5_A0_S5_ST3_V0

The Level ends In a generic Atory Event that connects ties the branches together. This a new Sequence, 5, and it is the 3rd Story in the Level. Since it is an event that is not dependent on any other events, the version number is 0.

Creating content in Friendfactory’s scriptwriter tool

When you, a “creator”, write a story for the Frever platform, you need to use our scriptwriting tool, which can be found at studio.friendfactory.com. This tool is essential for  us to create automated stories for you, fast.

You as a creator, write character-driven user-generated stories.

Based on your submissions, we will create (or use from our database) all assets (sounds, art, environments, animations, vfx) that are need to generate a story and post-produce it. Ideally, we want you as the voice and face behind each character you create, but if you cannot come to our Studio in Stockholm and record, or submit your own voice and face files through our face & voice recording app we will, assign voice and face files to your stories.

Architecture

A story is built up by events. The Story format for Frevers is short-form. You should aim for a total of 4-10 events that build your story.

Each event is a 1-10 seconds very short clip that holds maximum 1 voice line and one camera shot and animation. If you want a dialogue exchange, then you need a minimum of two events. If you want two camera angles or a cut-away shot, then you need two events, one for the first angle and one for the cut-away.

For each event you need to write 4 kinds of information that you fill in “cards” and then submit.

You submit information in “cards”. Each card holds either drop-down selections or text fields where you choose or enter information.

Cameras

There is 4 different camera shots that you can choose from, Midshot, Close-Up, Fullshot and Establishingshot.

     

       Midshot                     Close-Up                       Fullshot                   Establishingshot

An Establishing shot pans over the entire set location

A Fullshot is a still camera that show all characters in the set location

A Midshot shows the character in focus. This is the most common shot and should always be used for story input events.

Close-Up pans in on the character in focus.


Character Placement

A character's position throughout the event is always fixed.

Character 1 is always green. Character 2 is always blue. Character 3 is always red.

Create an account

Click Authorization in the upper right corner and register your account.

After registration, choose “Login”, in the same tab.

If you use a google account, use sign in with google button.

Write your first script

Once you’ve signed in you will face this screen. This is where you submit all information about the event.

1. Define event information

This is a mandatory step that provides us with the necessary metadata to create your event. First write which language your story is in, which game you're creating your story for and which Frever is the main character.

Next, choose what type of event it is. As well as which day, act, sequence number, and event numerator the event has. Depending on your input you will be given different options.

Story input event

If the event is a story input you need to add information about the choice buttons. All Story Input events must be a midshot.

Story output event

If the event is a story output you need to provide us with information regarding which event input the event is dependent on and which version the event is.

Story event

No additional fields need to be filled in

Once all of the above fields are filled in, an EventID will be automatically generated and shown in the middle upper screen.

Input Variables

If you want to write a story input event you will be prompted with another card, that requires you to fill in button name, icons, and audio (audio is not mandatory)

Output Variables

If you want to write a story output event you will be prompted with another card, that requires you to specify which story Input choice that is leading up to this event. You can at maximum only combine 4 story Input selections (resulting in a total of 16 different story output versions)

Event Output Version

When you write a story output, please use a unique version identifier a number 1-16 to allow the game to know which version should be connected to which story input.

2. Write the script

This is a mandatory step.

Event Description

First write a short description of the event so that the one performing the post production gets a clearer view of what's going on in the event. One sentence is usually enough.

Press Done once you’ve filled in the information.

Event Lines

Next add the voiceline. Only one Frever may speak during one event. If there is a dialogue between Frevers, there needs to be a new event for each line.

Press Done once you’ve filled in the information.

3. Design the event scene

Event location

Choose your event location from any of the alternatives from the dropdown menu.

The entire Story act must take place at the same location.

Event prop

Write which prop you want visible in the event and if you want the prop to be visible from the start of the event or after the character has finished their line. Use a capital letter e.g “Banana” not “banana”

Right now you CANNOT USE the select prop alternative. This is for later use.

Press Done once you’ve filled in the information.

You may have a maximum of 2 active props in the event.

Event graphics image

If you want a static 2D image to be present in the event, fill in the information here. Always start with a capital letter for instance “Bird”  (This is not equal to a button)

This option is rarely used.

Press Done once you’ve filled in the information.

Event Characters

Choose up to 3 characters that you want present in your event.

Press Done once you’ve filled in the information.

4. Direct your event

Event duration

Not relevant

Character Animations

This is where you fill in what types of animations you want to have in the event. You may have up to 4 animations in a sequence for each character per event. The animation name must be descriptive, have no blanks  and each word should start with a capital letter.

For example “ArmsOutAngry”

The animations will be played in the order you filled them in

Press Done once you’ve filled in the information.

Characters sights directions

Choose where the character should look. You may choose from the different characters and props present in the event.

Press Done once you’ve filled in the information.

Sound effects

Any obvious sound effects such as footsteps, the sound of someone falling to the ground etc will be applied automatically. If you want any other sound effects, fill them in here. For example a noise for when the character gets an idea. The name must be descriptive, have no blanks and each word should start with a capital letter.

You also need to choose if the sound should start at event start or after character line.

Press Done once you’ve filled in the information.

Event song

If you want a specific song in the event, fill in the information here. The Frever soundtrack will be there by default, this field is for specific songs. For example “Baby Shark”

You also need to choose if the sound should start at event start or after character line.

Press Done once you’ve filled in the information.

Event Visual FX

If you want any particle effects (explosions, magic clouds, etc.)  in the event, fill in the information here. For example a noise for when the character gets an idea.The name must be descriptive, have no blanks and each word should start with a capital letter.

You also need to choose if the sound should start at event start or after character line.

Press Done once you’ve filled in the information.

Event Score

Choose what mood you want the score to be.

Press Done once you’ve filled in the information.

Camera Object

Choose which character or prop that the camera should focus on.

Press Done once you’ve filled in the information.

Event Camera ID

Choose one of the cameras from the dropdown menu. Once you’ve clicked an camera there will be a preview picture of that camera and a short descriptive text.

Creator Comment

If you have any additional comments or wishes, to the post-productor add dem here.

Submit

The final step is to press Submit in the upper part of the screen. Once you’ve done this you’ll be able to see an overview of all of your submitted events.


Automatization

General rules