|
|
@@ -248,24 +248,7 @@ Chapter screen chunks are working like Markdown headers:
|
|
|
```
|
|
|
In-game, it would be chapter screen.
|
|
|
|
|
|
-### 3.2.4 Link chunk
|
|
|
-Goto statements are considered harmful since
|
|
|
-[1968](https://dl.acm.org/doi/epdf/10.1145/362929.362947).
|
|
|
-
|
|
|
-Well, **sometimes** they are useful. More often they are harmful.
|
|
|
-
|
|
|
-Good news is we can easily avoid them by using Markdown links:
|
|
|
-
|
|
|
-```markdown
|
|
|
-1 Let's call this a day...
|
|
|
-2
|
|
|
-3 [Non-obligatory description](next_day.vnrs)
|
|
|
-```
|
|
|
-
|
|
|
-This is how we can go from one file to another. Writing anything *after*
|
|
|
-is kinda useless, since it can't be viewed anyway.
|
|
|
-```
|
|
|
-### 3.2.5 Choice chunk
|
|
|
+### 3.2.4 Choice chunk
|
|
|
With bullet points and link we can give player a choice:
|
|
|
|
|
|
```markdown
|
|
|
@@ -286,5 +269,23 @@ useful for planning future chapters.
|
|
|
'\*' is for hidden choices. They are only viewable if the condition in
|
|
|
{} brackets is true.
|
|
|
|
|
|
+### 3.2.5 Link chunk
|
|
|
+Goto statements are considered harmful since
|
|
|
+[1968](https://dl.acm.org/doi/epdf/10.1145/362929.362947).
|
|
|
+
|
|
|
+Well, **sometimes** they are useful. More often they are harmful.
|
|
|
+
|
|
|
+Good news is we can easily avoid them by using Markdown links:
|
|
|
+
|
|
|
+```markdown
|
|
|
+1 Let's call this a day...
|
|
|
+2
|
|
|
+3 + [](next_day.vnrs)
|
|
|
+```
|
|
|
+**Yes, it's just a single choice chunk.**
|
|
|
+
|
|
|
+This is how we can go from one file to another. Writing anything *after*
|
|
|
+is kinda useless, since it can't be viewed anyway.
|
|
|
+
|
|
|
|
|
|
## 3.3 Inline parser
|
