Explore the moo:

Welcome to: Cosmic rage!

By Nathan Tech!


Web view

You are in the web view for viewing help files online in your browser.
Viewing category rp..
back to help list

rp help: The Story Weaver System

Overview

Sometimes as a player, you want to run a roleplay event of some kind which might involve NPC's, props, or even on some rare occasions, special rooms. Sure, you can build a factory or a house where these things can happen, but then how to get actual NPC's or props which could hold important clues for the people participating to use to solve your clever puzzles? In the past, you had to put in a support ticket with detail upon detail on order to get everything right. Then, a host had to be available to help run your story, and they might not even get it all right or be available when you want to do your thing. Well, the past is the past for a reason! Meet the story weaver system, a suite of roleplay tools that will allow you to create and animate NPC's, describe and teleport props around to the members of your story, and even become invisible in order to run a story which your character would not even be directly involved in. For a short time, become the host of your own story.

Key Terms

Within the story weaver systems, several key terms will be thrown around quite a lot, so we have attempted to gather all the relevant ones in one convenient list below along with their meanings.
Back stage: The location to which you teleport when you open your story prematurely. It's a useful place for you and fellow story weavers to practice with the commands and rehearse before the big day.
Cosmic Tapestry: Cosmic Rage's main timeline. The story of Cosmic Rage can be referred to whimsically as the cosmic tapestry, an overarching story which includes all pilots, enemies, planets or space stations, there timelines, etc. Most often, the hosts concern themselves with the cosmic tapestry and manipulate it from behind the scenes with news articles and headlines, invasions, and other major events.
Cosmic Loom: The nickname for the story tapestry creation wizard. Here, you enter the title, summary, description, and location of your event as well as who will be assisting you and when it will occur.
Story props: NPC's, objects, notes, etc. which you can create and manipulate throughout the course of your story.
Story Tapestry: Your particular event or story. Within your story tapestry, you can teleport props, manipulate NPC's or send messages to players or the room without having to include your name as in traditional emotes.
Story Weaver(s): The people running the story tapestry, referred to as story weavers because they are weaving their personal tapestry on the cosmic loom. A story weaver is an OOC concept as being a story weaver does not grant you extra status or powers within the IC landscape and only allows you those abilities to further your story tapestry.

How to become a story weaver

It might sound obvious, but the first thing you must do is have a solid idea for a story. Once you do, type STORY WEAVE to be placed into the cosmic loom. You must be able to fill in the following fields.
Title: The name of your story tapestry. This should be something which might catch the attention of the players and will appear on the event manager if you upload it there.
Summary: What will happen in your story? As the hosts and your fellow story weavers are the only ones who will read this, you may include spoilers or notes on how you would hope this story turns out.
Description: This is your typical IC story description. It will appear in the event manager if you upload it, and it is the method by which players can decide how they would enter your story or if they would be interested in joining it in the first place.
Location: Where your story tapestry will begin. This will appear in the event manager if you upload it and will let the players, hosts, and fellow story weavers know how exactly their story would begin or where to be in order to participate fully.
Notes: (OPTIONAL) If you have any special requirements for your story such as a room built, special objects made, or an object with special verbs on it, you would put it here. The more detail included, the better, though you may always update the notes with the STORY REVIEW command. The more complicated the request, the less likely it is to be fulfilled, especially if a coder is required to get involved.
Once you have submitted the field, you proceed to Step 2, choosing a date for the event. While all months of the year are shown, you cannot select a date in the past which means you are only able to plan stories as far ahead as the end of the current year.
Step 3 involves picking fellow story weavers. They will have most of the same abilities as you, though they cannot open, pause, close, post to event manager, or cancel your story. However, having fellow story weavers can make your life easier as you are free to roleplay while they do behind the scenes things.
Finally, you confirm everything you have entered and submit the story tapestry for host review. The more detailed you are in your requests and the more fleshed out your idea, the faster it will get approved though some correspondence within the notes section is inevitable.
To check on the status of your story tapestry, you or fellow story weavers may type STORY REVIEW.

Story Review

The story review section is a place where hosts and story weavers can coordinate using the notes function. Once the story is approved, the head story weaver can add a note, post event to manager, cancel event, and exit the review wizard. Co-story weavers may only add notes and exit the wizard, so it is up to the head story weaver to make the big decisions. Once a note is added, it appends to the end of the notes section of the story review readout.

Story Membership

Once all the minutiae of getting your story approved is out of the way, you are free to begin interacting with the story weaver system proper. As you may have noticed having read the help file thus far, all the commands are arguments to the STORY command, so this help file will henceforth refer to the arguments as commands and leave the word 'story' out of it.
OPEN: (Can only be performed by hosts and head story weaver) Opens the story in order to interact with the story weaver system's various functions. If performed before the event begins, you will be teleported to the back stage area to give you a chance to practice in private, and non-story weavers cannot join.
PAUSE: (Can only be performed by the hosts and head story weaver) Will pause your story and return everyone within the back stage area to the game if this story has been opened before the event time. If you are only practicing the commands and setting up your story, this MUST be the command you type if you do not wish to permanently end your story.
CLOSE: (Can only be performed by hosts and story weavers) The command used to bring your story tapestry to a close, thus ending it, deleting all props, and removing the event from the event manager if applicable. If you accidentally close your story, the hosts will not return it to the state it was at before you closed it as you are given a confirmation prompt warning you this action is permanent.
Invite: Allows story weavers and hosts to invite folks to their stories. Syntax, story Invite . Options include MI, JAG, SDL, GMC, ALL, and specific people.
Join: Allows someone to join a story. If it's not time for the event yet, only story weavers and hosts can join, and joining teleports one to the back stage area in order to practice story commands and prepare for the story. Once it is show time, anyone can join, though they are required to include a note which gives an IC reason for their presence in the story in the first place.
leave: For story weavers, allows them to exit the story temporarily where they lose access to all the story subcommands and moves them back to the game if they joined before the story was live. For players, permanently removes them from the story and does not allow them to join again so should not be performed lightly in an on-going story. When leaving a story, you are required to provide an IC method by which your character exits the story and would not be directly included. Often times, a reason for leaving a story is that you as the player need to log out prematurely, so it is helpful that you give the rest of the players a reason why your character is leaving to work into their roleplay. However, temporary absence from the location of the story need not be reasons to permanently leave, especially if you know you will be coming back to continue participating.

Emoting within the story

You are always free to emote just as you would outside a story, and if your character is involved, you are more than free to do so. However, story weavers get access to a few more emoting options while they are running a story tapestry which are outlined below along with case examples. All emotes written this way must be IC in some form or another.
story emote all : This will send an emote to everyone participating in the story and only those people. This is useful if there are members spread out over different rooms and you don't want to go to the effort of individually messaging them.
story emote : Does what it sounds like. If you are doing a murder mystery-type event and someone searches under the table for clues and you know they would see an interesting blood splatter pattern, you could send them a story emote. Example: story emote You notice an odd blood splatter pattern under the table as if a bloody object was briefly hidden here before being dragged away.
story emote room : Allows you to send an emote to the room without using your name. You are still able to use all other emoting tips and tricks such as matching to objects and things with $ and including your own name with %n if you desired. This could be useful if you are animating an NPC or providing on the spot ambient messages. Example: story emote room $shopkeeper lifts a rifle from behind his counter and says, "Stop right there or I shoot. Don't test me either, Ryuchi." His rifle swings around to point at $Brandon. In this case, $shopkeeper might match to a grizzled shopkeeper which you created, and $brandon would refer to Brandon Red designation, a player who is in the room.

Prop construction and use

As a story weaver, you have the ability to independently populate your story tapestry with up to ten props and move them around in order to make your stories come alive. Simply type STORY PROPS and select one of the options below. You can then move the props around with 'STORY PORT TO LOCATION>. Locations include 'here' for your location, 'person' for a member of your story tapestry, and 'storage' to remove the prop from the tapestry and place it back in storage where it began.
Retrieve props: Here, you are presented with a list of all the props in your story. You may select one or more of them by choosing them from the menu where they move into a staging area for you to bring out. Once you select the DONE option, you are required to put in an emote which may or may not include how the props come into the story. However, you are not required to include yourself, the objects, or any of the characters within the room, and your emote is displayed to the hosts. Props which must be bolted down will be moved to your location while the rest are moved to your inventory. You can then use the PORT argument to move them where they need to be.
Create props: Select a generic prop from the list you are given. You are then placed into an input field. Simply fill out the required fields and follow the prompts (if any).
Review or delete props: as with retrieving props, you are presented with a list of props in your story tapestry's storage area. When you select them, their name and description is displayed for review. Choosing yes in that prompt will add it to the staging area where selecting DONE deletes them.
Exit: Aborts out of the menu.

Miscellaneous functions

As before, these arguments will be given without the 'STORY' command, though keep in mind these are all arguments for that command.
Chat : Hosts and story weavers may need to communicate on an OOC level, so the story chat is a perfect way to do so as OTR's and ROOC are disabled for people participating in a story. However, story members can also use the chat if they need to ask something of the hosts and weavers.
Announce: (Only accessible to story weavers) Allows a weaver to send an OOC message to all story participants. Useful to respond to questions that perhaps everyone is asking.
Fade: (Only accessible to story weavers) Causes your character to become invisible. This is an OOC action which enables a story weaver to not have their character be present and is useful in situations where your character would not be involved in the story tapestry whether indirectly or at all.
port to : Allows you to teleport props to different locations such as players, your own location, or storage. You can also teleport players with their consent, but they must have joined the story first. The destinations can still be objects, players, or your location, though the player will always be moved to the room where that object is. This is useful if you need to move yourself to another location so you're ready to begin the event there or you need to move a player to a location they wouldn't be able to access suchh as a house. It should go without saying, but moving a player in such a manner is strictly out of character and should be done sparingly. The hosts are informed every time a player is moved in suchh a way.
Report : Will open a prompt for you to type a one-line note to the hosts regarding a fellow player within the story tapestry. This echo's to the hosts and sends a message outside of the game to a monitored channel, so this should only be used in emergencies and situations which the story weavers or players are unable to change themselves such as harassment, bullying, or overly graphic content or power play. From there, hosts may kick a player from the story tapestry and ban them from rejoining.

All arguments to the story weaver system

The below commands will all be arguments to the STORY command, so keep that in mind when typing them.
Story weavers...
Weave: Prepare a new story
Review: See the status of story requests and chat with the hosts
Open: Opens an approved story
Pause: Pauses an on-going story
Close: Permanently ends a story
Invite: Invite people to your story once it is open.
announce : Sends an OOC announcement to all participents from the story weavers.
Emote : Sends an emote to the target whether it be everyone, a single person, or the room.
PROPS: Opens the prop manager.
Port or to : Silently teleports props or people around between your location, story members, and (in the case of props) storage to remove it from play.
Fade: Toggle your invisibility.
Story members...
Join: Joins an on-going story
Leave: Permanently leaves a story
Chat : talks on the story chat
Report : Opens the report prompt to poke the hosts about a fellow player.

Shortcuts to certain story commands

These commands can be typed without the story command.
stemote : Shortcut for story emote
stc : Shortcut for the story chat command.
Recommended help files: Help Event.
--------- End of file -------
Back to the top of the file
Back to help file list

Why not explore the moo!

Explore the moo:
Back to the top

Thank you for visiting!

Thanks for visiting this page. Please tell your friends about us!

You are visitor number 924 to this page since November 3rd, 2018.
Why not follow us on Twitter: @NathanTech7713

Nathan Tech

It's not disability

It's ability!

Last updated Wednesday 20th November 2024 03:55:37
Copyright © 2013-2024 Nathan Tech. All rights reserved.