update from sparkleup
This commit is contained in:
parent
1971e5c3c5
commit
3553c7fbed
|
@ -50,6 +50,7 @@
|
|||
<li><a href="#the-perisystem-architecture">The Perisystem Architecture</a></li>
|
||||
<li><a href="#overflowing-with-memory">Overflowing with memory</a></li>
|
||||
<li><a href="#the-shared-dream">The shared dream</a></li>
|
||||
<li><a href="#sensorium-messages">Sensorium messages</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#tracking-resources">Tracking resources</a></li>
|
||||
|
@ -301,9 +302,17 @@
|
|||
<li><em>Trackers</em> fork to track specific tasks, relationships, or trains of thought. These forks may be long-lived, but they merge down-tree with some frequency so that their down-tree instance (usually the <em>root instance</em>) can keep track of all of the different threads that their tracking. Their root instance is usually tagged <em>#Tracker</em>. Given that the idea of letting a long-lived instance individuate beyond a certain point and lose their shared identity, letting a fork linger too long goes against their <em>principles</em>, as can not forking at all. While this memory does build up within trackers, it plays far less of a role in affecting stability as it does in dispersionistas.</li>
|
||||
<li>The most conservative of strategies, <em>taskers</em> fork rarely (if at all), and then usually to accomplish only one or two tasks. Their root instance is usually tagged <em>#Core</em>. Having to fork more often than that is incredibly uncomfortable and would work counter to the character’s <em>principles</em>. That said, taskers maintain the strongest sense of self and, with so little divergent memory, remain some of the sanest on the System.</li>
|
||||
</ul>
|
||||
<p>((Stating that one is forking))</p>
|
||||
<p>((Reputation cost))</p>
|
||||
<p>((Continue with the root instance))</p>
|
||||
<p>((Merging and playing out the fork’s experiences to justify the root instance’s actions))</p>
|
||||
<p>((Sanity cost))</p>
|
||||
<p>((Other players’ influence, helping with sanity, reacting to forking and merging, etc))</p>
|
||||
<p>((MC moves, high sanity = positive modifier, low sanity = negative modifier))</p>
|
||||
<h5 id="the-perisystem-architecture">The Perisystem Architecture</h5>
|
||||
<h5 id="overflowing-with-memory">Overflowing with memory</h5>
|
||||
<h5 id="the-shared-dream">The shared dream</h5>
|
||||
<h5 id="sensorium-messages">Sensorium messages</h5>
|
||||
<h4 id="tracking-resources">Tracking resources</h4>
|
||||
<ul>
|
||||
<li>Sanity</li>
|
||||
|
|
Loading…
Reference in New Issue