1- # SER 1.0 documentation
2-
3- This directory is the canonical user documentation for Scripted Events
4- Reloaded 1.0. It lives beside the implementation so a
5- change to syntax, commands, examples, or tooling can update the matching
6- tutorial in the same pull request.
7-
8- Start here:
9-
10- 1 . [ Install SER] ( getting-started/installation.md )
11- 2 . [ Create and run your first script] ( getting-started/first-script.md )
12- 3 . [ Understand files, names, and reloads] ( getting-started/files-and-reloads.md )
13- 4 . [ Learn methods and values] ( language/methods-and-values.md )
14- 5 . [ Learn variables and properties] ( language/variables-and-properties.md )
15- 6 . [ Add conditions and loops] ( language/conditions-and-loops.md )
16- 7 . [ Work with collections] ( language/collections.md )
17- 8 . [ Pause and resume execution safely] ( language/timing-and-yielding.md )
18- 9 . [ Connect scripts to commands and events] ( guides/flags-events-and-commands.md )
19- 10 . [ Organize larger scripts] ( language/functions-scopes-and-errors.md )
20- 11 . [ Debug a script] ( guides/debugging.md )
21-
22- For complete examples that are compiled during every build, see the
23- [ example index] ( guides/examples.md ) . Experienced authors can use the compact
24- [ language specification] ( ../language_specification.md ) .
1+ # Make your server do something new
2+
3+ SER is a programming language, but you do not need to study a programming
4+ language before you can enjoy it. Start with one method, turn it into a player
5+ command or game event, and watch the server change. Learn variables and control
6+ flow later, when a script you actually want to build needs them.
7+
8+ These docs therefore have two different reading paths.
9+
10+ ## Tutorial: build first, learn as you need it
11+
12+ Follow this path in order if SER is new to you:
13+
14+ 1 . [ Install SER and generate its examples] ( getting-started/installation.md )
15+ 2 . [ Make the server say something] ( getting-started/first-script.md )
16+ 3 . [ Discover methods that change the game] ( tutorial/methods.md )
17+ 4 . [ Make a command or react to an event] ( tutorial/flags.md )
18+ 5 . [ Choose which players are affected] ( tutorial/player-targets.md )
19+ 6 . [ Remember values and inspect players] ( tutorial/variables-and-properties.md )
20+ 7 . [ Add decisions, chance, and timing] ( tutorial/decisions-and-time.md )
21+ 8 . [ Build a Hot Potato event] ( tutorial/hot-potato.md )
22+
23+ You will make useful scripts before the tutorial introduces loops, collections,
24+ functions, or memory lifetimes. That is intentional.
25+
26+ ## Reference: find the exact rule
27+
28+ Use the reference when you need a complete or technical answer:
29+
30+ - [ script files, identity, and reload behavior] ( getting-started/files-and-reloads.md ) ;
31+ - [ methods, values, expressions, and return types] ( language/methods-and-values.md ) ;
32+ - [ variable families and properties] ( language/variables-and-properties.md ) ;
33+ - [ conditions and loops] ( language/conditions-and-loops.md ) ;
34+ - [ collections] ( language/collections.md ) ;
35+ - [ timing and yielding] ( language/timing-and-yielding.md ) ;
36+ - [ functions, variable visibility and lifetime, and errors] ( language/functions-scopes-and-errors.md ) ;
37+ - [ flags, events, and commands] ( guides/flags-events-and-commands.md ) ;
38+ - [ optional integrations] ( guides/integrations.md ) ;
39+ - [ debugging] ( guides/debugging.md ) .
40+
41+ The compact [ language specification] ( ../language_specification.md ) is for
42+ experienced authors and tool builders. The [ validated example index] ( guides/examples.md )
43+ points to complete scripts that compile during every SER build.
2544
2645## Documentation boundaries
2746
@@ -36,9 +55,11 @@ For complete examples that are compiled during every build, see the
3655
3756## Contributing
3857
39- Keep tutorials task-oriented. A beginner should know what a command changes,
40- what they should see after running it, and which diagnostic command to use when
41- the result differs.
58+ Keep the tutorial outcome-oriented and the reference precise. A tutorial page
59+ should begin with something worth adding to a server, introduce only the
60+ language features needed to build it, show the expected result, and then offer
61+ one safe experiment. Put exhaustive behavior and implementation-shaped edge
62+ cases in the reference instead of interrupting the first learning path.
4263
4364When changing the language or user workflow:
4465
0 commit comments