Difference between revisions of "MUSH to MOO Guide"
Jump to navigation
Jump to search
Tag: Undo |
|||
| Line 1: | Line 1: | ||
| − | + | If you're coming from another modern roleplaying codebase, such as MUSH or MUCK, there are a few peculiarities to MOO that may throw you. You're likely used to the general flow of play, which has been substantially unchanged, but there will be differences here and there. We've taken a fair amount of time to adjust them, with interoperability as a priority. | |
| − | |||
| − | + | **Non-Channel Communications** | |
| − | + | Communication on MOOs is much like communication on MUSHes; the usual command markers -- ", :, and @emit -- all work equally well. There are only two core differences between the commands. One has to do with spacing, while the other has to do with semiposing. | |
| − | + | Spacing | |
| − | + | * " and : are meant to be compact, short commands on MOOs. These commands do not evaluate %r, %t, and %b; however, they will take any number of nonbreaking spaces you happen to want, unlike MUSHes, which sanitize multiple spaces down to a single space. Emit/@emit still takes %r, %t, and %b in more or less the expected ways. | |
| + | * %t, rather than inserting an indent to a fixed point, inserts eight consecutive spaces. As %t is generally used only to start a pose, and %b is preferred in formatting internally anyway, this should not cause more than the occasional hiccup. (Use %b for internal formatting. It is more reliable, in general.) | ||
| − | + | Semiposing | |
| − | + | In MUSH syntax, the semicolon is used to perform semiposes. While semiposes still exist in MOO (how else would we talk about the things we own?), the syntax for one is ::, rather than ;. For instance, if you, Amuro Ray, wanted to announce that your Haro is stinky, you would input: | |
| − | + | ::'s Haro is stinky. | |
| − | |||
| − | + | And receive: | |
| − | + | Amuro Ray's Haro is stinky. | |
| − | + | **Colors** | |
| − | + | Someone smarter than me will have to write this one. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 10:33, 6 September 2021
If you're coming from another modern roleplaying codebase, such as MUSH or MUCK, there are a few peculiarities to MOO that may throw you. You're likely used to the general flow of play, which has been substantially unchanged, but there will be differences here and there. We've taken a fair amount of time to adjust them, with interoperability as a priority.
- Non-Channel Communications**
Communication on MOOs is much like communication on MUSHes; the usual command markers -- ", :, and @emit -- all work equally well. There are only two core differences between the commands. One has to do with spacing, while the other has to do with semiposing.
Spacing
- " and : are meant to be compact, short commands on MOOs. These commands do not evaluate %r, %t, and %b; however, they will take any number of nonbreaking spaces you happen to want, unlike MUSHes, which sanitize multiple spaces down to a single space. Emit/@emit still takes %r, %t, and %b in more or less the expected ways.
- %t, rather than inserting an indent to a fixed point, inserts eight consecutive spaces. As %t is generally used only to start a pose, and %b is preferred in formatting internally anyway, this should not cause more than the occasional hiccup. (Use %b for internal formatting. It is more reliable, in general.)
Semiposing
In MUSH syntax, the semicolon is used to perform semiposes. While semiposes still exist in MOO (how else would we talk about the things we own?), the syntax for one is ::, rather than ;. For instance, if you, Amuro Ray, wanted to announce that your Haro is stinky, you would input:
- 's Haro is stinky.
And receive:
Amuro Ray's Haro is stinky.
- Colors**
Someone smarter than me will have to write this one.