Fireheart&: Typo

2024-02-19T22:11:02Z

Typo

← Older revision		Revision as of 22:11, 19 February 2024
Line 21:		Line 21:
	</pre>		</pre>

	You probably want to ''name'' ~~you~~ fork, however, for convenience. To do so, you can write `fork <tag>`.		You probably want to ''name'' your fork, however, for convenience. To do so, you can write `fork <tag>`.

	<pre>		<pre>

Fireheart&: Commit to the bit, initially.

2024-02-19T22:07:52Z

Commit to the bit, initially.

New page

{{Aside|
<center>This article is part of the {{ll|Category:MUCK Guide|MUCK Guide}}.</center>
<center style{{=}}"font-weight: bold;">« [[MUCK:Character Setup|Character Setup]] • Forking • [[MUCK:Building New Areas|Building New Areas]] »</center>
| color = 0080FF
| float = center
}}

This is the Post-Self MUCK! Of ''course'' you can fork!

== Command Usage ==

=== Creating A Fork ===
<div style="font-style: italic; font-size: 90%;">`fork <tag>`</div>

To create a new fork, you could simply type `fork`.

<pre>
> fork
A Finger Pointing forks into A Finger Pointing#DA4076A1.‌
Default fork set to #DA4076A1.‌
</pre>

You probably want to ''name'' you fork, however, for convenience. To do so, you can write `fork <tag>`.

<pre>
> fork Demo
A Finger Pointing forks into A Finger Pointing#Demo.‌
Default fork set to #Demo.‌
</pre>

This creates a type of object called a [https://wiki.tinymux.org/index.php/PUPPET Puppet], which basically behaves like an extension of your character. Traditionally, these are used to represent pets or NPCs; they still can, but doing so with the `fork` command will not work very well.

=== Controlling A Fork ===
<div style="font-style: italic; font-size: 90%;">`> <tag> = <command>`</div>

This is the one case where you are actually supposed to type the `>` at the start. To control a fork, write `> <command>`.

<pre>
> > : waves!
A Finger Pointing#Demo waves!
</pre>

If you want to control a fork other than the last one you controlled, write `> <tag> = <command>`.

<pre>
> > Previous = " Hello, #Demo.
A Finger Pointing#Previous says, "Hello, #Demo."
Default fork set to #Previous.
</pre>

You can also write an abbreviated version of the fork's tag.

<pre>
> > prev = " Still me!
A Finger Pointing#Previous says, "Still me!"
</pre>

=== Quitting ===
<div style="font-style: italic; font-size: 90%;">`quit`</div>

A fork can quit at any time by using the `quit` command.

<pre>
> > demo = quit
A Finger Pointing#Demo quits.
</pre>

Alternatively, you can use `quit 1`, bubbling up instead of merging down. This teleports you to the fork before they quit.

<pre>
> > demo = quit 1
A Finger Pointing bubbles up to #Demo.
</pre>

=== Memory Management ===
If you want to store a memory, you can write `memo <text>`.

<pre>
> memo May Then My Name thinks dandelions smell like muffins.
Memory saved.
</pre>

You can look up a list of stored memories with `memo`.

<pre>
> memo
280+51.90: May Then My Name thinks dandelions smell like muffins.‌
</pre>

== Individuation ==
The best way to represent an individuated fork is to create a new character. If you simply rename them or make a puppet from scratch, their forks will technically be your direct up-trees, inheriting none of their properties. This is because only one generation of forks is represented under the hood; forks of forks are flattened down. Roleplay is the means by which more diverse clade structures are expressed.

[[Category:MUCK Guide]]
{{DISPLAYTITLE:Forking}}

MUCK:Forking - Revision history

Fireheart&: Typo

Fireheart&: Commit to the bit, initially.