- 1 Adult Content
- 2 Advancement
- 3 Age
- 4 Alts
- 5 Aspirations
- 6 Books
- 7 Building on the MUX
- 8 Cheating
- 9 Consent
- 10 Core Themes
- 11 Experience
- 12 Experience Transfers
- 13 IC Leadership
- 14 IC Time
- 15 Idle Timeout
- 16 Player Builds
- 17 Player Ethics
- 18 Player Run Plots
- 19 Player Versus Player
- 20 Respec
- 21 Staff Ethics
- 22 Vitae
The following policies are in place on the MUX. All players are expected to read and abide by them.
Echoes in the Mist is a game for adults, with themes and images of a mature nature. As such, it is not unlikely or against the rules for roleplay of a sexual or violent nature to occur. However, we do ask that you respect your fellow players.
Read the full policy text.
Before engaging in any sexually explicit roleplay, please receive OOC consent from everyone involved or who is in the location of the scene. Likewise, violence is a common occurrence in the IC reality of Echoes. While the existence of violence does not require consent, please note that all players have the right to limit the amount of actively-roleplayed violent descriptors.
Discussions of an explicit sexual or violent nature should not be held on public channels or in out of character areas.
Staff or Player-Run plots that are expected to contain mature themes should be labeled as such whenever possible, though all players should be aware that this is a World of Darkness game, and mature themes can occur without warning.
The following policies apply to posting adult content on the wiki:
- Logs which contain mild nudity or innuendo do not require labeling as NSFW.
- Logs which contain explicit sexual activity should be marked as NSFW.
- Logs which contain mild violence do not need to be labeled as NSFW.
- Logs which contain extensive but vague violence (most lethal combat) do not need to be labeled NSFW.
- Logs which contain graphic violence (torture, more descriptive and brutal combat) should be marked as NSFW.
- Logs which contain sexual violence (rape) should not be posted on the wiki.
- Logs which contain on-screen violence or sexual activity involving minors (characters or NPCs below the age of 18) should not be posted on the wiki.
- Images of nudity (exposed female nipples, exposed genitals, exposed buttocks) may not be posted on the wiki.
- Images of a graphic sexual nature may be linked to but not directly shown on the wiki, so long as they are clearly labeled NSFW.
Staff is the final arbiter of what constitutes graphic or explicit content.
On Echoes, to reflect the learning process of new abilities while still allowing players to spend their XP more or less as they wish, the following policies apply.
Read the full policy text.
All traits may only be raised freely, with a few notable exceptions. These include:
- Power Stats: Blood Potency and Primal Urge are handled a bit differently on Echoes. The formula for determining the waiting period before a Power Stat can be raised is, in simple terms, [Desired Level] in months. For example, a vampire with Blood Potency 2 would need to wait 3 months to raise it to 3. This waiting period may be lowered by one month with the submission of at least two logs that show actual roleplay of the character's effort to advance their Power Stat.
- Supernatural Powers: A character may raise an individual Discipline, Renown or Supernatural Merit (i.e. Telekinesis) once per month.
- Renown: With 'Thorough' justification, a character may raise an individual Renown with no wait time. With 'Minimal' justification, the wait time is [Months x Current Level].
- Devotions: A character may learn up to 2 Devotions in a month.
- Gifts: A character may unlock up to 2 Shadow Gifts in a month.
- Tells: A character may learn up to 2 Tells in a month.
- Fighting Merits: Merits designated as 'Fighting Merits' may be raised once per month.
- Status: A character may raise an individual Status once per month. These are not free on Echoes in the Mist.
Note: Some trait increases will require that certain IC situations be met, such as out-of-clan Disciplines needing a taste of appropriate Vitae, Shadow Gift unlocks requiring a PrP, etc. Except in the case of restricted stats, players may purchase multiple levels at a time, but each intervening level must be paid for and IC prerequisites met. Staff reserves the right to deny a request to raise a trait by multiple dots at once, if they feel it is unrealistic or ICly unfeasible.
Important: Wait timers for Power Stats and Renown begin at character approval.
By logging on to the game, you acknowledge that you are a legal adult in the jurisdiction in which you reside. All player characters on the MUX must be physically and emotionally eighteen years of age or more, and may not be depicted otherwise in text, image, or any other manner.
Echoes allows players to have up to five active characters, with some restrictions.
Read the full policy text.
A player can never have more than one character as a member of the same IC organization, including but not limited to the Portland Police Bureau, any pack, coterie, Tribe, Clan, Covenant, Lodge or any other organization.
Should on-grid situations result in a violation of this policy (Embrace, First Change, involvement with a group, etc), the player has one week to freeze characters of their choice or respec them to remove any conflict.
A player can have one super in each sphere (Werewolf or Vampire) and one 'support' character in each sphere (Ghoul, Thrall, Wolf-blooded) -- but the latter cannot share any IC or OOC things in common with their super character (same groups, etc). Players may have 2 Mortal+ characters, and as many mundane humans as they like, up to the max of 5 characters allowed for the game.
Players cannot have any meaningful IC interaction with the same character or organization across multiple characters. Casual social interaction is fine, but in no way can two PCs of one player both have significant ties, or benefit from, the same character or group.
A player may never have multiple characters in the same scene. A player may have multiple characters involved in the same ongoing plot, but never in any individual scene.
At any given time, you should have one (1) Long-Term aspiration - this is something that will take multiple scenes or possibly an entire arc to fulfill. Additionally, a character should have two (2) active Short-Term aspirations. These are goals that either will not take multiple scenes, or are not goals that are meant to be difficult for your character to accomplish over time.
Progressing or fulfilling an aspiration.
When you fulfill an aspiration, it needs to be done on screen or via job. For example, if your aspiration is to meet the County Medical Examiner, this should be roleplayed out. If your aspiration is to discover the ban of Monstro, the spirit of Birds and Knives, this could be handled via a research job.
When an aspiration is fulfilled or significant progress is made towards an aspiration, a Beat is awarded. Progress must be significant - if your aspiration is to become a world class dancer, buying a dot of Expression counts, but if your aspiration is to live forever, waking up in the morning does not. If a short (or long) term aspiration is fulfilled, you may immediately chose a new aspiration. You may also request that an aspiration be abandoned, though this may require a convincing argument. Valid reasons include, but are absolutely not limited to, loss of Integrity/Humanity/Harmony, major IC changes, an aspiration becoming impossible, etc.
The Following Books are considered to be in use. If you have a question about material presented in another book, please contact staff with questions.
Read the full book listing.
- Chronicles of Darkness, 2nd Edition
- Chronicles of Darkness: Hurt Locker
- Werewolf: the Forsaken, 2nd Edition
- The Pack
- Lodges: The Faithful (Lodge Themes)
- Lodges: The Splintered (Lodge Themes)
- Tribes of the Moon (Lodges Themes)
- Vampire: the Requiem, 2nd Edition
- Secrets of the Covenants
- Clanbook: Daeva
- Clanbook: Gangrel
- Clanbook: Mekhet
- Clanbook: Nosferatu
- Clanbook: Ventrue
- Ancient Bloodlines (Select Bloodlines Theme Only)
- Bloodlines: the Hidden (Select Bloodlines Theme)
- Bloodlines: the Chosen (Select Bloodlines Theme)
- Bloodlines: the Legendary (Select Bloodlines Theme)
- The Invictus (Select Bloodlines Theme)
- Carthians (Select Bloodlines Theme)
- Ordo Dracul (Select Bloodlines Theme)
- Lancea Sanctum (Select Miracles and Select Bloodlines Theme)
- Circle of the Crone (Select Rituals and Select Bloodlines Theme)
- World of Darkness: Shadows of Mexico (Select Bloodline Theme)
Building on the MUX
Here on Echoes in the Mist, we welcome the idea of players creating their own personalized builds for the grid. Whether it's a business, a group hangout or a private residence, so long as it fits into the general theme of the game and doesn't fly in the face of quasi-realism, all you need to do is ask!
Read the building policy and process here.
Well, that isn't exactly true. All you need to do is ask, and desc the damned thing.
Breaking it down, here's the process:
- Decide what the building should be called. As an example, we'll use Murder House.
- Decide what area of the grid the build should be linked to, such as Central Eastside or University Park. If you need guidance on what sort of neighborhood your build would be best suited for (i.e. you wouldn't want a mansion in a crime-ridden district or a junk yard in an upscale residential area), ask! We're happy to help.
- Decide what the layout of the building should be. How many rooms are there, and what should each be called? How do those rooms connect to one another? Please note that although we do not strictly link Resources to the size of build you can have, there'll have to be a very good reason why your Resources 0 hobo is requesting a 10 room mansion.
- Put in a request with the above information. For example:
+request Build = Hi, I'd like a building please. It should be called Murder House and needs to be linked to Hazelwood. The layout is Lounge leading to Kitchen and Upstairs, then a room from Upstairs called Master Bedroom, and a room from Kitchen called Cellar.
- Wait for a short period of time until a staff member sets up your project in the Build Nexus. The staffer will approve the job with directions on how to get to your build, and what your next steps should be.
- Add descs to all rooms and exits. Room descriptions must always begin with %R%T. Separate paragraphs with %R%R%T and tack a single %R onto the very end of the description. Please check your descs for correct spelling, and break up any paragraphs longer than 4-5 lines for readability. Exit descriptions are not strictly necessary, but can be helpful in certain circumstances. These only need to be a brief sentence, like:
There is a circular staircase of wrought iron going up to the second floor.
- When all is finished, submit a new +request to staff, letting them know that your build is ready to be inspected and linked to the grid. If everything looks good, it will be moved from the Build Nexus to the location originally requested, and you'll be all set!
IMPORTANT: Roleplay is not allowed in the Build Nexus. If you need to simulate being in your as-yet-nonexistent property, please make use of our Temp Room Nexus, off the OOC Lounge.
Certain behavior will not be tolerated on Echoes in the Mist. This behavior includes:
- Violating any core Game Policies such as age or mature content.
- Deliberate attempts to deceive others in regards to the rolls or capabilities of a game mechanic.
- Attempts to infringe on the privacy of other players.
- Deliberate attempts to mislead or deceive staff.
- Harassment of players or staff.
- Any egregious behavior not covered above.
The MUX is neither entirely consent-based nor non-consent; it's a hybrid of both. The consent policies are in place because the point of the game is for the players to have fun. Some subjects are fun for some, and absolutely not fun for others.
Characters on the game may be adversarial, but players should not be. While we do not expect every player to be BFFs with every other player who frequents the MUX, we do expect - even require - players to negotiate, collaborate, and work toward ends that are mutually agreeable to the players, whether their characters like this outcome or not. IC/OOC separation is crucial.
When we refer to consent in policy, we're talking about the player's consent, not the character's.
Look to the spirit and intent behind these exceptions in addition to the letter of the law, because that's what staff will be doing if concerns are brought to us, and it would be ill-advised to consider this list 'pure letter of the law' or comprehensive. If something that falls outside of what we've directly addressed in policy, we'll try to address it with a definitive answer promptly.
Trying to rules-lawyer this policy does not look good for anyone making the attempt from any direction; don't.
It's important to be explicitly clear about what you're expecting from the IC relationship if you're expecting anything other than "whatever happens, happens, and anything goes." If you're not interested in playing a cuckold? Tell the other person. If you're not interested in playing lovey-dovey everything is fine forever romance? Tell the other person. If you're not interested in your character falling in love? Tell the other person. If you are interested in falling in love at the speed of light, getting married, and having three babies via magical pregnancy so you can pop'em out in two months? Tell the other person.
And if you change your mind regarding any of the above (or any other conversation like them) - tell the other person.
If you are not clear in communicating your expectations, but you have expectations other than 'anything goes', then when you are disappointed by the other person not meeting your expectations, it is your fault.
The subjects listed below require OOC consent without exception. They have been carefully selected due to the profound discomfort they cause some players when the issue is forced. This list represents the subject matter that staff has determined to be reasonably objectionable enough when forced on other players to require consent by default.
Other scenarios may arise that require consent.
It is important to note that character death is not, and will not, be added to this list, nor will 's/he's not allowed to leave me!'. Nor will injury, intimidation, and so on. (Some players are discomforted by not winning all the time, for example, and we don't find this to be reasonable.)
Some subjects may require a +note to be set on the character with a record of what has been agreed upon amongst the involved parties, as it may affect roleplay going forward. In these cases, please submit a request so staff can properly review and approve the +notes for you.
Sexual and romantic relationships and the roleplay thereof are wholly subject to OOC consent. Consent is required. Not only that, continued consent is required. When someone wants out, they're out. It's over. If they ask you to leave them alone OOC, do it. This is a situation in which OOC comfort and continued peace on the game trumps IC reality if it becomes necessary.
Sometimes relationships have IC consequences that are noteworthy when they come to an end. The IC relationship between an ghoul and their regnant, for example, is not balanced or equal, but as players, both are equally important and have the same rights.
We will work with the players involved and try to determine as reasonable an outcome as possible if this occurs, but we will not force punitive losses on one or the other player, even if it's thematic or 'justified', just because someone didn't want the other person to leave, or because they left due to OOC discomfort with the other player.
Refrain from being a jerk about this, and do not ask staff to be a jerk for you in this regard.
Lastly, you don't get to 'no consent' to someone leaving your character for someone else's character, or insist two other players must, or may not allow, their characters to get involved. This should be common sense.
Subject matter that would normally be considered 'taboo' requires direct player consent before you proceed. The only absolutely forbidden taboo with zero exceptions is underaged sexual situations. As to the rest, we leave you to your own devices, and the consent system. (Note: Rape is still a forbidden element in PrPs. Period.)
- Do not assume something is fair game in roleplay because you've had an abstract discussion with the player about it in the past and they didn't immediately pagelock you or freak out. That's not the same thing as getting consent.
- Do not assume something is fair game in roleplay because it's not a big deal to you.
- Do not assume your personal fetishes or predilections are so well-known that someone consents to them by default because they have chosen to roleplay with you.
- If you want to go somewhere in a scene that involves any sexual taboo, ask first.
Staff in no way wishes to police your roleplay. Frankly, we'd rather stay well removed from it, and trust you all to behave like mature, conscientious adults. Gaining consent may seem like an extra hoop to jump through, but it will help to prevent problems down the road (and likely save Staff from needing brain bleach).
A change of template or becoming cannot be forced on a character without the player's consent.
This sounds like common sense, but it isn't. Circumstances in the game world, and the system itself, can allow for this to happen. If the player is content with the change, or would like to pursue the roleplay, they're welcome to do so.
The staff magic of handwavium will be applied if the player is not interested this change if necessary. Players create the character they want to play; if they wanted the character to be a different type, they would have made them that way or would have applied for a becoming. Further, as there are alt restrictions by template, this could potentially force someone to freeze or abandon the character or another character they don't wish to sacrifice.
This is a simple check and balance to reflect the difference between the way a game is traditionally played in a tabletop environment vs. how a game is typically played on a MUX.
Players create the character they wish to play, with the personality they want the character to have.
Brainwashing, mind control, and similar methods to completely rewrite the character's personality into something vastly different for an extended period of time are subject to player consent.
Consent is not required for circumstances to cause a PC to do something out of character. Consent is required to cause a PC to become a completely different character for any extended length of time.
For example, circumstances may require a normally law-abiding and honest character to steal something; that's a single action, which may be ICly coerced without the player's consent. This is the kind of personal challenge and hard choice encouraged by the system and embraced by the game.
What is not permitted is this: "Your normally law-abiding and honest character is now my willing and eager thief sidekick until I say otherwise. The dice say so, and you don't get a say." This is where player consent comes in. If this sounds like fun to the player, they can grant consent and run with it. If it doesn't - bearing in mind that if the player wanted to spend their time playing an eager thief sidekick, they would have made one in chargen - this will NOT occur.
Important Note: This does not mean your character cannot be deceived, intimidated, charmed, frightened, ignored, impressed, disbelieved, and many of the other things people seem to think can never possibly mesh with their character's personality that are the primary complaint regarding 'twinking through consent'.
All of the above can happen on a transient basis, provided it does not violate other consent subject areas. Someone simply cannot completely change your character's entire personality permanently, or for an extended period of play, without your permission.
Consent of both involved parties must be confirmed for an IC pregnancy to occur.
Consent of both involved parties must be confirmed for any dramatic change in the pregnancy.
- No springing trauma drama miscarriages on anyone, ever.
- If a falling out occurs between the players, and the character of the female character does not wish to continue the roleplay, or it is determined that consent to end the pregnancy is being withheld out of spite or complete disregard for the other player's enjoyment of the game, it will be retconned with the magic of hocus pocus medical jargon handwavium by staff.
Consent is required from anyone participating or subject of a lost pregnancy before roleplay regarding these events may occur around them. This is similar to the rape clause, and exists for the same reason; even if you and your RP partner agree to have a miscarriage or otherwise end the pregnancy, do not subject third parties to the fallout without their consent.
Roleplay of sexual assault is wholly subject to OOC consent among all parties involved. This includes characters informed or asked to participate in investigations or recovery efforts after the event itself has occurred. This is the standard rape clause. 'Sexual assault' is a fairly broad category - we're going to go by the general definition of 'any unwanted sexual contact.'
Roleplay of this type cannot commence without OOC consent from the target and it must be clearly stated and recorded.
If you consent IC and OOC to either of these things and then later cry, 'RAPE!', there is likely to be a problem. Unless the other player crossed the line by extremes and has been told as much by you at the time, that problem is not going to be for them.
If you have an issue, you need to speak up.
Consent must be gained to involve others in the aftermath of sexual assault RP. This includes investigations, recovery efforts, evasion, and similar subjects directly related to the event.
It doesn't matter what someone's preference is in this regard, and whether the player's preference matches the character's or not. Consent is required if you want a character to act contrary to their IC sexual preference.
It is not intended to prevent people from flirting IC, from friendly joking around IC, or using IC means of determining if another character is interested or not without force in the form of IC physical force, the application of powers, or other dice-rolled methods. Casual flirtation, or IC attempts to discover if something more than flirting is welcome without mechanical system-based force, do not require consent.
Fade to Black
All players have the absolute right to request a scene Fade to Black, or Fade to Summary.
This choice can be made for a variety of reasons: discomfort with the subject matter, limited time, or a lack of desire to roleplay a basic activity that isn't of special interest, or is otherwise commonplace or rote.
Fade to Black Posing stops. Rolls are made if required. OOC discussion determines the outcome of the scene.
A Fade to Black can come about due to the above actions, in which the outcome is assumed due to the basic nature of the activity. More importantly, fade to black can be invoked to avoid posing subject matter one or more players find uncomfortable to pose in depth.
Players may agree on a final outcome, and as above, this outcome is what has actually happened to the character. If an outcome cannot be agreed upon, the necessary rolls are made to determine the outcome of the scene. Whether determined by rolls or negotiation, the results are binding, despite the fact that they have not been posed, and have only determined by OOC means.
Fade to Summary Posing stops. Rolls are made if required. OOC discussion determines the outcome of the scene. The scene is posed in a very limited fashion, usually for purposes of clarity in the log, with a single pose from each necessary participant summarizing their actions.
The negotiation process works the same as Fade to Black, but the players agree to write a brief summary pose encapsulating the final outcome. Some players opt to do this in cases in which the scene is logged, for clarity or completeness.
It is not required or preferred to Fade to Black; it's entirely up to the players involved to choose which they prefer.
Solutions that generate mutually awesome roleplay are generally encouraged over those that make further RP (even if it's that the characters never interact again but are able to do so with others) impossible. Actions that remove a character from play should be a last resort, not your first go-to option. Actions that would certainly have a lasting and negative impact on another player's ability to enjoy their character should, likewise, not be your primary aim.
If there are viable alternatives that will satisfy the player's goals and they're specifically dead set on that one that you can't live with, and it's a valid consent topic? It's time to call in a staff member to mediate and see if things can be worked out.
Mediation is no guarantee things are going to go the way either person wants them to, but it is an important check and balance.
If someone is aware they're trying to pull something fishy, they do not want observers present - particularly observers who must be impartial.
This is handled no differently than any other +timestop. It means rolls and roleplay stop immediately, and a +request is put in for a staff storyteller to oversee the situation. Either player - target or aggressor - has the right to request this at any time and the moment it is requested, it must be respected.
Like any timestop, this means a few things:
- Someone may not be immediately available and you may have to wait.
- No roleplay can proceed with any of the characters involved until the timestop is resolved.
- If it has to be picked up at another time, this may have to be scheduled and it may take a while to find a time everyone is available.
- Some issues may be able to be resolved or determined through the +request job. This is a real option and may help resolve the issue, especially if schedules are not particularly cooperative.
...so, really, you can probably see why we'd really prefer people act like adults and work things out respectfully amongst themselves.
"I'm not going to wait for that! We need to do the thing this way now!" is not going to fly. Nobody gets to bully their way through by using the additional work and wait as their reasoning. "If you don't give me my way, I'm going to call for a timestop!" is also a Darwin-Awards-level bad idea.
Bait and Switch
Be clear in what you are asking for when requesting a scene or storyline from another player. Don't request one thing, then do much more, without consent for the additional material.
Be clear about your stated goals and what you're asking of the other player.
Don't ask for a scene that involves casual flirtation and then, after they say yes, zip right along to violent rape and think you're in the clear because they consented! - because they didn't consent to that.
If someone agrees to an inch, you don't get to take ten miles. You get that inch, and that's it.
You want the rest, you ask for it, and they get the right to say no, no matter what they've agreed to previously, and no still means no, no matter what they've agreed to previously.
If the parameters are not clear, clarify.
If circumstances change, clarify along the way and record it.
Echoes in the Mist is designed with 5 core themes in mind. These are not the only possible themes one can explore in the setting, but will be the core foundation with which Staff approaches the game.
Read about our game's themes.
Tigers and Bears
Kindred and Uratha inhabit the same world. A MAD world. Mutually-Assured Destruction. Both are apex predators. Both share a hunting ground. But they must coexist. Thankfully, they hunt different prey. Sporadic violence between vampires and werewolves is as inevitable as sporadic violence among vampires and among werewolves (and among humans). But an all out, large scale war is unthinkable to both. They have almost nothing to gain, and everything to lose.
- This Core Theme applies when members from more than one Sphere are present in the scene, for good or ill.
More Things in Heaven and Earth
What you don't know will kill you. Besides Kindred and Uratha, the World of Darkness is a panoply of the strange and the unknown. Cursed trinkets, shadowy life thieves, prehistoric murderfish and so much more lurk in the dark. While the Kindred and Uratha fancy themselves the top of the food chain, there are places so dark and unknowable that even they fear to tread.
- This Core Theme applies when elements introduced are beyond the scope of the characters' prior experience.
Blood Always Spills
There's always a cost. Amazing strength and senses come with a hair trigger temper. Immortality comes with hunger. Nothing is for free, and there is always violence or loss as a possibility.
- This Core Theme applies when there is a significant risk - or occurrence - of violence or loss in the scene.
At Night, the Ice Weasels Come
There is an absurd quality to the world. Things can be funny, and they can be painless. But truth is stranger than fiction, and in the World of Darkness, oddity is a little more exposed. From the occasional monster out of a B-Movie to an ancient order of Samurai Schoolgirls, there is room in the darkness for a little light, but what is revealed is rarely pretty.
- This Core Theme applies when the unique and bizarre (and sometimes funny!) are highlighted in the scene.
Death and Rebirth
Nothing lasts, and everything changes. Sometimes change is positive, a city grows, a bank account increases, a predator secures fertile hunting grounds. Change can be negative. A cancerous growth, urban decay, financial collapse. Portland is a city constantly cycling through cycles of Growth and Decay.
- This Core Theme applies when change - for better or for worse - is a significant element of the scene.
Experience on Echoes in the Mist will be earned through three primary methods.
- Once per week, each active and approved character will be awarded 1 Experience.
- Each character also has the option of earning up to 2 further Experiences by participating in Plots and earning Beats. If your character encounters a situation where a Beat should be granted, such as via a Condition, it is the responsibility of the player to open a request as soon as possible via the +beat command, and explaining how the beat was gained.
- Running plots or scenes for others to participate in. See our policy on player-run plots here. Important note: Experience gained by running a plot does not count toward the 3xp cap per week. This is to encourage people to run plot for their fellow players often.
On Echoes in the Mist, we understand that sometimes a character simply doesn't work out. A player can't get a feel for it, or it runs into situations that make it less than enjoyable - or even impossible - to play. Hell, a character can even die. In an ideal world, the time and effort a player invested into that character shouldn't simply be considered a wash. This is where XP transfers come into play.
However, some restrictions are necessary.
Read the full policy text.
- First, the source character must be permanently retired. That means never coming back to this game in any way, shape, or form.
- The retired character must have some verifiable evidence of activity prior to being frozen. This is to prevent players from creating alts and letting them sit idle, 'farming' experience for a future alt. If it is suspected that this is the case, Staff reserves the right to deny a transfer request. Participation in plots and events, non-automatic Beats being earned, logs posted to the wiki, et cetera, are all examples of such 'proof of activity'.
- You may transfer 100% of your dead or permafrozen character's earned experience to a new character.
- The transfer must be directed to a fresh character that has not yet been approved. There will be no experience transfers to approved PCs. Don't even ask. Additionally, new characters may only receive transferred experience from one permanently retired character.
- Transfers are only allowed in any direction, lateral or otherwise. In other words, so long as you can show evidence that you have been active with your Mortal, you can transfer that experience to a fresh Werewolf.
- This experience is set in place of the normal starting experience, and you cannot still earn an additional 5xp by writing a background for the transfer-recipient. Other incentives may apply when appropriate, however.
Positions of leadership in In Character organizations are demanding, both from an IC and an OOC perspective. In an effort to make sure that power is not being abused or neglected, staff asks that anyone in a position of leadership remain in communication with Staff about the status and direction of their organization.
Holding Status at 4-5 dots is considered to be in an IC leadership position. The following is a list, albeit not necessarily comprehensive, of what organizations are subject to this rule.
Read the full policy text.
- Mystery Cults
- Lost Boys Network
Small PC groups such as packs or coteries are not subject to this policy. The leader of any of the above groups (generally the one with the highest Status), will be queried no less than once and no more than twice a month to check for activity. Secondary positions will also be queried on occasion, such as if the faction head is non-responsive, on vacation, or there is a conflict of interest.
If there is deemed to be an OOC lack of responsibility or ability to organize a faction, then staff may intercede. Possible responses range from the institution of a new PC faction head, a NPC faction head, or a measure suitable for the situation.
The purpose of this ruling is not to prevent IC leadership of organizations, but to prevent any obstructions relating to players joining organizations and to help ensure that said organizations thrive.
Some merits and abilities are only usable at certain time intervals, or have a specific duration. Terms like 'session,' 'chapter,' et cetera make more sense in a tabletop setting, whereas time works differently on a MUX. Here on Echoes, the following can be used as a guideline for how long each of these subjective time measurements are:
- Turn: 3 seconds.
- Scene: 3 hours, or until the current scene ends.
- Session: 1 day.
- Chapter: 1 week.
- Story: 1 month.
We do not expect that all players can log in to the game every day, or even every week. Approved characters that go without logging on for 30 days will be unapproved and frozen; these characters may return without penalty but will not accrue experience while frozen. Characters that have never gone through the character generation process will be @nuked after 30 days of idle, in order to free names up in the system.
While player builds are not inviolable and should not be used as places to escape to where nothing bad can ever happen, there is a level of etiquette associated with running a scene using a build that somebody has spent time and effort making. Below are the rules we would expect STs to follow.
- Seek consent. The owner of the build must give their consent, or the build wizard should give their consent. This must be obtained before the plot is run using a player-owned build.
- Be respectful. A plot using a player-owned build, while it may cause some damage, should not wreck hours of work on a whim. Irreparable damage to the building or noted items within the building should be avoided at all costs, unless prior consent has been given which includes the acceptance of this damage beforehand.
- Show gratitude. Notify staff as part of your scene submission that a player's build was used, and we may give a discretionary award of XP to the build owner.
We expect Echoes players to behave as mature, responsible adults. This means, at a bare minimum, following the policies laid out here, and treating one another and staff with courtesy and respect out of character.
Player Run Plots
Players on Echoes are encouraged to actively run scenes for others. To this end, Staff will provide multiple Story Seeds originating from various NPCs. These, however, are not the only plots capable of being run by a player. Aside from the following exceptions, players have significant leeway to run a plot.
Read the full policy text.
Forbidden and Restricted Elements
- The God Machine
- Other Splats' Realms (Hedge, Supernal, Abyss, Etc.)
- Child Abuse
- Gods (Rank 5+ Ephemerals)
Restricted Plot Elements
While allowed, these plot elements require pre-approval of Headstaff to be used:
- Staff-Featured NPCs
- Rank 4+ Ephemerals
- Rank 3-4 Idigam
- Destruction of Grid
- Other Splat NPCs (Mage, Changeling, Etc.)
- Other Splat Antagonists (Banishers, Abyssals, Etc.)
- Packs of Pure or Bale Hounds
- Coteries of VII
- Groups of Strix
- Coteries of Belial's Brood
Does Not Require Approval
- Rank 1-3 Ephemerals
- Solo Pure or Bale Hound
- Solo Strix, VII or Belial's Brood
- Custom Monsters
Desired Plot Elements
- Scene involves four or more Player Characters.
- Scene features some noteworthy real-life Portland element in a significant fashion.
Note: Merely basing a scene in an actual Portland location does not qualify a scene for this reward.
- Social challenges, from Trivia Nights for bragging rights to City Hall favor-exchanging scenes.
- Non-Combat Physical Challenges.
- Mental Challenges, from police investigations to puzzle solving or book searching.
- Scene is comprised solely of characters with minor templates (this can include Wolf-Blooded and Ghouls).
- Mortal Cult-Specific Scene
- Scene involves the Supernatural
- Always the Little Guy: Scene features a situation or challenge that's over the characters' heads.
- Feed or hunting scenes, dice rolled or not.
- Scenes upon which a vampire meaningfully interacts with her Touchstone.
- Political Scenes where pacts and bargains are struck to further someone's aims.
- Covenant-specific Scene. Only scenes that touch upon Covenant-specific themes qualify for this Beat.
- Scene features interaction between multiple members of a Coterie.
- Hunt or Chase Scene
- Spirit Interaction
- Scene features Territory as a predominant theme.
- Interaction or coordination with members of another pack.
- Incorporation of one or more Rites in the scene.
Storytellers and PCs participating in plots gain certain rewards. No one award is eligible more than once per scene. When submitting a log of a plot, please note what rewards are eligible. All rewards are equal to 1 Beat. Plot rewards for the storyteller will be granted as player experience, which can be transferred to any of the storyteller's registered alts. You can only earn 10 Beats (2XP) max from player run plots in a week.
- Core Themes: Scene features one of the game's Core Themes.
- Open Invitation: Scene is made available for anyone to participate in, or anyone in a specified Sphere.
- Pre-Approval: Scene is pre-approved by Staff. This usually applies to plots posted as +events.
- Plot Finale: Scene is the final step of a multi-scene plot.
- Danger Zone!: Scene involves genuine physical, mental, or social risk to the characters involved.
- Desired Elements: Scene has one of the Desired Elements above. A character can claim two Generic Beats and one Sphere-Specific Beat.
- New People Into The Plot: Scene provides significant IC information designed to draw others into a pre-existing plot.
Submission To make things easier on both Storytellers and Staff, the following is an example of how plot/event submissions should look:
- Log is posted at: http://portland.echoes.wiki/fakelink/
- Storyteller: Ecliptic
- Participants: Moonshrimp, Sasquatch, Blackwater, Harvester
- Rewards: Core Theme: Tigers and Bears, Desired Element: 4+ Player Characters, Open Invitation, Soundtrack, Pre-Approval
- Projected Beats: 5
You could write the request up manually using the following template:
+request Plot: <plot name here>=%R%xhLog is posted at:%xn <link to log>%R%xhStoryteller:%xn <name>%R%xhParticipants:%xn <list of names>%R%xhRewards:%xn <list of eligible rewards>%R%xhProjected Beats:%xn <total of beats>%R
OR... Make your life even easier by using the amazing interactive form that Ecliptic coded up, that has drop-down menus and spits out the +request for you and everything! (Srsly, save yourself the headache and use it.)
Player Versus Player
There are splats in place on Echoes that at times, historically, have been at odds with one another. We want to state, clearly and for the record, that Echoes is not a PvP game. Players from differing spheres should never be afraid to interact ICly with each other, unless their PC is clearly engaging in behavior that would force a response from someone of another template. There will be zero tolerance for PCs targeting each other simply because "He's a <template>!"
To reiterate, however, this does not protect PCs who behave in a blatantly monstrous way, corrupting and/or maiming anyone in their path, or run around gleefully breaking the Oath of the Moon or breaching the Masquerade. If you want to play this out, have at it! But if you get caught? Whatever happens, happens, and we will all deal with it accordingly through +jobs. ICA=ICC.
At the end of the day, nobody is forced to RP with people they do not wish to, so this can and should be used to your advantage, with the caveat that this cannot be used to escape or avoid consequences for your previous IC actions.
We all make mistakes. A character may opt to have their sheet wiped and all experience and starting points redistributed.
This is possible under two circumstances:
- The adoption of a Supernatural template, or
- Once in the character's lifespan, within 3 months of character creation.
Additionally, during the first month following a character's approval, a player can request that a mild alteration to their sheet be made. A reason for this free alteration must be given, such as "I did not realize that Dominate required the Expression Skill" or "I confused Resolve and Composure."
A respec cannot change any innate features of a character, such as Auspice, Gender, Age, Clan, Bloodline, Lodge, Supernatural Template, Covenant, or Tribe. Covenants and Tribes are social institutions that can only be left through IC action.
Staff on Echoes in the Mist are expected to hold themselves to a high standard of ethical conduct. Staff is not to infringe on the privacy of players or to abuse their power. The purpose of staff is to facilitate an environment where people can roleplay and enjoy themselves, as well as to process and maintain the virtual infrastructure of the game. Staffers are not to use their powers to spy on others, or to gain access to information that is not related to their duties as staff.
Staff members are forbidden from processing any non-automatic job created by the player character of someone they have a significant IC interaction with (Packmate, Regnant, Significant Other, Nemesis) etc. Staffers are forbidden from processing ANY jobs from their own character.
For the purposes of these rules, non-automatic jobs are any in which the slightest degree of judgement is necessary - anything but valid XP spends.
Vitae is the most potent addictive substance in the World of Darkness. A single taste can change the course of a life (or unlife). Whenever a character tastes the blood of a Kindred, it must be documented. This is to ensure that it is properly noted who has an Addiction to Vitae, what vinculums are in play, and who is a thrall to whom.
Characters who are addicted to vitae immediately gain the persistent condition, Addicted. Characters who are under a blood bond function as described in Vampire: the Requiem 2nd Edition, page 100.
This information does not need to be made publicly available OOC - if a character possesses a blood bond or vitae addiction, they do not need to share this unless it is relevant to an occurring scene.
All ghouls are considered to begin play under a full vinculum to their regnant, unless the ghouling process occurs on grid, post-approval.