Skip to content

Commit c88c9a9

Browse files
authored
Update region-shows.md
1 parent 799d271 commit c88c9a9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/region-shows.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,16 +24,16 @@ cleanup: 'myProject/queue/waving_animatronic/cleanup'
2424
2525
Region Show Schema files must end in `_regionshowschema.yml`.
2626
- `region` refers to the region that the region for which the show listener should be keeping track of player entrances/exits.
27-
- `setup` refers to the show that should be run when the first player enters `region` (i.e. when the number of players in `region` goes from 0 to 1). See [`setup` Show Example](/Technicians/RegionShows#setup-show-example) for more information.
28-
- `loop.name` refers to the show that should continue playing on loop as long as there are players `region`. See [`loop` Show Example](/Technicians/RegionShows#loop-show-example) for more information.
29-
- `loop.delay` exists because some commands take time to fully execute, and you don't want to have your `loop` show start over while a long-running command is still executing. We cover this more in [`loop` Show Example](/Technicians/RegionShows#loop-show-example). The `loop.delay` field is optional and defaults to `0`. If you don't a delay between instances of your loop show, your schema can look like:
27+
- `setup` refers to the show that should be run when the first player enters `region` (i.e. when the number of players in `region` goes from 0 to 1). See [`setup` Show Example](#setup-show-example) for more information.
28+
- `loop.name` refers to the show that should continue playing on loop as long as there are players `region`. See [`loop` Show Example](#loop-show-example) for more information.
29+
- `loop.delay` exists because some commands take time to fully execute, and you don't want to have your `loop` show start over while a long-running command is still executing. We cover this more in [`loop` Show Example](#loop-show-example). The `loop.delay` field is optional and defaults to `0`. If you don't a delay between instances of your loop show, your schema can look like:
3030
```yaml
3131
region: "myRegion"
3232
setup: 'myProject/queue/waving_animatronic/setup'
3333
loop: 'path/to/loopShow/that/doesnt/need/a/delay'
3434
cleanup: 'myProject/queue/waving_animatronic/cleanup'
3535
```
36-
- `shows.cleanup` refers to the show that should be run when the last player leaves `region` (i.e. when the number of players in `region` goes from 1 to 0). See [`cleanup` Show Example](/Technicians/RegionShows#cleanup-show-example) for more information.
36+
- `shows.cleanup` refers to the show that should be run when the last player leaves `region` (i.e. when the number of players in `region` goes from 1 to 0). See [`cleanup` Show Example](#cleanup-show-example) for more information.
3737

3838

3939
### `setup` Show Example
@@ -118,7 +118,7 @@ cleanup: 'path/to/cleanup'
118118
```
119119

120120
### Setup Delay
121-
Sometimes, you might want to a delay between when your [`setup` show](/Technicians/RegionShows#setup-show-example) completes and when your [`loop` show](/Technicians/RegionShows#loop-show-example) starts looping. You can accomplish this in the Schema file very similarly to how you add a delay for your loop show:
121+
Sometimes, you might want to a delay between when your [`setup` show](#setup-show-example) completes and when your [`loop` show](#loop-show-example) starts looping. You can accomplish this in the Schema file very similarly to how you add a delay for your loop show:
122122
```yaml
123123
region: 'testregion'
124124
setup:

0 commit comments

Comments
 (0)