Jump to content
FlamboyantNewEra

Lore Sub Guide 1: Categories and Formatting

Recommended Posts

Lore Sub Guide 1: Categories and Formatting

The lore submission rules and guide exists in order to help organize lore on the server and make sure that every submission has the minimum requirements that the LT is looking for. This particular thread goes over the categories of lore submissions and their required formatting. Each category comes with some background information, but we suggest also looking at other accepted lore of that type to get a feel for what we’re talking about. If you’re looking for our other guide on guidelines for writing specifics in a lore submissions, go here: Click me.

 

General Formatting

This is a brief introductory on what you should follow when going off the format below. Each section should be cleanly labeled using the terms from the formatting. For example with abilities, you should have something that ends up like this:

Spoiler

Ability – Spectral Fireball

 

Description – You are able to conjure a ball of fire from your deity’s realm. With training, you will be able to manipulate it around and throw it at your opponents.The size and speed depends on how proficient the mage is. Et cetera

 

Mechanics – It takes 3 emotes to summon forth a full fireball. 1 emote to start channeling your deific power, 1 to start bringing the fire over, 1 to fully form the fireball. Et cetera

 

Specific Red Lines – The fireball can not travel further than 10 blocks before fading from existence. Et cetera

 

If you have multiple things under one section, such as multiple paragraphs or acts in the backstory, you do not need to keep labeling each section as “Backstory” and can just have the one “Backstory” title at the beginning of it. This may seem tedious, but it is very beneficial in the long run as it allows for the reader to understand what section is what. This also makes it way easier for the wiki team to port over your lore into the wiki. I don’t want them to waste time trying to segment your lore themselves, they should just be able to skim through the piece and find each label and then port the contents of the label into the specific section of the wiki formatting during page creation. At the end of the day, it makes things more efficient, so I thank you in advance for cooperating.

 

Rewrites/Amendments

If the piece you are submitting is a rewrite, you should follow the formatting that is described down below for whatever category the piece falls under. If you are writing an amendment, then you do not need to follow the formatting. An amendment is not something that is going to replace the original lore piece and instead will be merged with the base lore to apply the fixes or changes that the amendment is adding.

 


 

Magic Submissions

This subsection is going to briefly go over the types of magic submissions you might make and what you should be wary of or keep in mind. Please bear in mind that magic submissions will likely require a guide, which is detailed towards the end of the thread.

 

Feats

A feat is a magic or ability that is very limited compared to a full magic. It typically can only perform one function and does not provide any significant advantages. For example, the Seers of Vaasek use a feat that allows them to see again. There is nothing overpowered about that and it doesn’t grant them any advantages that allow for them to win in combat.

 

If you intend on submitting a feat, you should bear in mind that it is meant to be limited. If you want something that has multiple abilities and combat potential, aim to submit a full magic.

 

1-Slot Magic

A 1-Slot is a magic that takes up 1 magic slot. Each normal character has 5 magic slots, so they have the capability to pick up 5 1-Slot magics. A 1-Slot magic should be thoroughly fleshed out and have multiple spells. 5-10 is a good amount to aim for.

 

Freeform Magic” is something that is not outright frowned upon, but we expect it to be properly written in terms of its capabilities/restrictions. A magic submission that is too vague in what it can do while also having broad capabilities is not something that is going to be accepted.

 

Multi-Slot Magic

A multi-slot magic, as the name suggests, is a magic that takes up multiple magic slots. This is not to be confused with a magic that has multiple 1-Slot subtypes.

 

A common misconception is that because it takes up multiple magic slots, it’s allowed to be vastly more powerful than a 1-Slot magic. This is not the case. A multi-slot magic is meant to have more spells/abilities than your average 1-Slot magic, but these spells are not meant to be god-tier or overpowered.

 

Format – Title should be [Magic Lore] – [Name of the Magic], e.g. Magic Lore – Fire Evocation

Spoiler
  • Background/Origin of the magic/General Description of the magic. This is your fluff/backstory to what the magic is and what its origins are/how it was discovered. You do not need to go in-depth on the abilities yet, but someone should have a general grasp on what the magic is about after reading this.
  • Magic Explanation. This is the section where you go into more detail on how the magic functions (e.g. what powers it, how a mage can learn it, requirements et cetera) as a whole.

  • Abilities/Spells. This is the section where you go into the specifics of each ability.

    • Name of the spell.

    • Description of the spell. This is the RP description of the spell and its capabilities.

    • Mechanics of the spell. This is the OOC description of the spell that covers things like emote count requirement and other specifications that you need to be aware of.

    • Specific Red Lines. This section is put under each ability and covers any restrictions that the ability may have.

  • Tier Progression. This section is where you cover the progression rate of a person undertaking the magic, beginning at tier one. Below is an example of the first two, but you will need to add in all of the tiers when you submit (tier 5 is max under the standard system).

    • Tier One

      • Abilities that can be learned.

      • Limits of those abilities.

    • Tier Two

      • Any changes to the limitations of the abilities learned in tier one (e.g. if the radius of a spell increases, if you can cast it faster, et cetera).

      • New abilities that can be learned.

      • Limits of those abilities.

  • Red lines. This section is where you cover the important restrictions and other things that a mage has to note. The specific ability red lines should also be repeated in this section, following the format of “Ability Name: [insert red line]”. E.g. Fireball: This spell can not go past 10 blocks before fading.

    • General red lines. This is where you list general red lines of the entire magic. If the mage is restricted from learning magics or has restrictions of a similar nature (e.g. not being able to turn into a CA creature), be sure to include that here.

    • Spell specific red lines. After the general red lines, you follow with red lines that are tied to specific abilities.

    • Weaknesses or counters to the magic/spells. This displaying the balance and seeing how it compares/counters with other magics currently used.

    • State how the magic reacts to other magics/creatures. This is for those of other magics or those that play creatures to be able to properly emote when encountering this magic.( Example being a magic submission of using spirits. What does a shaman or a mystic feel/experience when encountering this?)

  • Repeat “Magic Description” through “Red Lines/Restrictions”. MULTIPLE SUB-TYPE SUBMISSION ONLY. Ignore if your magic submission is just a single slot one.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 


 

Playable Races/Creatures

This subsection will cover the different types of race submissions that a person is allowed to make. Please bear in mind that some of these submissions will likely require a guide, which is detailed towards the end of the thread.

 

Open Races

Races that can be played without a creature application or ET, such as descendant subraces (example: mountain dwarves), combinations of descendant races (example: adunians), or entirely new races (example: kha, before the CA). They cannot be specifically any stronger or have more advanced abilities than your average descendant, and if they’re a subrace or mix, they must adhere to the racial curses that already exist in lore, though they may be somewhat altered (for instance, halflings live longer than humans somewhat and their dwarven greed is expressed in food and drink rather than gold).

 

We are not currently looking for any new open races or subtypes, but will still review any submissions made for them. Something you NEED to keep in mind for these submissions is that you will be required to have a significant backing. Open races are meant to be active and accessible to everyone. If it fails to gain traction, there’s a big chance that it will be demoted to a CA race or potentially shelved. We also require that Open Race submissions be substantially detailed and not lacking or vague with information.

 

Format - Title: [Open Race Lore] - [Name of Race], e.g. Open Race Lore – Billybobians

Spoiler
  • Origin/Backstory. How the race came into existence and was discovered/how they came to the current map should be described in this section.
  • Description. All of the traits that the race may have should be detailed here, both physical and mental.

  • History. This should cover the history of the race, including the major turning points and general direction they have been going in.

  • Culture(s). This section should detail the culture(s) of the race and any notable distinctions they may have.

  • Abilities. This part should go over any unique abilities this race may have that a normal descendant lacks. It does not have to be magical in nature and could be a unique physical trait.

    • Name of the ability.

    • Description of the ability. This is the RP description of the ability and its capabilities.

    • Mechanics of the ability. This is the OOC description of the spell that covers things like emote count requirement and other specifications that you need to be aware of.

    • Specific Red Lines. This section is put under each ability and covers any restrictions that the ability may have.

  • Red lines. This section is where you cover the important restrictions and other things that the player has to note.

    • General red lines. This is where you list general red lines of the race if any are required. If your race is restricted from learning magic or has restrictions of a similar nature, be sure to include that here.

    • Ability specific red lines. After the general red lines, you follow with repeating the red lines that are tied to specific abilities which were provided in the above section. It should be following the format of “Ability Name: [insert red line]”. E.g. Fireball: This spell can not go past 10 blocks before fading.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

Creature Application Races

Generally more powerful and/or often harder to play or have more potential issues of powergaming than an Open Race. The players that successfully apply to play these creatures are trusted with advanced abilities and strengths compared to the Open Races.

 

These creatures have powers comparable to some magics (some even might reference specific magical abilities, such as lich’s necromantic draining ability). These powers may be tiered as magic if the creatures become more powerful with time or specific efforts. Bear in mind, magic slots also apply to creatures. If the creature is crammed full of abilities, the LT will likely want it to take up multiple magic slots or all of them.

 

They should also have weaknesses to help balance the creature in roleplay, especially in combat. The balancing should be such that they should at least be at a disadvantage should they be outnumbered by average descendants.

 

These races also are monitored for activity. Should you plan on submitting a CA race, you should bear in mind that there is a possibility of shelving if any warnings about inactivity are ignored.

 

Format - Title: [Playable CA Race Lore] - [Name of Race], e.g. Playable CA Race Lore – Kha’rajyr

Spoiler
  • Origin/Background/Culture. Lore written here should not directly conflict with existing lore and should not be written in such a way it can void existing rp of playerbases if it can be avoided.
  • Physical Description.

    • Physical descriptions should be clear and can include pictures. Traits, such as anatomy or changed body parts (e.g. scales instead of skin) should be talked about thoroughly and not left vague.

    • Strengths and weaknesses of the creature. This area should be used to explain the pros that the creature has (e.g. increased strength) and weaknesses (e.g. fire). As well listing what magics/mundane things are effective/non-effective against it. Include as well how some magics feel/react to in regards to said creature.(Example: A creature that is a spirit of sorts. How does a shaman or a mystic feel/able to react when encountering said creature?). Make sure to be descriptive if it isn’t elaborated on in a later section (e.g. increased strength should be described in detail on how strong the person is and their limitations).

  • Mental Description. The mindset and mental aspects of your creature should be laid out here.

    • Mindset. This part should be used to describe how your creature thinks and any changes you might see between this creature vs a descendant. Does your creature have an innate way of thinking (e.g. x creature is always cautious, regardless of the situation)? Does it vary from person to person? Or is it the same as a descendant’s? Stuff like that.

    • Mental State. You should use this section to describe if your creature suffers from any mental instability or other abnormalities that a player should be aware of when RP’ing. Does your creature suffer from any specific mental illness? Do things trigger them? For example, your creature could be designed to suffer from PTSD due to the changing method, where certain things such as loud noises trigger the PTSD and make them have flashbacks to when they were changed.

  • Abilities. Any kind of unique abilities, such as a magic or special body functions (e.g. forming acid and spitting it out), should be covered here.

    • Name of the ability.

    • Description of the ability. This is the RP description of the ability and its capabilities.

    • Mechanics of the ability. This is the OOC description of the spell that covers things like emote count requirement and other specifications that you need to be aware of.

    • Specific Red Lines. This section is put under each ability and covers any restrictions that the ability may have.

  • Red lines/Restrictions. This section is where you cover the important restrictions and other things of note.

    • General red lines/restrictions. This is where you list general red lines of the creature, such as ways their special traits should not be used. If your creature is restricted from learning magic or has restrictions of a similar nature, be sure to include that here.

    • Ability specific red lines. After the general red lines, you follow with repeating the red lines that are tied to specific abilities which were provided in the above section. It should follow the format of “Ability Name: [insert red line]”. E.g. Fireball: This spell can not go past 10 blocks before fading.

  • Repeat background through Red Lines/Restrictions. ONLY IF YOU ARE MAKING MULTIPLE CREATURE TYPES or the abilities are in subtypes, ignore if your creature is just a single slot/single creature.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

ET-Only Creatures (Non-Index)

ET-only creatures are those that are allowed to be the most powerful and/or diverse submittable creatures and can only be used by ET. Some of these creatures require approval from either an ET manager, the ET Lead, or the LT/LT Management. Such creatures include dragons and their sub-creatures (wyverns, wyrms), aengudaemonic entities (i.e. the Aspects), some historical entities and deific/aengudaemonic entities, and anything that approaches such power/significance as these. Otherwise, an ET-only creature will have advanced powers that can be unbalanced and break or bend the guidelines explained in the CA and Open creatures.

 

The difference between non-index and index event creatures is rather simple. Non-index event creatures are event creatures that are established in LotC’s canon rather than some run-of-the-mill monster. If you wish to submit a minor monster for hunting events and things of that nature, the creature index suits your needs. If you wish to establish an event creature race that is a significant faction that you intend to use for multiple events/larger scale eventlines, non-index submissions are required.

 

ET-only creatures are not supposed to be used as a player’s character but for events and eventlines, only. As such, they cannot, for instance, procreate outside of their own race (most are not descendants, anyway, and would already not be able to) and would not be available to make Teacher Applications for magics they may have.

 

It’s advised, if making an ET-only creature, to make ones geared towards event-play as a result, not towards day-to-day play. There’s a difference between prolonged, daily roleplay and events catered by the ET, even with heavy roleplay or non-combat events.

 

Weaknesses are also advised, especially for monsters or entities meant for combat roleplay, so that an exploitable quality of them can be used by the players interacting with them in the event to defeat them. They generally should be defeatable by a group at least.

 

Formatting - Title: [Event Creature Lore] - [Name of Creature], e.g. Event Creature Lore – Crazyaztecians

Spoiler

The formatting is identical to the Creature Application Races.

 


Deific Submissions

This subsection covers the types of deific submissions that you can make on LotC.

 

Aengudaemons

Aengudaemons are a type of deity created by the Creator during creation. Mortals have dubbed a split with one side being “Aenguls” and the other being “Daemons”. Neutral ones are regarded as regular Aengudaemons. However, these are just labels and there is no difference between an Aengul and a Daemon in terms of capabilities. What differs is their personality and/or goals.

 

An Aengul typically is a “good” deity compared to some of the Daemons and have goals that they actively push for in the mortal realm. These deities tend to openly use mortals as followers, granting them power in exchange for worship and/or service.

 

Daemons are generally seen as the “mean” or more dangerous variety, as they are not afraid to get their hands dirty themselves in the Mortal Realm. While some do have followers like Aenguls, it is not uncommon for them to send in Patrons or descend themselves to mess with the mortal realms. However, a misconception is that all Daemons are “evil”. Many simply have a goal and are ruthless about carrying it out, but a good amount of these goals are not to destroy the realm or wipe mortals out.

 

When designing an Aengudaemon, you do not need to conform to the “good” vs. “evil” trope. An example of this would be Tahariae, who on the surface seems “good”, but their actual goal is to rid the mortal realm of what they believe is impure. Children, women, elderly, fellow Aengudaemons, it doesn’t matter who they are to Tahariae, if they are deemed impure he will go all out in trying to have them purged. Conversely, Metztli is a Daemon due to the fact that they abducted mortals and experimented on them in an attempt to create the ultimate race. However, they do not wish to wipe out humanity or anything that actually endangers the mortals as a whole.

 

Each Aengudaemon has a “title” that showcases what they are about. Tahariae is the Aengul of Purity, Xan is the Aengul of Order and Guardianship, Llahir is the Daemon of Trickery, Thievery, and Luck. 1-3 titles is the norm and each should be reflected in the Aengudaemon’s lore/purpose. Any magic that they grant their followers or patrons that they raise should also reflect the titles and their purpose. E.g. Tahariae grants their followers the power to “purge” impurities, Xan grants their followers the power to maintain Order, and Llahir grants their followers ways to trick and steal from others.

 

Format - Title: [Aengudaemon Lore] – [Name], [Aengudaemon of (insert titles here)], e.g. Aengudaemon Lore – John, Aengudaemon of Baseball

Spoiler
  • Origin/Background. This should cover the backstory of the Aengudaemon and why they are now paying attention to the Mortal Realm OR detail what they are doing in the immortal realms. Their title/purpose should be explained here as well. Make sure it follows and aligns with existing lore.

  • Realm. This should cover information about the deity’s realm or place of current residence.

  • Following. This should detail if the Aengudaemon seeks out followers/if they have existing ones and what they offer to their followers (e.g. do they only communicate with them? Do they offer small boons? A magic? etc).

  • Present Day. This should elaborate on what the Aengudaemon is currently up to and how they will impact the current story (if at all).

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

Patrons

Patrons are beings that have been infused with power or created with power by an Aengudaemon. These are typically servants of the Aengudaemon in question or serve some purpose that the Aengudaemon wants to see fulfilled. Patrons range in power and do not always need to be deific figures. Examples of this would be the Ascended or Undead, mortals given boons by Aengudaemons that give them a new form or traits. Conversely, there are beings such as Dragaar/Drakaar and the Spirits which have overwhelming power in certain situations.

 

When designing a Patron, you have to bear in mind their purpose and how they are designed relationship-wise to their creator. Questions like the following should be asked: Are their souls bound to the Aengudaemon where they have to serve? Are they given free will to carry out some goal and if so, what goal? Do they respect the Aengudaemon or are they looking to backstab them? How do they view Mortals? Are they capable of giving boons to people?

 

Format - Title should be: [Patron Lore] – [Name], [Patron of (insert name here)], e.g. Patron Lore – Abe, Patron of Tahariae

Spoiler
  • Origin/Backstory. This is where you detail how the Patron was created or raised into power by the Aengudaemon. Make sure to do some research with said Aenguldaemon so that it aligns with current lore.
  • Purpose. This is where you describe what the Patron was made for and how they are trying to carry that goal out.

  • Abilities. This section is where the capabilities of the Patron are described.

  • Current Location. This section should cover where they are currently and what would entail them leaving it to be used for future events/storylines. This section doesn’t mean there has to be a way for the Patron to appear/be used however. It’s more of a general means of having insight to what is currently going on with the Patron or if there are any future possible interactions.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

Non-Aengudaemonic Deity-Class Entities

This section covers deific-level beings that aren’t related to Aengudaemons. These are rather rare in the grand scheme of things, but we wouldn’t be opposed to accepting new ones. The primary ones at the moment are Voidal Behemoths. These entities are some of the most powerful voidal entities. However, due to the fact that they are voidal horrors, they usually remain outside of the mortal realm.

 

Format - Title should be: [Deity Class Lore] – [Name], [Entity type], e.g. Deity Class Lore – Gnomics, Voidal Behemoth

Spoiler
  • Origin/Backstory. This section covers how the entity came about and if they are interacting with the mortal realm, what caused them to start doing that.
  • Description and Purpose/Goals. This section covers what the entity is and what they are attempting to do. If it’s a submission for something never been seen on LotC before, making sure to put plenty of detail.

  • Capabilities. This section goes over what the entity is capable of doing, what boons they can grant, et cetera.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 


 

World Lore

This subsection covers the different types of world lore that can be submitted.

 

Location

Location lore is lore written for places outside of the current map or hidden areas in the current map that have not been discovered. Places outside of the current map should be areas that are used as starting locations or have some kind of historical impact on the existing/a future map. With the addition of Wayfinding portals, it’s possible to have places that are far away or not accessible via ship that still connect to our current map. So don’t be afraid to include that in your submission.

 

Format - Title: [World Lore] - [Name of Location], e.g. World Lore – The Avark Archipelego

Spoiler
  • Location. Describe where this is located in the Mortal Realm and if it’s possible to get there.
  • Geography. Cover the layout of the land, what creatures/plantlife is there, and if any civilizations are based in the land.

  • Civilization. Cover the culture and other traits that the civilization has. If someone is going to say they came here from this area, they are going to need a reference for how they were raised up.

  • History. Cover the history of the land. If any civilizations exist, go into detail about their events as well.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

Historical

Historical lore can be written for a few things. Firstly, it is written for time periods that players were not around for OR for time periods for areas that the players did not have access to. Secondly, it can be written for deities and other entities outside of the Mortal Realm to give them depth.

 

Format - Title: [Historical Lore] - [Name], e.g. Historical Lore – Horen’s Battle Against Iblees

Spoiler
  • History. This part is where you put in the historical information. There isn’t a set method for this, so you can style it as if it was someone’s journal, two people talking in a pub, et cetera.
  • OOC explanation. This is where you cover the historical text from an OOC standpoint, explaining it to the LT. This does not need to be particularly long, so long as you get to the point about what it is about.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 

Legends

Legends Thread This thread covers Legend submissions, along with what formatting to use when submitting them.

 

Indexes – Opening Soon

The index covers non-playable creatures, including ET creatures (discussed in the ET-Only Race section), plants, and potions. For the moment, the index is not up yet. It will be remade in a few days once I fix the issues that we were having with the google form.

 

Creatures: Something to keep in mind is that we will not be accepting tameable creatures that are overpowered in terms of combat. Combat pets must be reasonable. 7 foot wolves that can kill people in one bite are an example of unreasonable. Event creatures can be rather strong, but keep in mind what the ET-Only Race section mentioned regarding the difference between non-index and index ET creatures.

 

Plants: Similarly, we are looking for balance among plants. A plant that acts as a deadly poison and instantly kills someone or a plant that can turn into a salve that instantly heals people are not the types of plants we are looking for. Aim for more mild effects and add some variety to the plant if you’re making something bigger like a tree. For example, a special tree could have wood that acts a special way, along with the bark and leaves each having unique traits. This allows for the plant to be used in multiple ways and open up multiple routes of RP.

 

Potions: Currently not being accepted due to the alchemy changes going on at the moment. This section will be updated when those changes are finalized.

 

Inventions

Inventions that are complex and/or push the boundaries of the tech lock and/or introduce new substances (e.g. metals) belong here. Same thing with new siege weapons.

 

Things that are from modern times, such as a car, will not be accepted as it goes against the tech lock. Things that push the tech lock will be reviewed by the administration after the LT have voted on it.

 

Siege weapons will also be reviewed by the GM team to make sure that its functions are compatible with the warclaim system.

 

Format – Title: [Invention Lore] – [Name], e.g. Invention Lore – Halfling Explosives

Spoiler
  • Origin/Backstory. This section is devoted to how the invention was discovered and who discovered it.
  • Description. This is the place where you’re supposed to describe the invention in detail. What it is made of, how it functions, et cetera.

  • Capabilities. This ties in with the above section and you are meant to cover what the invention is capable of doing.

  • Siege Information. If your submission is a siege weapon or something to be used in a war claim, you must add information on how it functions in the war claim (e.g. how many emotes it needs, what kind of rolls it needs to achieve, how much damage it does, if it can self-destruct, et cetera). A proposed pricing for it (e.g. 1000 mina per warclaim) should also be included. This will all be sorted out with the GM team if it makes it past the LT.

  • Red Lines/Restrictions. The limitations of the invention should be listed here. It should be noted if this is an invention that needs regulation via apps or if this is an invention anyone can pick up.

  • Purpose. This section is where you describe what purpose your lore is serving, what it is bringing to the table that other lore pieces aren’t, and why it fits into LotC’s canon.

  • Citation Spoiler. You should have a spoiler at the bottom that includes links to any lore pieces that you referenced or based your lore submission off of.

 


 

Guides

For magic and racial submissions, a guide is required to be written up once the lore is accepted before implementation will be allowed. Other submissions, such as inventions, might require a guide, but that is a case by case basis. The LT will notify you if a guide is required upon the lore’s acceptance.

 

Due to the variety of different types of magic and creatures and ways you can write a guide for them, there’s no set in stone format for this. A guide focuses on how to RP the lore piece, so it is not required to cover things such as the piece’s origin or other fluff. Instead, it should focus on providing help on how a player should emote and RP the piece.

 

Requirements:

Spoiler

- Brief summary of the lore, including a link to the lore page.

- Description of any physical changes and examples/suggestions of how to RP them.

- Description of any mental changes and examples/suggestions of how to RP them.

- Description of any abilities, briefly covering the RP behind it with an in-depth focus on the mechanics and restrictions of it.

- Emote examples for the abilities. If there are changes in how the ability works over time (e.g. tier progression), you should include examples of that as well (e.g. providing an emote example of a t1 version of a spell followed by its t3 and t5 version).

- An overview of the piece’s progression system. This is not limited to tier progression, but also things like creature progression. Each stage of the piece’s progression system should be described in detail so a player understands what changes at each stage.

 

Share this post


Link to post
Share on other sites

Update #1: Added in the citing requirement where you need to link any lore referenced/used in a spoiler at the end of the thread.

  • This is to make things easier for people trying to understand the lore who might not be up to date on whatever you are basing your lore off of. For example, if someone was reading a Mani addition they might not understand certain things. So giving them a link to the base Mani lore allows for them to delve further and help them understand where the addition fits in terms of LotC’s canon.

 

Update #2: Added in an introductory section on formatting as a whole.

  • This is to make it easier for people to understand what they need and don’t need when formatting a piece.

 

Update #3: Updated the Magic and CA Creature formats to reflect multi-slot/multi subtype versions.

  • This is to avoid formatting confusion if someone is trying to write multiple subtypes/versions of the creature/magic in one lore piece.

 

Update #4: Updated the CA Creature race format to include mental states.

  • This was a piece that was forgotten to be included and overall helps a person flesh out their creature further.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.



×