Writers Guide

Preamble

So, I see you've stumbled upon the RPC Database. This place is filled with numerous anomalies that are dangerous or outright disturbing, and you found them fascinating? Well, this is definitely the right place to come if you want to learn how to write one! This writing guide is here to ensure that your idea becomes a reality (though, hopefully not physically).

Now, please remember, we highly encourage you to read through a good chunk of the articles to have a clear understanding how things are done around here. Without further delay, let's get to it.

Considering Some Things Before Beginning

Before we actually get onto the concept, there are a few things that one has to consider:

  • Is the concept interesting?
  • Is the anomaly's containment class and threat indicator appropriate?
  • Are the containment protocols appropriate and rational?
  • Is the anomaly well described?

It's highly necessary and recommended for writers to follow these four pillars to allow the reader to have a sense of understanding of how the anomaly functions as an article. One should endeavor to draw the reader in, not push them away with needless clearance restrictions or how the reader should stay away from the article due to the dangerous properties that the anomaly exhibits.

It's quite understandable that articles, like yours, would not exactly be successful due to the writer having issues with execution or simple lack of experience. Regardless, your first article may either be a success or a dismal failure. Remember, don't take the article as a reason to give up; use it to fix your mistakes and not repeat them.

Now, to avoid your idea getting thrown to the hounds, ask for feedback on the idea from the community in either the Forums section or in the Discord server. Remember, don't ignore feedback even if the person's comments aren't very detailed. Being told "It's boring" can sometimes help improve an article to the point that "It's fascinating."

Lastly, if someone is a bit… harsh on your concept, please don't hesitate to contact a Curator or a Moderator if this behavior is continual.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License