lb:coincidence
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| lb:coincidence [2026-02-01 10:38:32] – removed - external edit (Unknown date) 127.0.0.1 | lb:coincidence [2026-02-01 10:38:33] (current) – ↷ Page moved from playground:story:coincidence to lb:coincidence ninjasr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Coincidence ====== | ||
| + | The problem of coincidence in stories is that they, by nature, fundamentally violate setup/ | ||
| + | The solution that EFAP (and myself) have come to is that coincidences are okay if: | ||
| + | * They begin a story. | ||
| + | * They don't resolve a situation. | ||
| + | * They //create// situations. | ||
| + | I realized recently that these are not quite satisfying, so I decided to come up with a different means of determining the good/ | ||
| + | |||
| + | These are related to the [[lb: | ||
| + | |||
| + | Basically, a coincidence is fine if the order of events leading to the coincidence can be rebuilt with the benefit of hindsight. | ||
| + | |||
| + | This doesn' | ||
| + | |||
| + | For example, a good coincidence would be one where two characters meet by chance in the same location because both characters, independently, | ||
| + | |||
| + | A bad coincidence is one in which one (or both) characters have no particular reason to be meeting each-other. | ||
| + | |||
| + | Regarding the beginning of stories, read [[lb: | ||
| + | |||
| + | Freak coincidences are generally not okay either. | ||
| + | {{tag> | ||