scripting:cutscenes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| scripting:cutscenes [2012/03/23 03:05] – mit | scripting:cutscenes [2025/05/28 16:34] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Introduction to Cutscenes | + | ===== Cutscenes Overview ===== |
| - | + | ||
| - | You can trigger a cutscene for someone at any point in your script. The cutscene itself is defined in a file on the server that the client will download. Cutscenes allow you to control the camera and player, add models and graphics, add UI text and do things like play music and control special effects. | + | |
| - | + | ||
| - | e.g. You might have a cutscene triggered when a new player joins, that might pan the camera around to show them their environment, | + | |
| - | Or you might have a building (or item) that when accessed triggers a cutscene giving the user a storyline or clues that would lead to other gameplay on your world. | + | |
| - | + | ||
| - | * [[Scripting: | + | |
| - | * [[Scripting: | + | |
| - | * [[Scripting: | + | |
| - | + | ||
| - | * [[Scripting: | + | |
| - | + | ||
| - | ===== Cutscene Language | + | |
| - | + | ||
| - | Purely for the reason that this feature was added as an interesting experiment, cutscenes are defined using a separate, custom, object-orientated language. | + | |
| - | + | ||
| - | Here is a basic example: | + | |
| + | You can trigger a cutscene for someone from script or manually using the command : | ||
| < | < | ||
| - | section(1) | + | *cutscene [PLAYERNAME] [CUTSCENE_FILENAME] |
| - | { | + | </ |
| - | | + | |
| - | | + | |
| - | | + | The cutscene is contained within a file on the server that the client will download. Cutscenes allow you to control the camera and player, add models and graphics, add UI text and do things like play music and control special effects. |
| - | | + | |
| - | | + | e.g. You might have a cutscene triggered when a new player joins, that pans the camera around to show them their environment, and tells them some stuff about your world. Or you might have a building (or item) that when accessed triggers a cutscene giving the user a storyline or clues that leads to bigger things. \\ |
| - | | + | \\ |
| + | Cutscenes use a different language (don't ask), where you set thing such as 'the camera will pan from //this// point, to //this// point, from time x to time y' or 'this model will move from //here// to //here// and do //this// animation' | ||
| + | \\ | ||
| + | If you're new to world building, come back here later - you'll get more benefit exploring the event scripting side of things. If you're an advanced world-builder, | ||
| + | \\ | ||
| + | ===== Cutscene Reference Materials ===== | ||
| - | | + | |
| - | | + | * [[Scripting: |
| + | * [[Scripting: | ||
| - | | + | |
| - | | + | * [[Scripting: |
| - | | + | |
| - | + | ||
| - | cam = Camera( campos, modelpos ); | + | |
| - | | + | |
| - | + | ||
| - | | + | |
| - | | + | |
| - | | + | |
| - | } | + | |
| - | </ | + | |
| - | + | ||
| - | This example adds a house model near to the player, sets lighting, sets a camera that pans across the scene, and adds a caption that fades in then fades out. | + | |
| - | + | ||
| - | More details to follow. | + | |
scripting/cutscenes.1332471931.txt.gz · Last modified: (external edit)
