The Plural Code

• Start

What is the plural code?

The Plural code (PLC) is a code designed to help plural systems convey a lot about their system in a short amount of space. It was inspired by the multiple code, another code for a similar purpose. The plural code aims to be more simplified than the multiple code, but the multiple code may go into more detail than the plural code. This is NOT an attempt at replacing the MuC; only an alternative version of a system based code, and my utmost respect goes to the creators of the MuC and its redux.

Update as of 8/28/21: There is now a tumblr post with the code as well!

• Down Arrow

The Full Code

To write this code, you may either use the emojis listed, or you can write it out fully in text by using the two-letter codes in parentheses. This way, people who may have a hard time looking at emojis can have a text variant, and people who have a hard time reading text can use emojis.

First, we should look at the universal modifiers for the code. This, too, was inspired by the multiple code. No matter where you put these symbols in your code, it will always mean the same thing. Even if you use the emoji version of this code, you can use the regular symbol variant of these if the emojis are hard to see (which they can be on platforms like Discord.)

1. Member Count

2. Collective (or Most Common) Gender ID

If you want to specify alignment, put the emoji you're aligned with first, and then your main ID.

3. Physical Body Age

4. System Origins

While "thoughtform" and "parogenic/willogenic" roughly mean the same thing, both are included for those who prefer one or the other.

5. System Types / Modifiers

For the "general disordered" emoji, this was added because, while DID, OSDD-1, UDD/DDNOS, MADD, and BPD are the most common disorders I know of that affect or create systems, it likely is not the only one. As such, you can use this emoji if you either have a different disorder that affects your system in some way, or you may use it if you're disordered in an unspecified way, or don't want to specify by choice.

6. Collective (or Most Common) Orientation

For the mspec emoji, if you want to specify your label as bi, pan, omni, or ply, use a colored circle emoji. For bi, it's blue, or b (🎸🔵)/(MPb), for pan, it's yellow, or p (🎸🟡)/(MPp), for omni, it's purple, or o (🎸🟣)/(MPo), and for ply, it's green, or l (🎸🟢)/(MPl).

7. How to refer to your system

How to write the plural code

It may be written in just about any way, so long as you go in order, from top to bottom (of this page). With emojis, you may simply have a string of emojis with no dividers (example 1) use a side slash (/), a dash (-) (example 3), a comma (,) (example 2), or any other way of separating them. You may also choose to keep the emojis together in the same category, and only separate when going to the next one, or you may separate ones in the same category with a dash and move onto the next with a slash. (example 4). With text, it is recommended to space out the text with commas, slashes, or something else (example 5 and 6.)

If you want to specify the fact that you're using the plural code, you may put "(PLC)", "PLC:", "(👥)", or "👥:" before or after your code.

If you want to make a plural code for a subsystem, or other kind of smaller part of a system, you may add an emoji or symbol that represents it within the plural code beginning. Examples may be (🔥PLC), 🔥(PLC)🔥, (🔥👥), or 🔥👥:. Alternatively, you may put in their name before the code, as well, such as (Subsystem PLC), (Subsystem)👥:, (Subsystem👥), or however else you'd like to write it. So long as you designate it with some kind of text or emoji before the code, it works.

Examples:

• Down Arrow

Continuous improvement? Suggestions?

I do plan to possibly update this some more in the future, though I doubt I'll completely rehaul it. This code is supposed to be kept relatively simple, but I am open to suggestion and further improvement. You can send me an ask @extranth if you have anything to add.

• Home