Aurora Information Uplink - User contributions [en]

Lore Staff Guidelines

2021-11-11T06:40:46Z

Mofo1995: /* WHITELIST MANAGEMENT */ Added "Granting a whitelist" to the whitelist management section.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Caelphon as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== GRANTING A WHITELIST ====
Whitelists may only be granted following a whitelist application process, unless special permission for a specific case has been granted by lore team administration. However, lore team administration may never grant itself special permission to dispense whitelists, even in the case of a lore writer vacancy.

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

== MISCELLANEOUS ==

In the event of any situation which is currently not covered by these rules, use your best judgement to ascertain the spirit of the law. '''Never be afraid to ask the Loremaster for guidance''' in any situation where you are unsure about the applicability of the rules and regulations, or code of conduct.

Lore Staff Guidelines

2021-08-01T17:31:29Z

Mofo1995: Changed deputy from "Vacant" to "Caelphon."

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Caelphon as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

== MISCELLANEOUS ==

In the event of any situation which is currently not covered by these rules, use your best judgement to ascertain the spirit of the law. '''Never be afraid to ask the Loremaster for guidance''' in any situation where you are unsure about the applicability of the rules and regulations, or code of conduct.

User:Mofo1995

2021-07-03T02:44:40Z

Mofo1995: /* "New" Shit */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg|1000px]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

===No Continent===
Craterview

==Transfer of Current Notes to Digital==

===Belle Cote===
Decently far north, northernmost city. At southernmost edge of peninsula. Which is hedged in by mountains. Forests? Plains? Canals, focus on high fashion, always pushing the envelope with yearly fhasion shows. Citizens there are known to be a bit stuck up, heavy focus on manners, looks down on others for not being up to date on their trends. Even the poorest dress in their outlandish styles. Common honeymoon and wedding destination. Industry of Belle Cote based around mostly artisans producing hand-made textiles competing for the most prestigious fashion. SOme textiles mills also exist belonging to more unscrupulous designers, though they are very looked down on by most natives and only the least fashionable wear them. The mills use the fame of the city to sell their merch to department stores abroad.

===Ashton===
Far away from water or bodies of water. Located at a very central place on Selene continent. Could be in middle of plains surrounded by farmlands. Central location necessary for its business focus. Could have started as a central butchery and meat processing location for the surrounding farmlands. Important crossroads location connecting all of them, maybe actually started as large farmer's market before industries started popping up. As Biesel became populated enough, maybe the first local automotive and hovercar manufacturing sprung up there. Moguls began building up the city with their niceties so they could live there and manager their businesses year round instead of travelling from Mendell. Today known for old money combined with redneck cowboy aesthetic, think "Doug Dimmadome." Still holds yearly farmer's market in one of its suburbs.

===Cape City===
Jokingly and affectionately called "the city of hereos" and the location of modern superhero movies in the Biesellite film industry. Some actors even travel the streets in costume for press and PR events and to drum up hype for upcoming releases.

=="New" Shit==
===Craterview===
Beach vacation and resort city. Large hotels line the interior perimeter of the beaches. Small family-run motels from before tourism rose in popularity still dot plots of land surrounded by the big boys. High crime from the local poor people who also work the service industry in the area. Lots of drug smuggling/dealing. Lots of seafood hibachi restaurants with local dishes. Sunny and tropical weather year round with occasional severe tropical storms. Annual boating races are a popular attraction. Boating clubs line the beaches along with large beachside estates in the wealthy suburbs.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

=Cool Flags =
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

User:Mofo1995

2021-07-03T02:43:07Z

Mofo1995: Added craterview.

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg|1000px]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

===No Continent===
Craterview

==Transfer of Current Notes to Digital==

===Belle Cote===
Decently far north, northernmost city. At southernmost edge of peninsula. Which is hedged in by mountains. Forests? Plains? Canals, focus on high fashion, always pushing the envelope with yearly fhasion shows. Citizens there are known to be a bit stuck up, heavy focus on manners, looks down on others for not being up to date on their trends. Even the poorest dress in their outlandish styles. Common honeymoon and wedding destination. Industry of Belle Cote based around mostly artisans producing hand-made textiles competing for the most prestigious fashion. SOme textiles mills also exist belonging to more unscrupulous designers, though they are very looked down on by most natives and only the least fashionable wear them. The mills use the fame of the city to sell their merch to department stores abroad.

===Ashton===
Far away from water or bodies of water. Located at a very central place on Selene continent. Could be in middle of plains surrounded by farmlands. Central location necessary for its business focus. Could have started as a central butchery and meat processing location for the surrounding farmlands. Important crossroads location connecting all of them, maybe actually started as large farmer's market before industries started popping up. As Biesel became populated enough, maybe the first local automotive and hovercar manufacturing sprung up there. Moguls began building up the city with their niceties so they could live there and manager their businesses year round instead of travelling from Mendell. Today known for old money combined with redneck cowboy aesthetic, think "Doug Dimmadome." Still holds yearly farmer's market in one of its suburbs.

===Cape City===
Jokingly and affectionately called "the city of hereos" and the location of modern superhero movies in the Biesellite film industry. Some actors even travel the streets in costume for press and PR events and to drum up hype for upcoming releases.

=="New" Shit==
===Craterview===
Beach vacation and resort city. Large hotels line the interior perimeter of the beaches. Small family-run motels from before tourism rose in popularity still dot plots of land surrounded by the big boys. High crime from the local poor people who also work the service industry in the area. Lots of seafood hibachi restaurants with local dishes. Sunny and tropical weather year round with occasional severe tropical storms. Annual boating races are a popular attraction. Boating clubs line the beaches along with large beachside estates in the wealthy suburbs.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

=Cool Flags =
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

Lore Staff Guidelines

2021-05-13T02:11:48Z

Mofo1995:

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and [Vacant] as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

== MISCELLANEOUS ==

In the event of any situation which is currently not covered by these rules, use your best judgement to ascertain the spirit of the law. '''Never be afraid to ask the Loremaster for guidance''' in any situation where you are unsure about the applicability of the rules and regulations, or code of conduct.

Lore Staff Guidelines

2021-05-13T02:10:24Z

Mofo1995: Added "Miscellaneous" to include helpful advice, as well as any other updates in the future which may not necessarily fit into any of the current categories.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and [Vacant] as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

== MISCELLANEOUS ==

In the event of any situation which is currently not covered by these rules, use your best judgement to ascertain the spirit of the law. '''Never be afraid to ask the Loremaster for guidance''' in any situation where you are unsure about the applicability of the rules and regulations, or code of conduct.

Lore Staff Guidelines

2021-05-13T02:03:10Z

Mofo1995: Undo revision 19994 by Mofo1995 (talk) Not actually undone, forgot to mention in previous change note that the "How-To" section on IC news articles was removed, due to them being integrated automatically.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and [Vacant] as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2021-05-13T02:00:53Z

Mofo1995: Removed Kyres as deputy, added point #7 to wiki development. The Gentials Lore Ban was unintentionally forgotten when drafting these rules and regulations, which state that all lore rules not contained within it are null and void, thereby allowing them. The ban is instated once again.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and [Vacant] as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2020-12-18T05:03:41Z

Mofo1995: /* MAJOR RETCONS */

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2020-12-18T05:02:25Z

Mofo1995: /* MAJOR RETCONS */

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, ask the Lore Master or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2020-12-18T05:00:18Z

Mofo1995: /* = MAJOR RETCONS */

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following does not qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, ask the Lore Master or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2020-12-18T04:59:31Z

Mofo1995: Added the Major Retcon section.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

==== MAJOR RETCONS ===
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following does not qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, ask the Lore Master or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Corporate Regulations

2020-09-15T05:03:21Z

Mofo1995: /* Misc */ Added link to updated guide to law page for legal drugs.

{{Reference}}
{{IC_Laws}}

= Corporate Regulations =

Corporate Regulations are penned regulations that all Nanotrasen employees have agreed to abide by in the signing of their employment contract. These regulations apply across the board on any Nanotrasen owned property, be it station, ship, or outpost.

Onboard each facility there will be a dedicated Security department in charge of making sure that all Nanotrasen employees follow these regulations.

*'''Regulations protecting prisoners from mistreatment applies to even non-crew.'''

*'''Executions are illegal and not allowed by regulations.''' Station security nor command should be doing any executions. The maximum possible penalty for major infractions is cyborgification.

*'''The brig timer of a prisoner begins after processing.''' All prisoner processing is expected to be completed in a timely manner. Should a detainee's processing take an unreasonably long time, the personnel responsible for that processing may be liable for illegal detention.

=== Interpretation of the Regulations ===

Every person on the station should have a good knowledge of Corporate Regulations. Following them could mean the difference between having a peaceful day or paying 1000 credits for multiple infractions. Extensive knowledge of Corporate Regulations is required for such positions as the Warden, Head of Personnel, Captain, and the Head of Security.

For all incidents, the '''suspect's intent''' is very important. Some incidents are mutually exclusive.

A single incident has a single sentence, so if, for instance, the prisoner took 3 items off someone, this is a single count of pickpocketing.

Aiding and abetting a criminal makes you an accomplice; '''you can be charged with the same crime as the person you aided and abetted.'''

The charges “Battery”, “Attempted murder” and “Murder” do not apply to crimes committed against [[IPC|IPCs]], whether they are free intelligences or owned by a person or company. Consult employment/security records to determine whether an IPC is owned or not.

Positronic intelligences are not protected by capital punishment laws. Those charged with red level infractions may be at risk of being dismantled or destroyed.

=== Additional ===

==== Captains and Authority ====

Captains are not above Corporate Regulations and can be arrested by Security for breaking them. However, this should only happen if active Heads of Staff agree in a unanimous decision to approve the arrest, or the arrest is ordered by Central Command. '''Captains should not be removed from their position in this way for anything but violations that would normally require holding until transfer.''' Lesser violations can and should be reported to Central Command, but are not generally severe enough to warrant this drastic action. If a Captain is arrested in this manner, an Acting Captain should be appointed immediately, and Central Command should be informed.

The station's assigned Captain has full and final authority over the operation of the station. They are authorized to issue direct orders to entire departments or specific crew members. They may take any actions or issue orders that violate regulations during non-standard situations. Generally, these orders must be carried out. Even if you feel an order from the Captain to be against regulation, your moral code, or generally detestable, you still have to follow it. You are entitled to begin a vote within Command (if you're part of Command) to have the Captain arrested if the order breaks a serious regulation, or fax Central Command (if you have access to a fax machine) to have them weigh in, but disobeying the order (if given to you) or obstructing it (if not given to you directly) is Failure to Execute an Order. This is upgraded to Sedition if you start encouraging others to refuse the Captain's orders.

If a crew member breaks regulations while following a direct order from the Captain, when there are other legal ways to carry it out, that crew member is generally considered at fault for the violation.

Pardons are only legitimate if they come from Central Command. Not even the Captain can deliver pardons, but they can grant parole with or without a tracking implant.

==== Injunctions ====

The Captain, Head of Security, and Internal Affairs Agents may issue injunctions to the crew if deemed necessary.

An injunction is a restriction on a crew member, meant to prohibit disruptive behavior that may not otherwise explicitly break regulations. Violating the terms of these injunctions '''is''' breaking regulations however, covered by '''i108 Violation of Injunction''' below. Examples of valid uses of injunctions include things like preventing two belligerent crew members from interacting with one another, or stopping someone from abusing alcohol at the bar. They are not meant to circumvent the chain of command, however, and efforts to resolve problems within that structure should be made first.

The Head of Security and Internal Affairs Agents may issue injunctions to any non-Command member of the crew. The Captain's orders may override these injunctions.

Only the Captain, Central Command itself, or every other member of Command acting as the Captain in a unanimous decision, may issue injunctions to a member of Command Staff.

==== Misc ====

Do '''NOT''' demand a tribunal for anything. You'll just be laughed at.

A '''Warrant''' must be provided for almost any search or arrest conducted under code green. Exceptions to this rule exist if an officer is a direct witness to a crime, or may reasonably conclude that failure to act will pose an immediate danger to the crew and/or station. Search warrants may also be circumvented if the Head of Staff over the employee being searched has given their direct consent.

'''Suspensions''' are used to temporarily suspend an employee from active duty, restricting them from holding any station rank. They are typically used in situations where an employee can no longer be trusted to continue their work.

'''Demotions''' are used to temporarily demote an employee to a rank below their previous occupation, allowing them to continue active duty under a position of less authority. They are typically reserved for situations in which the employee is still trusted to continue work, but may require additional training or oversight.

'''Drugs''' such as alcohol, tobacco, Ambrosia Deus, Ambrosia Vulgaris, etcetera are not covered by the '''Contraband''' regulation as these are legal under Tau Ceti law. A full list of legalized recreational drugs can be found [[Guide to Law|here]].

=== Low Level Infractions (Yellow Violations; i100's) ===
==== Regarding warnings ====

Officers are allowed to give out official warnings for first-time low level infractions. Any repeat offenders are to be sentenced.

Officers are not obligated to first issue out an official warning, but are encouraged to do so if the situation allows it.

{| width="950px" style="background-color:#ffee99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffee55;"|No.
!style="background-color:#ffee55; width:150px"|Incident
!style="background-color:#ffee55; width:300px"|Description
!style="background-color:#ffee55;"|Notes
!style="background-color:#ffee55;"|Traditional Sentence
!style="background-color:#ffee55;"|Repeat Offense
!style="background-color:#ffee55;"|Fine
|-
| i101
| '''Trespassing'''
| To be in an area which a person does not have access to.
| Remember that people can either break in, sneak in, or be let in. Always check that the suspect wasn't let in to do a job by someone with access, or were given access on their ID. Trespassing and theft often committed together; both sentences should be applied. Severity is increased if they refuse to leave the area peacefully, more so if they attempt to use important equipment there, so feel free to add other charges if they do.
| 3 minutes.
| Up to 10 minutes and/or demotion.
| 200 credits
|-
| i102
| '''Petty Theft'''
| To take items from areas one does not have access to, or to take items belonging to others or the station as a whole. Includes theft of credits up to 500cr. For higher amounts see i220 - Fraud
| Keeping items which are in short supply where they belong is what is important here. A doctor who takes all the surgical tools and hides them still commits theft, even though he had access. Items can include anything in limited supply. Remember to take the items away from them and return them to where they stole them.
| 3 minutes, returning of stolen item to the owner or department.
| Up to 10 minutes and/or demotion.
| 150 credits
|-
| i103
| '''Minor Assault'''
| To use, or threaten, physical force against someone, without intent to kill or seriously injure. To cause easily repairable damage to a free IPC chassis, up to and including the removal of limbs.
| If it causes minor damage and easily treatable damage, it's minor assault. Starting fights with other employees or punching fellow employees counts too, as well as seriously threatening them with it. Force-feeding someone is this unless it's poisonous or knocks them unconscious.
| 4 minutes.
| Up to 10 minutes and/or demotion.
| 400 credits
|-
| i104
| '''Battery'''
| To have unwanted physical contact with someone, even where the contact is not violent.
| Bumping into someone in a corridor doesn't really count. Touching someone, when they have explicitly told you not to, does.
| 2 minutes.
| Up to 8 minutes and/or demotion.
| 200 credits
|-
| i105
| '''Indecent Exposure or Hooliganism'''
| To be intentionally and publicly unclothed, yelling at people for no reason in public or on comms, throwing around stuff where it could hit someone, yelling about how terrible NanoTrasen is, etc.
| Running around the station naked or in underwear, or other such degrading activities. Drunks can be keep to sober up, but only if they are badly harassing other crew members. Regular drunks don't get arrested and if they are only a nuisance you keep them for the regular time. The mutual degradation of chasing a naked man down while he screams rape is only worth it on slow rounds. Skrell are required to be clothed just like anyone else. Tajaran can have rolled down jumpsuits unless ordered by their Head of Staff to keep it up.
| 5 minutes.
| Up to 8 minutes and/or demotion.
| 250 credits
|-
| i106
| '''Misuse of Public Radio Channels'''
| To continually broadcast unimportant, untrue, or insignificant messages on the public radio frequency.
| This is really only for people who are constantly spamming the radio, such as 'DJs' or Chaplains reading their services over the comms. Screaming fake messages like "halp security is beating me" when they aren't also counts. Speaking excessively non basic on comms also falls under this, unless it is your departmental comms (at the head's discretion and on non emergencies) and on green and yellow alert codes.
| 3 minutes.
| Ban from using any radio equipment, which requires a filed injunction.
| 150 credits
|-
| i107
| '''Violation of Injunction'''
| To violate the terms of an injunction made by Security or other legal professions.
| Injunctions can be filed for lots of different things, such as a ban on weapons carrying, or the above radio ban. They can be applied by the Head of Security, Captain, or equivalent. If they break the law in some other way, apply that sentence too.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| N/A
|-
| i108
| '''Slandering a Head of Staff'''
| To directly insult a Head of Staff with no valid complaints.
| This is most likely to happen when someone is being fired. The charge is only applicable when the statements are slanderous and untrue.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| 250 credits
|-
| i109
| '''Slander or Verbal Abuse'''
| To spread false rumors in order to damage someone's reputation, or to use racially offensive language.
| Lying about anything to make someone else look bad, or making use of obscene or offensive slurs against someone else. For example, a drunk assistant starts shouting racial slurs at xeno crew. Since this has to be proven, it's up to the appropriate officer to determine. You should also see if the insults were real, rather than friendly banter between two friends.
| 3 minutes.
| 5 minutes.
| 50 credits per applicable minute
|-
| i110
| '''Failure to Execute an Order'''
| To ignore or disregard a superior's valid orders.
| If the order is stupid, or causes you to break a law (e.g. "Release the singularity!" or "Steal that RCD for me!") you can ignore it, and probably make a complaint. However, if it's perfectly doable, lawful, and in your job description, you better do it or resign. If not following an order caused severe damage or loss of life, see "Failure to Execute an Order with Serious Consequences".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| 500 credits
|-
| i111
| '''Sexual Harassment'''
| To make unwanted sexual advances or obscene remarks towards another employee.
| This is for VERY MINOR things the other person finds offensive that are sexually related. For anything more serious see "Sexual Assault".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| N/A
|-
| i112
| '''Animal Cruelty'''
| To inflict unnecessary suffering or harm upon animals with malicious intent.
| Monkeys appropriately used for experiments or well-being (e.g Genetics, Virology, etc.) don't count, neither do the animals ordered from cargo. Shoving them in washing machines, or throwing them down disposals while still alive falls under this. Using them as food is a grey area, as long as they are not overtly caused pain in the process.
| 5 minutes
| Up to 10 minutes and/or Demotion.
| N/A
|-
| i113
| '''Vandalism'''
| To deliberately damage or deface the station without malicious intent. To cause easily repairable damage to an owned IPC, up to and including disabling the chassis.
| This can range from disassembling furniture unnecessarily, to drawing on the floor with crayons or other substances outside the chapel. Littering may also fall under this.
| 3 minutes
| Up to 10 minutes in total and/or Demotion.
| 450 credits
|-
| i114
| '''Threat of Murder or Serious Injury'''
| To threaten to kill or seriously injure an employee.
| The threat has to somewhat tangible. If it's just people arguing over the radio, it's probably not worth it. Someone shouting at someone else while chasing them with a fire extinguisher is more valid.
| 3 minutes and mandatory Tracking implant.
| Up to 10 minutes with psychiatric evaluation.
| 500 credits. Tracking implant.
|-
| i115
| '''Disrespect to the Dead'''
| To abuse bodies of dead or previously dead employees.
| Examples include, the chef using bodies in the morgue as meat, Security beating on a prisoners corpse, or using someone's body for 'experimental surgery'. Preventing a body from being cloned or cyborged also falls under this. The Chaplain or medbay tended to corpses in preperation for autopsy or funeral does not fall under this unless they're doing something bizarre and unnecessary.
| 5 minutes
| 10 minutes per corpse.
| 400 credits
|-
| i116
| '''Excessive use of force in detainment'''
| To use more than the required force to subdue a suspect.
| Repeatedly batoning a prisoner after they've been handcuffed, Using force against an unarmed and compliant suspect, and usage of lethal weapons in a non-lethal situation.
| 5 minutes and/or demotion to cadet.
| 10 minutes and demotion.
| 350 credits.
|-
| i117
| '''Violation of privacy laws'''
| To intentionally leak private aspects of employee records or financial account information to unauthorized personnel.
| Janitors found reading records flushed down disposals would be charged with this as well. Command can discuss medical records with other command (or IAA and Detectives on request) if they have a good reason, and similar with employee and security records. Using a station announcement asking someone come pick up their hemorrhoid cream is also a no. The punishment goes to the source of the leak. Authorization for respective records goes to their respective heads of staff. (CMO, HoP, HoS, and the final say of Captain.
| Fine.
| Demotion and/or Suspension.
| 500 credits.
|-
| i118
| '''Illegal search'''
| To preform a search of an employee or workplace without a search warrant, clearance, or probable cause.
| An extension of the Privacy Laws, crew members are entitled to the privacy against searches on green alert. Security is required to obtain a search warrant from either the Head of Security, Captain, or lacking either, a Warden. Searches of workplaces falls under this. Security can circumvent a search warrant requirement if they: have clearance from the respective head of staff, have directly witnessed a crime taking place, or feel there is a real and imminent danger to the safety of crew and/or station. This also does not apply to searches conducted after another, legitimate arrest.
| A written apology. Return of non-contraband goods and reduced brig time for victim.
| Demotion and/or Suspension.
| 500 credits.
|}

=== Medium Level Infractions (Amber Violations; i200's) ===
{| width="950px" style="background-color:#ffcc99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffaa55;"|No.
!style="background-color:#ffaa55; width:150px"|Infraction
!style="background-color:#ffaa55; width:300px"|Description
!style="background-color:#ffaa55;"|Notes
!style="background-color:#ffaa55;"|Standard Sentence
!style="background-color:#ffaa55;"|Repeat Offense
|-
| i201
| '''Failure to Execute an Order with Serious Consequences'''
| To ignore or disregard a superior's valid orders, which then causes serious damage to property or life.
| Like the minor crime, except this one has caused serious damage to the station, or seriously injured someone. Examples are Medical Doctors ignoring the Chief Medical Officer while patients are piling up in medbay, or Engineers ignoring the Chief Engineer and then having the singularity eat part of the station. If this causes loss of life, refer to 302.
| 15 minutes and/or demotion
| Immediate suspension. Holding until transfer
|-
| i202
| '''Resisting Arrest and/or Sparking a Manhunt'''
| To not cooperate with an officer who attempts a proper arrest, or to cause a manhunt by hiding from security.
| '''Refusing handcuffs is not resisting arrest'''. Pushing the officer trying to arrest you, or running away falls under this.
| 5 minutes. If they sparked a manhunt and did not surrender themselves, tracking implant
| Up to 15 minutes in addition to regular time
|-
| i203
| '''Suicide Attempt'''
| To attempt or threaten to commit suicide.
| An employee trying or threatening to kill himself for any reason. This includes someone saying "AI OPEN THIS DOOR OR I KILL MYSELF".
| Compulsory psychiatric examination and tracking implant
| Demotion and isolation in solitary
|-
| i204
| '''Abuse of Confiscated Equipment'''
| To take and use equipment confiscated as evidence.
| Security shouldn't be using evidence for anything but evidence. Taking "trophies" or using weapons and items seized from operatives counts as this.
| 10 minutes, re-confiscation of equipment
| Suspension or demotion
|-
| i205
| '''Illegal Detention, Arrest, or Holding'''
| To arrest, brig, or punish an employee without proper cause or reason.
| This is mainly for Security Officers who believe THEY ARE THE LAW.
| 10 minutes and/or demotion to cadet
| 15 minutes and immediate suspension
|-
| i206
| '''Neglect of Duty'''
| To fail to perform a job to a satisfactory standard.
| This can be due to honest or dishonest mistakes that the Head of the Department feels hampers Department productivity. Examples include scientists/engineers releasing phoron or causing a breach, doctors mixing up medicines that cause injury to patients, or the Warden not doing his job. Additionally, a member of Command may only be charged with Neglect of Duty with the agreement of the Captain, or through a Captain level decision passed by the Command Staff.
| 10 minutes
| 15 minutes and/or demotion
|-
| i207
| '''Infiltration'''
| To attempt to, or successfully, enter a high-security area without authorization.
| This includes the Bridge, AI upload or core, Teleporter, vault, or EVA. Using AI or Cyborg help for infiltration purposes is also considered breaking and entering.
| 15 minutes and tracking implant
| Holding until transfer and/or demotion
|-
| i208
| '''Assault'''
| To cause severe injury to another employee. To cause irreparable damage to the chassis of a free IPC.
| Anything beyond a few punches like in "Minor Assault". Also see "Attempted Murder" if the intent was to kill. This also includes poisoning with drugs, or using hallucinogens.
| 15 minutes and/or demotion
| Up to 30 minutes and suspension
|-
| i209
| '''Escaping From Confinement'''
| To escape from confinement as someone who is serving a non-permanent sentence.
| See "Escaping From a Permanent Sentence" for those who do it with permanent sentences.
| 10 minutes added and tracking implant. The original time is not reset
| Up to 30 minutes and demotion
|-
| i210
| '''Unlawful Modification of AI/Cyborg Laws'''
| To modify the laws of a cyborg or artificial intelligence, without need, proper access, or authority.
| An exception would be a law reset when obviously harmful laws have been uploaded. Only the Captain, Chief Engineer, Research Director, or Two other Heads of Staff can authorize a law change.
| 20 minutes and tracking implant
| Demotion. Holding until transfer
|-
| i211
| '''Sedition'''
| To incite rebellion, or rally against the established chain of command.
| This includes attempting to make separate areas of the ship into "Nations", arresting a head of staff without cause, or generally conspiring against the chain of command.
| 15 minutes and/or demotion
| Suspension and holding until transfer
|-
| i212
| '''Contraband'''
| To possess, use, or distribute contraband items, including drugs.
| For what does and does not count as contraband, see [[Guide to Contraband]].
| 15 minutes and confiscation of said items
| 20 minutes and demotion
|-
| i213
| '''Sabotage'''
| To hinder the efforts of the crew or station with malicious intent. To cause irreparable damage to the chassis or positronic brain of an owned IPC.
| This includes causing hull breaches, sabotaging air supplies, stealing vital equipment, etc. The intent is the most important bit here.
| 15 minutes and/or demotion
| 30 minutes, suspension and/or tracking implant
|-
| i214
| '''Exceeding Official Powers'''
| To act beyond what is allowed by the Chain of Command.
| This is for any head of staff who abuses the power given to them, such as the Head of Personnel acting like a security officer in a non-emergency, the captain acting as if he is above the law, etc. Heads of Staff trying to order a different department or ignoring the captain also comes under this. Also covers anyone illegally promoting themselves, such as with a stolen ID.
| 15 minutes and/or demotion. Head demotions require Captain or majority Command approval
| 20 minutes and suspension
|-
| i215
| '''Grand Theft'''
| To steal items that are dangerous, of a high value, or a sensitive nature. Applicable to the theft of an owned IPC.
| This means weapons, explosives or ammunition, and also includes items from the [[Guide to Contraband|High-risk Items]] page. Security Officers stealing things from the armory is an example.
| 15 minutes, confiscation of stolen items
| Suspension, tracking implant and holding until Transfer
|-
| i216
| '''Organising a Breakout'''
| To attempt, or succeed, in freeing criminals from the brig or other holding areas.
| Breaking brig windows
| 15 minutes and tracking implant
| 30 minutes
|-
| i217
| '''Illegal Blocking of Areas'''
| To make an area inaccessible for those with appropriate access.
| Bolting doors in public hallways or to those of departments you don't have control over are examples of this.
| 10 minutes
| Up to 25 minutes and/or demotion
|-
| i218
| '''Use of Excessive Force'''
| To put a victim in critical state in defense of yourself or others, or seriously injuring a suspect while attempting to detain them. This includes pulling them when they have open wounds.
| Severely injuring someone attacking you or others with no obvious threat to life, or panicking and shooting a suspect to near-death.
| 10 minutes and/or demotion to cadet
| 25 minutes and suspension
|-
| i219
| '''Mistreatment of Prisoners'''
| To intentionally act, or cause an act that puts a non-hostile prisoner's well-being in danger.
| Preventing proper treatment from being given to a prisoner, abusing a prisoner, and preventing them from having access to a viable method of communication. This includes pulling them when they have open wounds counts as abuse. In the event that a prisoner dies because of mistreatment, the charge is immediately upgraded to either murder or manslaughter.
| 10 minutes and/or demotion to cadet
| 25 minute and suspension
|-
| i220
| '''Fraud'''
| To steal or use deliberate deception in order to obtain credits from someone. Applies to amounts greater than 500 credits.
For lesser amounts, see i102 - Petty Theft.

For items of equivalent value, see i215 - Grand Theft.
| Emptying a station account for personal gain. Tricking someone into entrusting large amounts of money to another under false pretenses.
| 15 minutes and/or demotion
| 30 minutes and immediate suspension
|-
| i221
| '''Gross Negligence'''
| To display a severe lack of diligence or disregard for safe conduct, which causes or will cause serious harm to people or property.

For instances of negligence that are not seriously and imminently harmful, see i206 Neglect of Duty.
| For this charge to apply, the threat of harm must be both significant and obvious. A chemist accidentally releasing phoron gas into the station, security practicing with weapons while people are downrange, or a xenobiologist who lets slimes escape without malicious intent are eligible examples. When possible, defer to Command and the existing Neglect of Duty charge. This is more useful when the negligent crew member is acting unsupervised.
| 15 minutes
| 20 minutes and/or demotion
|-
| i222
| '''Unregistered Positronic Machine'''
| To function as an untagged positronic machine within the Republic of Biesel, or to function as a positronic machine with a tag that has been tampered with or rendered inoperable.
| [[IPC|IPCs]] are required by Republic law to be electronically tagged. This tag is typically visible to an onlooker.

Those who assist affected synthetics in tampering with or removing their tags are considered to be aiding and abetting them in this violation, and are themselves liable for heavy fines or brig time where applicable. These accomplices do not need to be retagged (if synthetic) or implanted.
| 10 minutes, immediate retagging, tracking implant, 1000 credit fine.
| 30 minutes, immediate retagging, 5000 credit fine.
|-
| i223
| '''Kidnapping of Free Intelligence'''
| To take away or transport a free positronic intelligence against its will.
| If the positronic intelligence is held for ransom or exchange, there is no difference in sentence.
| 15 Minutes
| Up to 25 Minutes
|}

=== High Severity Infractions (Red Violations; i300's) ===
==== Regarding cyborgification ====

*'''The NSS Aurora is in Tau Ceti space, which does not consider cyborgification capital punishment, making it an optional punishment.''' If Izweski or Jargon Federation citizens have a Do Not Borgify order in their records, '''their punishment becomes holding until transfer.'''

{| width="950px" style="background-color:#ffaa99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ff8855;"|No.
!style="background-color:#ff8855; width:150px"|Crime
!style="background-color:#ff8855; width:300px"|Description
!style="background-color:#ff8855;"|Notes
!style="background-color:#ff8855;"|Sentence
|-
| i301
| '''Murder'''
| To kill someone, or attempt to kill someone, with premeditated malicious intent.
| Also cover Attempted Murder. The premeditated and malicious bit is important here.
| Cyorgification or Holding Until Transfer on majority Command decision.
|-
| i302
| '''Manslaughter'''
| To kill someone without malice or forethought.
| This includes causing death due to negligence or dereliction of duty. Can also be used for excessive self-defense.
| 20 minutes and/or demotion. Tracking implant.
|-
| i303
| '''Mutiny'''
| To openly rebel against or attempt to remove command staff with violent intent.
| See "Sedition" for less violent mutineers. This generally means they use harm-intent or try to kill their superiors or advocate the same.
| Loyalty implant or cyborgification on majority Command decision.
|-
| i304
| '''Kidnapping and Hostage taking'''
| To take away or transport a victim against the victim's will.
| If the person is held for ransom or exchange, then it is considered hostage taking, which is automatically a holding until transfer.'''
| Hold until transfer.
|-
| i305
| '''Terrorist Acts'''
| To engage in maliciously destructive actions, which seriously threaten the crew or station.
| This includes deliberate arson, use of bombs, detonation of the Supermatter, etc. Collateral damage or severe station damage has to be involved. For less disastrous actions, see sabotage.
| Hold until transfer or cyborgification on majority command decision.
|-
| i306
| '''Assaulting a Head of Staff'''
| To assault a Head of Staff, causing severe damage.
| Exactly like "Assault", but this time against a Head of Staff.
| 20 minutes and/or demotion.
| 40 minutes, suspension, and tracking implant.
|-
| i307
| '''Escaping From Holding Until Transfer'''
| To escape, or attempt to escape, from the brig or other holding area when being held until transfer.
| They have to have been properly convicted for it to be a life sentence.
| Cyborgification or hold until transfer at majority command decision.
|-
| i308
| '''Corporate Espionage'''
| To act as an agent of a terrorist or anti-Corporation group.
| Espionage, disclosure of corporate secrets, or any other assistance rendered to outside hostile organisations, or their representatives in hostile activities to the Corporation, committed by a employee of Corporation.
| Holding until transfer or cyborgification at majority command decision.
|-
| i309
| '''Sexual Assault'''
| To assault, or attempt to assault, someone else sexually, including rape.
| ERP scenes, or erotic roleplay, is a permabannable offence. Adminhelp it if this happens to you; it's against server rules, not just station rules.
| 30 minutes, tracking implant.
| Holding until transfer.
|-
| i310
| '''Automacide'''
| To willfully, unlawfully and permanently terminate a free positronic intelligence.
| Essentially the murder charge for free IPCs. Premeditation and malicious intent are still important here.
| 20 minutes, demotion
| Holding until transfer.
|}

=== Modifiers & Special Situations ===

{| width='825px' style='text-align:center; background-color:#aaffaa;' border=1 cellspacing=0
! style='background-color:#55ff55;' width='150px'|Situation
! style='background-color:#55ff55;' width='300px'|Description
! style='background-color:#55ff55;' width='100px'|Benefit
|-
|'''Surrender'''
| Coming to the brig, confessing what you've done and taking the punishment. Getting arrested without putting a fuss is not surrender. For this, you have to actually come to the brig yourself.
| Up to -25%, and should be taken into account when determining the severity of crimes.
|-
|'''Re-education'''
| Getting de-converted from revolutionary.
| Up to and including immediate release
|-
|'''Cooperation with prosecution or security'''
| Being helpful to the members of security, revealing things during questioning or providing names of head revolutionaries.
| Up to -25%. In the case of revealing a head revolutionary, up to -50%.
|-
|'''Immediate threat to the prisoner'''
| The singularity eats something near the brig, an explosion goes off, etc.
| Officer must relocate the prisoner(s) to a safe location. Otherwise, immediate release. Life sentences must be reapplied after danger has passed.
|-
|'''Medical reasons'''
| Prisoners are entitled to medical attention if sick or injured.
| Medical personnel can be called, or the prisoner can be escorted to the Medbay. The timer continues to run during this time.
|-
|'''Self Defence'''
| Assault and even homicide can be justified if it was necessary for prevention of loss of life. (Note that there are borders of acceptable self-defence, and killing a man who just punched you is subject to "Use of Excessive Force")
| Up to and including immediate release.
|}

==== Parole ====

Parole is temporarily releasing a prisoner before their sentence has been fully completed on the promise of good behavior. Parole can be given for any number of reasons, including brig overcrowding, a reward for good behavior or confession, or if the prisoner's skills are in need by the station such as a doctor or engineer.

The Warden or Head of Security can choose to give prisoners parole. A tracking implant is recommended if the prisoner is a flight risk (IE an engineer going EVA, but it is up to the Warden/HoS to determine how much of a risk they are.) Tracking implants for minor crimes are not worth it.

On the completion of their time they are simply marked as released as normal.

If they commit any crimes their parole is ended and they must serve out the remainder of their time in the brig with the new crime's time added on.

Parole can be given immediately after initial processing; theoretically a prisoner can spend their entire sentence out of the brig.

=== Terminology and Clarifications ===
'''Cyborgification''' The removal of a person's brain for transplanting into a Cyborg Chassis. Often also known as Shackling.

'''Suspension''': Changing ID title to "suspended", zero access.

'''Demotion''': Can be done up to and including Assistant position, by Head of Personnel or Captain's decision.

'''Employee''': Employee of NanoTrasen, as defined by the station's commanding officer. All non-employee subjects are still protected by these laws.

'''Empowering''': Illegal acquiring (not via Head of Personnel or Captain) of access.

'''Head of Staff''': Crew members occupying one of the following positions: Captain, Chief Engineer, Head of Personnel, Head of Security, Chief Medical Officer, Research Director.

'''HuT''' Holding until Transfer

'''Lethal Situation''': A situation in which there is an apparent and real threat the the well-being of all those involved.

'''Repeat Offenders''': For repeat offenders, use the "repeat offense" punishment.

'''Severe Injury''': A state in which the victim is in a critical condition and is having difficulty maintaining consciousness.

Demotion and dismissal also require the removal of equipment from the previous job. E.g: Uniforms, weapons, bombs, PDA cartridges, etc.

For the purposes of Cyborg/AI laws, crewmembers that have been convicted, or are being held in detention, are considered to be below even the AI/Cyborgs in terms of rank.

In cases where the final sentence is more than 90 minutes, it is changed to HuT

The standard penalty can be applied without a tribunal by Security Officers.

{{Security}}
{{Command}}
{{Gameplay Guides}}
[[Category:Guides]]
[[Category:Pages]]
[[Category:Security]]
[[Category:Command]]

Guide to Law

2020-09-15T04:53:40Z

Mofo1995: /* Republic of Biesel */ Added Vulgaris to the list, to conform with pre-existing sentence on corp regs page.

{{WIP}}

{{Navbox Lore}}

This is a brief guide on how the Law works in different parts of the galaxy.

'''Note:''' Nanotrasen has NOT signed onto this convention.
Our station regulations are the regulations Biesel mandates NT enforce in Biesel space.

==Luna Convention of Galactic Law==
#Declares capital punishment a violation of sentient rights.
#Outlaws torture or 'revenge' attacks on captured hostiles after armed conflict.
#Forbids hindrance of humanitarian or medical workers.
#Forbids cruel or excessive punishment of criminals.
#Guarantees all sentients the rights to: Water, food, medical care, and protection of civilians from armed conflict.

==Republic of Biesel==

*You are entitled to a lawyer.
*Capital punishment is not legal.
*Cyborgification is not considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a tribunal for major crimes; with a public or personal defender.
*Mega-corporations are expected to follow Biesel laws when in Tau Ceti space.
*Biesel is a signatory of the Luna Convention of Galactic Law.
*Alcohol, Tobacco, Mercury Mono lithium Sucrose (space drugs), Psilocybin, Ambrosia Deus, Ambrosia Vulgaris, and Reshi are are all legal for possession and distribution.

===On Capital Punishment And Major Crimes in Biesel===
Capital punishment is illegal, but Biesel does not consider borging as a form of execution despite the Luna Convention of Galactic Law. Borgification is considered an alternative to life imprisonment.

==The Sol Alliance==
*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are expected to follow local laws when in Alliance space.
*The Alliance is a signatory of the Luna Convention of Galactic Law.

===On Capital Punishment And Major Crimes in the Sol Alliance===
Capital punishment is legal, and regularly executes 714 people every year on average; all of them major felons. This is despite being a signatory of the Luna Convention of Galactic Law.

==Izweski Hegemony==
*You are not given lawyer.
*Capital punishment is legal.
*Cyborgification is considered a fate worse than death and is illegal.
*Authorities do not need warrants to search or arrest you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. You make your case before the relevant Lord of the land you committed the crime on.
*Mega-corporations are expected to follow local laws when in Hegemony space.
*The Hegemony is not a signatory of the Luna Convention of Galactic Law.

==People's Republic of Adhomai==
*You are given a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment, but is rarely done by lack of ability.
*Authorities do need warrants to search or arrest you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in People's Republic of Adhomai space.
*The People's Republic is not a signatory of the Luna Convention of Galactic Law.

==Democratic People's Republic of Adhomai==
*You are given a lawyer.
*Capital punishment is legal.
*Cyborgification is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in Democratic People's Republic of Adhomai space.
*The Democratic People's Republic is not a signatory of the Luna Convention of Galactic Law.

==New Kingdom of Adhomai==
*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in New Kingdom of Adhomai space.
*The New Kingdom of Adhomai is not a signatory of the Luna Convention of Galactic Law.

==Jargon Federation==
*???

==The Republic of Elyra==
*???

==The Empire of Dominia==
*You are entitled to a lawyer.
*Capital punishment is not legal with a large caveat (See Religious Crimes below).
*Cyborgification is considered a fate worse than death and is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are expected to follow local laws when in the Empire of Dominia.
*The Empire is not a signatory of the Luna Convention of Galactic Law.

===On Religious Crimes===
Alongside standard law sits the religious law of the Tribunal. The religious laws overrule that of the standard law and though most punishments are in the form of heavy fines or corporal punishment all can lead to captial punishment - death by firing squad. Any religious law/edict breaker is judged by a panel of randomly selected local clergy of the rank Priest or higher.

==The Eridani Corporate Federation==
As a special member of the Sol Alliance the Eridani Corporate Federation laws largly mimic those of SolGov with a few caveats.

*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you however warrants based on "suspected sabotage of corporate interests" or "suspected violation of the Non Aggression Protocol" are extremely easy to obtain.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are '''not''' expected to follow local laws when in Eridani Corporate Federation space.
*The Eridani Corporate Federation is a signatory of the Luna Convention of Galactic Law.

===The Non Aggression Protocol===

The Non Aggression Protocol is considered sacrosanct within the Eridani Corporate Federation and though complex legally, can largely be reduced to the idea that no one within Eridani space should conspire to damage, take part in damaging or incite others to damage corporate interests within Eridani space. Punishments vary from fines to capital punishment. Though oft times a divided people, most Eridanians enshrine the protocol and place great importance on it, though many Eridanians would debate what constitutes a "corporate interest" and "damage(s)".

==Coalition of Colonies==
*???

[[Category:Lore]]
[[Category:Pages]]
[[Category:Humanity]]
[[Category:Skrell]]
[[Category:Unathi]]
{{Navbox Lore}}

Guide to Law

2020-09-15T04:51:06Z

Mofo1995: /* Republic of Biesel */ Updated to add the drugs that were legalized in this article: https://forums.aurorastation.org/topic/8890-the-bieselitte-times/?tab=comments#comment-105204

{{WIP}}

{{Navbox Lore}}

This is a brief guide on how the Law works in different parts of the galaxy.

'''Note:''' Nanotrasen has NOT signed onto this convention.
Our station regulations are the regulations Biesel mandates NT enforce in Biesel space.

==Luna Convention of Galactic Law==
#Declares capital punishment a violation of sentient rights.
#Outlaws torture or 'revenge' attacks on captured hostiles after armed conflict.
#Forbids hindrance of humanitarian or medical workers.
#Forbids cruel or excessive punishment of criminals.
#Guarantees all sentients the rights to: Water, food, medical care, and protection of civilians from armed conflict.

==Republic of Biesel==

*You are entitled to a lawyer.
*Capital punishment is not legal.
*Cyborgification is not considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a tribunal for major crimes; with a public or personal defender.
*Mega-corporations are expected to follow Biesel laws when in Tau Ceti space.
*Biesel is a signatory of the Luna Convention of Galactic Law.
*Alcohol, Tobacco, Mercury Mono lithium Sucrose (space drugs), Psilocybin, Ambrosia Deus and Reshi are are all legal for possession and distribution.

===On Capital Punishment And Major Crimes in Biesel===
Capital punishment is illegal, but Biesel does not consider borging as a form of execution despite the Luna Convention of Galactic Law. Borgification is considered an alternative to life imprisonment.

==The Sol Alliance==
*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are expected to follow local laws when in Alliance space.
*The Alliance is a signatory of the Luna Convention of Galactic Law.

===On Capital Punishment And Major Crimes in the Sol Alliance===
Capital punishment is legal, and regularly executes 714 people every year on average; all of them major felons. This is despite being a signatory of the Luna Convention of Galactic Law.

==Izweski Hegemony==
*You are not given lawyer.
*Capital punishment is legal.
*Cyborgification is considered a fate worse than death and is illegal.
*Authorities do not need warrants to search or arrest you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. You make your case before the relevant Lord of the land you committed the crime on.
*Mega-corporations are expected to follow local laws when in Hegemony space.
*The Hegemony is not a signatory of the Luna Convention of Galactic Law.

==People's Republic of Adhomai==
*You are given a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment, but is rarely done by lack of ability.
*Authorities do need warrants to search or arrest you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in People's Republic of Adhomai space.
*The People's Republic is not a signatory of the Luna Convention of Galactic Law.

==Democratic People's Republic of Adhomai==
*You are given a lawyer.
*Capital punishment is legal.
*Cyborgification is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in Democratic People's Republic of Adhomai space.
*The Democratic People's Republic is not a signatory of the Luna Convention of Galactic Law.

==New Kingdom of Adhomai==
*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are entitled to a trial for your crimes, presided by a judge and against a jury of your peers.
*Mega-corporations are expected to follow local laws when in New Kingdom of Adhomai space.
*The New Kingdom of Adhomai is not a signatory of the Luna Convention of Galactic Law.

==Jargon Federation==
*???

==The Republic of Elyra==
*???

==The Empire of Dominia==
*You are entitled to a lawyer.
*Capital punishment is not legal with a large caveat (See Religious Crimes below).
*Cyborgification is considered a fate worse than death and is illegal.
*You do have the rights of privacy; police need a warrant to search you.
*You do not need to be told your rights when being arrested.
*You do not need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are expected to follow local laws when in the Empire of Dominia.
*The Empire is not a signatory of the Luna Convention of Galactic Law.

===On Religious Crimes===
Alongside standard law sits the religious law of the Tribunal. The religious laws overrule that of the standard law and though most punishments are in the form of heavy fines or corporal punishment all can lead to captial punishment - death by firing squad. Any religious law/edict breaker is judged by a panel of randomly selected local clergy of the rank Priest or higher.

==The Eridani Corporate Federation==
As a special member of the Sol Alliance the Eridani Corporate Federation laws largly mimic those of SolGov with a few caveats.

*You are entitled to a lawyer.
*Capital punishment is legal.
*Cyborgification is considered capital punishment.
*You do have the rights of privacy; police need a warrant to search you however warrants based on "suspected sabotage of corporate interests" or "suspected violation of the Non Aggression Protocol" are extremely easy to obtain.
*You do not need to be told your rights when being arrested.
*You do need to be informed of your charges when arrested.
*You are not entitled to a tribunal for major crimes; with a public or personal defender. This is instead handled by a Trial by Magistrate.
*Mega-corporations are '''not''' expected to follow local laws when in Eridani Corporate Federation space.
*The Eridani Corporate Federation is a signatory of the Luna Convention of Galactic Law.

===The Non Aggression Protocol===

The Non Aggression Protocol is considered sacrosanct within the Eridani Corporate Federation and though complex legally, can largely be reduced to the idea that no one within Eridani space should conspire to damage, take part in damaging or incite others to damage corporate interests within Eridani space. Punishments vary from fines to capital punishment. Though oft times a divided people, most Eridanians enshrine the protocol and place great importance on it, though many Eridanians would debate what constitutes a "corporate interest" and "damage(s)".

==Coalition of Colonies==
*???

[[Category:Lore]]
[[Category:Pages]]
[[Category:Humanity]]
[[Category:Skrell]]
[[Category:Unathi]]
{{Navbox Lore}}

Lore Staff Guidelines

2020-08-01T06:56:52Z

Mofo1995: Bolded disclaimer

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. In order to maintain consistency, lore developers may apply to lore team administration to retcon past news articles. When applying to have an article retconned, they must include a link to the article, and an explanation for why it is no longer canon and contradicts present lore. If it at all possible news articles should not be retconned and this should be used as a last resort. Unless if the content is grossly and wholly incompatible and contradictory to current lore, the request may be denied. If a request for news retcon is accepted, the loremaster will move it to the archive subforum in the Galaxy News Database. The archive will exist entirely for the purpose of archiving retconned news articles. An explanation for why it is no longer canon will be added to the top of the article which is being retconned. By having the articles which are no longer canon in an archive with reasons for removal attached, we preserve the creative writing of the past, explain the necessity for its removal, and maintain high visibility for article removals so that the community can stay informed on the changes.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must have the approval of lore team management.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

Lore Staff Guidelines

2020-08-01T06:56:27Z

Mofo1995: The rules and regulations for lore team, imported from the forum. Last updated May 20 2020.

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Mofo1995 as Interim Loremaster and Kyres1 as Deputy Interim Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. In order to maintain consistency, lore developers may apply to lore team administration to retcon past news articles. When applying to have an article retconned, they must include a link to the article, and an explanation for why it is no longer canon and contradicts present lore. If it at all possible news articles should not be retconned and this should be used as a last resort. Unless if the content is grossly and wholly incompatible and contradictory to current lore, the request may be denied. If a request for news retcon is accepted, the loremaster will move it to the archive subforum in the Galaxy News Database. The archive will exist entirely for the purpose of archiving retconned news articles. An explanation for why it is no longer canon will be added to the top of the article which is being retconned. By having the articles which are no longer canon in an archive with reasons for removal attached, we preserve the creative writing of the past, explain the necessity for its removal, and maintain high visibility for article removals so that the community can stay informed on the changes.

=== IN-GAME NEWS ARTICLES ===

When possible, news articles should be posted to the in-game newscasters through the web interface. The web interface can be found at https://byond.aurorastation.org/ which is also a valuable resource for whitelist management. In-game news articles can be found in the news category under the admin tab. Other than events, in-game newscaster articles are the highest visibility method of lore writing, and should be used at every opportunity. The procedures and rules for utilizing the in-game news articles are the same as the forum articles. See the following thread for a guide on how to use the web interface to make in-game articles:

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must have the approval of lore team management.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

=== WHITELIST MANAGEMENT ===

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives. After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration. Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

User:Mofo1995

2020-06-18T02:06:58Z

Mofo1995: /* Scratch Pad Work: */ Transferred pen and paper notes to scratch pad for ease of access, readability, and editing.

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg|1000px]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

===No Continent===
Craterview

==Transfer of Current Notes to Digital==

===Belle Cote===
Decently far north, northernmost city. At southernmost edge of peninsula. Which is hedged in by mountains. Forests? Plains? Canals, focus on high fashion, always pushing the envelope with yearly fhasion shows. Citizens there are known to be a bit stuck up, heavy focus on manners, looks down on others for not being up to date on their trends. Even the poorest dress in their outlandish styles. Common honeymoon and wedding destination. Industry of Belle Cote based around mostly artisans producing hand-made textiles competing for the most prestigious fashion. SOme textiles mills also exist belonging to more unscrupulous designers, though they are very looked down on by most natives and only the least fashionable wear them. The mills use the fame of the city to sell their merch to department stores abroad.

===Ashton===
Far away from water or bodies of water. Located at a very central place on Selene continent. Could be in middle of plains surrounded by farmlands. Central location necessary for its business focus. Could have started as a central butchery and meat processing location for the surrounding farmlands. Important crossroads location connecting all of them, maybe actually started as large farmer's market before industries started popping up. As Biesel became populated enough, maybe the first local automotive and hovercar manufacturing sprung up there. Moguls began building up the city with their niceties so they could live there and manager their businesses year round instead of travelling from Mendell. Today known for old money combined with redneck cowboy aesthetic, think "Doug Dimmadome." Still holds yearly farmer's market in one of its suburbs.

===Cape City===
Jokingly and affectionately called "the city of hereos" and the location of modern superhero movies in the Biesellite film industry. Some actors even travel the streets in costume for press and PR events and to drum up hype for upcoming releases.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

=Cool Flags =
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

User:Mofo1995

2020-06-18T01:58:29Z

Mofo1995:

User:Mofo1995

2020-06-18T01:58:11Z

Mofo1995: /* Flags */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

===No Continent===
Craterview

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

=Cool Flags =
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

User:Mofo1995

2020-06-18T01:57:52Z

Mofo1995: /* Breakdown of Cities by Continents: */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

===No Continent===
Craterview

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

== Flags ==
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

User:Mofo1995

2020-06-18T01:57:19Z

Mofo1995: /* Scratch Pad Work: */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

== Flags ==
[[File:PRA Flag.png|500px]] [[File:DiamondALA.png|500px]] [[File:New Kingdom of Adhomai.png|500px]]

User:Mofo1995

2020-06-18T01:56:52Z

Mofo1995: /* Scratch Pad Work: */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png|500px]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:56:11Z

Mofo1995: Added map for quick reference on current project.

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Biesel Cities.png]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:55:30Z

Mofo1995: /* Eos */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scottsdan

Lakeside

Ports-Ville

Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:55:15Z

Mofo1995: /* Breakdown of cities by continents: */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of Cities by Continents:==
===Astraeus===
Cape City

Mendell City

===Selene===
Belle Cote

Phoenix Port

Ashton
===Eos===
Scotssdan

Lakeside

Ports-Ville

Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:54:43Z

Mofo1995: /* Scratch Pad Work: */

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

= Scratch Pad Work:=

==Breakdown of cities by continents:==
===Astraeus===
Cape City
Mendell City
===Selene===
Belle Cote
Phoenix Port
Ashton
===Eos===
Scotssdan
Lakeside
Ports-Ville
Metropolis

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:52:27Z

Mofo1995:

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:52:12Z

Mofo1995:

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Interim Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

''Contact me with any questions about the following: [[Tajara]], [[Adhomai]], [[Notable Tajara]], [[Tajaran Military Structures]], [[The Nal'tor College of Career Excellence]], [[Tajaran Ethnicities]], [[Adhomai Economy]], [[Ma'ta'ke Gods]], [[S'rand'marr]], the timeline of the Tajara''

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2020-06-18T01:49:18Z

Mofo1995: /* Plans: */

{{Navbox Tajara Lore}}

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

''Contact me with any questions about the following: [[Tajara]], [[Adhomai]], [[Notable Tajara]], [[Tajaran Military Structures]], [[The Nal'tor College of Career Excellence]], [[Tajaran Ethnicities]], [[Adhomai Economy]], [[Ma'ta'ke Gods]], [[S'rand'marr]], the timeline of the Tajara''

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Cities on the planet of Biesel expansion WHY CAN'T CITIES OUTSIDE OF MENDELL HAVE NICE THINGS???

== Helpful Maps ==
[[File:Ahdomai Political cities1.png|825px|left]]
[[File:Geographical1.png|825px|right|]]
[[File:AdhomaiAncientRegimesNames.png|825px|left]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

Aut'akh

2019-12-05T07:48:30Z

Mofo1995: /* Clan Saramiite - The Sledgehammers */ Link to autakh picture removed, in accordance with accomodating VUX's desire for the picture to be removed along with their dismissal from the team.

{{Navbox Lore}}
{{Navbox Unathi Lore}}
{{Infobox Species
|Species = Unathi
|Scientific = U. Sapiens / Sinta'Unathi
|Image = Autakimagedone.png
|System = Uueoa-Esa
|World = Moghes
|Language = Sinta'Unathi
|Politic = The Free Conclave / The Polar Insurrection
}}
{{toc_right}}

== Overview ==

The Aut'akh are a decentralized, leaderless religious movement and society. Formed by a group of scientists and engineers after the Contact War, the Aut'akh symbolically seize and control their own spiritual destiny through ritualistic augmentation. After revealing themselves to the galaxy, the immediately besieged and haggard Aut'akh have been making friendly gestures toward nearly every power in the galaxy in an attempt to be formally recognized and avoid destruction by their brothers in the Hegemony. The Aut'akh use an information network called the "Mesh" that allows their operating system, called Oss, to facilitate decisions and projects based on input and projections to aid in the management of society. While Oss is considered to be a manifestation of Sk'akh, Oss has no binding authority over the Aut'akh as its decisions are informed by programmers and followed voluntarily.

=== Job Restrictions ===
'''Aut'akh can take any non-command job.'''

On their introduction to March 23rd 2019, Aut'akh could have only taken the following jobs:
*Assistant or internship level positions. (Medical Resident, Engineering Apprentice, Security Cadet)
*Janitor.
*Cargo Technician.
*Counselor
*Shaft Miner

This represented their integration and job training needed for higher level positions. Aut'akh could have still been promoted interim during rounds if a Head chose to.

'''Now they can take any non-command job.'''

=== Mechanics ===
*Aut'akh have fair resistance to cold and reduced resistance to heat.
*Aut'akh have mechanical limbs which can be detached at will. Some of these limbs have additional functionality such as department-appropriate tools.
*Aut'akh have mechanical eyes that allow them to access department HUDs, but which can be shut down by flashes.
*Aut'akh have the ability to exchange nutrition and hydration for emergency life-saving chemicals.
*Aut'akh have a slightly elevated stamina and a slightly slower sprint.
*For limb repairs, Aut'akh need cables or welders like IPC repairs.
*For surgery you must first cut open the metal chest with a saw, and then operate as normal.

=== Biology and Augments===

Aut'akh claim they are immortal due to their augmentation, but being around for only a decade there is no way to truly verify this. Their life expectancy ranges from between hundreds to thousands of years, but time will tell. Currently the oldest Aut'akh is 72, being augmented at 68.

Since they are carnivorous species, their diet mostly consists of meat, though they do have a tolerance to some plants and fruits. However, they do not get any nutrition from plants, so they are mostly used as garnish or decoration.

Internally, barring the additional organs, Aut'akh retain all of the regular internal organs of regular Unathi.

Both male and females retain all functions necessary for reproduction.

Aut'akh can still 'feel' and sense pain, but face difficulty in really feeling abstract things like the warmth of a sunny day at the beach, or a cool breeze. They are still able to feel, but many Aut'akh describe feeling physical sensation like hearing a muted conversation from another room. Aut'akh retain their sense of smell and taste, and enjoy many diverse foods when they can get it.

==== Organs Present In Game ====

*'''Haemodynamic control system''' - Allows the user to stabilize themselves (at least temporarily) from major injuries at the cost of 50% to 75% of their hunger.

*'''Adrenal management system''' - A series of mechanical stimulants and extra glands placed along the adrenal system. Allows the user to cause minor toxin/brute damage to the entire body for the duration of the effect in exchange for a temporary endurance boost.

*'''Soul Anchor''' - Flavor organ in the head. Takes the form of a brain implant connected to the region associated with religious experience. Does nothing in gameplay. Contains the Oss Operating system.

===== Graspers =====

Graspers must always be placed where your right hand is, and will not work as a left hand or left arm!

===Physical Appearance===

Aut'akh tend to favor colors that match existing Unathi scale colors. The major color categories Red, Black, Orange-brown ("sand colored") and Green. However, some Aut'akh choose to express themselves with colors ranging from white, dark blue, or gray.

Female and male Aut'akh look almost completely indistuinguishable, and only Aut'akh tend to be able to tell each other apart.

Aut'akh tend to weigh between 290 - 320 pounds.

Aut'akh tend to be between 5'9" to 7'0".

Both sexes stand on plantigrade legs, jointed backwards, and have clawed feet and hands. They retain their very long tongues, which may stretch up to a foot and a half long, forked just like a serpent's. In much the same manner as snakes, the Unathi can sample the air around them using their tongue, on top of their present sensors. This tongue is usually black or an extremely dark red, and usually a foot in length. Some Aut'akh still lick their own eyeballs out of habit, despite not longer needing to.

=== Naming Schemes ===

Aut'akh Unathi will identify themselves with their Aut'akh clan name and then their personally chosen name, although those nostalgic for their past may append their former clan name on the end.
For example, Gorish Mum'bazi, when he joins the Aut'akh, would be named '''Veetek Uza'''. Or if he was nostalgic, '''Veetek Uza-Mum'bazi'''.

Commonly, interactions within the Mesh are facilitated with a 'username' for every Aut'akh. User names are deeply personal things, denoting one's soul separated from Sk'akh.
For example, '''Veetek Uza''' may be represented as '''VeetUz#Aut'akhJoy''' or may discard the name entirely, '''RedPolymer4Sk'akh'''

== Clans of the Communes ==

The Aut'akh clans are more akin to guilds than actual clans, being voluntary organizations biased toward certain crafts. This is due to most of the Aut'akh population being exiles from other clans, or those whose clans were destroyed in the contact war, and many unrelated Unathi can belong to a single clan.

Not all decisions are made from Oss itself. Anything that is not a community wide decision is handled internally with the Clans or immediate family/friends. Issues such as digging, mining, power generation, electrical grids, aquaculture building, or personal matters between people, are handled by the Clan it pertains to, or that Clan asks for a mediator if they have a dispute with another clan. Clans almost always cooperate with each other if it enables their work or the other clan's work. That said, disagreements between Clans or internally usually have the Aut'akh involved in the debate citing projections made by Oss, if any were made. But in day to day life, miners will dig, fishermen will fish, and Optikam will engage in daring raids to sabotage Hegemon incursions.

Almost all of the traditional Clans of the Aut'akh subscribe to traditional [[Unathi Honor]].

===Clan Veetek - The Engineers===

Named after the VTEC modules they carefully craft, no mech race is complete without a Veetek representative present, and Veetek members tend to make up the core of the Aut'akh exosuit effort. They tend not to become involved too heavily in internal Aut'akh politics in their eternal quest for speed. Veetek mechanics are often found making dangerous, ill-advised modifications to Aut'akh drones and androids, or posting endlessly on the Mesh about the newest mech models.

*'''Moghean Veteek''' have begun creating 'Scrapyard Mechs' because of the on-going blockade limiting their access to complex resources for mech production. Assembled from scrap and components recovered by scavenging teams in the Wasteland, Veteek mecha drivers take deep pride in their hodgepodge, ugly, "good enough" mechs that they treat like one of their own hatchlings. This includes the mechs meant for combat.

*'''New Gibson Commune''' Veetek have better access to mech technology present in NanoTrasen, but many struggle to come to terms with the reality that whatever mechs they produce for NanoTrasen are property of NanoTrasen itself, and that they will need to hand it over eventually.

When working for Nanotrasen, clan Veetek tends to work in the '''science''' and '''medical''' departments.

===Clan Mahashik - The Miners===

Named after the geologic mohorovicic layer they probe for minerals, this mining clan has a high proportion of heavy robot frames. They are often employed as a back line defense for the home bunkers, and they generally see themselves as the pillars on which Aut'akh society are built. Clan Mahashik is also responsible for power management and construction in many cases, as their heavy, durable bodies are well suited to the task.

*'''Moghean''' Mahashik spend most of their time underground mining into the crust, expanding the bunkers, and repairing damage caused by incursions from the wider world. They are slowly developing a more revanchist attitude towards the attacking Izweski and Maraziites, and are beginning to question the doctrine of remaining strictly defensive. They are known to host BBQ's whenever there is available meat.

*'''Gibson Mahashik''' spend most of their time trying to dig into the crust of New Gibson and quickly running afoul of the complex legal troubles regarding land ownership, digging permits, and other bureaucratic elements of the State. They also help maintain the fragile infrastructure of the new colony when they are not working for NanoTrasen to help repay the debt the commune owes. With their wide ranging responsibilities, many lament their lack of time to host BBQs.

When working for Nanotrasen, clan Mahashik tends to work in the '''supply''' and '''engineering''' departments.

===Clan Siansi - The Industrialists===

Named after the automated production systems they maintain. They're often seen as a more spiritual clan, as they tend to take rather minimalist bodies, or alternatively remain mostly organic, instead using direct or wireless connection to control industrial equipment with their minds. They tend to provide most of the industrial goods that the Autakh require, and they tend to style themselves as wise sages, often using mystified terms and technical jargon unique to Siansi.

*'''Moghean Siansi''' spend most of their time inside underground workshops, producing finished goods and trying to find more effective ways to utilize dwindling resources in their factories and workshops. As a group they are struggling to reconcile their desire to keep the polar commune peaceful and defensive only. Siansi sages often preach against the growing revanchism, but their words are beginning to become less convincing to the clans who face nearly daily strikes and attacks from the outside world.

*'''Gibson Siansi '''spend most of their time inside retrofitted workshops, designing consumer and finished goods. Production costs on New Gibson remain high due to the monopoly NanoTrasen has over the system and exclusive supply deals with the commune. The Siansi are growing increasingly frustrated at NanoTrasen requiring them to sell almost a third of all produced goods to the company at prices that match production costs, only to have NanoTrasen then turn around and sell those goods at a mark up with the profits going to NanoTrasen shareholders rather than towards repayment of the debt.

When working for Nanotrasen, clan Siansi tends to work in the '''science''' and '''civilian''' departments.

===Clan Optikam - The Shadowscales===

Named after the optical camouflage systems they covet, Optikam busies themselves with the business of stealth, scouting, and long-range battle. Optikam commandos contribute some of their members of the Autakhs' highly mobile Hussar units, and they tend to recruit out of sickly, thin, short, or albino members of the species. They tend to have a sort of scheming underdog mentality; they'll do anything to win, because winning is the only honorable thing. Other clans tend to look down upon them because of their use of underhanded tactics. Strangely, members of clan Optikam often end up filling simple roles such as custodians and delivery people.

*'''Moghean Optikam''' have exhausted all of their patience for non-Aut'akh Unathi. The Clan has openly advocated for striking back at the Hegemony and Maraziite Order to bring the fight away from their homes. Optikam commanders use the controversial BattleTrance.OSS Implement to engage in brutal and ruthless attacks on encroaching forces. With a grim determination to win the war by any means necessary, Optikam are beginning to worry the rest of the Commune by abandoning ancient traditions of honorable warfare in favor of a new, efficient doctrine of asymmetrical war.

*'''Gibson Optikam''' resent the exploitation of the Commune by NanoTrasen and humanity. While not as brazenly hostile and revanchist as their Moghean counterparts, Optikam are still known to try to engage in small acts of sabotage and resistance. Losing paperwork, turning off pumps, disabling a pipe, faxing solid black papers to CCIA offices to waste all their ink, and dozens of other minuscule acts. The Optikam in New Gibson are attempting to kill NanoTrasen by a thousand tiny cuts.

When working for Nanotrasen, clan Optikam tends to work in the '''security''', '''civilian''', and '''medical''' departments.

===Clan Saramiite - The Sledgehammers===

Named after the diamond-hard material that makes up their projectiles and the tips of their weapons, and given the styling of a religious order, the Saramiite clan operates the largest number of heavy combat cyborgs, serving as the core of the Autakhs' heavy infantry cuirassier units. They tend to recruit out of the largest, strongest unathi available, seeing themselves as the ultimate shield of the Aut'akh, the pinnacle of warfare, without whom the other clans would be exterminated.

*'''Moghes Saramiite''' are considered all fire and brimstone by the rest of the Commune. They are the driving force behind the growing revanchism. The majority of Saramiites want nothing more than to destroy the Hegemony and the Maraziites to keep everyone safe. They continue rigorous training and demand stronger and stronger weapons and augments be allocated to them. As resources are strained, many groups within the Commune willingly hand over their own limited supplies to aid the Saramiites who are keeping them safe.

*'''Gibsonite Saramiite''' are generally frustrated that their primary purpose as defenders and warriors has been made redundant. Many of them still patrol the Commune, but with a lack of threats and the presence of Tau Ceti law enforcement (who now have jurisdiction over Saramiites entirely) many of them are becoming increasingly listless and strike off to work for NanoTrasen or the [[Tau Ceti Foreign Legion]]. They resent the soullessness with which their job is treated in Tau Ceti and in corporate work in general. They don't like the mundane work that is a corporate or government security job but it's the only thing they're really prepared for. Other Saramiites go as far as to join criminal elements as hired muscle to help the Commune and experience something fulfilling and exciting in their purpose, despite the dread it brings.

When working for Nanotrasen, clan Saramiite tends to work in the '''security''' and '''engineering''' departments.

===Clan Kethresh - The Fishermen===

Named after the aquafarmer equipment they prize, clan Kethresh specializes in bringing aquaculture vats and fisheries to dangerous places. Most of clan Kethresh operate in heated domes above the bunker complexes, and thus are generally the first to suffer during a Hegemony incursion. For this reason, Kethresh aquafarmers tend to adopt a determined but fatalistic attitude. They have little fear, but are absolutely resigned to death.

*'''Moghes Kethresh''' feel increasingly fatalistic. They're hopeful that the Saramiites can stop the harassment from the Hegemony but they're cynical in that they expect nothing will change and all their work will continue to be destroyed over and over.

*'''Gibsonite Kethresh''' are slowly becoming more hopeful. They are unlikely to be attacked and aquaculture is one of the few things that NanoTrasen and the State do not intrude on, so they're left nearly unmolested for the first time ever.

When working for Nanotrasen, clan Kethresh tends to work in the '''supply''' and '''civilian''' departments.

===Clan Ansiba - The Scholars===

Named after an arcane piece of telecommunication equipment, clan Ansiba is the newest and weakest of all the clans, only existing as long as the Exile Convoy. They are a highly thoughtful and scientific clan, recruiting exclusively from the ranks of the most intelligent unathi. Ansiba is the clan that has the closest relationship with non-Aut'akh unathi, even going so far as to operate cults in several of the Hegemony's major cities. Ansiba tends to have a smug, superior attitude towards the other clans, and they have the highest proportion of Paradigms of any clan.

*'''Moghean Ansiba''' started as scientists, but they've since expanded into the production and maintenance of telecommunications equipment, broadcasting, and infiltration of the Hegemony. They coordinate with the Optikam for infiltration missions. They run pirate radio and broadcast pro-Autakh propaganda. In disguises or even lacking any external, obvious augments, they also travel the Wasteland and Moghes to seek out exiles and people unhappy with the hegemony in order to recruit them. They are extremely interested in robotics and, despite their lack of complex electronics to build them, view the [[IPC]] as entities of magic and as valuable friends and allies. This puts them at odds with other members of the Commune, who view synthetics as mere tools.

*'''Gibsonite Ansiba''' also focus on the sciences, but without needing to commit infiltration. They spread pro-Autakh propaganda and attempt to recruit out of the underclasses of Tau Ceti, regardless of species. They are also extremely interested in positronics as allies and members of the commune and are generally ecstatic by being near so many in Tau Ceti. They remain an outlier in viewing Synthetics as being entities of pure magic (due to their fully 'augmented' nature) and try to persuade the rest of the wary commune to this idea.

When working for Nanotrasen, clan Ansiba tends to work in the '''science''' and '''service''' departments.

== Religion ==

In-depth information on the Aut'akh's spiritual beliefs can be found on the [[Unathi Religion]] page.

=== Oss and The Mesh ===

Sk'akh spoke to the first who would become Aut'akh, and led them to create Oss and the Mesh. The combined expression of all the magic of the Aut'akh is called Oss, which is an avatar of Sk'akh in cyberspace. For the non-religions, Oss is an operating system and a numbers cruncher housed within an implant in an Aut'akhs mind. This implant, called a '''Soul Anchor''' also connects an Aut'akh to the Mesh. Through its use, Aut'akh can share experiences on communal boards that are then tabulated by Oss into useful information. For example, when a commune is building a new power grid, Oss analyzes everything about the project, such as resources being used, manpower, and desired output. It then gives the communes engineers projections at every level so that the engineers can make extremely informed decisions.

Because Oss is an operating system, different communes not in close contact may over time begin to have doctrinal and policy drifts. Over more time and distance this may cause their version of Oss to become very different or even incompatible from one another. The Mesh is best described as a mental form of internet that works on any device that runs Oss.

Aut'akh priests or shamans are known as '''Paradigms''', and they are the example to which every Aut'akh strives. An Aut'akh becomes a "Paradigm" when they contribute an update to Oss that improves its operating system. Whether or not an update is considered an improvement is decided by the commune on a semi-daily basis.

=== Decrees ===

In extraordinarily rare situations, Oss will generate projects for a Commune to complete that are phrased as commands rather than analysis. These broadcasts from Oss are treated as '''Decrees''' from Sk'akh themself, speaking through Oss. Most Aut'akh act with crusader-like zeal in completing them. Other Aut'akh question whether or not these are simply glitch behaviors from the operating system, pointing to the context of the Decrees that have been implemented in the past.

There have been two Decrees in Aut'akh history; both emerged in the middle of incredible divisive debate and uncertainty within the Polar Commune. More information is in the history section.

While some Aut'akh continue to believe that the Decrees indeed come from Sk'akh, there are still divides on how to interpret them or ultimately if they are merely the product of a polarized commune.

===Oss In Daily Life===

Oss does not communicate with its followers directly outside extraordinarily rare Decrees, and debate still rages on whether it is conscious or not. Despite this assertion, many Aut'akh describe Oss the operating system as a religious conscience, acting as third feeling in oneself should their activities, thoughts, attitudes go with or against the moralities of the commune. These standards are decided by voting, and it is the Paradigms that are ultimately in charge of writing an ethical update to Oss so it can be updated with the latest version. Whether or not this is true, Aut'akh still have agency during these feelings.

===The Implements===

Like a computer, Soul Anchors can only run so many aspects of Oss at a time. Aut'akh have a set of programs called the Implements. When ran, the Aut'akh operates under the parameters of that Implement. The Soul Anchor has enough space for three Implements, but only one can safely run at a time. With a Mesh connection Aut'akh can delete an Implement from their Anchor and download a new one in the space of an hour or less.

*'''PublicSquare.OSS''' is similar to a public forum and instant messaging board. It allows Aut'akh to communicate with Aut'akh also connected to their local Mesh network. The program overlays in their vision with the help of their augmented eyes. There is also video, image, and audio sharing in public or private chats or dedicated sites on the Mesh. This program is also how Aut'akh form Consensus, using the various platforms.

*'''TacticalNetwork.OSS''' is a complex combat system designed for incredible levels of coordination and tactical prowess. Aut'akh running this Implement have access to maps, orders, and predictions on the outcome of battle, as well as the status and sensory data of their comrades.

*'''WorkSafe.OSS''' uses cybernetics to achieve its goals. This Implement is used by Aut'akh who are working in day to day tasks within the Commune. Aut'akh who take on a work assignment gain the ability to do complex tasks in unison with all other Aut'akh around them. Aut'akh in a workshop all working with the WorkSafe.OSS Implement have the same speed and methodical ability as an automated factory. It has been described as a proactive muscle memory - any number of Aut'akh can work in close proximity on the same project without anyone bumping into each other or going out of sync when utilizing the right Implement.

*'''BattleTrance.OSS''' is a controversial Implement used almost exclusively by the Optikam. Is a cut-out switch for the conscious mind. Upon activation, the user simply falls asleep standing. A modified version of the TacticalNetwork.OSS Implement then activates, putting their body directly under the control of the software, which itself is abstractly commanded by a nearby commander. This Commander remains conscious, and commands all units running the Implement. This grants the user extremely fast reaction times, and its users are known to be vicious and methodical killers on the battlefield. It is primarily used by specialized groups of Optikam infiltrators. Optikam Commanders have dark humor about the Implement, sometimes referring to the Implement as a "real time strategy game".

*'''TravelGrid.OSS''' has been described as having the same scale as a traffic-control network for a major urban city. It gives Aut'akh the ability to easily navigate even the most complex mazes within their network. Thousands of Aut'akh can move around in halls or on roads without a single hiccup in traffic. The program can also visually lay out a path before Aut'akh to get to their destination.

There are hundreds more .OSS programs that serve a lot of individual functions. They are as diverse and mundane as programs are in contemporary laptops.

=== Baffles ===
Having a spotty connection to the Mesh results in unusual scenarios known as '''Baffle Events'''. Oss is “baffled” as the mesh connection drops out abruptly and everything starts going wrong. People bump into each other, stuff falls over and breaks, then the connection comes back and it all goes smoothly again.

For Aut’akh without a reliable connection to the Mesh, such as for Aut'akh that travel outside the exile fleet to work on the Aurora or elsewhere in Tau Ceti, they don’t have this easy, instant communication with everyone around them. This loneliness can be unnerving to Aut’akh, so they are eager to talk to people; to ask them questions and learn about their experiences. Aut’akh in Tau Ceti are almost constantly trying to strike up friendly conversations with everyone around them. While they mean well, to many this can come off as unnerving.

== The Polar Bunkers ==

The Polar Bunkers are the home turf of the Aut'akh. They were originally a series of military bunkers and climate research stations which were abandoned after the nuclear exchanges and left mostly intact. The Aut'akh, at the end of their wanderings, found some of these places and converted them into a fortified but peaceful subterranean empire. Although the Aut'akh know no central authority, the Polar Bunkers are considered the heartland of the Aut'akh civilization.

The interiors of these places are maddeningly complex, intertwined warrens of tunnels and rooms dug seemingly at random and filled with thousands of Aut'akh. TravelGrid.OSS takes Aut'akh to their destinations safely, guiding each individual to their destinations while minimizing collisions.

== Consensus ==

The laws of the Aut’akh, as it can be said they have them, are called '''Consensus'''. Consensus are agreements between the majority of Aut’akh for a certain rule, guideline, or objective. When Aut’akh are connected to the Mesh they can communicate with all other Aut’akh in radio range, allowing a whole community to rapidly communicate with one another. The range of the Mesh can extend out to regions of a planet but cannot extend through interstellar distances or between planets without infrastructure.

'''Consensus is not needed for every single decision that an individual or group might make,''' but on matters that affect an entire commune. Most individuals know their job and how to do it without needing to call for an entire consensus. Mahashik will keep digging, Saramiite will keep training, and Optikam will keep patrolling. Consensus is for major projects.

In the Exile fleet, the lack of being able to easily reach a Consensus has lead to a growing rise of minor issues and a generally much slower rate at reaching consensus or being slow to respond to unwanted behavior.

== The Exile Convoy ==

After the Aut'akh emerged from their bunkers, they were met with immediate hostility from the Maraziite Order and the Hegemony. A full blockade was put in place, and the convoys that secretly shuttled supplies to and from the Polar Bunkers was left stranded in the start of 2461.
[https://forums.aurorastation.org/topic/2662-mendell-city-bugle/?do=findComment&comment=109252| In Feburary of 2461 the Exile Fleet arrived in Tau Ceti, and after negotiations with Nanotrasen and the Biesellite government they were settled on New Gibson.] The majority of their ships touched down and have been joined together in a makeshift colony as they start to dig into the crust to make their more suitable subterranean complexes.

The Exile Fleet is still unable to return to Moghes due to the ongoing blockade of the polar bunkers, and they cannot supply or resupply with their brethren. They are in effect having to restart their civilization all over again from the ground up. With only around 10,000 Aut'akh, they are finding it difficult to exist within Tau Ceti; humans continue to misunderstand or belittle the necessity of Consensus. They are also locked into work contracts with NanoTrasen to pay off the debts they owe them and the governments for the purchase of the New Gibson land. Many Aut'akh now have no control over the work they do for NanoTrasen. If they work outside New Gibson they also have a spotty or total lack of a connection to the Mesh, leading them to feel lonely and listless. They also face constant hostility and fear from other Unathi within Tau Ceti, as well as patronizing or hostile attitudes from humans and other aliens.

Regardless of how individual Aut'akh feel, there is a collective strengthening of their will as they continue on their quest to adapt and survive by any means necessary. They express their camraderei and desire for peace and understanding by referring to everyone they talk to as '''friend'''. (Hello friend, how are you doing, can you hand me that wrench friend, thank you friend, you're welcome friend).

== History ==

The Aut'akh trace their origin to a collective group of scientists, engineers, and philosophers gathering after human contact. They were trying to respond to the rise in instability and tensions across the world. The one hundred or so members of the movement traveled the many Kingdoms of Moghes and met with many Lords of the Izweski Hegemony. '''They lobbied for peace and the avoidance of war''', giving any Lords or commoners that would listen to dire warnings about the fate of the world if war were to break out.

When the '''Contact War''' started they continued their pleas but war fervor saw them repeatedly kicked out of Coalition and Izweski cities alike. They continued to campaign for an end to the war, but no one would listen.

'''When the atomic bombs were exchanged,''' the movement began to hemorrhage followers. They were scattered to the winds and many lost their lives in the resulting chaos. Only half the original followers remained, and almost all of them were maimed or wounded from the violence or bombs. They wandered the growing Wasteland trying to piece together what had happened and how to go forward. They were heavily disenfranchised and chased out of towns and cities, and many of its members abandoned the group, feeling that all their efforts had been pointless.

Eventually their number whittled down to just a dozen people remaining. One night as they slept in the ruins of a destroyed castle, the entire group allegedly '''received a divine message from Sk’akh.'''

Sk’akh told the group in their shared dream that '''Sinta’Unathi had their souls overtaken by demons,''' and that the entire species was henceforth barred from joining Her in death. All Sinta’Unathi were doomed to reincarnate for as long as they allowed the blight of demons to continue to fester within them. Sk’akh told them that they must purify their souls by creating a new vessel; the “vessel of the flesh” was no longer within Sk’akh’s vision. Finally, Sk’akh laid out for them a vision of a single Tear falling from His cheek onto Moghes that would hold the key to the salvation of their people.

The group woke up and quickly chattered in astonishment about the shared prophecy they had just received. With a religious zeal they packed up their makeshift camp and made the dangerous expedition from the Wasteland to the forests of the north.

Prior to this, during the Contact War, an Eridanian recon and research vessel had been brought down from the skies by a strong nuclear blast, sending it careening into ruined farmland. This ship was the '''Mandjet''', destined long ago to quietly observe Unathi and to entice rural villagers to board with vague promises and a contract the Unathi could not read. The Eridani’s exploitative contracts allowed them to experiment with augments on Unathi in an, ultimately wrong-headed, attempt to be the first to get their foot in the door in selling prosthetics and augments to the Hegemony. When the computer and vaults were cracked open by the proto-Aut’akh scientist and engineers and the databases and personnel files opened, they found wonders. Prosthetic spines, eyes, and blueprints for a new evolution of Sinta’Unathi - all of them with the corporate logo of the Corporate Federation.

Most importantly, a handful of mining equipment and industrial fabrication units were present, along with a primitive colony management software, still ready for setup and sale to a Unathi Lord that would never hear the sales pitch. In the early days, the group was working with rickety garbage scavenged from the Eridanian expedition and shabby replicas produced out of rusty scrap and scavenged wiring. They built the first crude bodies for themselves and called themselves Aut’akh: '''"The Automatons of Sk'akh"'''

The cult tried to spread its message in a naive optimism, but they were repeatedly and harshly rejected by any village they came across. Harassed at every turn they eventually made a final expedition to the north pole, where they began to dig into the mountains and even found abandoned research labs that once belonged to the Hegemony. '''The Commune's founding is considered to be 2450, and this is the earliest that a playable Aut'akh can join the commune.'''

The settlement of the north pole and the resources gained from mantle mining have allowed a boom in both R&D and production. This mantle mining has been achieved by a local phenomenon near the bunkers known as the Well of The Ancestors.

=== The First Decrees and the Modern Aut'akh ===

The first '''Decree''' came in 2452. The original Aut'akh had been debating for weeks on whether or not to recruit from outside the Communes or rely on growing the population internally. The Commune taxed Oss with constant, unceasing research about the issue. Finally, in December, a bulletin with no author appeared on the Mesh that said, '''PROJECT: RECRUIT FROM EXILES'''. After exhaustive efforts by Paradigms to find the source of the bulletin, they eventually found that it was posted from Oss itself. After this point on, while many questioned this emergent behavior, the opinion within the Commune shifted dramatically.

The second '''Decree''' came in April of 2461. The Polar Commune was deeply divided on whether or not it was time to reveal their existence to the Hegemony and the wider galaxy. After months of intense debate, again stressing the limits of Oss' processing power, a bulletin was again posted on the Mesh. This one simply said, '''PROJECT: REVEAL TO OUTSIDE'''. Again there was a divide between those that found this to be simply a 'glitch' in the system, while many others took it on faith. It lead directly to the Aut'akh revealing themselves to the galaxy.

In the present day, unaugmented Aut'akh followers quietly travel the Wasteland and the underbellies of cities across Moghes. They recruit from the Guwan population, refugees, or anyone that was maimed or otherwise feels unhappy within their own bodies. These recruiters are ruthlessly hunted down whenever they are found, but the cult remains a stubborn, covert presence, sending hundreds of Sinta'Unathi on a dangerous trek to the north pole with the promise of a better life. These wandering Paradigms are an open secret, and rumors of their presence can send entire towns or cities into frantic witch hunts.

== Potential Character Concepts ==

'''Characters from the Exile Fleet are likely to:'''

*Prefer to wear jumpsuits or Ouerean-style dress.
*Call everyone friend.
*Been a dispossessed, Guwan, orphan, or lost Unathi at some point in their life.
*Know their job well and eagerly work to do it.
*Be uncomfortable when alone, and extremely stressed if left alone for a length of time.
*Signed up with NanoTrasen to help the New Gibson commune.
*Quietly resolve to survive by any means necessary.

'''Here is an example character from the Exile Fleet:'''

'''Kethresh Yozi-Cri'ti''', 44, was a quartermaster in a cargo shuttle in the fleet but now works on the NSS Aurora. She is fascinated by non-Unathi and constantly tries to talk to them.

*Yozi-Cri'ti is 5'8" and has a white chassis that weighs 280 lbs. Her mechanical eyes are yellow and she has decorative blue frills.
*Before being augmented she wandered the Wasteland missing her arm and being severely scarred by burns from an atomic blast, relying on charity from town to town that evetually kicked out with other refugees.
*She lives in a small room in the New Gibson colony with spare amenities. She enjoys the simple life, but quietly enjoys her new, small radio for the Tau Ceti talk shows.
*She does not regret her choice to be augmented, but she misses the feeling of a sunny day on Moghes.
*She still struggles to understand money after years without it within the commune, and she frequently gets persuaded to buy people their meals or to loan them money, leaving her with little left.
*She mourns the fact the Hegemony reject her people and deny the blessing of Oss. She is fascinated the most by Tajara because of their own communal lifestyles.
*She has another Kethresh that she is frequently assigned with by Oss, and she recently asked him to update their relationship status to 'dating' on the Mesh. He accepted.
*She will survive by any means necessary.

'''Here is another example character from the Exile Fleet:'''

'''Saramiite Kizki''', 55, was responsible for fleet security but now works as a security cadet on the NSS Aurora, trying to become an officer. He is quiet and reserved to aliens but opens up to Unathi and especially other Aut'akh.

*Kizki is 5'9" and has a red chassis that weights 289 lbs. His mechanical eyes are blue and he has white horns.
*Before being augmented Kizki was a minor noble in a Traditionalist city besieged by the Izweski late in the war. He fled the city as its walls were breached, abandoning his post. He never forgave himself, and wandered the desert as a Guwandi before stumbling on an Aut'akh missionary hiding under heavy cloaks. Initially fearful and angry, he was eventually convinced to join their movement.
*He lives in a small room in the New Gibson colony with nothing but a bed and his e-pistol. He puts on his security-arm as soon as he returns home, and doesn't feel comfortable without it.
*He feels like being augmented was the only thing that saved his soul. He does not miss his old body; it was weak.
*He avoids frivolous spending and gives all of the money he feasibly can back to the commune to help repay NanoTrasen. He deeply resents the exploitation his fleet is facing.
*He struggles to reconcile his hatred for the Hegemony with the Aut'akh emphasis on unconditional acceptance. He tries to avoid talking to non-Unathi, believing they are ignorant for having pride in their weak, mortal bodies. He is very friendly and protective to other Aut'akh.
*He has yet to find another Aut'akh that he would want to go steady with; he is too focused on his work.
*He will survive by any means necessary.

Tajaran History

2019-11-07T18:22:17Z

Mofo1995: /* Gunpowder Age */ added an "a" article in a sentence.

{{Navbox Lore}}
{{Navbox Tajara Lore}}

= Pre-Contact History =

For as long as Tajara care to remember, Adhomai had always been under the rule of nobility. The oldest historical text that exists in Tajaran possession dates back at least three thousand years and talks about the presence of nobles. Many historians agree that the trend of blood rule is more deeply-rooted in Tajaran existence than was before considered.

The tajaran history is divided into the following periods: Pre-History, Incarnate Dominion, Migration Period, Warring Kings Era, Gunpowder Age, Steeple Peace, Galactic Age.

The traditional Adhomian calendar uses the start of the Incarnate Age, in '''1158 BCE''', as its epoch. The current year '''2461''', would be '''3619''' in the Adhomian calendar.

== Pre-History ==

The ancient past of the Tajara is poorly documented and historical texts are almost non-existent; meticulous combing and destruction of educational material by millennia of harsh rule resulted in total atrophy of most scientific arts in Tajaran society. Little is known about Tajara civilization before '''500 BID/1500 BCE'''

The south of Ras’nrr, between the Razhar and Khazan mountains, is the cradle of the tajaran civilization. The first recorded culture is known as the [[Tajaran Ethnicities#Hharar|Proto-Hharar]], they were responsible for the invention of agriculture, writing and the foundations of the religion that would develop into the [[S'rendarr and Messa|S'rand'marr Worship]] and the [[Ma'ta'ke Gods|Ma'ta'ke pantheon]]. The earliest form of government were local monarchies supported by religious authorities; the ruler and their families were considered of divine origin. Most of the settlements were similar to rural fiefs, with the population working for those dynasties in trade of their protection. Urbans centers started to appear around places of worship, with Trizar and Mezuma being the most important ones.

In '''150 BID/1308 BCE''' a nomadic horde, also known as the [[Tajaran Ethnicities#M’sai|Proto-M’sai]], migrated into the region of Southern Ras’nrr. Modern archaeological evidence indicates that they were natives from the plains close to the the Nraz’i mountains. This new tajaran people clashed with the sedentary [[Tajaran Ethnicities#Hharar|Proto-Hharar]]. Riding Zhsram into battle and using curved bows as their weapons, they were able to raid the northern territories with little resistance. This threat was only subdued in '''25 B.I./1183 BCE''' when the king of Mezuma, '''Dirrnavirr'Almalik''', defeated the nomads in battle.

Instead of expelling or exterminating the invaders, the [[Tajaran Ethnicities#M’sai|Proto-M’sai]] were assimilated into the tajaran civilization. They were employed as soldiers and enforcers by '''Dirrnavirr'Almalik''', creating the foundations of the modern [[Tajaran Ethnicities#M’sai|M’sai]] ethnicity. The nomadic leaders intermingled with the [[Tajaran Ethnicities#Hharar|Proto-Hharar]] aristocracy, giving birth to the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]]. '''Dirrnavirr'Almalik''' launched a military campaign against the remaining independent territories, subjugating the entire south of Ras’nrr in twenty-five years. At the end of his conquest Dirrnavirr proclaimed himself as a living avatar of the Sun gods, adopting the title of '''Incarnate''', inaugurating the start of the '''Incarnate Dominion'''.

== Incarnate Dominion ==

Southern Ras’nrr experienced a long period of prosperity under the rule of the Incarnate, a dynasty of kings that claimed to be the divine manifestation of the Suns themselves. Each Incarnate'would adopt the name of '''Dirrnavirr'Almalik''' when crowned, affirming to be the continuation of the previous monarch.

The fields of metallurgy, science and religion saw great advances during this age. The holy city of [[S'rendarr and Messa#Sana Sahira|Sana Sahira]] was founded in '''150 AI/1008 BCE''', serving as the seat of the main priesthood. The urban population grew exponentially, burdening the peasants with increasing demands for food and other materials. In '''180 AI./1003 BCE''' the Incarnate turned his attention to the tajaran population living at the eastern mountains of Ras’nrr, the [[Tajaran Ethnicities#Zhan-Khazan|Proto-Zhan-Khazan]]. In a military effort he subdued most of their tribes, transferring their population to the fields and mines of the dominion. Those that managed to escape the abduction adopted a nomadic lifestyle, becoming the [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]].

It was during this time that the caste system, that is still a living part of the tajaran society, was institutionalized. Each ethnicity had their place and duties enforced by law, interbreeding was punished with death or exile. This social structure would remain in place for the rest of the tajaran history, only being challenged in modern times. This era lasted until '''800 AI/383 BCE''', when harsh winters, plagues and constant revolts caused the collapse of the dominion. The Incarnate dynasty and title came to an end when the last of the divine Kings was assassinated by a group of rebellious peasants. The kingdom of Mezuma was then split into several city states and territories controlled by nobles. This disaster marked the start of the '''Migration Period'''.

== Migration Period ==

Due to the difficult conditions at Southern Ras’nrr, several nobles families accompanied by their serfs and retinues migrated to other regions of Adhomai, establishing their own kingdoms, towns and fiefs. The rest of '''Ras’nrr''' was settled by the first wave of migrant, establishment societies similar to the ones that they experienced at the south. Amohda and Das’nrra were reached using paths of ice created by the harsh winters. The first settlers of those islands organized themselves into villages based around fishing and archaic shipwrighting. The continent of Harr’masir was left uninhabited during this period, even if amohdan sailors were aware of its existence.

The lack of central leadership strengthened the priesthood, changing the religion that venerated the deceased God King into the [[S'rendarr and Messa#The Parivara|church of S'rand'marr]]. The concept of the Incarnate as the avatar of the Suns was abandoned, with Dirrnavirr'Almalik being considered only prophet or a great leader by the priests. The theology of the faith shifted to justifying the existence of the caste system, alongside with legitimizing the rule of the nobility.

The '''Migration Period''' came to an end in 1270 A.I./88 CE with the foundation of Shastar kingdom in Das’nrra. With the severe winters coming to an end, the new monarchies started to expand and compete with each other, inaugurating the '''Warring Kings Era'''.

== Warring Kings Era ==

This age was marked by the expansion and the constant warring between the monarchies established after the end of the '''Migration Period'''. Advances in farming, medicine and construction techniques allowed the population numbers to blossom once more, encouraging further territorial expansion. The countless kings started to compete with each other, subjugating all independent towns and cities found in the way. The power and importance of the nobility grew even stronger, with most of the population being forced into a state of servitude in the fields.

The system of serfdom characteristic of this age, named '''Ras’nrr Model''' by historians, would be enforced until the end of the first tajaran civil war. [[Tajaran Ethnicities#Zhan-Khasan|Zhan-Khasan]] and [[Tajaran Ethnicities#Hharar|Proto-Hharar]] peasants would work in large plantations and mines owned by the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]] nobles. Serfs had no political rights, social mobility or access to education. The [[Tajaran Ethnicities#M’sai|M’sai]] were the designated martial caste, serving as soldiers and law enforcers under the service of the nobility. The few existing cities were usually inhabited by free artisans, unlanded nobles, merchants, clergy or philosophers.

The period of wars between kingdoms lasted from '''1270 AI/88 CE''' until '''1900 AI/718 CE''', at this point most of the territories were under control of the major monarchies. A long period of relative peace followed, with trade between countries starting to flourish. [[Crevus]] in the Kingdom of Das’nrra, initially a small fishing town founded during the '''Migration Period''', was indispensable in establishing naval trade routes between Das’nrra, Ras’nrr and Amohda. The most rich nobles families in [[Crevus]] played an important role in the kingdom’s politics at the time, influencing the king into investing into ambitious expeditions to explore the seas of Adhomai.

In '''2107 A.I./925 CE''' the first colony, a settlement that would become the city of Baltor, was founded in Harr'masir as a result of an expedition financed by the Kingdom of Das’nrra. For the next few years, several other colonies were established into the continents by many of the Adhomian kingdoms. This new competition for territories sparked another period of conflicts, referred to as the '''Colonial Wars of Harr'masir''', between those states. Many peasants and nobles families were relocated to these new lands, serving as their settlers and guardians. The politics of displacement and the constant warfare created a powerful feeling of resentment in the colonists of Harr'masir.

The '''Colonial Wars of Harr'masir''' came to an abrupt end in '''2378 AI/1286 CE''', when an ambitious [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]] caravan elder started a campaign of conquest against the nations of South Ras’nrr. '''Tajrhalrr Jrruzhani''' was a famous nomad mercenary of his time, that managed to acquire a large fortune under the service of the Kingdoms of Mezuma and Nazira. Using his experience and wealth he was able to unite several nomadic caravans under his control.

'''Tajrhalrr Jrruzhani''' waged war against Mezuma and Nazira, subjugating both by making use of a mobile force of Zhan Nomads armed with bows and spears. The [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]] created the title of '''Almalik’Rhazar''', meaning “King of the Mountains”, denoting his rule over all of his people. The Nomadic domain disintegrated after the death of Tajrhalrr, divided between his sons and generals.

While the kings of Ras’nrr turned their attention to the Nomadic threat, many nobles administrating the colonies at east saw this an opportunity. The continent of Harr'masir erupted into several wars of independence. Those conflicts would last until '''2512 AI/1420 CE''', resulting in all nations, except of the Kingdom of Nal’tor, losing their territories at Harr'masir.

This later period of violence favored the development of new military technologies, among them the invention of gunpowder, rustic firearms and cannons. The first use of field guns in '''2537 AI/1445 CE''' marked the end of the '''Warring Kings Era'''. This new discovery changed the battlefields of Adhomai, inaugurating the '''Gunpowder Age'''.

== Gunpowder Age ==

The Gunpowder Age was marked by the slow replacement of traditional Adhomian battle tactics and weapons, that included melee weapons and crossbows, in favor of cannons and primitive firing lines. The Kingdoms of Amohda, Nal’tor and Das’nrra were the first countries to make use of this new technology.

During this period, many kings had the ambition of uniting their continents or regions under their rule. This aspiration gave birth to large and powerful states, with each of their rulers claiming to be the '''Kings of Kings'''. Long and destructive wars were waged with the goal of uniting those territories. The use of massive cannons barrages, early firearms and bayonets charges were a common sight in battle. [[Tajaran Minor Religions#The Suns War of Harr'masir|The Suns War of Harr'masir]] is an example of one of those early conflicts. Three mains empires emerged during this period; the Empire of Amohda, Empire of Das’nrra and Empire of Ras’nrr.

Even with technological advances, the Adhomian society was stuck with their old feudal system. The tension between nobility and peasantry increased due to new burdens brought by recent military campaigns. The first writings against the serfdom and caste systems started to appear around '''2800 A.I./1732 CE''', with those early revolutionaries being dealt with violent by M’sai enforcers. Draconian laws and sanctions were introduced against those that defied the status quo.

Relations between the ruling class and commoners were precarious, believed to have stemmed from harsh rulers and laws. Technological and cultural knowledge and breakthroughs had begun to trickle down from the noble families to the peasantry. The invention of the printing press in '''2824 A.I./1756 CE''' favored the spread of anti-monarchist pamphlets. Owning a copy of an unapproved text was a capital crime.

Despite the best efforts of the monarchies, a large underground ring of revolutionaries was formed in the Empire of Das’nrra. Philosophers, merchants, peasants and a few landless nobles were united against the old ways. This movement was lead by a tajara known as '''Purrjar Ekhranrar'''. A revolt happened in '''2945 A.I./1877 CE''', with several cities experiencing combat between imperial troops and rebels fighting against the monarchy.

The other kingdoms, fearing the victory of rebellion, sent military expeditions to help the Empire of Das’nrra. The revolution was defeated in '''2951 A.I./1883 CE''', with the revolutionaries defeated and Purrjar Ekhranrar hanged for his crimes. The regimes, now aware of more dangerous enemies than themselves, created a way to secure their rule over Adhomai. The '''Steeple''' was established in Nal’tor. An internal embassy where the countries of Adhomai would resolve their disputes through diplomacy, creating a robust intelligence system aimed at subduing any threat to the world order. This event started the '''Steeple Peace'''.

== Steeple Peace ==

The '''Steeple Peace''' is a period marked for centuries of peace between the Adhomian kingdoms, slow and controlled development of technologies and systematic repression of the population. Tension between the peasantry and nobility continued to worsen, resulting in further enactment of more harsh regulations.

Adhomai underwent a form of industrialization with the creation and proliferation of the steam engine in '''3022 A.I./1954 CE'''. This forced the peasants into harsh new laborious professions, digging in mines and working 18 hour days building rail lines for private use by the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]] nobility. Laws were soon enacted that banned any commoners from utilizing electricity or riding on trains.

Thirty years before human discovery of Adhomai, the deep-seated mistrust between peasants and nobles had reached an all time high. The Tajaran species was trapped in a technological bubble forced upon them by their nobility. At the height of their industrial revolution only a few years prior, the leadership at the time became wary of the unification of many Tajaran workers who demanded greater rights, seeing themselves in what could be accounted as another 'Renaissance' era and result in more 'enlightened' individuals straining their already crumbling control over the populace.

The realms of education, science, and luxury found themselves under severe restrictions, and your basic Tajara was forced into almost twenty hour work days with minimal time afforded for eating and sleeping on the job. Analysis of the noble houses proves that during this time in Tajaran history, the nobility had never been worth more in Sol credits than before. This is attributed to the fact that rather than modernizing Adhomai the nobility had seen fit to confiscate and use these fruits of scientific thinking for themselves.

Automobiles are considered one of the best examples of this. The first automobile is recorded to have been created in '''3360 A.I./2292 CE'''. Using a combustion engine much like primitive human vehicles, with extra anti-freezing measures and thick treads, one of the first functional automated cars had been produced by a collection of Tajaran engineers and scientists, at the behest of the nobility. These large creations were considered by many older Tajara to be a symbol of negligence and gluttony by their leaders. Workers were never provided with such things; they were forced to transport themselves through Adhomai's harsh winter conditions on foot or by using designed 'snow bicycles', regardless of how far they were from their place of work.

Further restrictions of the rights of the individual Tajara were enacted by a furious nobility after several instances of violence against [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]], but specific information on these incidents has been lost. Legislation was introduced against 'workers unions' as well as any sort of illicit groups; a permit was required to form anything from hunting parties to agencies. In this whirlwind of political turmoil, a fresh generation of Tajara were growing up, deprived of what most humans consider to be 'basic rights'. As they grew older and angrier, the nobility saw fit to continue tightening their control over their subjects until a civil war was almost inevitable. Like a powder keg ready to blow, only a single spark was needed to light the flame.

This came in the form of human discovery in '''3576 A.I./2418 CE'''. A [[Sol Alliance]] funded expedition into the Tajaran home system discovered the pre-space age species and their homeworld of Adhomai. The first contact with these aliens started the '''Galactic Age'''.

= Modern History =

== First Contact ==

[[File:AdhomaiAncientRegimesNames.png|300px|thumb|A map of Adhomai before the first contact]]

Lush with untapped resources and potential workers, Adhomai was an attractive prospect for many human super corporations, especially NanoTrasen. Because of their slow technological progress, most of Adhomai's valuable minerals remained untapped by mining or drilling. It was due to this that several corporations attempted to insert themselves into the dealings of Adhomai.

However, the nobility felt incredibly threatened by what they considered 'intrusions' by humanity and completely refused them diplomatic access to their planet. The Alliance stepped in, initially unwilling to interfere in a pre-space age society and, reluctantly, the super corporations were forced to abandon their wishes to stake claims on Adhomai's resources - at least in the open. In the year '''3578 AI/2420 CE''', a group of Tajaran intellectuals - considered rebels by the state - were shuttled off-world by a still unknown entity. Given asylum in the [[Sol Alliance]], they met and discussed much with human scientists and officials. Tensions between the Alliance and Tajaran nobility rose after such an event and they accused the humans of harboring terrorists.

Eventually, these rebels were returned to Adhomai with supplies and weapons. Fed with new ideals of personal freedom and 'rights afforded to all' by their influential human friends, the seeds of revolution were sowed among the Tajaran populace, spread by word of mouth. Workers, doctors, teachers, even soldiers that were questionably loyal to the nobility were swayed by these promises of freedom and equality. Meetings in the basements of dark taverns or barns were common, and relations between the nobility and their peasants were at the lowest ever recorded in Tajaran history.

==The Uprisings==

It took little more than a year for a formal uprising to be staged. On '''3579 AI/2421 CE''', after the nobility had captured one of the original Tajara that had been shuttled off world, he was sentenced to be publicly hanged by the neck in front of their peasants to show just how serious they were about keeping control. Ultimately, many historians believe this to be a highly egregious mistake. Rebels in the audience, armed with advanced off-world weapons, proceeded to open fire on loyalist forces and kill a nobleman in the process. This event, called the '''D'as'ral Massacre''' (so named for the city it took place in) by the nobility was all the excuse they needed to enact martial law.

However, they found themselves in a cornered position. Weapons and supplies were being shipped in off-world by mysterious benefactors, and their collections of scientists and engineers had either fled to safety being noblemen themselves, or took up arms and joined the revolution. Without significant scientific presence to deconstruct or understand these new human weapons or support the war effort, the conflict resulted in a string of rebel victories that drew closer and closer to the capital cities of each providence. Fighting was extremely fierce and atrocities were recorded by both sides.

Among the noble families, the largest and nearly the most powerful was a dynasty called the '''Hadii'''. Their castle was amongst the best defended in the region and the battle to take it was waged for six months of non-stop fighting. As it became increasingly clear to them that they were eventually going to be overrun, the Hadii struck a deal with the rebel leader; in return for complete immunity from the war, as well as persecution, they afforded the revolutionaries with unique tools and even blueprints of other families' castles, pointing out weak points and infiltration spots.

It was this turn coating that tipped the revolution in favor of the peasantry. Armed with this new information, they made use of radio systems previously restricted for nobility to methodically and ruthlessly end their uprising by murdering most of the noble families and whatever soldiers and civilians remained loyal to them. By '''3588 AI/2431 CE''' the revolution had finally come to an end with a total of more than '''92 million casualties''' with more than half of that being loyalist forces, and '''40 million civilian deaths'''. Many Tajaran cities and villages were utterly destroyed by vicious fighting as well as bombardment by uncaring nobles. A informal ceasefire was declared between the factions, though skirmishes were still common.

==Outcome of the Revolution==

Following this total upheaval of Tajaran society, rebel leaders met with Hadii noblemen and discussed how to form a government, given that only the Hadii were experienced with ruling. Human corporations took express interest in this; the Hadii were one of the few noble families that saw profit in human stakes on Adhomai, and many back-room deals were made until ultimately the Hadii were placed at the head of Tajaran government in '''3589 AI/2432 CE''', and ushered in a new federal republic: The People's [[Republic of Adhomai]]. The Tajaran public was markedly distressed by this turn of the events, and fearing another uprising, human intervention again helped defuse the situation. The Hadii promised that it would not be like it was before.

NanoTrasen, suspected by many conspiracy theorists to be behind the funding and supplying of Tajara during the war, holds claim to most of Adhomai and has a monopoly over most of the planet's valuables. Collaboration between them, the [[Sol Alliance]] and the Jargon Federation has resulted in more technological advances in Tajaran society recently than ever before in their recorded history. Approval ratings for the current leadership rose in response.

However, serious problems remained. '''Rhagrrhuzau Hadii''' suddenly began to back out of the People's Republic's agreed upon business deals with NanoTrasen, all of which saw a massive amount of Tajaran natural resources exported. Citing humanity as greedy and destructive, '''Rhagrrhuzau''' made clear his intentions to make Adhomai independent until it was ready to take on the burden of interstellar politics.

==The Second Revolution==

The disagreements and hatred of the Hadii republican government had led to insurrection and treachery between Adhomai's major power figures since '''Rhagrrhuzau Hadii''''s new economic policies were revealed. Many Tajaran business contractors - just recently denied their ability to sell ludicrous amounts of natural resources and workers to the massive human megacorporation, NanoTrasen - felt threatened by the reforms of the Hadii government and its first President, '''Rhagrrhuzau Hadii'''. On '''3608 AI/2451 CE''', during a military parade, President Rhagrrhuzau was assassinated by a young Zhan-Khazan radical. A known secret service agent of the People's Republic, the radical was sentenced to death for his treachery, brought on by the violent tendencies of his Zhan-Khazan genetics. His brother and vice-president [[Notable Tajara#President Njadrasanukii Hadii|Njadrasanukii Hadii]] quickly assumed the office of the presidency and immediately passed brutal laws that punished Zhan-Khazans and 'subversive elements'. NanoTrasen was invited back to Adhomai and menial workers were sold en masse to NanoTrasen workplaces while the rights to the bountiful natural resources of Adhomai were sold off to NanoTrasen. Public hangings and firing squads became the norm once again.
[[File:Godblessalmarihadii.png|thumb|400px|left|Picture taken by the Adhomai Chronicle moments before the Assassination of Rhagrrhuzau Al'Mari Hadii. The single most defining moment of this generation of Tajara.]]

Many military generals that had fought for the Republic soon defected under the banner of the Adhomai Liberation Army, the leader of which being '''Rhagrrhuzau Hadii''''s old friend and ally, [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]], and Adhomai found itself embroiled in yet another global conflict that continues to this day. "His gun was on stun" became the rallying cry of Rhagrrhuzau's fiercest supporters, "Hadiists," as they alluded to how he not only left himself greatly vulnerable during the parade, but had even left his energy pistol on stun while he was assassinated.

===Adhomai Today===

The Tajaran home world has suffered plenty in the three decades since the end of the First Revolution. With the sudden injection of advanced technology into their relatively simple life, the discrepancy between modernized cities and outlying areas could not be more obvious. While the Tajaran capital boasts the most modern developments with sleek skyscrapers, advanced connections and phone lines, as well as hospitals and schools, the further you get from the larger cities, the more apparent it is that things are not quite so flashy. Expanding infrastructure remains difficult, as most public funds are seized for use by the military or used to repair infrastructure damaged by shelling or bombings.

There is a steady stream of money being fed into the People's Republic of Adhomai. NanoTrasen, as per it's agreement with the president, have set up mining and logging operations on Adhomai using the local work force for the most menial of tasks. In return, company funded clinics and schools are slowly being spread out and build in the needy areas. Tajaran resource operations are now all but nonexistent; the buildings that were once part of the nobility's small gathering efforts have now been refurbished and are being used by NanoTrasen.

Literacy has risen to its all time high on Adhomai, and with the assistance of the Alliance, teachers have been brought in from off world to educate the younger generation of Tajara. However, this number has begun to decline as the dangers of working on Adhomai are beginning to become common knowledge. Special establishments for older students have also been constructed to assist the elder generation in being brought to the same level of education, but NanoTrasen has not expressed significant interest in this; these people make up the brunt of their low-paid workforce and they want to ensure that they are kept that way.

There are still several proponents of revolution that oppose the current government, which has plunged the planet into another all-encompassing civil war that remains at a standstill today.

= Timeline of the Modern History =

At the dawn of the new century, the Tajaran people were at peace. For centuries the old monarchies of Adhomai maintained a balance of power, carefully averting anything greater than small scale conflicts through cooperation and manipulation. In time, this intricate system of international politics centralized into one building within the city of Nal'Tor, the Steeple. This building which started as an international embassy to coordinate diplomacy and maintain the balance of power gradually became the seat of power for a new world order. By the 25th century, all of the world's monarchies existed under an informal international confederation which acted with collective security to end rebellions, police hot zones across Adhomai, and curtail the distribution of newer technologies to the masses. A repressive culture of anti-intellectualism and adherence to tradition kept the lower classes from organizing or attempting any large scale rebellions. The literacy rate across the species was less than 20% and literature is still frowned upon by most of society to this day. Most history and stories were told orally by Kraszarrumalkarii, named after a Ma'ta'ke god of storytelling. The high end of technology was on par with early 20th century Earth, however industrialization was still dawning and only catered to the rich. Majority of the planet remained agricultural workers with most goods crafted by skilled artisans rather than factories. On the underbelly of society, small numbers of disenfranchised nobles privately sought to change the status quo- some with a bleeding heart and others with personal gain in mind.

===Pre-War Era===

'''2418: '''A [[Sol Alliance]] funded expedition arrived in the S'rand'marr system and made first contact with the Tajara. The first landing was made in [[Crevus]] and local nobles entertained the alien visitors. The meeting was kept a secret but rumors spread on the Das'nrra continent. A few weeks later, diplomats from the [[Sol Alliance]] and the Nralakk Federation met with with Adhomai's global community in Nal'Tor to establish diplomatic ties. Each were given apartments in the '''Steeple''' to serve as a working embassy. The international nobility continued to keep the meetings with aliens a secret, but someone leaked the information to the outside world and rumors swept the cities. The governments finally decided to make formal announcements about the discovery of aliens, sending shock waves through urban centers across Adhomai. Rural peasantry remained apathetic, but across the first week, six thousand Tajara killed themselves from the shock of the event. Nobility actively inhibited the proliferation of alien media to the masses, but were quick to negotiate trade deals for high technology oddities. After several mega-corporations, especially NanoTrasen, attempted to lure several states into imperial ambitions the '''Steeple''' successfully petitioned the [[Sol Alliance]] to prevent open interference with the governments of Adhomai.

'''2420:''' Groups of Tajaran intellectuals, primarily young nobility and high-standing Hharar, conspired for liberalized governments. Many took refuge off planet where they learned of human ideals, and returned to Adhomai to spread them. Small scale insurgencies broke out across the planet as the stability of the old order began to show cracks. The language of Siik'tajr was born as a means of covert communication between dissidents.

===The First Revolution===
'''2421:''' The Great Revolution erupted following the '''D'as'ral Massacre'''. Nobles across the planet declared martial law in retaliation and mobilized their armies.

In southern Rasn'rr', disgruntled and oppressed Zhan-Khazan populations along the Zhan mountains joined forces with impoverished dilettante Njarir-Ahkran seeking to restore former glory. The ancient city of Mezuma became the birthplace of the "People's Emancipation Movement." Weeks later, the city of Trizar joined the movement after a coup d'etat. After hasty organization, the rebel army moved north and besieged Nazira.

In the city of Orul, factories were closed by the military for their role as meeting places for dissidents to meet and organize. The workers were all sent home without pay. An event known as the "Poorhouse Riots" occured as the starving and impoverished took to the streets. After three days of violence, the city was conquered by its rebellious poor which formed the "Republic of Free Tajara." All Njarir-Ahkran who failed to evacuate were executed.

'''2422:''' The city of Nazira was taken by the People's Emancipation Movement. Rebel units continued to enforce martial law and rationed food. Soup kitchens and bread lines became hotbeds for riots, many ending in massacres by the rebel military. Recruitment into the rebel military surged following the introduction of incentives which offered better food rations for soldiers and their families. Noble forces made several offensives over the next two years from Mal'jor military base, in order to retake the city. None succeeded in reaching the city outskirts, despite large casualties on both sides.

The city of Orul was reconquered and occupied by loyalist forces based out of Zatushka. The Republic of Free Tajara carried out a series of insurgent activities ranging from sniper attacks of officers to using improvised explosive devices on the streets. Unable to bear the burden of witnessing the crimes against Tajara and citing "unprecedented barbarity," the noble in charge of the occupying forces withdrew from the city. His name was '''Tajrhalrr Hadii'''. The Republic of Free Tajara propagandized the event as having repulsed monarchist invaders, and began rapidly reconstructing their war potential.

'''2424:''' The Republic of Free Tajara and the People's Emancipation Movement formed a unified "Rasn'rr Confederacy of Free Republics." The new confederacy launched a coordinated offensive to conquer the equatorial region of the Rasn'rr continent.

The Das'nrra continent balkanized as various regional nobles attempted to secure the throne for themselves. The Empire was weakened from providing large amounts of financial support to monarchist forces on '''Rasn'rr''', and the Imperial Military had to be recalled from B'urr where it had been preparing the defense of the city. The Emperor himself disappeared during the fighting and was never seen again. An international coalition of monarchist forces formed and attempted to restore order on the continent.

The military base at Baltor severed ties with its government across the ocean at Nal'Tor. The base became the home of a military dictatorship under its M'sai general. The rogue general marched on the Kingdom of Kaltir, seeking to rapidly expand his holdings. The city of Olska was taken by surprise and brutally subjugated. The Kaltir Expeditionary Force, which has been deployed to Das'nrra to suppress noble revolts, was recalled to the Harr'masir continent.

'''2425:''' Loyalist forces left B'urr to oncoming rebels without a fight. The city of Tampiska as well as vital roads to Nal'Tor were heavily reinforced by these units, and the navy stationed at B'urr were deployed to aid loyalist forces for the Das'nrra Empire.

Rebels based out of Orul overran Mal'Jor military base. The loyalists retreated to Tampiska, further enhancing its fortifications. Rather than pursuing, the Orul Rebels changed their focus northward and besieged Zatushka. This siege would later be discovered to be a feint for a different offensive.

The Kaltir Expeditionary force seized Baltor through the first major amphibious assault in Tajaran history. The city of Olska was liberated by the end of the year, with cheering citizens praising the King and celebrations filling the streets.

A peasant revolt from the rural areas around Dolor seized the city, naming themselves the "Liberated People's of Harr'masir." Their coastal area to the west was quickly assaulted by the Kingdom of Amodha, which sought to reconquer their ancestral lands.

'''2426:''' The surviving monarchies adopted the Sol Alliance Credit as their official currency in an attempt to curry favor for international support. The move failed to gather public support as many Tajara did not have enough wealth to afford the currency trade-ins.

The Siege of Tampiska began after months of artillery battles. Hordes of rebels attacked the city in waves as building to building combat lead to the bloodiest urban conflict of the war.

Citadel Hadii, the stronghold of the Hadii Family, came under siege in a surprise attack following an arduous rebel march through the Nraz'i mountains. The small garrison of the immense citadel held strong until forces recalled from the abandoned Zatushka base broke the rebel siege. '''Tajrhalrr Hadii''' died in the fighting, leaving his eldest son, '''Rhagrrhuzau Hadii''', at the head of the Hadii dynasty. Rebel forces which had taken Zatushka followed the recalled army and renewed the siege shortly after the last was broken. The siege only ended when the young Rhagrrhuzau Hadii struck a deal with the rebels, giving blueprints to other noble fortresses, information about other armies, and loyalty in exchange for immunity and protection. Forces of the Hadii family withdrew from Das'nrra and began subjugating monarchist forces north of Hadii lands.

Fighting on Das'nrraled to the collapse of most noble families involved in the fighting. The coalition of noble forces from across Adhomai which sought to restore order was forced to disband as rebels on various homefronts forced the withdrawal of each army. Based out of the capital of Shastar City, anti-monarchist rebels calling themselves the Das'nrra Resistance Movement formed and gained momentum against the tired noble armies.

The Liberated People's of Harr'masir surrounded and destroyed the invading army of the Kingdom of Amohda, before moving northwards to defend against an offensive by the Kingdom of Kaltir.

'''2427:''' The Das'nrra Resistance Movement rapidly absorbed much of the continent, marketing themselves as a beacon of stability and sanity among the autocratic madness. By employing principles of Tajarism and providing humane treatment of occupied populations, the movement became popular among the masses who had suffered through the atrocities of the noble infighting. Any noble families who did not surrender were executed, while their subjects were treated with kindness as liberated Tajara.

The Kingdom of Amodha began a second invasion of the western coast of Harr'masir, seeking to put the pressure on the rebels to aid the Kingdom of Kaltir. The armies of Kaltir defeated the Liberated Peoples of Harr'masir, besieging the retreated army at Dolor.

The Hadii Faction subjugated the northern areas of Rasn'rr' before stationing their soldiers at various fortresses and beginning large scale mobilization of populations under the control. The Faction lobbied successfully under Confederate Command to place the Republic of Free Tajara and all of its holdings under the Hadii's jurisdiction.

'''2428:''' The Das'nrra Resistance Movement and the Rasn'rr Confederacy formed an alliance and became the Western Coalition of Free Adhomai. The resistance movement finalized its conquest of the Das'nrra continent and began naval bombardment of Nal'Tor. Near the end of the year, of Siege of Tampiska drew to a close. The Siege of Nal'Tor began after the last remaining western monarchists retreated to the city.

The armies of the Kingdoms of Amodha and Kaltir joined together for the Siege of Dolor, but the rebels manage to maintain their defense.

'''2429:''' The Western Coalition of Free Adhomai and the Liberated People's of Harr'masir formed an alliance, changing their name tentatively to the Coalition of Free Adhomai. Navies of the Western Coalition sailed west across the Nas'kin Ocean to invade Kaltir. The force was intercepted by the navies of the Kingdom of Kaltir supplemented by the Kingdom of Ahmoda, which had crossed the Ras'val canal. Monarchist navies were triumphant, sinking most of the rebel fleet. A second rebel fleet sailed east across the Sum'add Ocean and blockaded Amodhan ports.

The city of Dolor was retaken by nobility forces. All rebels and their sympathizers were offered amnesty. Although many accepted, some refused on ideological grounds and were imprisoned for treason.

'''2430:''' The city of Nal'Tor was taken by rebel forces after the surrender of its defenders. The rebel fleet prepared for a large scale amphibious invasion of Harr'masir. Weakened by a year of starvation from the blockade of its ports and the destruction of the fishing operations, the Kingdom of Amodha defeated by a combination of peasant revolts and invading rebels. The island became the staging point for a planned invasion of Harr'masir as rebel forces gathered.

The fleet of the Kingdom of Kaltir engaged rebel naval forces on the western coast of Harr'masir south of Baltor. After a the battle lasted over 72 hours, the Kingdom's navy was finally sunk.

'''2431:''' All Adhomian monarchies except the Kingdom of Kaltir were overthrown by rebels. Following what is considered the end of the "Great Revolution," most of the rebel groups joined under '''Rhagrrhuzau Hadii's''' faction to form the [[People's Republic of Adhomai]].

The city of Orul, the People's Emancipation Movement, and other proponents of confederacy rose in rebellion to the federalization of the Coalition of Free Adhomai. The city of Orul was quickly and brutally occupied by the armies of the Hadii Faction which had remained home as the defensive force for the Rasn'rr Continent. Soldiers of the Dasn'rra Resistance Movement, which had joined under the Hadii's rule, suppressed units of other forces where they had all gathered on Amodha. The newly formed Republican Army under Hadii's command marched south to suppress the undefended cities of the People's Emancipation Movement and cement the rule of the People's Republic.

'''2432:''' The Hadii Faction was able to finalize the suppression and subjugation of all other rebel groups and began preparing to resume the amphibious invasion of Harr'masir.

The Kingdom of Kaltir capitulated to People's Republic rule before an invasion could be performed. Despite popular requests for amnesty and peace from the Kingdom, many of the nobility were executed. '''Farkhanzirhal Azunja''' imprisoned his 32 year old son, [[Notable Tajara#King Vahzirthaamro Azunja|Vahzirthaamro Azunja]], in order to hide him during the executions. The People's Republic of Adhomai became the lone global government of Adhomai.

===Interwar Period===
'''2433:''' The recently formed [[People's Republic of Adhomai]] obtained a charter from the Central Bank of the [[Sol Alliance]]. This charter allowed them to retool the Nal'Tor mint for printing Sol Alliance Credits.

===The Second Revolution===
'''2449:''' [[Notable Tajara#King Vahzirthaamro Azunja|Vahzirthaamro Azunja]] and his retinue of intellectuals were released from prison in secret in the middle of the night. They traveled the Kaltir region, gathering support for an independence movement. Copies of a constitution with the title "The New Kingdom" circulated by underground printing presses, and were praised by many locals for its generous civil liberties. Rumors spread of a [[New Kingdom of Adhomai]]. People's Strategic Intelligence Service Agents were unable to locate and take Azunja into custody.

Citing humanity as destructive and greedy, President '''Rhagrrhuzau Hadii''' announced a series of new economic policies which eliminated many deals favorable to NanoTrasen. He openly denounced human imperialism and proclaimed that Adhomai must be independent.

'''2450:''' Having gathered widespread support across Harr'masir, Azunja and his loyalists began an open rebellion against the People's Republic, calling themselves the "[[New Kingdom of Adhomai]]". Many supporting Njarir-Ahkran were given nobility and assigned land to govern based on their prior involvement in the movement and their friendships with King Azunja. The Dymtris Line was hastily constructed to block the isthmus leading into the Kal'tir region. The New Kingdom lost majority of its territory in the first year and millions fled northward as refugees to avoid brutal reprisals.

'''2451:''' President '''Rhagrrhuzau Hadii''' was assassinated during a military parade in Nal'Tor by a Zhan-Khazan secret service agent. His brother and vice president, [[Notable Tajara#President Njadrasanukii Hadii|Njadrasanukii Hadii]], assumed office. The 2449 economic reforms of '''Rhagrrhuzau Hadii''' were rolled back by Njadrasanukii.

Former head of the armed forces, [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]], attempted a coup with many other generals but failed. The Adhomai Liberation Army was formed by these rebels.

'''2457:''' Starlet '''Yasmin Piaf''' performed the "Heavensward" Tour. Anti-ALA sentiments are infused into the highest grossing musical tour in Tajaran history.

'''2458:''' The [[PRA Orbital Fleet Structure|Adhomai Orbital Defense Navy]] (AODN) ended its last lease for old NanoTrasen ships following the launch of the PRS Njarir and PRS Vostak. Anti-Piracy operations in the space around Adhomai were conducted solely by the AODN without foreign aid.

The People's Republic of Adhomai introduced conscription following the loss of Tampiska to Liberation Army forces. The surge in military manpower resulted in the retaking of Pur'r by the Republican Army. The city of P'urr was renamed to its prewar name, "B'urr".

A four Mt nuclear weapon was deployed against the headquarters of Liberation Army forces in the Quizosa military base, north of Ron'Tul in the Rhazkjara mountains. The nuclear attack caused international outrage and lead to diminished foreign support for the People's Republic. Ron'Tul was firebombed by the People's Republic of Adhomai, and much of the city was destroyed. Liberation Army forces withdrew and the city was occupied by the Republican Army.

Rehabilitation programs are established by the People's Republic of Adhomai, seeking to purge subverside and humanized elements among its population. Several labor camps are created in the republican territory. Homosexuals, dissidents and political enemies are arrested and interned in those installations in the following months.

On the Harr'masir continent, The Dymtris Line was overrun by a Republican Offensive. The Republican Army was repulsed by the Imperial Army when it was forced to retreat to deal with insurrections by rebel forces. Highly coordinated mass guerrilla attacks orchestrated by the ALA swept the People's Republic, creating a week of chaos and bloodshed. Lines of communication and infrastructure were crippled long enough for the Liberation Army to make considerable gains.

'''2459:'''
The People's Republic's colony of Hro'zamal is founded in the Nrrahrahul system.

Tajara Rights Act of 2459 is passed by the People's Republic Congress, improving working conditions on labor camps, providing better medical relief efforts for refugees from areas of conflict, and a reducing homosexuality to a misdemeanor.

'''2459:''' Imperial Parliament of the [[New Kingdom of Adhomai]] was bombed by a suspected ALA radical. [[Notable Tajara#King Vahzirthaamro Azunja|King Vahzirthaamro Azunja]] was hospitalized for a month, and [[Notable Tajara#Field-Marshal Rrhazhal Zarkradar'Akhan | Field-Marshal Rrhazhal Zarkradar'Akhan]] remained in the hospital for a year. Enough members of parliament were killed to default the Kingdom to temporary absolute monarchy. After completing offensive operations, the New Kingdom of Adhomai began construction of the Vlrralkhzazhul Line to consolidate their gains.

The various civilian governments under Adhomai Liberation Army rule were brought together under the [[Democratic People's Republic of Adhomai]]. Within months of its creation, the DPRA effected large-scale repairs and improvements to electrical infrastructure.

'''2460:''' The Republican Army is expelled from Das'nrra by a rebel offensive. Republican forces manage to evacuate by sacrificing the [[Tajaran Military Structures#The Republican Guard|the Republican Guard.]]

The New Kingdom announces the New Crown heir; [[Notable Tajara#Crown Heir Shumaila Azunja|Shumaila Azunja]].

The Democratic People's Republic of Adhomai and the New Kingdom sign a ceasefire. Royalists forces evacuate Amohda, allowing the Adhomai Liberation Army to control it as part of their agreement.

The campaign for DPRA president begins, with a dispute between National Adhomai Worker’s Party and Free Tajaran People’s Party..

'''2461:''' Almrah Harrlala, the leader of the National Adhomai Worker’s Party, wins the DPRA elections. A coup attempt against her government by the military is thwarted with the help of [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]].

Zhan nomads forces of Harr'masir are united by [[Notable Tajara#King of the Mountains Rustam Harmaliik | Rustam Harmaliik]], claiming the title of '''Almalik’Rhazar'''. Rustam and his people join the New Kingdom of Adhomai's war effort after losing support from their ALA allies.

A successful offensive is launched by the New Kingdom of Adhomai against the People's Republic at Harr'masir. Republican forces are expelled from the continent after the siege of Olska.

Sol Alliance forces and [[PRA Orbital Fleet Structure|Orbital Defense Navy]] engage each other in a short space skirmish, caused by the dispute on the lease rights of a space port. Sol Alliance imposes an embargo against the People's Republic, cutting all military aid and weakening their economy.

The city of Dolor is liberated by the forces of the Adhomai Liberation Army.

The People's Republic of Adhomai is attacked by the Adhomai Liberation Army and the Royal Navy, triggering the creation of a coalition. Allied states, NanoTrasen, mercenaries and volunteers join the PRA in their defense against the rebels.

{{Navbox Tajara Lore}}
{{Navbox Lore}}
[[Category:Pages]]
[[Category:Tajara]]

Tajaran History

2019-11-07T18:20:55Z

Mofo1995: /* Gunpowder Age */ Added a space

{{Navbox Lore}}
{{Navbox Tajara Lore}}

= Pre-Contact History =

For as long as Tajara care to remember, Adhomai had always been under the rule of nobility. The oldest historical text that exists in Tajaran possession dates back at least three thousand years and talks about the presence of nobles. Many historians agree that the trend of blood rule is more deeply-rooted in Tajaran existence than was before considered.

The tajaran history is divided into the following periods: Pre-History, Incarnate Dominion, Migration Period, Warring Kings Era, Gunpowder Age, Steeple Peace, Galactic Age.

The traditional Adhomian calendar uses the start of the Incarnate Age, in '''1158 BCE''', as its epoch. The current year '''2461''', would be '''3619''' in the Adhomian calendar.

== Pre-History ==

The ancient past of the Tajara is poorly documented and historical texts are almost non-existent; meticulous combing and destruction of educational material by millennia of harsh rule resulted in total atrophy of most scientific arts in Tajaran society. Little is known about Tajara civilization before '''500 BID/1500 BCE'''

The south of Ras’nrr, between the Razhar and Khazan mountains, is the cradle of the tajaran civilization. The first recorded culture is known as the [[Tajaran Ethnicities#Hharar|Proto-Hharar]], they were responsible for the invention of agriculture, writing and the foundations of the religion that would develop into the [[S'rendarr and Messa|S'rand'marr Worship]] and the [[Ma'ta'ke Gods|Ma'ta'ke pantheon]]. The earliest form of government were local monarchies supported by religious authorities; the ruler and their families were considered of divine origin. Most of the settlements were similar to rural fiefs, with the population working for those dynasties in trade of their protection. Urbans centers started to appear around places of worship, with Trizar and Mezuma being the most important ones.

In '''150 BID/1308 BCE''' a nomadic horde, also known as the [[Tajaran Ethnicities#M’sai|Proto-M’sai]], migrated into the region of Southern Ras’nrr. Modern archaeological evidence indicates that they were natives from the plains close to the the Nraz’i mountains. This new tajaran people clashed with the sedentary [[Tajaran Ethnicities#Hharar|Proto-Hharar]]. Riding Zhsram into battle and using curved bows as their weapons, they were able to raid the northern territories with little resistance. This threat was only subdued in '''25 B.I./1183 BCE''' when the king of Mezuma, '''Dirrnavirr'Almalik''', defeated the nomads in battle.

Instead of expelling or exterminating the invaders, the [[Tajaran Ethnicities#M’sai|Proto-M’sai]] were assimilated into the tajaran civilization. They were employed as soldiers and enforcers by '''Dirrnavirr'Almalik''', creating the foundations of the modern [[Tajaran Ethnicities#M’sai|M’sai]] ethnicity. The nomadic leaders intermingled with the [[Tajaran Ethnicities#Hharar|Proto-Hharar]] aristocracy, giving birth to the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]]. '''Dirrnavirr'Almalik''' launched a military campaign against the remaining independent territories, subjugating the entire south of Ras’nrr in twenty-five years. At the end of his conquest Dirrnavirr proclaimed himself as a living avatar of the Sun gods, adopting the title of '''Incarnate''', inaugurating the start of the '''Incarnate Dominion'''.

== Incarnate Dominion ==

Southern Ras’nrr experienced a long period of prosperity under the rule of the Incarnate, a dynasty of kings that claimed to be the divine manifestation of the Suns themselves. Each Incarnate'would adopt the name of '''Dirrnavirr'Almalik''' when crowned, affirming to be the continuation of the previous monarch.

The fields of metallurgy, science and religion saw great advances during this age. The holy city of [[S'rendarr and Messa#Sana Sahira|Sana Sahira]] was founded in '''150 AI/1008 BCE''', serving as the seat of the main priesthood. The urban population grew exponentially, burdening the peasants with increasing demands for food and other materials. In '''180 AI./1003 BCE''' the Incarnate turned his attention to the tajaran population living at the eastern mountains of Ras’nrr, the [[Tajaran Ethnicities#Zhan-Khazan|Proto-Zhan-Khazan]]. In a military effort he subdued most of their tribes, transferring their population to the fields and mines of the dominion. Those that managed to escape the abduction adopted a nomadic lifestyle, becoming the [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]].

It was during this time that the caste system, that is still a living part of the tajaran society, was institutionalized. Each ethnicity had their place and duties enforced by law, interbreeding was punished with death or exile. This social structure would remain in place for the rest of the tajaran history, only being challenged in modern times. This era lasted until '''800 AI/383 BCE''', when harsh winters, plagues and constant revolts caused the collapse of the dominion. The Incarnate dynasty and title came to an end when the last of the divine Kings was assassinated by a group of rebellious peasants. The kingdom of Mezuma was then split into several city states and territories controlled by nobles. This disaster marked the start of the '''Migration Period'''.

== Migration Period ==

Due to the difficult conditions at Southern Ras’nrr, several nobles families accompanied by their serfs and retinues migrated to other regions of Adhomai, establishing their own kingdoms, towns and fiefs. The rest of '''Ras’nrr''' was settled by the first wave of migrant, establishment societies similar to the ones that they experienced at the south. Amohda and Das’nrra were reached using paths of ice created by the harsh winters. The first settlers of those islands organized themselves into villages based around fishing and archaic shipwrighting. The continent of Harr’masir was left uninhabited during this period, even if amohdan sailors were aware of its existence.

The lack of central leadership strengthened the priesthood, changing the religion that venerated the deceased God King into the [[S'rendarr and Messa#The Parivara|church of S'rand'marr]]. The concept of the Incarnate as the avatar of the Suns was abandoned, with Dirrnavirr'Almalik being considered only prophet or a great leader by the priests. The theology of the faith shifted to justifying the existence of the caste system, alongside with legitimizing the rule of the nobility.

The '''Migration Period''' came to an end in 1270 A.I./88 CE with the foundation of Shastar kingdom in Das’nrra. With the severe winters coming to an end, the new monarchies started to expand and compete with each other, inaugurating the '''Warring Kings Era'''.

== Warring Kings Era ==

This age was marked by the expansion and the constant warring between the monarchies established after the end of the '''Migration Period'''. Advances in farming, medicine and construction techniques allowed the population numbers to blossom once more, encouraging further territorial expansion. The countless kings started to compete with each other, subjugating all independent towns and cities found in the way. The power and importance of the nobility grew even stronger, with most of the population being forced into a state of servitude in the fields.

The system of serfdom characteristic of this age, named '''Ras’nrr Model''' by historians, would be enforced until the end of the first tajaran civil war. [[Tajaran Ethnicities#Zhan-Khasan|Zhan-Khasan]] and [[Tajaran Ethnicities#Hharar|Proto-Hharar]] peasants would work in large plantations and mines owned by the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]] nobles. Serfs had no political rights, social mobility or access to education. The [[Tajaran Ethnicities#M’sai|M’sai]] were the designated martial caste, serving as soldiers and law enforcers under the service of the nobility. The few existing cities were usually inhabited by free artisans, unlanded nobles, merchants, clergy or philosophers.

The period of wars between kingdoms lasted from '''1270 AI/88 CE''' until '''1900 AI/718 CE''', at this point most of the territories were under control of the major monarchies. A long period of relative peace followed, with trade between countries starting to flourish. [[Crevus]] in the Kingdom of Das’nrra, initially a small fishing town founded during the '''Migration Period''', was indispensable in establishing naval trade routes between Das’nrra, Ras’nrr and Amohda. The most rich nobles families in [[Crevus]] played an important role in the kingdom’s politics at the time, influencing the king into investing into ambitious expeditions to explore the seas of Adhomai.

In '''2107 A.I./925 CE''' the first colony, a settlement that would become the city of Baltor, was founded in Harr'masir as a result of an expedition financed by the Kingdom of Das’nrra. For the next few years, several other colonies were established into the continents by many of the Adhomian kingdoms. This new competition for territories sparked another period of conflicts, referred to as the '''Colonial Wars of Harr'masir''', between those states. Many peasants and nobles families were relocated to these new lands, serving as their settlers and guardians. The politics of displacement and the constant warfare created a powerful feeling of resentment in the colonists of Harr'masir.

The '''Colonial Wars of Harr'masir''' came to an abrupt end in '''2378 AI/1286 CE''', when an ambitious [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]] caravan elder started a campaign of conquest against the nations of South Ras’nrr. '''Tajrhalrr Jrruzhani''' was a famous nomad mercenary of his time, that managed to acquire a large fortune under the service of the Kingdoms of Mezuma and Nazira. Using his experience and wealth he was able to unite several nomadic caravans under his control.

'''Tajrhalrr Jrruzhani''' waged war against Mezuma and Nazira, subjugating both by making use of a mobile force of Zhan Nomads armed with bows and spears. The [[Tajaran Ethnicities#Rhazar'Hrujmagh|Rhazar'Hrujmagh]] created the title of '''Almalik’Rhazar''', meaning “King of the Mountains”, denoting his rule over all of his people. The Nomadic domain disintegrated after the death of Tajrhalrr, divided between his sons and generals.

While the kings of Ras’nrr turned their attention to the Nomadic threat, many nobles administrating the colonies at east saw this an opportunity. The continent of Harr'masir erupted into several wars of independence. Those conflicts would last until '''2512 AI/1420 CE''', resulting in all nations, except of the Kingdom of Nal’tor, losing their territories at Harr'masir.

This later period of violence favored the development of new military technologies, among them the invention of gunpowder, rustic firearms and cannons. The first use of field guns in '''2537 AI/1445 CE''' marked the end of the '''Warring Kings Era'''. This new discovery changed the battlefields of Adhomai, inaugurating the '''Gunpowder Age'''.

== Gunpowder Age ==

The Gunpowder Age was marked by the slow replacement of traditional Adhomian battle tactics and weapons, that included melee weapons and crossbows, in favor of cannons and primitive firing lines. The Kingdoms of Amohda, Nal’tor and Das’nrra were the first countries to make use of this new technology.

During this period, many kings had the ambition of uniting their continents or regions under their rule. This aspiration gave birth to large and powerful states, with each of their rulers claiming to be the '''Kings of Kings'''. Long and destructive wars were waged with the goal of uniting those territories. The use of massive cannons barrages, early firearms and bayonets charges were a common sight in battle. [[Tajaran Minor Religions#The Suns War of Harr'masir|The Suns War of Harr'masir]] is an example of one of those early conflicts. Three mains empires emerged during this period; the Empire of Amohda, Empire of Das’nrra and Empire of Ras’nrr.

Even with technological advances, the Adhomian society was stuck with their old feudal system. The tension between nobility and peasantry increased due to new burdens brought by recent military campaigns. The first writings against the serfdom and caste systems started to appear around '''2800 A.I./1732 CE''', with those early revolutionaries being dealt with violent by M’sai enforcers. Draconian laws and sanctions were introduced against those that defied the status quo.

Relations between the ruling class and commoners were precarious, believed to have stemmed from harsh rulers and laws. Technological and cultural knowledge and breakthroughs had begun to trickle down from the noble families to the peasantry. The invention of the printing press in '''2824 A.I./1756 CE''' favored the spread of anti-monarchist pamphlets. Owning a copy of an unapproved text was a capital crime.

Despite the best efforts of the monarchies, a large underground ring of revolutionaries was formed in the Empire of Das’nrra. Philosophers, merchants, peasants and few landless nobles were united against the old ways. This movement was lead by a tajara known as '''Purrjar Ekhranrar'''. A revolt happened in '''2945 A.I./1877 CE''', with several cities experiencing combat between imperial troops and rebels fighting against the monarchy.

The other kingdoms, fearing the victory of rebellion, sent military expeditions to help the Empire of Das’nrra. The revolution was defeated in '''2951 A.I./1883 CE''', with the revolutionaries defeated and Purrjar Ekhranrar hanged for his crimes. The regimes, now aware of more dangerous enemies than themselves, created a way to secure their rule over Adhomai. The '''Steeple''' was established in Nal’tor. An internal embassy where the countries of Adhomai would resolve their disputes through diplomacy, creating a robust intelligence system aimed at subduing any threat to the world order. This event started the '''Steeple Peace'''.

== Steeple Peace ==

The '''Steeple Peace''' is a period marked for centuries of peace between the Adhomian kingdoms, slow and controlled development of technologies and systematic repression of the population. Tension between the peasantry and nobility continued to worsen, resulting in further enactment of more harsh regulations.

Adhomai underwent a form of industrialization with the creation and proliferation of the steam engine in '''3022 A.I./1954 CE'''. This forced the peasants into harsh new laborious professions, digging in mines and working 18 hour days building rail lines for private use by the [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]] nobility. Laws were soon enacted that banned any commoners from utilizing electricity or riding on trains.

Thirty years before human discovery of Adhomai, the deep-seated mistrust between peasants and nobles had reached an all time high. The Tajaran species was trapped in a technological bubble forced upon them by their nobility. At the height of their industrial revolution only a few years prior, the leadership at the time became wary of the unification of many Tajaran workers who demanded greater rights, seeing themselves in what could be accounted as another 'Renaissance' era and result in more 'enlightened' individuals straining their already crumbling control over the populace.

The realms of education, science, and luxury found themselves under severe restrictions, and your basic Tajara was forced into almost twenty hour work days with minimal time afforded for eating and sleeping on the job. Analysis of the noble houses proves that during this time in Tajaran history, the nobility had never been worth more in Sol credits than before. This is attributed to the fact that rather than modernizing Adhomai the nobility had seen fit to confiscate and use these fruits of scientific thinking for themselves.

Automobiles are considered one of the best examples of this. The first automobile is recorded to have been created in '''3360 A.I./2292 CE'''. Using a combustion engine much like primitive human vehicles, with extra anti-freezing measures and thick treads, one of the first functional automated cars had been produced by a collection of Tajaran engineers and scientists, at the behest of the nobility. These large creations were considered by many older Tajara to be a symbol of negligence and gluttony by their leaders. Workers were never provided with such things; they were forced to transport themselves through Adhomai's harsh winter conditions on foot or by using designed 'snow bicycles', regardless of how far they were from their place of work.

Further restrictions of the rights of the individual Tajara were enacted by a furious nobility after several instances of violence against [[Tajaran Ethnicities#Njarir’Akhran|Njarir’Akhran]], but specific information on these incidents has been lost. Legislation was introduced against 'workers unions' as well as any sort of illicit groups; a permit was required to form anything from hunting parties to agencies. In this whirlwind of political turmoil, a fresh generation of Tajara were growing up, deprived of what most humans consider to be 'basic rights'. As they grew older and angrier, the nobility saw fit to continue tightening their control over their subjects until a civil war was almost inevitable. Like a powder keg ready to blow, only a single spark was needed to light the flame.

This came in the form of human discovery in '''3576 A.I./2418 CE'''. A [[Sol Alliance]] funded expedition into the Tajaran home system discovered the pre-space age species and their homeworld of Adhomai. The first contact with these aliens started the '''Galactic Age'''.

= Modern History =

== First Contact ==

[[File:AdhomaiAncientRegimesNames.png|300px|thumb|A map of Adhomai before the first contact]]

Lush with untapped resources and potential workers, Adhomai was an attractive prospect for many human super corporations, especially NanoTrasen. Because of their slow technological progress, most of Adhomai's valuable minerals remained untapped by mining or drilling. It was due to this that several corporations attempted to insert themselves into the dealings of Adhomai.

However, the nobility felt incredibly threatened by what they considered 'intrusions' by humanity and completely refused them diplomatic access to their planet. The Alliance stepped in, initially unwilling to interfere in a pre-space age society and, reluctantly, the super corporations were forced to abandon their wishes to stake claims on Adhomai's resources - at least in the open. In the year '''3578 AI/2420 CE''', a group of Tajaran intellectuals - considered rebels by the state - were shuttled off-world by a still unknown entity. Given asylum in the [[Sol Alliance]], they met and discussed much with human scientists and officials. Tensions between the Alliance and Tajaran nobility rose after such an event and they accused the humans of harboring terrorists.

Eventually, these rebels were returned to Adhomai with supplies and weapons. Fed with new ideals of personal freedom and 'rights afforded to all' by their influential human friends, the seeds of revolution were sowed among the Tajaran populace, spread by word of mouth. Workers, doctors, teachers, even soldiers that were questionably loyal to the nobility were swayed by these promises of freedom and equality. Meetings in the basements of dark taverns or barns were common, and relations between the nobility and their peasants were at the lowest ever recorded in Tajaran history.

==The Uprisings==

It took little more than a year for a formal uprising to be staged. On '''3579 AI/2421 CE''', after the nobility had captured one of the original Tajara that had been shuttled off world, he was sentenced to be publicly hanged by the neck in front of their peasants to show just how serious they were about keeping control. Ultimately, many historians believe this to be a highly egregious mistake. Rebels in the audience, armed with advanced off-world weapons, proceeded to open fire on loyalist forces and kill a nobleman in the process. This event, called the '''D'as'ral Massacre''' (so named for the city it took place in) by the nobility was all the excuse they needed to enact martial law.

However, they found themselves in a cornered position. Weapons and supplies were being shipped in off-world by mysterious benefactors, and their collections of scientists and engineers had either fled to safety being noblemen themselves, or took up arms and joined the revolution. Without significant scientific presence to deconstruct or understand these new human weapons or support the war effort, the conflict resulted in a string of rebel victories that drew closer and closer to the capital cities of each providence. Fighting was extremely fierce and atrocities were recorded by both sides.

Among the noble families, the largest and nearly the most powerful was a dynasty called the '''Hadii'''. Their castle was amongst the best defended in the region and the battle to take it was waged for six months of non-stop fighting. As it became increasingly clear to them that they were eventually going to be overrun, the Hadii struck a deal with the rebel leader; in return for complete immunity from the war, as well as persecution, they afforded the revolutionaries with unique tools and even blueprints of other families' castles, pointing out weak points and infiltration spots.

It was this turn coating that tipped the revolution in favor of the peasantry. Armed with this new information, they made use of radio systems previously restricted for nobility to methodically and ruthlessly end their uprising by murdering most of the noble families and whatever soldiers and civilians remained loyal to them. By '''3588 AI/2431 CE''' the revolution had finally come to an end with a total of more than '''92 million casualties''' with more than half of that being loyalist forces, and '''40 million civilian deaths'''. Many Tajaran cities and villages were utterly destroyed by vicious fighting as well as bombardment by uncaring nobles. A informal ceasefire was declared between the factions, though skirmishes were still common.

==Outcome of the Revolution==

Following this total upheaval of Tajaran society, rebel leaders met with Hadii noblemen and discussed how to form a government, given that only the Hadii were experienced with ruling. Human corporations took express interest in this; the Hadii were one of the few noble families that saw profit in human stakes on Adhomai, and many back-room deals were made until ultimately the Hadii were placed at the head of Tajaran government in '''3589 AI/2432 CE''', and ushered in a new federal republic: The People's [[Republic of Adhomai]]. The Tajaran public was markedly distressed by this turn of the events, and fearing another uprising, human intervention again helped defuse the situation. The Hadii promised that it would not be like it was before.

NanoTrasen, suspected by many conspiracy theorists to be behind the funding and supplying of Tajara during the war, holds claim to most of Adhomai and has a monopoly over most of the planet's valuables. Collaboration between them, the [[Sol Alliance]] and the Jargon Federation has resulted in more technological advances in Tajaran society recently than ever before in their recorded history. Approval ratings for the current leadership rose in response.

However, serious problems remained. '''Rhagrrhuzau Hadii''' suddenly began to back out of the People's Republic's agreed upon business deals with NanoTrasen, all of which saw a massive amount of Tajaran natural resources exported. Citing humanity as greedy and destructive, '''Rhagrrhuzau''' made clear his intentions to make Adhomai independent until it was ready to take on the burden of interstellar politics.

==The Second Revolution==

The disagreements and hatred of the Hadii republican government had led to insurrection and treachery between Adhomai's major power figures since '''Rhagrrhuzau Hadii''''s new economic policies were revealed. Many Tajaran business contractors - just recently denied their ability to sell ludicrous amounts of natural resources and workers to the massive human megacorporation, NanoTrasen - felt threatened by the reforms of the Hadii government and its first President, '''Rhagrrhuzau Hadii'''. On '''3608 AI/2451 CE''', during a military parade, President Rhagrrhuzau was assassinated by a young Zhan-Khazan radical. A known secret service agent of the People's Republic, the radical was sentenced to death for his treachery, brought on by the violent tendencies of his Zhan-Khazan genetics. His brother and vice-president [[Notable Tajara#President Njadrasanukii Hadii|Njadrasanukii Hadii]] quickly assumed the office of the presidency and immediately passed brutal laws that punished Zhan-Khazans and 'subversive elements'. NanoTrasen was invited back to Adhomai and menial workers were sold en masse to NanoTrasen workplaces while the rights to the bountiful natural resources of Adhomai were sold off to NanoTrasen. Public hangings and firing squads became the norm once again.
[[File:Godblessalmarihadii.png|thumb|400px|left|Picture taken by the Adhomai Chronicle moments before the Assassination of Rhagrrhuzau Al'Mari Hadii. The single most defining moment of this generation of Tajara.]]

Many military generals that had fought for the Republic soon defected under the banner of the Adhomai Liberation Army, the leader of which being '''Rhagrrhuzau Hadii''''s old friend and ally, [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]], and Adhomai found itself embroiled in yet another global conflict that continues to this day. "His gun was on stun" became the rallying cry of Rhagrrhuzau's fiercest supporters, "Hadiists," as they alluded to how he not only left himself greatly vulnerable during the parade, but had even left his energy pistol on stun while he was assassinated.

===Adhomai Today===

The Tajaran home world has suffered plenty in the three decades since the end of the First Revolution. With the sudden injection of advanced technology into their relatively simple life, the discrepancy between modernized cities and outlying areas could not be more obvious. While the Tajaran capital boasts the most modern developments with sleek skyscrapers, advanced connections and phone lines, as well as hospitals and schools, the further you get from the larger cities, the more apparent it is that things are not quite so flashy. Expanding infrastructure remains difficult, as most public funds are seized for use by the military or used to repair infrastructure damaged by shelling or bombings.

There is a steady stream of money being fed into the People's Republic of Adhomai. NanoTrasen, as per it's agreement with the president, have set up mining and logging operations on Adhomai using the local work force for the most menial of tasks. In return, company funded clinics and schools are slowly being spread out and build in the needy areas. Tajaran resource operations are now all but nonexistent; the buildings that were once part of the nobility's small gathering efforts have now been refurbished and are being used by NanoTrasen.

Literacy has risen to its all time high on Adhomai, and with the assistance of the Alliance, teachers have been brought in from off world to educate the younger generation of Tajara. However, this number has begun to decline as the dangers of working on Adhomai are beginning to become common knowledge. Special establishments for older students have also been constructed to assist the elder generation in being brought to the same level of education, but NanoTrasen has not expressed significant interest in this; these people make up the brunt of their low-paid workforce and they want to ensure that they are kept that way.

There are still several proponents of revolution that oppose the current government, which has plunged the planet into another all-encompassing civil war that remains at a standstill today.

= Timeline of the Modern History =

At the dawn of the new century, the Tajaran people were at peace. For centuries the old monarchies of Adhomai maintained a balance of power, carefully averting anything greater than small scale conflicts through cooperation and manipulation. In time, this intricate system of international politics centralized into one building within the city of Nal'Tor, the Steeple. This building which started as an international embassy to coordinate diplomacy and maintain the balance of power gradually became the seat of power for a new world order. By the 25th century, all of the world's monarchies existed under an informal international confederation which acted with collective security to end rebellions, police hot zones across Adhomai, and curtail the distribution of newer technologies to the masses. A repressive culture of anti-intellectualism and adherence to tradition kept the lower classes from organizing or attempting any large scale rebellions. The literacy rate across the species was less than 20% and literature is still frowned upon by most of society to this day. Most history and stories were told orally by Kraszarrumalkarii, named after a Ma'ta'ke god of storytelling. The high end of technology was on par with early 20th century Earth, however industrialization was still dawning and only catered to the rich. Majority of the planet remained agricultural workers with most goods crafted by skilled artisans rather than factories. On the underbelly of society, small numbers of disenfranchised nobles privately sought to change the status quo- some with a bleeding heart and others with personal gain in mind.

===Pre-War Era===

'''2418: '''A [[Sol Alliance]] funded expedition arrived in the S'rand'marr system and made first contact with the Tajara. The first landing was made in [[Crevus]] and local nobles entertained the alien visitors. The meeting was kept a secret but rumors spread on the Das'nrra continent. A few weeks later, diplomats from the [[Sol Alliance]] and the Nralakk Federation met with with Adhomai's global community in Nal'Tor to establish diplomatic ties. Each were given apartments in the '''Steeple''' to serve as a working embassy. The international nobility continued to keep the meetings with aliens a secret, but someone leaked the information to the outside world and rumors swept the cities. The governments finally decided to make formal announcements about the discovery of aliens, sending shock waves through urban centers across Adhomai. Rural peasantry remained apathetic, but across the first week, six thousand Tajara killed themselves from the shock of the event. Nobility actively inhibited the proliferation of alien media to the masses, but were quick to negotiate trade deals for high technology oddities. After several mega-corporations, especially NanoTrasen, attempted to lure several states into imperial ambitions the '''Steeple''' successfully petitioned the [[Sol Alliance]] to prevent open interference with the governments of Adhomai.

'''2420:''' Groups of Tajaran intellectuals, primarily young nobility and high-standing Hharar, conspired for liberalized governments. Many took refuge off planet where they learned of human ideals, and returned to Adhomai to spread them. Small scale insurgencies broke out across the planet as the stability of the old order began to show cracks. The language of Siik'tajr was born as a means of covert communication between dissidents.

===The First Revolution===
'''2421:''' The Great Revolution erupted following the '''D'as'ral Massacre'''. Nobles across the planet declared martial law in retaliation and mobilized their armies.

In southern Rasn'rr', disgruntled and oppressed Zhan-Khazan populations along the Zhan mountains joined forces with impoverished dilettante Njarir-Ahkran seeking to restore former glory. The ancient city of Mezuma became the birthplace of the "People's Emancipation Movement." Weeks later, the city of Trizar joined the movement after a coup d'etat. After hasty organization, the rebel army moved north and besieged Nazira.

In the city of Orul, factories were closed by the military for their role as meeting places for dissidents to meet and organize. The workers were all sent home without pay. An event known as the "Poorhouse Riots" occured as the starving and impoverished took to the streets. After three days of violence, the city was conquered by its rebellious poor which formed the "Republic of Free Tajara." All Njarir-Ahkran who failed to evacuate were executed.

'''2422:''' The city of Nazira was taken by the People's Emancipation Movement. Rebel units continued to enforce martial law and rationed food. Soup kitchens and bread lines became hotbeds for riots, many ending in massacres by the rebel military. Recruitment into the rebel military surged following the introduction of incentives which offered better food rations for soldiers and their families. Noble forces made several offensives over the next two years from Mal'jor military base, in order to retake the city. None succeeded in reaching the city outskirts, despite large casualties on both sides.

The city of Orul was reconquered and occupied by loyalist forces based out of Zatushka. The Republic of Free Tajara carried out a series of insurgent activities ranging from sniper attacks of officers to using improvised explosive devices on the streets. Unable to bear the burden of witnessing the crimes against Tajara and citing "unprecedented barbarity," the noble in charge of the occupying forces withdrew from the city. His name was '''Tajrhalrr Hadii'''. The Republic of Free Tajara propagandized the event as having repulsed monarchist invaders, and began rapidly reconstructing their war potential.

'''2424:''' The Republic of Free Tajara and the People's Emancipation Movement formed a unified "Rasn'rr Confederacy of Free Republics." The new confederacy launched a coordinated offensive to conquer the equatorial region of the Rasn'rr continent.

The Das'nrra continent balkanized as various regional nobles attempted to secure the throne for themselves. The Empire was weakened from providing large amounts of financial support to monarchist forces on '''Rasn'rr''', and the Imperial Military had to be recalled from B'urr where it had been preparing the defense of the city. The Emperor himself disappeared during the fighting and was never seen again. An international coalition of monarchist forces formed and attempted to restore order on the continent.

The military base at Baltor severed ties with its government across the ocean at Nal'Tor. The base became the home of a military dictatorship under its M'sai general. The rogue general marched on the Kingdom of Kaltir, seeking to rapidly expand his holdings. The city of Olska was taken by surprise and brutally subjugated. The Kaltir Expeditionary Force, which has been deployed to Das'nrra to suppress noble revolts, was recalled to the Harr'masir continent.

'''2425:''' Loyalist forces left B'urr to oncoming rebels without a fight. The city of Tampiska as well as vital roads to Nal'Tor were heavily reinforced by these units, and the navy stationed at B'urr were deployed to aid loyalist forces for the Das'nrra Empire.

Rebels based out of Orul overran Mal'Jor military base. The loyalists retreated to Tampiska, further enhancing its fortifications. Rather than pursuing, the Orul Rebels changed their focus northward and besieged Zatushka. This siege would later be discovered to be a feint for a different offensive.

The Kaltir Expeditionary force seized Baltor through the first major amphibious assault in Tajaran history. The city of Olska was liberated by the end of the year, with cheering citizens praising the King and celebrations filling the streets.

A peasant revolt from the rural areas around Dolor seized the city, naming themselves the "Liberated People's of Harr'masir." Their coastal area to the west was quickly assaulted by the Kingdom of Amodha, which sought to reconquer their ancestral lands.

'''2426:''' The surviving monarchies adopted the Sol Alliance Credit as their official currency in an attempt to curry favor for international support. The move failed to gather public support as many Tajara did not have enough wealth to afford the currency trade-ins.

The Siege of Tampiska began after months of artillery battles. Hordes of rebels attacked the city in waves as building to building combat lead to the bloodiest urban conflict of the war.

Citadel Hadii, the stronghold of the Hadii Family, came under siege in a surprise attack following an arduous rebel march through the Nraz'i mountains. The small garrison of the immense citadel held strong until forces recalled from the abandoned Zatushka base broke the rebel siege. '''Tajrhalrr Hadii''' died in the fighting, leaving his eldest son, '''Rhagrrhuzau Hadii''', at the head of the Hadii dynasty. Rebel forces which had taken Zatushka followed the recalled army and renewed the siege shortly after the last was broken. The siege only ended when the young Rhagrrhuzau Hadii struck a deal with the rebels, giving blueprints to other noble fortresses, information about other armies, and loyalty in exchange for immunity and protection. Forces of the Hadii family withdrew from Das'nrra and began subjugating monarchist forces north of Hadii lands.

Fighting on Das'nrraled to the collapse of most noble families involved in the fighting. The coalition of noble forces from across Adhomai which sought to restore order was forced to disband as rebels on various homefronts forced the withdrawal of each army. Based out of the capital of Shastar City, anti-monarchist rebels calling themselves the Das'nrra Resistance Movement formed and gained momentum against the tired noble armies.

The Liberated People's of Harr'masir surrounded and destroyed the invading army of the Kingdom of Amohda, before moving northwards to defend against an offensive by the Kingdom of Kaltir.

'''2427:''' The Das'nrra Resistance Movement rapidly absorbed much of the continent, marketing themselves as a beacon of stability and sanity among the autocratic madness. By employing principles of Tajarism and providing humane treatment of occupied populations, the movement became popular among the masses who had suffered through the atrocities of the noble infighting. Any noble families who did not surrender were executed, while their subjects were treated with kindness as liberated Tajara.

The Kingdom of Amodha began a second invasion of the western coast of Harr'masir, seeking to put the pressure on the rebels to aid the Kingdom of Kaltir. The armies of Kaltir defeated the Liberated Peoples of Harr'masir, besieging the retreated army at Dolor.

The Hadii Faction subjugated the northern areas of Rasn'rr' before stationing their soldiers at various fortresses and beginning large scale mobilization of populations under the control. The Faction lobbied successfully under Confederate Command to place the Republic of Free Tajara and all of its holdings under the Hadii's jurisdiction.

'''2428:''' The Das'nrra Resistance Movement and the Rasn'rr Confederacy formed an alliance and became the Western Coalition of Free Adhomai. The resistance movement finalized its conquest of the Das'nrra continent and began naval bombardment of Nal'Tor. Near the end of the year, of Siege of Tampiska drew to a close. The Siege of Nal'Tor began after the last remaining western monarchists retreated to the city.

The armies of the Kingdoms of Amodha and Kaltir joined together for the Siege of Dolor, but the rebels manage to maintain their defense.

'''2429:''' The Western Coalition of Free Adhomai and the Liberated People's of Harr'masir formed an alliance, changing their name tentatively to the Coalition of Free Adhomai. Navies of the Western Coalition sailed west across the Nas'kin Ocean to invade Kaltir. The force was intercepted by the navies of the Kingdom of Kaltir supplemented by the Kingdom of Ahmoda, which had crossed the Ras'val canal. Monarchist navies were triumphant, sinking most of the rebel fleet. A second rebel fleet sailed east across the Sum'add Ocean and blockaded Amodhan ports.

The city of Dolor was retaken by nobility forces. All rebels and their sympathizers were offered amnesty. Although many accepted, some refused on ideological grounds and were imprisoned for treason.

'''2430:''' The city of Nal'Tor was taken by rebel forces after the surrender of its defenders. The rebel fleet prepared for a large scale amphibious invasion of Harr'masir. Weakened by a year of starvation from the blockade of its ports and the destruction of the fishing operations, the Kingdom of Amodha defeated by a combination of peasant revolts and invading rebels. The island became the staging point for a planned invasion of Harr'masir as rebel forces gathered.

The fleet of the Kingdom of Kaltir engaged rebel naval forces on the western coast of Harr'masir south of Baltor. After a the battle lasted over 72 hours, the Kingdom's navy was finally sunk.

'''2431:''' All Adhomian monarchies except the Kingdom of Kaltir were overthrown by rebels. Following what is considered the end of the "Great Revolution," most of the rebel groups joined under '''Rhagrrhuzau Hadii's''' faction to form the [[People's Republic of Adhomai]].

The city of Orul, the People's Emancipation Movement, and other proponents of confederacy rose in rebellion to the federalization of the Coalition of Free Adhomai. The city of Orul was quickly and brutally occupied by the armies of the Hadii Faction which had remained home as the defensive force for the Rasn'rr Continent. Soldiers of the Dasn'rra Resistance Movement, which had joined under the Hadii's rule, suppressed units of other forces where they had all gathered on Amodha. The newly formed Republican Army under Hadii's command marched south to suppress the undefended cities of the People's Emancipation Movement and cement the rule of the People's Republic.

'''2432:''' The Hadii Faction was able to finalize the suppression and subjugation of all other rebel groups and began preparing to resume the amphibious invasion of Harr'masir.

The Kingdom of Kaltir capitulated to People's Republic rule before an invasion could be performed. Despite popular requests for amnesty and peace from the Kingdom, many of the nobility were executed. '''Farkhanzirhal Azunja''' imprisoned his 32 year old son, [[Notable Tajara#King Vahzirthaamro Azunja|Vahzirthaamro Azunja]], in order to hide him during the executions. The People's Republic of Adhomai became the lone global government of Adhomai.

===Interwar Period===
'''2433:''' The recently formed [[People's Republic of Adhomai]] obtained a charter from the Central Bank of the [[Sol Alliance]]. This charter allowed them to retool the Nal'Tor mint for printing Sol Alliance Credits.

===The Second Revolution===
'''2449:''' [[Notable Tajara#King Vahzirthaamro Azunja|Vahzirthaamro Azunja]] and his retinue of intellectuals were released from prison in secret in the middle of the night. They traveled the Kaltir region, gathering support for an independence movement. Copies of a constitution with the title "The New Kingdom" circulated by underground printing presses, and were praised by many locals for its generous civil liberties. Rumors spread of a [[New Kingdom of Adhomai]]. People's Strategic Intelligence Service Agents were unable to locate and take Azunja into custody.

Citing humanity as destructive and greedy, President '''Rhagrrhuzau Hadii''' announced a series of new economic policies which eliminated many deals favorable to NanoTrasen. He openly denounced human imperialism and proclaimed that Adhomai must be independent.

'''2450:''' Having gathered widespread support across Harr'masir, Azunja and his loyalists began an open rebellion against the People's Republic, calling themselves the "[[New Kingdom of Adhomai]]". Many supporting Njarir-Ahkran were given nobility and assigned land to govern based on their prior involvement in the movement and their friendships with King Azunja. The Dymtris Line was hastily constructed to block the isthmus leading into the Kal'tir region. The New Kingdom lost majority of its territory in the first year and millions fled northward as refugees to avoid brutal reprisals.

'''2451:''' President '''Rhagrrhuzau Hadii''' was assassinated during a military parade in Nal'Tor by a Zhan-Khazan secret service agent. His brother and vice president, [[Notable Tajara#President Njadrasanukii Hadii|Njadrasanukii Hadii]], assumed office. The 2449 economic reforms of '''Rhagrrhuzau Hadii''' were rolled back by Njadrasanukii.

Former head of the armed forces, [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]], attempted a coup with many other generals but failed. The Adhomai Liberation Army was formed by these rebels.

'''2457:''' Starlet '''Yasmin Piaf''' performed the "Heavensward" Tour. Anti-ALA sentiments are infused into the highest grossing musical tour in Tajaran history.

'''2458:''' The [[PRA Orbital Fleet Structure|Adhomai Orbital Defense Navy]] (AODN) ended its last lease for old NanoTrasen ships following the launch of the PRS Njarir and PRS Vostak. Anti-Piracy operations in the space around Adhomai were conducted solely by the AODN without foreign aid.

The People's Republic of Adhomai introduced conscription following the loss of Tampiska to Liberation Army forces. The surge in military manpower resulted in the retaking of Pur'r by the Republican Army. The city of P'urr was renamed to its prewar name, "B'urr".

A four Mt nuclear weapon was deployed against the headquarters of Liberation Army forces in the Quizosa military base, north of Ron'Tul in the Rhazkjara mountains. The nuclear attack caused international outrage and lead to diminished foreign support for the People's Republic. Ron'Tul was firebombed by the People's Republic of Adhomai, and much of the city was destroyed. Liberation Army forces withdrew and the city was occupied by the Republican Army.

Rehabilitation programs are established by the People's Republic of Adhomai, seeking to purge subverside and humanized elements among its population. Several labor camps are created in the republican territory. Homosexuals, dissidents and political enemies are arrested and interned in those installations in the following months.

On the Harr'masir continent, The Dymtris Line was overrun by a Republican Offensive. The Republican Army was repulsed by the Imperial Army when it was forced to retreat to deal with insurrections by rebel forces. Highly coordinated mass guerrilla attacks orchestrated by the ALA swept the People's Republic, creating a week of chaos and bloodshed. Lines of communication and infrastructure were crippled long enough for the Liberation Army to make considerable gains.

'''2459:'''
The People's Republic's colony of Hro'zamal is founded in the Nrrahrahul system.

Tajara Rights Act of 2459 is passed by the People's Republic Congress, improving working conditions on labor camps, providing better medical relief efforts for refugees from areas of conflict, and a reducing homosexuality to a misdemeanor.

'''2459:''' Imperial Parliament of the [[New Kingdom of Adhomai]] was bombed by a suspected ALA radical. [[Notable Tajara#King Vahzirthaamro Azunja|King Vahzirthaamro Azunja]] was hospitalized for a month, and [[Notable Tajara#Field-Marshal Rrhazhal Zarkradar'Akhan | Field-Marshal Rrhazhal Zarkradar'Akhan]] remained in the hospital for a year. Enough members of parliament were killed to default the Kingdom to temporary absolute monarchy. After completing offensive operations, the New Kingdom of Adhomai began construction of the Vlrralkhzazhul Line to consolidate their gains.

The various civilian governments under Adhomai Liberation Army rule were brought together under the [[Democratic People's Republic of Adhomai]]. Within months of its creation, the DPRA effected large-scale repairs and improvements to electrical infrastructure.

'''2460:''' The Republican Army is expelled from Das'nrra by a rebel offensive. Republican forces manage to evacuate by sacrificing the [[Tajaran Military Structures#The Republican Guard|the Republican Guard.]]

The New Kingdom announces the New Crown heir; [[Notable Tajara#Crown Heir Shumaila Azunja|Shumaila Azunja]].

The Democratic People's Republic of Adhomai and the New Kingdom sign a ceasefire. Royalists forces evacuate Amohda, allowing the Adhomai Liberation Army to control it as part of their agreement.

The campaign for DPRA president begins, with a dispute between National Adhomai Worker’s Party and Free Tajaran People’s Party..

'''2461:''' Almrah Harrlala, the leader of the National Adhomai Worker’s Party, wins the DPRA elections. A coup attempt against her government by the military is thwarted with the help of [[Notable Tajara#Supreme Commander Halkiikijr Nated'Hakhan|Halkiikijr Nated'Hakhan]].

Zhan nomads forces of Harr'masir are united by [[Notable Tajara#King of the Mountains Rustam Harmaliik | Rustam Harmaliik]], claiming the title of '''Almalik’Rhazar'''. Rustam and his people join the New Kingdom of Adhomai's war effort after losing support from their ALA allies.

A successful offensive is launched by the New Kingdom of Adhomai against the People's Republic at Harr'masir. Republican forces are expelled from the continent after the siege of Olska.

Sol Alliance forces and [[PRA Orbital Fleet Structure|Orbital Defense Navy]] engage each other in a short space skirmish, caused by the dispute on the lease rights of a space port. Sol Alliance imposes an embargo against the People's Republic, cutting all military aid and weakening their economy.

The city of Dolor is liberated by the forces of the Adhomai Liberation Army.

The People's Republic of Adhomai is attacked by the Adhomai Liberation Army and the Royal Navy, triggering the creation of a coalition. Allied states, NanoTrasen, mercenaries and volunteers join the PRA in their defense against the rebels.

{{Navbox Tajara Lore}}
{{Navbox Lore}}
[[Category:Pages]]
[[Category:Tajara]]

Template:Navbox Dionae Lore

2019-08-27T02:31:59Z

Mofo1995: Changed format and added link to Dionaea lore page

<div class="padded" width="100%" style="font-size: 12px; padding: 5px">
{| style="cellpadding: 5px; text-align: center;width: 100%" class="mw-collapsible mw-uncollapsed wikitable"
|-
! colspan="3" style="width: 50%; background-color:#907E4A" | [[:Category:Dionaea|<span style="color: White">Dionaea Lore Pages</span>]]
|-
! style="width: 10%" colspan="2"| Species Page
| align="center" | [[Dionaea]]
|-
|}
</div><noinclude>
[[Category:Templates]]
[[Category:Pages]]

Retroactive License List

2019-08-13T20:25:30Z

Mofo1995: Double those enter keys, fams

All work written after 13 August 2019 is licensed under CC BY-SA 4.0. The license only applies to '''text as it is written.''' Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All people signed under here agree to retroactively license their contributions on this wiki under CC BY-SA 4.0

Mofo1995

Jamchop23334

Alberyk

Retroactive License List

2019-08-13T20:04:54Z

Mofo1995: Removed my name

Retroactive License List

2019-08-13T20:04:04Z

Mofo1995:

Retroactive License List

2019-08-13T20:02:46Z

Mofo1995: Licensing agreement for writers!

All work written after 13 August 2019 is licensed under CC BY-SA 4.0. The license only applies to '''text as it is written.''' Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode
Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All people signed under here agree to retroactively license their contributions on this wiki under CC BY-SA 4.0

Tyler Morford (Mofo1995)

User:Mofo1995

2019-07-21T01:42:25Z

Mofo1995:

{{wip
|assign = Loow}}

{{Navbox Tajara Lore}}

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)
Loremaster (July 2019 - Current)

[[File:Death of Sylvester.jpg]]

''Contact me with any questions about the following: [[Tajara]], [[Adhomai]], [[Notable Tajara]], [[Tajaran Military Structures]], [[The Nal'tor College of Career Excellence]], [[Tajaran Ethnicities]], [[Adhomai Economy]], [[Ma'ta'ke Gods]], [[S'rand'marr]], [[Timeline of Tajara]]''

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Timeline of events from discovery of space aliens to 2459, setting the canon for the events of the first revolutionary war. <--- WIP

2.) Cities lore. Outlining the culture, architecture, and common professions of each city. <--- Regional lore is coming first, then this

3.) Elaborating on the various dance sensations on Adhomai according to region. <---- Maybe.

---4.) Canonizing cave-dwellers and tribes of cuddling cat people.--- NO way

You just lost the game.

== Helpful Maps ==
[[File:Ahdomai Political cities.png|825px|left]]
[[File:Geographical1.png|825px|right|]]
[[File:AdhomaiAncientRegimesNames.png|825px|left]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

User:Mofo1995

2019-07-21T01:41:58Z

Mofo1995:

{{wip
|assign = Loow}}

{{Navbox Tajara Lore}}

'''I WAS the master of the cats.''' (RIP Sept 2016 - July 2019)

[[File:Death of Sylvester.jpg]]

''Contact me with any questions about the following: [[Tajara]], [[Adhomai]], [[Notable Tajara]], [[Tajaran Military Structures]], [[The Nal'tor College of Career Excellence]], [[Tajaran Ethnicities]], [[Adhomai Economy]], [[Ma'ta'ke Gods]], [[S'rand'marr]], [[Timeline of Tajara]]''

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Timeline of events from discovery of space aliens to 2459, setting the canon for the events of the first revolutionary war. <--- WIP

2.) Cities lore. Outlining the culture, architecture, and common professions of each city. <--- Regional lore is coming first, then this

3.) Elaborating on the various dance sensations on Adhomai according to region. <---- Maybe.

---4.) Canonizing cave-dwellers and tribes of cuddling cat people.--- NO way

You just lost the game.

== Helpful Maps ==
[[File:Ahdomai Political cities.png|825px|left]]
[[File:Geographical1.png|825px|right|]]
[[File:AdhomaiAncientRegimesNames.png|825px|left]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

Corporate Regulations

2019-05-04T09:23:50Z

Mofo1995: /* Low Level Infractions (Yellow Violations; i100's) */ Clarified to prevent abuse.

{{Reference}}
{{IC_Laws}}

= Corporate Regulations =

Corporate Regulations are penned regulations that all Nanotrasen employees have agreed to abide by in the signing of their employment contract. These regulations apply across the board on any Nanotrasen owned property, be it station, ship, or outpost.

Onboard each facility there will be a dedicated Security department in charge of making sure that all Nanotrasen employees follow these regulations.

*'''Regulations protecting prisoners from mistreatment applies to even non-crew.'''

*'''Executions are illegal and not allowed by regulations.''' Station security nor command should be doing any executions. The maximum possible penalty for major infractions is cyborgification.

*'''The brig timer of a prisoner begins after processing.''' All prisoner processing is expected to be completed in a timely manner. Should a detainee's processing take an unreasonably long time, the personnel responsible for that processing may be liable for illegal detention.

=== Interpretation of the Regulations ===

Every person on the station should have a good knowledge of Corporate Regulations. Following them could mean the difference between having a peaceful day or paying 1000 credits for multiple infractions. Extensive knowledge of Corporate Regulations is required for such positions as the Warden, Head of Personnel, Captain, and the Head of Security.

For all incidents, the '''suspect's intent''' is very important. Some incidents are mutually exclusive.

A single incident has a single sentence, so if, for instance, the prisoner took 3 items off someone, this is a single count of pickpocketing.

Aiding and abetting a criminal makes you an accomplice; '''you can be charged with the same crime as the person you aided and abetted.'''

The charges “Battery”, “Attempted murder” and “Murder” do not apply to crimes committed against [[IPC|IPCs]], whether they are free intelligences or owned by a person or company. Consult employment/security records to determine whether an IPC is owned or not.

Positronic intelligences are not protected by capital punishment laws. Those charged with red level infractions may be at risk of being dismantled or destroyed.

=== Additional ===

==== Captains and Authority ====

Captains are not above Corporate Regulations and can be arrested by Security for breaking them. However, this should only happen if active Heads of Staff agree in a unanimous decision to approve the arrest, or the arrest is ordered by Central Command. '''Captains should not be removed from their position in this way for anything but violations that would normally require holding until transfer.''' Lesser violations can and should be reported to Central Command, but are not generally severe enough to warrant this drastic action. If a Captain is arrested in this manner, an Acting Captain should be appointed immediately, and Central Command should be informed.

The station's assigned Captain has full and final authority over the operation of the station. They are authorized to issue direct orders to entire departments or specific crew members. They may take any actions or issue orders that violate regulations during non-standard situations. Generally, these orders must be carried out. Even if you feel an order from the Captain to be against regulation, your moral code, or generally detestable, you still have to follow it. You are entitled to begin a vote within Command (if you're part of Command) to have the Captain arrested if the order breaks a serious regulation, or fax Central Command (if you have access to a fax machine) to have them weigh in, but disobeying the order (if given to you) or obstructing it (if not given to you directly) is Failure to Execute an Order. This is upgraded to Sedition if you start encouraging others to refuse the Captain's orders.

If a crew member breaks regulations while following a direct order from the Captain, when there are other legal ways to carry it out, that crew member is generally considered at fault for the violation.

Pardons are only legitimate if they come from Central Command. Not even the Captain can deliver pardons, but they can grant parole with or without a tracking implant.

==== Injunctions ====

The Captain, Head of Security, and Internal Affairs Agents may issue injunctions to the crew if deemed necessary.

An injunction is a restriction on a crew member, meant to prohibit disruptive behavior that may not otherwise explicitly break regulations. Violating the terms of these injunctions '''is''' breaking regulations however, covered by '''i108 Violation of Injunction''' below. Examples of valid uses of injunctions include things like preventing two belligerent crew members from interacting with one another, or stopping someone from abusing alcohol at the bar. They are not meant to circumvent the chain of command, however, and efforts to resolve problems within that structure should be made first.

The Head of Security and Internal Affairs Agents may issue injunctions to any non-Command member of the crew. The Captain's orders may override these injunctions.

Only the Captain, Central Command itself, or every other member of Command acting as the Captain in a unanimous decision, may issue injunctions to a member of Command Staff.

==== Misc ====

Do '''NOT''' demand a tribunal for anything. You'll just be laughed at.

A '''Warrant''' must be provided for almost any search or arrest conducted under code green. Exceptions to this rule exist if an officer is a direct witness to a crime, or may reasonably conclude that failure to act will pose an immediate danger to the crew and/or station. Search warrants may also be circumvented if the Head of Staff over the employee being searched has given their direct consent.

'''Suspensions''' are used to temporarily suspend an employee from active duty, restricting them from holding any station rank. They are typically used in situations where an employee can no longer be trusted to continue their work.

'''Demotions''' are used to temporarily demote an employee to a rank below their previous occupation, allowing them to continue active duty under a position of less authority. They are typically reserved for situations in which the employee is still trusted to continue work, but may require additional training or oversight.

'''Drugs''' such as alcohol, tobacco, Ambrosia Deus, Ambrosia Vulgaris, etcetera are not covered by the '''Contraband''' regulation as these are legal under Tau Ceti law.

=== Low Level Infractions (Yellow Violations; i100's) ===
==== Regarding warnings ====

Officers are allowed to give out official warnings for first-time low level infractions. Any repeat offenders are to be sentenced.

Officers are not obligated to first issue out an official warning, but are encouraged to do so if the situation allows it.

{| width="950px" style="background-color:#ffee99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffee55;"|No.
!style="background-color:#ffee55; width:150px"|Incident
!style="background-color:#ffee55; width:300px"|Description
!style="background-color:#ffee55;"|Notes
!style="background-color:#ffee55;"|Traditional Sentence
!style="background-color:#ffee55;"|Repeat Offense
!style="background-color:#ffee55;"|Fine
|-
| i101
| '''Trespassing'''
| To be in an area which a person does not have access to.
| Remember that people can either break in, sneak in, or be let in. Always check that the suspect wasn't let in to do a job by someone with access, or were given access on their ID. Trespassing and theft often committed together; both sentences should be applied. Severity is increased if they refuse to leave the area peacefully, more so if they attempt to use important equipment there, so feel free to add other charges if they do.
| 3 minutes.
| Up to 10 minutes and/or demotion.
| 200 credits
|-
| i102
| '''Petty Theft'''
| To take items from areas one does not have access to, or to take items belonging to others or the station as a whole. Includes theft of credits up to 500cr. For higher amounts see i220 - Fraud
| Keeping items which are in short supply where they belong is what is important here. A doctor who takes all the surgical tools and hides them still commits theft, even though he had access. Items can include anything from toolboxes to metal to insulated gloves. Remember to take the items away from them and return them to where they stole them.
| 3 minutes, returning of stolen item to the owner or department.
| Up to 10 minutes and/or demotion.
| 150 credits
|-
| i103
| '''Minor Assault'''
| To use, or threaten, physical force against someone, without intent to kill or seriously injure. To cause easily repairable damage to a free IPC chassis, up to and including the removal of limbs.
| If it causes minor damage and easily treatable damage, it's minor assault. Starting fights with other employees or punching fellow employees counts too, as well as seriously threatening them with it. Force-feeding someone is this unless it's poisonous or knocks them unconscious.
| 4 minutes.
| Up to 10 minutes and/or demotion.
| 400 credits
|-
| i104
| '''Battery'''
| To have unwanted physical contact with someone, even where the contact is not violent.
| Bumping into someone in a corridor doesn't really count. Touching someone, when they have explicitly told you not to, does.
| 2 minutes.
| Up to 8 minutes and/or demotion.
| 200 credits
|-
| i105
| '''Indecent Exposure or Hooliganism'''
| To be intentionally and publicly unclothed, yelling at people for no reason in public or on comms, throwing around stuff where it could hit someone, yelling about how terrible NanoTrasen is, etc.
| Running around the station naked or in underwear, or other such degrading activities. Drunks can be keep to sober up, but only if they are badly harassing other crew members. Regular drunks don't get arrested and if they are only a nuisance you keep them for the regular time. The mutual degradation of chasing a naked man down while he screams rape is only worth it on slow rounds. Skrell are required to be clothed just like anyone else. Tajaran can have rolled down jumpsuits unless ordered by their Head of Staff to keep it up.
| 5 minutes.
| Up to 8 minutes and/or demotion.
| 250 credits
|-
| i106
| '''Suspicious Conduct'''
| To possess a suspiciously wide skill set not indicated in employee record, wielding dangerous weapons near other staff, extensive inquiring about critical areas, or stalking other employees. A search or arrest warrant is needed to apply this charge on code green.
| Basically, metagamey/powergamey behaviour. It's worth reporting to the Head of Personnel or your Head of Staff if you want to play a character who knows more than they should. You may also want to adminhelp if you feel the person is using metagamey or powergamey behavior.
| 2 minutes. Immediate search.
| Tracking implant.
| 200 credits. Immediate search.
|-
| i107
| '''Misuse of Public Radio Channels'''
| To continually broadcast unimportant, untrue, or insignificant messages on the public radio frequency.
| This is really only for people who are constantly spamming the radio, such as 'DJs' or Chaplains reading their services over the comms. Screaming fake messages like "halp security is beating me" when they aren't also counts.
| 3 minutes.
| Ban from using any radio equipment, which requires a filed injunction.
| 150 credits
|-
| i108
| '''Violation of Injunction'''
| To violate the terms of an injunction made by Security or other legal professions.
| Injunctions can be filed for lots of different things, such as a ban on weapons carrying, or the above radio ban. They can be applied by the Head of Security, Captain, or equivalent. If they break the law in some other way, apply that sentence too.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| N/A
|-
| i109
| '''Slandering a Head of Staff'''
| To directly insult a Head of Staff with no valid complaints.
| This is most likely to happen when someone is being fired. The charge is only applicable when the statements are slanderous and untrue.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| 250 credits
|-
| i110
| '''Slander or Verbal Abuse'''
| To spread false rumors in order to damage someone's reputation, or to use racially offensive language.
| Lying about anything to make someone else look bad, or making use of obscene or offensive slurs against someone else. For example, a drunk assistant starts shouting racial slurs at xeno crew. Since this has to be proven, it's up to the appropriate officer to determine. You should also see if the insults were real, rather than friendly banter between two friends.
| 3 minutes.
| 5 minutes.
| 50 credits per applicable minute
|-
| i111
| '''Failure to Execute an Order'''
| To ignore or disregard a superior's valid orders.
| If the order is stupid, or causes you to break a law (e.g. "Release the singularity!" or "Steal that RCD for me!") you can ignore it, and probably make a complaint. However, if it's perfectly doable, lawful, and in your job description, you better do it or resign. If not following an order caused severe damage or loss of life, see "Failure to Execute an Order with Serious Consequences".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| 500 credits
|-
| i112
| '''Sexual Harassment'''
| To make unwanted sexual advances or obscene remarks towards another employee.
| This is for VERY MINOR things the other person finds offensive that are sexually related. For anything more serious see "Sexual Assault".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| N/A
|-
| i113
| '''Animal Cruelty'''
| To inflict unnecessary suffering or harm upon animals with malicious intent.
| Monkeys appropriately used for experiments or well-being (e.g Genetics, Virology, etc.) don't count, neither do the animals ordered from cargo. Shoving them in washing machines, or throwing them down disposals while still alive falls under this. Using them as food is a grey area, as long as they are not overtly caused pain in the process.
| 5 minutes
| Up to 10 minutes and/or Demotion.
| N/A
|-
| i114
| '''Vandalism'''
| To deliberately damage or deface the station without malicious intent. To cause easily repairable damage to an owned IPC, up to and including disabling the chassis.
| This can range from disassembling furniture unnecessarily, to drawing on the floor with crayons or other substances outside the chapel.
| 3 minutes
| Up to 10 minutes in total and/or Demotion.
| 450 credits
|-
| i115
| '''Threat of Murder or Serious Injury'''
| To threaten to kill or seriously injure an employee.
| The threat has to somewhat tangible. If it's just people arguing over the radio, it's probably not worth it. Someone shouting at someone else while chasing them with a fire extinguisher is more valid.
| 3 minutes and mandatory Tracking implant.
| Up to 10 minutes with psychiatric evaluation.
| 500 credits. Tracking implant.
|-
| i116
| '''Disrespect to the Dead'''
| To abuse bodies of dead or previously dead employees.
| Examples include, the chef using bodies in the morgue as meat, Security beating on a prisoners corpse, or using someone's body for 'experimental surgery'. Preventing a body from being cloned or cyborged also falls under this. The Chaplain or medbay tended to corpses in preperation for autopsy or funeral does not fall under this unless they're doing something bizarre and unnecessary.
| 5 minutes
| 10 minutes per corpse.
| 400 credits
|-
| i117
| '''Excessive use of force in detainment'''
| To use more than the required force to subdue a suspect.
| Repeatedly batoning a prisoner after they've been handcuffed, Using force against an unarmed and compliant suspect, and usage of lethal weapons in a non-lethal situation.
| 5 minutes and/or demotion to cadet.
| 10 minutes and demotion.
| 350 credits.
|-
| i118
| '''Violation of privacy laws'''
| To intentionally leak private aspects of employee records or financial account information to unauthorized personnel.
| Janitors found reading records flushed down disposals would be charged with this as well. Command can discuss medical records with other command (or IAA and Detectives on request) if they have a good reason, and similar with employee and security records. Using a station announcement asking someone come pick up their hemorrhoid cream is also a no. The punishment goes to the source of the leak. Authorization for respective records goes to their respective heads of staff. (CMO, HoP, HoS, and the final say of Captain.
| Fine.
| Demotion and/or Suspension.
| 500 credits.
|-
| i119
| '''Illegal search'''
| To preform a search of an employee or workplace without a search warrant, clearance, or probable cause.
| An extension of the Privacy Laws, crew members are entitled to the privacy against searches on green alert. Security is required to obtain a search warrant from either the Head of Security, Captain, or lacking either, a Warden. Searches of workplaces falls under this. Security can circumvent a search warrant requirement if they: have clearance from the respective head of staff, have directly witnessed a crime taking place, or feel there is a real and imminent danger to the safety of crew and/or station. This also does not apply to searches conducted after another, legitimate arrest.
| A written apology. Return of non-contraband goods and reduced brig time for victim.
| Demotion and/or Suspension.
| 500 credits.
|}

=== Medium Level Infractions (Amber Violations; i200's) ===
{| width="950px" style="background-color:#ffcc99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffaa55;"|No.
!style="background-color:#ffaa55; width:150px"|Infraction
!style="background-color:#ffaa55; width:300px"|Description
!style="background-color:#ffaa55;"|Notes
!style="background-color:#ffaa55;"|Standard Sentance
!style="background-color:#ffaa55;"|Repeat Offense
|-
| i201
| '''Failure to Execute an Order with Serious Consequences'''
| To ignore or disregard a superior's valid orders, which then causes serious damage to property or life.
| Like the minor crime, except this one has caused serious damage to the station, or seriously injured someone. Examples are Medical Doctors ignoring the Chief Medical Officer while patients are piling up in medbay, or Engineers ignoring the Chief Engineer and then having the singularity eat part of the station. If this causes loss of life, refer to 302.
| 15 minutes and/or demotion
| Immediate suspension. Holding until transfer
|-
| i202
| '''Resisting Arrest and/or Sparking a Manhunt'''
| To not cooperate with an officer who attempts a proper arrest, or to cause a manhunt by hiding from security.
| '''Refusing handcuffs is not resisting arrest'''. Pushing the officer trying to arrest you, or running away falls under this.
| 5 minutes. If they sparked a manhunt and did not surrender themselves, tracking implant
| Up to 15 minutes in addition to regular time
|-
| i203
| '''Suicide Attempt'''
| To attempt or threaten to commit suicide.
| An employee trying or threatening to kill himself for any reason. This includes someone saying "AI OPEN THIS DOOR OR I KILL MYSELF".
| Compulsory psychiatric examination and tracking implant
| Demotion and isolation in solitary
|-
| i204
| '''Abuse of Confiscated Equipment'''
| To take and use equipment confiscated as evidence.
| Security shouldn't be using evidence for anything but evidence. Taking "trophies" or using weapons and items seized from operatives counts as this.
| 10 minutes, re-confiscation of equipment
| Suspension or demotion
|-
| i205
| '''Illegal Detention, Arrest, or Holding'''
| To arrest, brig, or punish an employee without proper cause or reason.
| This is mainly for Security Officers who believe THEY ARE THE LAW.
| 10 minutes and/or demotion to cadet
| 15 minutes and immediate suspension
|-
| i206
| '''Neglect of Duty'''
| To fail to perform a job to a satisfactory standard.
| This can be due to honest or dishonest mistakes that the Head of the Department feels hampers Department productivity. Examples include scientists/engineers releasing phoron or causing a breach, doctors mixing up medicines that cause injury to patients, or the Warden not doing his job. Additionally, a member of Command may only be charged with Neglect of Duty with the agreement of the Captain, or through a Captain level decision passed by the Command Staff.
| 10 minutes
| 15 minutes and/or demotion
|-
| i207
| '''Infiltration'''
| To attempt to, or successfully, enter a high-security area without authorization.
| This includes the Bridge, AI upload or core, Teleporter, vault, or EVA. Using AI or Cyborg help for infiltration purposes is also considered breaking and entering.
| 15 minutes and tracking implant
| Holding until transfer and/or demotion
|-
| i208
| '''Assault'''
| To cause severe injury to another employee. To cause irreparable damage to the chassis of a free IPC.
| Anything beyond a few punches like in "Minor Assault". Also see "Attempted Murder" if the intent was to kill. This also includes poisoning with drugs, or using hallucinogens.
| 15 minutes and/or demotion
| Up to 30 minutes and suspension
|-
| i209
| '''Escaping From Confinement'''
| To escape from confinement as someone who is serving a non-permanent sentence.
| See "Escaping From a Permanent Sentence" for those who do it with permanent sentences.
| 10 minutes added and tracking implant. The original time is not reset
| Up to 30 minutes and demotion
|-
| i210
| '''Unlawful Modification of AI/Cyborg Laws'''
| To modify the laws of a cyborg or artificial intelligence, without need, proper access, or authority.
| An exception would be a law reset when obviously harmful laws have been uploaded. Only the Captain, Chief Engineer, Research Director, or Two other Heads of Staff can authorize a law change.
| 20 minutes and tracking implant
| Demotion. Holding until transfer
|-
| i211
| '''Sedition'''
| To incite rebellion, or rally against the established chain of command.
| This includes attempting to make separate areas of the ship into "Nations", arresting a head of staff without cause, or generally conspiring against the chain of command.
| 15 minutes and/or demotion
| Suspension and holding until transfer
|-
| i212
| '''Contraband'''
| To possess, use, or distribute contraband items, including drugs.
| Chemists and Botanists are allowed to possess drugs for their line of work. It's a crime if they distribute the drugs. Also see Identifying Syndicate Items for a list of who knows what. Contraband from the Supply Shuttle also counts. This also includes firearms, such as the barman taking their shotgun outside the bar area, or illegal modification of such firearms. Snacks from hacked vending machines are not this. (List of [[Guide to Contraband|Contraband]])
| 15 minutes and confiscation of said items
| 20 minutes and demotion
|-
| i213
| '''Sabotage'''
| To hinder the efforts of the crew or station with malicious intent. To cause irreparable damage to the chassis or positronic brain of an owned IPC.
| This includes causing hull breaches, sabotaging air supplies, stealing vital equipment, etc. The intent is the most important bit here.
| 15 minutes and/or demotion
| 30 minutes, suspension and/or tracking implant
|-
| i214
| '''Exceeding Official Powers'''
| To act beyond what is allowed by the Chain of Command.
| This is for any head of staff who abuses the power given to them, such as the Head of Personnel acting like a security officer in a non-emergency, the captain acting as if he is above the law, etc. Heads of Staff trying to order a different department or ignoring the captain also comes under this. Also covers anyone illegally promoting themselves, such as with a stolen ID.
| 15 minutes and/or demotion. Head demotions require Captain or majority Command approval
| 20 minutes and suspension
|-
| i215
| '''Grand Theft'''
| To steal items that are dangerous, of a high value, or a sensitive nature. Applicable to the theft of an owned IPC.
| This means weapons, explosives or ammunition, and also includes items from the [[Guide to Contraband|High-risk Items]] page. Security Officers stealing things from the armory is an example.
| 15 minutes, confiscation of stolen items
| Suspension, tracking implant and holding until Transfer
|-
| i216
| '''Organising a Breakout'''
| To attempt, or succeed, in freeing criminals from the brig or other holding areas.
| Breaking brig windows
| 15 minutes and tracking implant
| 30 minutes
|-
| i217
| '''Illegal Blocking of Areas'''
| To make an area inaccessible for those with appropriate access.
| Bolting doors in public hallways or to those of departments you don't have control over are examples of this.
| 10 minutes
| Up to 25 minutes and/or demotion
|-
| i218
| '''Use of Excessive Force'''
| To put a victim in critical state in defense of yourself or others, or seriously injuring a suspect while attempting to detain them. This includes pulling them when they have open wounds.
| Severely injuring someone attacking you or others with no obvious threat to life, or panicking and shooting a suspect to near-death.
| 10 minutes and/or demotion to cadet
| 25 minutes and suspension
|-
| i219
| '''Mistreatment of Prisoners'''
| To intentionally act, or cause an act that puts a non-hostile prisoner's well-being in danger.
| Preventing proper treatment from being given to a prisoner, abusing a prisoner, and preventing them from having access to a viable method of communication. This includes pulling them when they have open wounds counts as abuse. In the event that a prisoner dies because of mistreatment, the charge is immediately upgraded to either murder or manslaughter.
| 10 minutes and/or demotion to cadet
| 25 minute and suspension
|-
| i220
| '''Fraud'''
| To steal or use deliberate deception in order to obtain credits from someone. Applies to amounts greater than 500 credits.
For lesser amounts, see i102 - Petty Theft.

For items of equivalent value, see i215 - Grand Theft.
| Emptying a station account for personal gain. Tricking someone into entrusting large amounts of money to another under false pretenses.
| 15 minutes and/or demotion
| 30 minutes and immediate suspension
|-
| i221
| '''Gross Negligence'''
| To display a severe lack of diligence or disregard for safe conduct, which causes or will cause serious harm to people or property.

For instances of negligence that are not seriously and imminently harmful, see i206 Neglect of Duty.
| For this charge to apply, the threat of harm must be both significant and obvious. A chemist accidentally releasing phoron gas into the station, security practicing with weapons while people are downrange, or a xenobiologist who lets slimes escape without malicious intent are eligible examples. When possible, defer to Command and the existing Neglect of Duty charge. This is more useful when the negligent crew member is acting unsupervised.
| 15 minutes
| 20 minutes and/or demotion
|-
| i222
| '''Unregistered Positronic Machine'''
| To function as an untagged positronic machine within the Republic of Biesel, or to function as a positronic machine with a tag that has been tampered with or rendered inoperable.
| [[IPC|IPCs]] are required by Republic law to be electronically tagged. This tag is typically visible to an onlooker.

Those who assist affected synthetics in tampering with or removing their tags are considered to be aiding and abetting them in this violation, and are themselves liable for heavy fines or brig time where applicable. These accomplices do not need to be retagged (if synthetic) or implanted.
| 10 minutes, immediate retagging, tracking implant, 1000 credit fine.
| 30 minutes, immediate retagging, 5000 credit fine.
|-
| i223
| '''Kidnapping of Free Intelligence'''
| To take away or transport a free positronic intelligence against its will.
| If the positronic intelligence is held for ransom or exchange, there is no difference in sentence.
| 15 Minutes
| Up to 25 Minutes
|}

=== High Severity Infractions (Red Violations; i300's) ===
==== Regarding cyborgification ====

*'''The NSS Aurora is in Tau Ceti space, which does not consider cyborgification capital punishment, making it an optional punishment.'''

{| width="950px" style="background-color:#ffaa99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ff8855;"|No.
!style="background-color:#ff8855; width:150px"|Crime
!style="background-color:#ff8855; width:300px"|Description
!style="background-color:#ff8855;"|Notes
!style="background-color:#ff8855;"|Sentence
|-
| i301
| '''Murder'''
| To kill someone, or attempt to kill someone, with premeditated malicious intent.
| Also cover Attempted Murder. The premeditated and malicious bit is important here.
| Cyorgification or Holding Until Transfer on majority Command decision.
|-
| i302
| '''Manslaughter'''
| To kill someone without malice or forethought.
| This includes causing death due to negligence or dereliction of duty. Can also be used for excessive self-defense.
| 20 minutes and/or demotion. Tracking implant.
|-
| i303
| '''Mutiny'''
| To openly rebel against or attempt to remove command staff with violent intent.
| See "Sedition" for less violent mutineers. This generally means they use harm-intent or try to kill their superiors or advocate the same.
| Loyalty implant or cyborgification on majority Command decision.
|-
| i304
| '''Kidnapping and Hostage taking'''
| To take away or transport a victim against the victim's will.
| If the person is held for ransom or exchange, then it is considered hostage taking, which is automatically a holding until transfer.'''
| Hold until transfer.
|-
| i305
| '''Terrorist Acts'''
| To engage in maliciously destructive actions, which seriously threaten the crew or station.
| This includes deliberate arson, use of bombs, release of singularity, etc. Collateral damage or severe station damage has to be involved. For less disastrous actions, see sabotage.
| Hold until transfer or cyborgification on majority command decision.
|-
| i306
| '''Assaulting a Head of Staff'''
| To assault a Head of Staff, causing severe damage.
| Exactly like "Assault", but this time against a Head of Staff.
| 20 minutes and/or demotion.
| 40 minutes, suspension, and tracking implant.
|-
| i307
| '''Escaping From Holding Until Transfer'''
| To escape, or attempt to escape, from the brig or other holding area when being held until transfer.
| They have to have been properly convicted for it to be a life sentence.
| Cyborgification or hold until transfer at majority command decision.
|-
| i308
| '''Corporate Espionage'''
| To act as an agent of a terrorist or anti-Corporation group.
| Espionage, disclosure of corporate secrets, or any other assistance rendered to outside hostile organisations, or their representatives in hostile activities to the Corporation, committed by a employee of Corporation.
| Holding until transfer or cyborgification at majority command decision.
|-
| i309
| '''Sexual Assault'''
| To assault, or attempt to assault, someone else sexually, including rape.
| ERP scenes, or erotic roleplay, is a permabannable offence. Adminhelp it if this happens to you; it's against server rules, not just station rules.
| 30 minutes, tracking implant.
| Holding until transfer.
|-
| i310
| '''Automacide'''
| To willfully, unlawfully and permanently terminate a free positronic intelligence.
| Essentially the murder charge for free IPCs. Premeditation and malicious intent are still important here.
| 20 minutes, demotion
| Holding until transfer.
|}

=== Modifiers & Special Situations ===

{| width='825px' style='text-align:center; background-color:#aaffaa;' border=1 cellspacing=0
! style='background-color:#55ff55;' width='150px'|Situation
! style='background-color:#55ff55;' width='300px'|Description
! style='background-color:#55ff55;' width='100px'|Benefit
|-
|'''Surrender'''
| Coming to the brig, confessing what you've done and taking the punishment. Getting arrested without putting a fuss is not surrender. For this, you have to actually come to the brig yourself.
| Up to -25%, and should be taken into account when determining the severity of crimes.
|-
|'''Re-education'''
| Getting de-converted from revolutionary.
| Up to and including immediate release
|-
|'''Cooperation with prosecution or security'''
| Being helpful to the members of security, revealing things during questioning or providing names of head revolutionaries.
| Up to -25%. In the case of revealing a head revolutionary, up to -50%.
|-
|'''Immediate threat to the prisoner'''
| The singularity eats something near the brig, an explosion goes off, etc.
| Officer must relocate the prisoner(s) to a safe location. Otherwise, immediate release. Life sentences must be reapplied after danger has passed.
|-
|'''Medical reasons'''
| Prisoners are entitled to medical attention if sick or injured.
| Medical personnel can be called, or the prisoner can be escorted to the Medbay. The timer continues to run during this time.
|-
|'''Self Defence'''
| Assault and even homicide can be justified if it was necessary for prevention of loss of life. (Note that there are borders of acceptable self-defence, and killing a man who just punched you is subject to "Use of Excessive Force")
| Up to and including immediate release.
|}

==== Parole ====

Parole is temporarily releasing a prisoner before their sentence has been fully completed on the promise of good behavior. Parole can be given for any number of reasons, including brig overcrowding, a reward for good behavior or confession, or if the prisoner's skills are in need by the station such as a doctor or engineer.

The Warden or Head of Security can choose to give prisoners parole. A tracking implant is recommended if the prisoner is a flight risk (IE an engineer going EVA, but it is up to the Warden/HoS to determine how much of a risk they are.) Tracking implants for minor crimes are not worth it.

On the completion of their time they are simply marked as released as normal.

If they commit any crimes their parole is ended and they must serve out the remainder of their time in the brig with the new crime's time added on.

Parole can be given immediately after initial processing; theoretically a prisoner can spend their entire sentence out of the brig.

=== Terminology and Clarifications ===
'''Cyborgification''' The removal of a person's brain for transplanting into a Cyborg Chassis. Often also known as Shackling.

'''Suspension''': Changing ID title to "suspended", zero access.

'''Demotion''': Can be done up to and including Assistant position, by Head of Personnel or Captain's decision.

'''Employee''': Employee of NanoTrasen, as defined by the station's commanding officer. All non-employee subjects are still protected by these laws.

'''Empowering''': Illegal acquiring (not via Head of Personnel or Captain) of access.

'''Head of Staff''': Crew members occupying one of the following positions: Captain, Chief Engineer, Head of Personnel, Head of Security, Chief Medical Officer, Research Director.

'''HuT''' Holding until Transfer

'''Lethal Situation''': A situation in which there is an apparent and real threat the the well-being of all those involved.

'''Repeat Offenders''': For repeat offenders, use the "repeat offense" punishment.

'''Severe Injury''': A state in which the victim is in a critical condition and is having difficulty maintaining consciousness.

Demotion and dismissal also require the removal of equipment from the previous job. E.g: Uniforms, weapons, bombs, PDA cartridges, etc.

For the purposes of Cyborg/AI laws, crewmembers that have been convicted, or are being held in detention, are considered to be below even the AI/Cyborgs in terms of rank.

In cases where the final sentence is more than 90 minutes, it is changed to HuT

The standard penalty can be applied without a tribunal by Security Officers.

{{Security}}
{{Command}}
{{Gameplay Guides}}
[[Category:Guides]]
[[Category:Pages]]
[[Category:Security]]
[[Category:Command]]

Corporate Regulations

2019-05-04T09:02:44Z

Mofo1995: /* Low Level Infractions (Yellow Violations; i100's) */ Changed i110 from Slander to Slander or Verbal Abuse.

{{Reference}}
{{IC_Laws}}

= Corporate Regulations =

Corporate Regulations are penned regulations that all Nanotrasen employees have agreed to abide by in the signing of their employment contract. These regulations apply across the board on any Nanotrasen owned property, be it station, ship, or outpost.

Onboard each facility there will be a dedicated Security department in charge of making sure that all Nanotrasen employees follow these regulations.

*'''Regulations protecting prisoners from mistreatment applies to even non-crew.'''

*'''Executions are illegal and not allowed by regulations.''' Station security nor command should be doing any executions. The maximum possible penalty for major infractions is cyborgification.

*'''The brig timer of a prisoner begins after processing.''' All prisoner processing is expected to be completed in a timely manner. Should a detainee's processing take an unreasonably long time, the personnel responsible for that processing may be liable for illegal detention.

=== Interpretation of the Regulations ===

Every person on the station should have a good knowledge of Corporate Regulations. Following them could mean the difference between having a peaceful day or paying 1000 credits for multiple infractions. Extensive knowledge of Corporate Regulations is required for such positions as the Warden, Head of Personnel, Captain, and the Head of Security.

For all incidents, the '''suspect's intent''' is very important. Some incidents are mutually exclusive.

A single incident has a single sentence, so if, for instance, the prisoner took 3 items off someone, this is a single count of pickpocketing.

Aiding and abetting a criminal makes you an accomplice; '''you can be charged with the same crime as the person you aided and abetted.'''

The charges “Battery”, “Attempted murder” and “Murder” do not apply to crimes committed against [[IPC|IPCs]], whether they are free intelligences or owned by a person or company. Consult employment/security records to determine whether an IPC is owned or not.

Positronic intelligences are not protected by capital punishment laws. Those charged with red level infractions may be at risk of being dismantled or destroyed.

=== Additional ===

==== Captains and Authority ====

Captains are not above Corporate Regulations and can be arrested by Security for breaking them. However, this should only happen if active Heads of Staff agree in a unanimous decision to approve the arrest, or the arrest is ordered by Central Command. '''Captains should not be removed from their position in this way for anything but violations that would normally require holding until transfer.''' Lesser violations can and should be reported to Central Command, but are not generally severe enough to warrant this drastic action. If a Captain is arrested in this manner, an Acting Captain should be appointed immediately, and Central Command should be informed.

The station's assigned Captain has full and final authority over the operation of the station. They are authorized to issue direct orders to entire departments or specific crew members. They may take any actions or issue orders that violate regulations during non-standard situations. Generally, these orders must be carried out. Even if you feel an order from the Captain to be against regulation, your moral code, or generally detestable, you still have to follow it. You are entitled to begin a vote within Command (if you're part of Command) to have the Captain arrested if the order breaks a serious regulation, or fax Central Command (if you have access to a fax machine) to have them weigh in, but disobeying the order (if given to you) or obstructing it (if not given to you directly) is Failure to Execute an Order. This is upgraded to Sedition if you start encouraging others to refuse the Captain's orders.

If a crew member breaks regulations while following a direct order from the Captain, when there are other legal ways to carry it out, that crew member is generally considered at fault for the violation.

Pardons are only legitimate if they come from Central Command. Not even the Captain can deliver pardons, but they can grant parole with or without a tracking implant.

==== Injunctions ====

The Captain, Head of Security, and Internal Affairs Agents may issue injunctions to the crew if deemed necessary.

An injunction is a restriction on a crew member, meant to prohibit disruptive behavior that may not otherwise explicitly break regulations. Violating the terms of these injunctions '''is''' breaking regulations however, covered by '''i108 Violation of Injunction''' below. Examples of valid uses of injunctions include things like preventing two belligerent crew members from interacting with one another, or stopping someone from abusing alcohol at the bar. They are not meant to circumvent the chain of command, however, and efforts to resolve problems within that structure should be made first.

The Head of Security and Internal Affairs Agents may issue injunctions to any non-Command member of the crew. The Captain's orders may override these injunctions.

Only the Captain, Central Command itself, or every other member of Command acting as the Captain in a unanimous decision, may issue injunctions to a member of Command Staff.

==== Misc ====

Do '''NOT''' demand a tribunal for anything. You'll just be laughed at.

A '''Warrant''' must be provided for almost any search or arrest conducted under code green. Exceptions to this rule exist if an officer is a direct witness to a crime, or may reasonably conclude that failure to act will pose an immediate danger to the crew and/or station. Search warrants may also be circumvented if the Head of Staff over the employee being searched has given their direct consent.

'''Suspensions''' are used to temporarily suspend an employee from active duty, restricting them from holding any station rank. They are typically used in situations where an employee can no longer be trusted to continue their work.

'''Demotions''' are used to temporarily demote an employee to a rank below their previous occupation, allowing them to continue active duty under a position of less authority. They are typically reserved for situations in which the employee is still trusted to continue work, but may require additional training or oversight.

'''Drugs''' such as alcohol, tobacco, Ambrosia Deus, Ambrosia Vulgaris, etcetera are not covered by the '''Contraband''' regulation as these are legal under Tau Ceti law.

=== Low Level Infractions (Yellow Violations; i100's) ===
==== Regarding warnings ====

Officers are allowed to give out official warnings for first-time low level infractions. Any repeat offenders are to be sentenced.

Officers are not obligated to first issue out an official warning, but are encouraged to do so if the situation allows it.

{| width="950px" style="background-color:#ffee99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffee55;"|No.
!style="background-color:#ffee55; width:150px"|Incident
!style="background-color:#ffee55; width:300px"|Description
!style="background-color:#ffee55;"|Notes
!style="background-color:#ffee55;"|Traditional Sentence
!style="background-color:#ffee55;"|Repeat Offense
!style="background-color:#ffee55;"|Fine
|-
| i101
| '''Trespassing'''
| To be in an area which a person does not have access to.
| Remember that people can either break in, sneak in, or be let in. Always check that the suspect wasn't let in to do a job by someone with access, or were given access on their ID. Trespassing and theft often committed together; both sentences should be applied. Severity is increased if they refuse to leave the area peacefully, more so if they attempt to use important equipment there, so feel free to add other charges if they do.
| 3 minutes.
| Up to 10 minutes and/or demotion.
| 200 credits
|-
| i102
| '''Petty Theft'''
| To take items from areas one does not have access to, or to take items belonging to others or the station as a whole. Includes theft of credits up to 500cr. For higher amounts see i220 - Fraud
| Keeping items which are in short supply where they belong is what is important here. A doctor who takes all the surgical tools and hides them still commits theft, even though he had access. Items can include anything from toolboxes to metal to insulated gloves. Remember to take the items away from them and return them to where they stole them.
| 3 minutes, returning of stolen item to the owner or department.
| Up to 10 minutes and/or demotion.
| 150 credits
|-
| i103
| '''Minor Assault'''
| To use, or threaten, physical force against someone, without intent to kill or seriously injure. To cause easily repairable damage to a free IPC chassis, up to and including the removal of limbs.
| If it causes minor damage and easily treatable damage, it's minor assault. Starting fights with other employees or punching fellow employees counts too, as well as seriously threatening them with it. Force-feeding someone is this unless it's poisonous or knocks them unconscious.
| 4 minutes.
| Up to 10 minutes and/or demotion.
| 400 credits
|-
| i104
| '''Battery'''
| To have unwanted physical contact with someone, even where the contact is not violent.
| Bumping into someone in a corridor doesn't really count. Touching someone, when they have explicitly told you not to, does.
| 2 minutes.
| Up to 8 minutes and/or demotion.
| 200 credits
|-
| i105
| '''Indecent Exposure or Hooliganism'''
| To be intentionally and publicly unclothed, yelling at people for no reason in public or on comms, throwing around stuff where it could hit someone, yelling about how terrible NanoTrasen is, etc.
| Running around the station naked or in underwear, or other such degrading activities. Drunks can be keep to sober up, but only if they are badly harassing other crew members. Regular drunks don't get arrested and if they are only a nuisance you keep them for the regular time. The mutual degradation of chasing a naked man down while he screams rape is only worth it on slow rounds. Skrell are required to be clothed just like anyone else. Tajaran can have rolled down jumpsuits unless ordered by their Head of Staff to keep it up.
| 5 minutes.
| Up to 8 minutes and/or demotion.
| 250 credits
|-
| i106
| '''Suspicious Conduct'''
| To possess a suspiciously wide skill set not indicated in employee record, wielding dangerous weapons near other staff, extensive inquiring about critical areas, or stalking other employees. A search or arrest warrant is needed to apply this charge on code green.
| Basically, metagamey/powergamey behaviour. It's worth reporting to the Head of Personnel or your Head of Staff if you want to play a character who knows more than they should. You may also want to adminhelp if you feel the person is using metagamey or powergamey behavior.
| 2 minutes. Immediate search.
| Tracking implant.
| 200 credits. Immediate search.
|-
| i107
| '''Misuse of Public Radio Channels'''
| To continually broadcast unimportant, untrue, or insignificant messages on the public radio frequency.
| This is really only for people who are constantly spamming the radio, such as 'DJs' or Chaplains reading their services over the comms. Screaming fake messages like "halp security is beating me" when they aren't also counts.
| 3 minutes.
| Ban from using any radio equipment, which requires a filed injunction.
| 150 credits
|-
| i108
| '''Violation of Injunction'''
| To violate the terms of an injunction made by Security or other legal professions.
| Injunctions can be filed for lots of different things, such as a ban on weapons carrying, or the above radio ban. They can be applied by the Head of Security, Captain, or equivalent. If they break the law in some other way, apply that sentence too.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| N/A
|-
| i109
| '''Slandering a Head of Staff'''
| To directly insult a Head of Staff with no valid complaints.
| This is most likely to happen when someone is being fired. The charge is only applicable when the statements are slanderous and untrue.
| 5 minutes.
| Up to 10 minutes and/or demotion.
| 250 credits
|-
| i110
| '''Slander or Verbal Abuse'''
| To spread false rumors in order to damage someone's reputation, or to use highly offensive language.
| Lying about anything to make someone else look bad, or making use of obscene or offensive slurs against someone else. For example, a drunk assistant starts shouting racial slurs at xeno crew. Since this has to be proven, it's up to the appropriate officer to determine. You should also see if the insults were real, rather than friendly banter between two friends.
| 3 minutes.
| 5 minutes.
| 50 credits per applicable minute
|-
| i111
| '''Failure to Execute an Order'''
| To ignore or disregard a superior's valid orders.
| If the order is stupid, or causes you to break a law (e.g. "Release the singularity!" or "Steal that RCD for me!") you can ignore it, and probably make a complaint. However, if it's perfectly doable, lawful, and in your job description, you better do it or resign. If not following an order caused severe damage or loss of life, see "Failure to Execute an Order with Serious Consequences".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| 500 credits
|-
| i112
| '''Sexual Harassment'''
| To make unwanted sexual advances or obscene remarks towards another employee.
| This is for VERY MINOR things the other person finds offensive that are sexually related. For anything more serious see "Sexual Assault".
| 5 minutes.
| Up to 15 minutes and/or Demotion.
| N/A
|-
| i113
| '''Animal Cruelty'''
| To inflict unnecessary suffering or harm upon animals with malicious intent.
| Monkeys appropriately used for experiments or well-being (e.g Genetics, Virology, etc.) don't count, neither do the animals ordered from cargo. Shoving them in washing machines, or throwing them down disposals while still alive falls under this. Using them as food is a grey area, as long as they are not overtly caused pain in the process.
| 5 minutes
| Up to 10 minutes and/or Demotion.
| N/A
|-
| i114
| '''Vandalism'''
| To deliberately damage or deface the station without malicious intent. To cause easily repairable damage to an owned IPC, up to and including disabling the chassis.
| This can range from disassembling furniture unnecessarily, to drawing on the floor with crayons or other substances outside the chapel.
| 3 minutes
| Up to 10 minutes in total and/or Demotion.
| 450 credits
|-
| i115
| '''Threat of Murder or Serious Injury'''
| To threaten to kill or seriously injure an employee.
| The threat has to somewhat tangible. If it's just people arguing over the radio, it's probably not worth it. Someone shouting at someone else while chasing them with a fire extinguisher is more valid.
| 3 minutes and mandatory Tracking implant.
| Up to 10 minutes with psychiatric evaluation.
| 500 credits. Tracking implant.
|-
| i116
| '''Disrespect to the Dead'''
| To abuse bodies of dead or previously dead employees.
| Examples include, the chef using bodies in the morgue as meat, Security beating on a prisoners corpse, or using someone's body for 'experimental surgery'. Preventing a body from being cloned or cyborged also falls under this. The Chaplain or medbay tended to corpses in preperation for autopsy or funeral does not fall under this unless they're doing something bizarre and unnecessary.
| 5 minutes
| 10 minutes per corpse.
| 400 credits
|-
| i117
| '''Excessive use of force in detainment'''
| To use more than the required force to subdue a suspect.
| Repeatedly batoning a prisoner after they've been handcuffed, Using force against an unarmed and compliant suspect, and usage of lethal weapons in a non-lethal situation.
| 5 minutes and/or demotion to cadet.
| 10 minutes and demotion.
| 350 credits.
|-
| i118
| '''Violation of privacy laws'''
| To intentionally leak private aspects of employee records or financial account information to unauthorized personnel.
| Janitors found reading records flushed down disposals would be charged with this as well. Command can discuss medical records with other command (or IAA and Detectives on request) if they have a good reason, and similar with employee and security records. Using a station announcement asking someone come pick up their hemorrhoid cream is also a no. The punishment goes to the source of the leak. Authorization for respective records goes to their respective heads of staff. (CMO, HoP, HoS, and the final say of Captain.
| Fine.
| Demotion and/or Suspension.
| 500 credits.
|-
| i119
| '''Illegal search'''
| To preform a search of an employee or workplace without a search warrant, clearance, or probable cause.
| An extension of the Privacy Laws, crew members are entitled to the privacy against searches on green alert. Security is required to obtain a search warrant from either the Head of Security, Captain, or lacking either, a Warden. Searches of workplaces falls under this. Security can circumvent a search warrant requirement if they: have clearance from the respective head of staff, have directly witnessed a crime taking place, or feel there is a real and imminent danger to the safety of crew and/or station. This also does not apply to searches conducted after another, legitimate arrest.
| A written apology. Return of non-contraband goods and reduced brig time for victim.
| Demotion and/or Suspension.
| 500 credits.
|}

=== Medium Level Infractions (Amber Violations; i200's) ===
{| width="950px" style="background-color:#ffcc99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ffaa55;"|No.
!style="background-color:#ffaa55; width:150px"|Infraction
!style="background-color:#ffaa55; width:300px"|Description
!style="background-color:#ffaa55;"|Notes
!style="background-color:#ffaa55;"|Standard Sentance
!style="background-color:#ffaa55;"|Repeat Offense
|-
| i201
| '''Failure to Execute an Order with Serious Consequences'''
| To ignore or disregard a superior's valid orders, which then causes serious damage to property or life.
| Like the minor crime, except this one has caused serious damage to the station, or seriously injured someone. Examples are Medical Doctors ignoring the Chief Medical Officer while patients are piling up in medbay, or Engineers ignoring the Chief Engineer and then having the singularity eat part of the station. If this causes loss of life, refer to 302.
| 15 minutes and/or demotion
| Immediate suspension. Holding until transfer
|-
| i202
| '''Resisting Arrest and/or Sparking a Manhunt'''
| To not cooperate with an officer who attempts a proper arrest, or to cause a manhunt by hiding from security.
| '''Refusing handcuffs is not resisting arrest'''. Pushing the officer trying to arrest you, or running away falls under this.
| 5 minutes. If they sparked a manhunt and did not surrender themselves, tracking implant
| Up to 15 minutes in addition to regular time
|-
| i203
| '''Suicide Attempt'''
| To attempt or threaten to commit suicide.
| An employee trying or threatening to kill himself for any reason. This includes someone saying "AI OPEN THIS DOOR OR I KILL MYSELF".
| Compulsory psychiatric examination and tracking implant
| Demotion and isolation in solitary
|-
| i204
| '''Abuse of Confiscated Equipment'''
| To take and use equipment confiscated as evidence.
| Security shouldn't be using evidence for anything but evidence. Taking "trophies" or using weapons and items seized from operatives counts as this.
| 10 minutes, re-confiscation of equipment
| Suspension or demotion
|-
| i205
| '''Illegal Detention, Arrest, or Holding'''
| To arrest, brig, or punish an employee without proper cause or reason.
| This is mainly for Security Officers who believe THEY ARE THE LAW.
| 10 minutes and/or demotion to cadet
| 15 minutes and immediate suspension
|-
| i206
| '''Neglect of Duty'''
| To fail to perform a job to a satisfactory standard.
| This can be due to honest or dishonest mistakes that the Head of the Department feels hampers Department productivity. Examples include scientists/engineers releasing phoron or causing a breach, doctors mixing up medicines that cause injury to patients, or the Warden not doing his job. Additionally, a member of Command may only be charged with Neglect of Duty with the agreement of the Captain, or through a Captain level decision passed by the Command Staff.
| 10 minutes
| 15 minutes and/or demotion
|-
| i207
| '''Infiltration'''
| To attempt to, or successfully, enter a high-security area without authorization.
| This includes the Bridge, AI upload or core, Teleporter, vault, or EVA. Using AI or Cyborg help for infiltration purposes is also considered breaking and entering.
| 15 minutes and tracking implant
| Holding until transfer and/or demotion
|-
| i208
| '''Assault'''
| To cause severe injury to another employee. To cause irreparable damage to the chassis of a free IPC.
| Anything beyond a few punches like in "Minor Assault". Also see "Attempted Murder" if the intent was to kill. This also includes poisoning with drugs, or using hallucinogens.
| 15 minutes and/or demotion
| Up to 30 minutes and suspension
|-
| i209
| '''Escaping From Confinement'''
| To escape from confinement as someone who is serving a non-permanent sentence.
| See "Escaping From a Permanent Sentence" for those who do it with permanent sentences.
| 10 minutes added and tracking implant. The original time is not reset
| Up to 30 minutes and demotion
|-
| i210
| '''Unlawful Modification of AI/Cyborg Laws'''
| To modify the laws of a cyborg or artificial intelligence, without need, proper access, or authority.
| An exception would be a law reset when obviously harmful laws have been uploaded. Only the Captain, Chief Engineer, Research Director, or Two other Heads of Staff can authorize a law change.
| 20 minutes and tracking implant
| Demotion. Holding until transfer
|-
| i211
| '''Sedition'''
| To incite rebellion, or rally against the established chain of command.
| This includes attempting to make separate areas of the ship into "Nations", arresting a head of staff without cause, or generally conspiring against the chain of command.
| 15 minutes and/or demotion
| Suspension and holding until transfer
|-
| i212
| '''Contraband'''
| To possess, use, or distribute contraband items, including drugs.
| Chemists and Botanists are allowed to possess drugs for their line of work. It's a crime if they distribute the drugs. Also see Identifying Syndicate Items for a list of who knows what. Contraband from the Supply Shuttle also counts. This also includes firearms, such as the barman taking their shotgun outside the bar area, or illegal modification of such firearms. Snacks from hacked vending machines are not this. (List of [[Guide to Contraband|Contraband]])
| 15 minutes and confiscation of said items
| 20 minutes and demotion
|-
| i213
| '''Sabotage'''
| To hinder the efforts of the crew or station with malicious intent. To cause irreparable damage to the chassis or positronic brain of an owned IPC.
| This includes causing hull breaches, sabotaging air supplies, stealing vital equipment, etc. The intent is the most important bit here.
| 15 minutes and/or demotion
| 30 minutes, suspension and/or tracking implant
|-
| i214
| '''Exceeding Official Powers'''
| To act beyond what is allowed by the Chain of Command.
| This is for any head of staff who abuses the power given to them, such as the Head of Personnel acting like a security officer in a non-emergency, the captain acting as if he is above the law, etc. Heads of Staff trying to order a different department or ignoring the captain also comes under this. Also covers anyone illegally promoting themselves, such as with a stolen ID.
| 15 minutes and/or demotion. Head demotions require Captain or majority Command approval
| 20 minutes and suspension
|-
| i215
| '''Grand Theft'''
| To steal items that are dangerous, of a high value, or a sensitive nature. Applicable to the theft of an owned IPC.
| This means weapons, explosives or ammunition, and also includes items from the [[Guide to Contraband|High-risk Items]] page. Security Officers stealing things from the armory is an example.
| 15 minutes, confiscation of stolen items
| Suspension, tracking implant and holding until Transfer
|-
| i216
| '''Organising a Breakout'''
| To attempt, or succeed, in freeing criminals from the brig or other holding areas.
| Breaking brig windows
| 15 minutes and tracking implant
| 30 minutes
|-
| i217
| '''Illegal Blocking of Areas'''
| To make an area inaccessible for those with appropriate access.
| Bolting doors in public hallways or to those of departments you don't have control over are examples of this.
| 10 minutes
| Up to 25 minutes and/or demotion
|-
| i218
| '''Use of Excessive Force'''
| To put a victim in critical state in defense of yourself or others, or seriously injuring a suspect while attempting to detain them. This includes pulling them when they have open wounds.
| Severely injuring someone attacking you or others with no obvious threat to life, or panicking and shooting a suspect to near-death.
| 10 minutes and/or demotion to cadet
| 25 minutes and suspension
|-
| i219
| '''Mistreatment of Prisoners'''
| To intentionally act, or cause an act that puts a non-hostile prisoner's well-being in danger.
| Preventing proper treatment from being given to a prisoner, abusing a prisoner, and preventing them from having access to a viable method of communication. This includes pulling them when they have open wounds counts as abuse. In the event that a prisoner dies because of mistreatment, the charge is immediately upgraded to either murder or manslaughter.
| 10 minutes and/or demotion to cadet
| 25 minute and suspension
|-
| i220
| '''Fraud'''
| To steal or use deliberate deception in order to obtain credits from someone. Applies to amounts greater than 500 credits.
For lesser amounts, see i102 - Petty Theft.

For items of equivalent value, see i215 - Grand Theft.
| Emptying a station account for personal gain. Tricking someone into entrusting large amounts of money to another under false pretenses.
| 15 minutes and/or demotion
| 30 minutes and immediate suspension
|-
| i221
| '''Gross Negligence'''
| To display a severe lack of diligence or disregard for safe conduct, which causes or will cause serious harm to people or property.

For instances of negligence that are not seriously and imminently harmful, see i206 Neglect of Duty.
| For this charge to apply, the threat of harm must be both significant and obvious. A chemist accidentally releasing phoron gas into the station, security practicing with weapons while people are downrange, or a xenobiologist who lets slimes escape without malicious intent are eligible examples. When possible, defer to Command and the existing Neglect of Duty charge. This is more useful when the negligent crew member is acting unsupervised.
| 15 minutes
| 20 minutes and/or demotion
|-
| i222
| '''Unregistered Positronic Machine'''
| To function as an untagged positronic machine within the Republic of Biesel, or to function as a positronic machine with a tag that has been tampered with or rendered inoperable.
| [[IPC|IPCs]] are required by Republic law to be electronically tagged. This tag is typically visible to an onlooker.

Those who assist affected synthetics in tampering with or removing their tags are considered to be aiding and abetting them in this violation, and are themselves liable for heavy fines or brig time where applicable. These accomplices do not need to be retagged (if synthetic) or implanted.
| 10 minutes, immediate retagging, tracking implant, 1000 credit fine.
| 30 minutes, immediate retagging, 5000 credit fine.
|-
| i223
| '''Kidnapping of Free Intelligence'''
| To take away or transport a free positronic intelligence against its will.
| If the positronic intelligence is held for ransom or exchange, there is no difference in sentence.
| 15 Minutes
| Up to 25 Minutes
|}

=== High Severity Infractions (Red Violations; i300's) ===
==== Regarding cyborgification ====

*'''The NSS Aurora is in Tau Ceti space, which does not consider cyborgification capital punishment, making it an optional punishment.'''

{| width="950px" style="background-color:#ffaa99; text-align:center;" border=1 cellspacing=0
!style="background-color:#ff8855;"|No.
!style="background-color:#ff8855; width:150px"|Crime
!style="background-color:#ff8855; width:300px"|Description
!style="background-color:#ff8855;"|Notes
!style="background-color:#ff8855;"|Sentence
|-
| i301
| '''Murder'''
| To kill someone, or attempt to kill someone, with premeditated malicious intent.
| Also cover Attempted Murder. The premeditated and malicious bit is important here.
| Cyorgification or Holding Until Transfer on majority Command decision.
|-
| i302
| '''Manslaughter'''
| To kill someone without malice or forethought.
| This includes causing death due to negligence or dereliction of duty. Can also be used for excessive self-defense.
| 20 minutes and/or demotion. Tracking implant.
|-
| i303
| '''Mutiny'''
| To openly rebel against or attempt to remove command staff with violent intent.
| See "Sedition" for less violent mutineers. This generally means they use harm-intent or try to kill their superiors or advocate the same.
| Loyalty implant or cyborgification on majority Command decision.
|-
| i304
| '''Kidnapping and Hostage taking'''
| To take away or transport a victim against the victim's will.
| If the person is held for ransom or exchange, then it is considered hostage taking, which is automatically a holding until transfer.'''
| Hold until transfer.
|-
| i305
| '''Terrorist Acts'''
| To engage in maliciously destructive actions, which seriously threaten the crew or station.
| This includes deliberate arson, use of bombs, release of singularity, etc. Collateral damage or severe station damage has to be involved. For less disastrous actions, see sabotage.
| Hold until transfer or cyborgification on majority command decision.
|-
| i306
| '''Assaulting a Head of Staff'''
| To assault a Head of Staff, causing severe damage.
| Exactly like "Assault", but this time against a Head of Staff.
| 20 minutes and/or demotion.
| 40 minutes, suspension, and tracking implant.
|-
| i307
| '''Escaping From Holding Until Transfer'''
| To escape, or attempt to escape, from the brig or other holding area when being held until transfer.
| They have to have been properly convicted for it to be a life sentence.
| Cyborgification or hold until transfer at majority command decision.
|-
| i308
| '''Corporate Espionage'''
| To act as an agent of a terrorist or anti-Corporation group.
| Espionage, disclosure of corporate secrets, or any other assistance rendered to outside hostile organisations, or their representatives in hostile activities to the Corporation, committed by a employee of Corporation.
| Holding until transfer or cyborgification at majority command decision.
|-
| i309
| '''Sexual Assault'''
| To assault, or attempt to assault, someone else sexually, including rape.
| ERP scenes, or erotic roleplay, is a permabannable offence. Adminhelp it if this happens to you; it's against server rules, not just station rules.
| 30 minutes, tracking implant.
| Holding until transfer.
|-
| i310
| '''Automacide'''
| To willfully, unlawfully and permanently terminate a free positronic intelligence.
| Essentially the murder charge for free IPCs. Premeditation and malicious intent are still important here.
| 20 minutes, demotion
| Holding until transfer.
|}

=== Modifiers & Special Situations ===

{| width='825px' style='text-align:center; background-color:#aaffaa;' border=1 cellspacing=0
! style='background-color:#55ff55;' width='150px'|Situation
! style='background-color:#55ff55;' width='300px'|Description
! style='background-color:#55ff55;' width='100px'|Benefit
|-
|'''Surrender'''
| Coming to the brig, confessing what you've done and taking the punishment. Getting arrested without putting a fuss is not surrender. For this, you have to actually come to the brig yourself.
| Up to -25%, and should be taken into account when determining the severity of crimes.
|-
|'''Re-education'''
| Getting de-converted from revolutionary.
| Up to and including immediate release
|-
|'''Cooperation with prosecution or security'''
| Being helpful to the members of security, revealing things during questioning or providing names of head revolutionaries.
| Up to -25%. In the case of revealing a head revolutionary, up to -50%.
|-
|'''Immediate threat to the prisoner'''
| The singularity eats something near the brig, an explosion goes off, etc.
| Officer must relocate the prisoner(s) to a safe location. Otherwise, immediate release. Life sentences must be reapplied after danger has passed.
|-
|'''Medical reasons'''
| Prisoners are entitled to medical attention if sick or injured.
| Medical personnel can be called, or the prisoner can be escorted to the Medbay. The timer continues to run during this time.
|-
|'''Self Defence'''
| Assault and even homicide can be justified if it was necessary for prevention of loss of life. (Note that there are borders of acceptable self-defence, and killing a man who just punched you is subject to "Use of Excessive Force")
| Up to and including immediate release.
|}

==== Parole ====

Parole is temporarily releasing a prisoner before their sentence has been fully completed on the promise of good behavior. Parole can be given for any number of reasons, including brig overcrowding, a reward for good behavior or confession, or if the prisoner's skills are in need by the station such as a doctor or engineer.

The Warden or Head of Security can choose to give prisoners parole. A tracking implant is recommended if the prisoner is a flight risk (IE an engineer going EVA, but it is up to the Warden/HoS to determine how much of a risk they are.) Tracking implants for minor crimes are not worth it.

On the completion of their time they are simply marked as released as normal.

If they commit any crimes their parole is ended and they must serve out the remainder of their time in the brig with the new crime's time added on.

Parole can be given immediately after initial processing; theoretically a prisoner can spend their entire sentence out of the brig.

=== Terminology and Clarifications ===
'''Cyborgification''' The removal of a person's brain for transplanting into a Cyborg Chassis. Often also known as Shackling.

'''Suspension''': Changing ID title to "suspended", zero access.

'''Demotion''': Can be done up to and including Assistant position, by Head of Personnel or Captain's decision.

'''Employee''': Employee of NanoTrasen, as defined by the station's commanding officer. All non-employee subjects are still protected by these laws.

'''Empowering''': Illegal acquiring (not via Head of Personnel or Captain) of access.

'''Head of Staff''': Crew members occupying one of the following positions: Captain, Chief Engineer, Head of Personnel, Head of Security, Chief Medical Officer, Research Director.

'''HuT''' Holding until Transfer

'''Lethal Situation''': A situation in which there is an apparent and real threat the the well-being of all those involved.

'''Repeat Offenders''': For repeat offenders, use the "repeat offense" punishment.

'''Severe Injury''': A state in which the victim is in a critical condition and is having difficulty maintaining consciousness.

Demotion and dismissal also require the removal of equipment from the previous job. E.g: Uniforms, weapons, bombs, PDA cartridges, etc.

For the purposes of Cyborg/AI laws, crewmembers that have been convicted, or are being held in detention, are considered to be below even the AI/Cyborgs in terms of rank.

In cases where the final sentence is more than 90 minutes, it is changed to HuT

The standard penalty can be applied without a tribunal by Security Officers.

{{Security}}
{{Command}}
{{Gameplay Guides}}
[[Category:Guides]]
[[Category:Pages]]
[[Category:Security]]
[[Category:Command]]

Tajara

2019-05-02T05:27:18Z

Mofo1995: /* Factions in the Civil War */

{{Navbox Lore}}
{{Navbox Tajara Lore}}
{{Infobox Species
|Species = Tajara
|Scientific = T. Sapiens
|Image = OldTajara.png
|System = S'rand'marr
|World = [[Adhomai]]
|Language = Siik'maas, Siik'Tajr, Nal'rasan, Ya'ssa, Delvahhi
|Politic = People's Republic of Adhomai,
Adhomai Liberation Army,
New Kingdom of Adhomai
}}
{{toc_right}}
== Overview ==

The Tajara (direct plural: Tajara – Tah-jaw-rah both singular and multiple) (adjective: Tajaran - Tah-jaw-ran) are a race of about 5.25 billion humanoids which possess markedly felinoid traits that include a semi-prehensile tail, a body covered in fur of varying shades and padded, digitigrade feet.

To apply to be Tajara, apply [http://aurorastation.org/forums/viewforum.php?f=28 here].

Additional information: [[Adhomai|Adhomai]] [[Notable Tajara]] [[Tajaran Military Structures]] [[Tajaran Ethnicities]]

==Heads of Staff==

Hharar and Njarir-Ahkran can be the following Heads of Staff:

* Head of Security
* Chief Medical Officer
* Head of Personnel
* Research Director
* Chief Engineer
* Internal Affairs Agent

M'sai can be the following Heads of Staff:
* Head of Security

== Mechanics ==

* Tajara can speak a number of unique languages, such as:
:- Siik'Maas. Use this in game by typing say ,j
:- Siik'Tajr. Use this in game by typing say ,w
:- Ya'ssa. Use this in game by typing say ,r
:- Nal'rasan. Only available to M'sai Tajara, use this in game by typing ,i
:- Delvahhi. Only available to Zhan-Khazan Tajara, use this in game by typing ,n
* All Tajara have claws, and will scratch with them instead of punching, dealing extra damage.
* Tajara can see much better in the dark than humans.
* Tajara are less vulnerable to harm from cold due to their fur, but more vulnerable to harm from heat.
* Tajara cannot use human gloves or shoes due to their claws and digitigrade limbs. They are only able to wear hardsuits and hardsuit helmets designed/modified for their Tajaran anatomy. They are able to wear 'softsuits' (such as non-hardsuit space suits, biosuits, and fire suits).
* Due to a long history of combined selective breeding and cultural factors, different Tajaran races have different physical qualities and attributes as well as levels of education. Visit the physiology sections of the [[Tajaran Ethnicities]] page for information about their differences.
=== Coloration ===

{| align:Center
|-
!Hharar group, usual coloration:
|[[File:H_BeaverBrown.png|300px|thumb|left|Beaver Brown (RGB 159, 139, 112).]]
|[[File:H_Kochiba.png|300px|thumb|left|Kochiba (RGB 107, 68, 35)]]
|[[File:H_Taupe.png|300px|thumb|left|Taupe (RGB 72, 60, 50)]]
|
|-
!Zhan-Khazan group, usual coloration:
|[[File:ZK_BlueGrey.png|300px|thumb|left|Blue-Grey (RGB 34, 37, 50)]]
|[[File:ZK_DarkGrey.png|300px|thumb|left|Dark Gray (RGB 30, 30, 30)]]
|[[File:ZK_Chocolate.png|300px|thumb|left|Chocolate (RGB 94, 38, 18)]]
|[[File:ZK_Black.png|300px|thumb|left|Black (RGB 0, 0, 0)]]
|
|-
!Njarir'Akhran group, usual coloration:
|[[File:NA_Orange.png|300px|thumb|left|Orange (RGB 238, 64, 0))]]
|[[File:NA_Cinammon.png|300px|thumb|left|Cinnamon (RGB 160, 82, 45)]]
|[[File:NA_Ruddy.png|300px|thumb|left|Ruddy (RGB 138, 54, 15)]]
|[[File:NA_Cream.png|300px|thumb|left|Cream (RGB 205, 175, 149)]]
|
|-
!M'sai group, usual coloration:
|[[File:M_White.png|300px|thumb|left|White (RGB 238, 223, 204)]]
|[[File:M_Ivory.png|300px|thumb|left|Ivory (RGB 205, 205, 192)]]
|[[File:M_Wheat.png|300px|thumb|left|Wheat (RGB 205, 186, 150)]]
|[[File:M_Silver.png|300px|thumb|left|Silver (RGB 192, 192, 192)]]
|}

== Biology ==
To the average human, the Tajara share many similarities with Earth felines; however, when looked at from a purely scientific perspective, this description is largely superficial. Unlike terrestrial felines, the Tajara are both omnivorous and bipedal. Their bodies are almost entirely covered in a thick coat of fur that is extremely good at insulating them from the extreme cold of Adhomai. The layer of body fat and fur is designed to trap body heat in an efficient manner. There are only a handful of areas where fur is not present, those being on the palm of their paws, the soles of their feet, and a number of various orifices as well as a small area around their eyes.

Occasionally, the fur around a Tajara's neck is known to grow into a shaggy 'mane' of sorts, giving them a distinct look not unlike a terran lion. This hair tends to be much stronger and a great deal more wiry than the rest of the fur on a Tajara's body. Some Tajara tend towards monochromatic bodies while others have multicolor or even calico fur patterns. These designs depend heavily on the genetics of the individual's parents, much like hair and eye color. Because of this, some parents are utterly incapable of producing multicolor children. Designs including flat colors, stripes, spots and most conceivable combinations have been recorded by scientists both Tajaran and human. A male Tajara is somewhere between 145 cm and 185 cm in height, while the mean body mass is between 55 kg and 90 kg. Females tend to range between 135 cm and 185 cm in height, with their own weight somewhere around 35 kg to 75 kg. As such, both their body weight and height is roughly comparable to the average human. A Tajaran fetus only takes six months to mature, and Tajaran children likewise mature rapidly, reaching the full extent of their growth by 15 or 16. This rapid maturation has a profound effect on the lifespan of Tajara, as only with modern medicine have Tajara reached ages above 70, with the oldest living Tajara being 84 years old. Most Tajara retire at age 60 when they are too old to work in any capacity.

===Tajaran Evolution===
The Tajara evolved as a predatory, cave-dwelling species upon their home planet of Adhomai, and as a result they have a pair of fairly large, well developed eyes that are forward set. These eyes are comparable to those of humans, but they are more effective in low-light situations due to the Tajaran ancestors having to hunt in dark cave tunnels. Tajaran eyes are set above a slightly elongated structure comprised of hard bone similar to a muzzle on terrestrial creatures. Their pupils are large and capable of contracting significantly faster than most other creatures, both sapient and otherwise. This allows for a considerable degree of low light vision, however they have a thin reflective layer which has the side-effect of appearing illuminated in the dark.

The Tajaran dental structure was at one point in their evolutionary history once geared for a carnivorous lifestyle, but has since evolved and shifted towards a more omnivorous role. Tajara have sharp, needle like teeth in the front of their jaw which are quite clearly geared to tear meat; the further along the jaw line one goes, teeth similar to human molars reside behind the sharp canines, evidence of the change to an omnivorous diet. Evolutionary biologists believe that predecessors to modern Tajara had rough tongues with few taste buds in order to facilitate eating raw meat. The contemporary species has evolved out of this a long time ago in conjunction with becoming omnivorous, and so they now have softer tongues with a full sense of taste. Atop their heads, Tajara have a pair of deft, normally erect ears that are capable of a wide range of motion. They can rotate to roughly ninety degrees, capable of even being able to fold back almost entirely onto the skull if needed.

===Extremities and Sleep Cycle===
Tajaran extremities, specifically their hands and feet have five digits, and are generally the same shape as human extremities. However, they are slightly stubbier in appearance, though still dexterous enough to be useful. Tajara employed in more professional roles such as engineers, architects, or other occupations that require dexterous manipulation often find themselves with filed down claws, reduced to a smooth end in order to allow easy usage of standard human based technology. This is a task that Tajara tend to do reluctantly, given that cutting too short is incredibly painful and will expose nerves to the air. Normally, these claws are non-retractable and grow from the fingertips, usually measuring around 1-2 centimeters.

The sleep cycles of the Tajaran species are one of their most scientifically curious features. A normal waking period is somewhere between thirty six and forty eight hours, with a subsequent twenty to twenty eight hours of sleep. Normally, the waking period is spotted with three to four fifteen minute naps in order to keep the Tajara refreshed and alert. This is universal on all worlds with Tajaran living upon them. Tajara are capable of great feats of intelligent, dedicated work but this is physically exhausting, which renders them utterly mentally and psychologically exhausted. Those that do not enter their sleep cycle properly may find themselves groggy, aggressive, paranoid and disoriented until their circadian rhythm is righted.

===Tajaran Build===
[[File:Cats.png|400px|thumb|right|An artist sketch of Tajaran dimorphism, builds and general stance.]]
In comparison to most other known species, the Tajaran body is designed to specifically be more flexible, lithe and slender despite their thick insulation. A handful of Tajaran ethnicities do not exhibit these traits and instead manifest increased muscle size, strength, or bulk. Tajara are sexually dimorphic; females have more elongated muzzles, shorter ears, as well as more petite forms, and their distribution of body fat is entirely different than that of a male. Females do not exhibit visible breasts until pregnancy, at which point they swell in order to provide for young. Males are in general taller, have broader shoulders, bigger hands and feet, and more pointed ears.

Tajara are built for the extremely low temperature environments that are incredibly common on Adhomai, giving them remarkable cold resistance. However, this gives them a tendency to overheat in more mild environments. To avoid this, most Tajara will dress lightly in warmer environments such as those on human installations or tropical worlds. Forgoing the usual layer-like clothing, these Tajara resign themselves to thin clothing. Those who find themselves confined to bio suit or radiation suit for extended periods of time will end up feeling extremely uncomfortable and perspiring heavily.

==Social==

Native Tajaran names are usually difficult for humans and other species to pronounce properly; as such, older Tajara prefer to take names (whereas young Tajara are given them at birth) that they find they themselves are able to pronounce and are also phonetically pleasing. For many, these are names derived from Arabic or Russian backgrounds, as they are the easiest for their inhuman mouths to pronounce. Traditionally, Tajaran names included the name of the dynasty they served, and some Tajara carry over this tradition and have their 'middle' name be their dynasty's name.

As with all other species who work in Human-centric environments. Tajara are expected and required to have passed a prerequisite test to test their comprehension of Tau-Ceti basic, the operating language of NanoTrasen and most transstellar corporations, in addition to most major sovereign entities. Admittedly the passing levels of these comprehension tests are quite low, but are high enough to ensure basic conversation between what will likely be a multi-species crew. However, private communication in Siik’Mas or Siik’tajr is not forbidden by NanoTrasen regulations and is often used to hold conversations between Tajara on the crew.

Though there are a variety of languages used by the Tajara, among the foremost of this vast plethora of languages is Siik’mas and Siik’tajr.

'''Siik'maas''' is theorized to have been the ancient language of the Tajara, the 'religious' language shared between most Tajara from their onset as a species. Despite Tajaran society evolving to a point where religious devotion became less encouraged, the universal service language used in all churches and worship sessions became the most common for Tajara and almost every Tajara knows how to speak it. It has been taught as the primary educational language amongst most Tajaran ethnicities since the Renaissance era and continues to be the most prevalent language on Adhomai since.

It is capable of being spoken by a learned human, as it is not as reliant on body language as Siik'tajr or the other native languages on Adhomai. However, just as Tau Ceti basic is difficult for Tajara to master given their muzzle structure, Siik'maas is the same to humans, since they lack the proper biology to perform certain inflections properly. Despite it focusing more on spoken word than others, some of the vocabulary requires subtle body movements that are challenging for humans to grasp, no less perform. Even if one were to learn these movements, they tend to be sluggish and slower, giving the speech a sort of 'drunken' feeling. Tajara speaking this over the radio often find themselves in similar positions.

Siik'maas is the federal language of the People's Republic of Adhomai. However, several groups of Tajara ranging from scholars to traditional followers of the old ways are attempting to revive older languages such as Nal'rasan, Delvahhi, Ya'ssa and other such languages.

'''Siik’tajr''' is the opposite of Siik’mas completely. A recent construction, it has seen more use recently following the overthrowing of the plutocracy. It was birthed from the necessity for a language that was difficult for law enforcers to understand, enabling revolutionaries to converse privately without having their conversations monitored or overheard. Revolutionary radicals have been a part of Adhomai's history for a long while, but were always small; however, when the Great War broke out, Siik'tajr saw widespread use by rebel forces during military operations similar to Navajo radio operators. It is a combination of Siik'mas and the more body language inclined Nal'rasan, a language traditionally used by hunters. It is not normally used in daily life due to its complexity, it is often maintained as a secondary language, especially for families who fought in the Great War.

Pro-human groups within Tajaran society have repeatedly attempted to push Cyrillic or Latin alphabets as 'easier to use' rather than the native Tajaran alphabet. However, the vast majority of Tajara use the old Siik alphabet and it is the federally enforced alphabet taught in schools, the original alphabet learned Tajara have been using for centuries. It has undergone certain modifications since the Great War to remove the influence of the plutocracy, and has made a widespread comeback with increasing literary levels among the Tajaran public.

Tajara have a strong biological inclination to roll the “R” sound, extending it. They also tend to refer to themselves in the third person perspective instead of the traditional first person ( “He has completed his work" instead of “I have completed my work") though Tajara who have spent a large amount of their lives in space or among other species may overcome this trait with great difficulty. Most Tajara will only speak to someone in the first person if it is someone they trust substantially. The occasional “slip up” can still be expected however, as being surrounded by a mostly Human crew can occasionally confuse them into using first person. The second person perspective is used in many regional dialects and does not imply any intimacy, however many Tajara prefer third person even in these cases as a preference. First person perspective is often used in the context of speeches or addresses to large populations in order enhance the rhetorical impact.

==Culture==

=== Fashion ===

Throughout Tajaran history, fashion has remained relatively simple. Extravagant vestments fabricated from silk and other high-quality animal hides were restricted exclusively to the nobility, and standard Tajaran peasantry had little time to choose their uniforms, usually donning overcoats made of rough fabric and patches of animal hide. The fluffier the design was, the wealthier a noble was considered.

Given the hardships of Tajaran life and the constant need to do work by hand, the peasantry came to favor practical, well insulated clothing rather than fanciful designs; they were also cheaper to weave, which made things easier on the weaver. Underwear usually came in the form of long-sleeved pants and a shirt typically woven from thick animal furs and plant fibers and is used as the inner most insulating layer. Then, a Tajara would overlay multiple garments to create several layers of insulation to stop the loss of body heat. Thick, full-length skirts, pants, and shirts were favored by the peasantry, all in dark colors to retain heat better. Typically pre-discovery and even post-discovery modern clothing consist of thermal underwear, pants for men or long, heavy skirts for women, with thick sweater-like shirts and fur cloaks.

The feared enforcers of the nobility wore great suits of armor designed to seal the user inside, creating an environment that was completely isolated from the harsh snows of Adhomai. Build for brute strength rather than comfort, the helmets of these suits made no room for Tajaran ears. These 'Enforcer Shells', as translated from Siik'maas, were usually brown or olive in color, with slit visors that masked the wearer's face.
[[File:Government_Officials.jpg|thumb||Typical Government Official wear.]]
Today, the Government Officials of the People's Republic of Adhomai are usually seen dressed in olive military fatigues, occasionally donning a commissar-styled cap. These caps are usually styled with small rosettes to signify authority. When in especially cold weather, officials usually layer on black trench coats and scarves rather than wearing the outfits of the lower class.

The lower and middle class of the Tajara are better heated by proxy, and can comfortably wear flat caps and long sleeved buttoned shirts for warmth when working in their factories rather than excessive garbs. When outside, typical Tajara will wear bomber jackets or fur coats with additional fur padding on the interior to better trap heat, paired with traditional slacks. Headwear for these working class citizens usually comes in the form of full head scarves to keep ears warm when in the wilderness, and standard soft and flat caps within cities.

=== Cuisine ===

Similarly, due to the cold temperatures of Adhomai, Tajara favor warming or hot food that can be consumed quickly before the freezing winds can cool the meal off. Porridges, soups, and chowders consisting of diced meat and vegetables for flavor was the usual meal of a working class Tajara, coupled with some bread and water or ale. Pre-industrial Tajara used to have community meals around bonfires to keep their food from cooling off too much, and almost all of their food source came in the form of porridges and oats. However, with the introduction of new technologies - such as higher quality insulation and home heating systems - Tajaran cuisine is being experimented with by chefs who are no longer restricted to compensating for the naturally low temperatures of Adhomai. Historically, culinary creations were reserved only for the nobility, who had better heated homes than the peasantry and more leeway was offered towards not having your meat turn blue in front of you.

===The Arts===

Of all arts, music is one of the most highly valued by Tajara. Stemming from the long-standing ban on most literature in their society, song and dance remained one of the only ways for Tajara to express themselves through words. Composers and musicians were traditionally held in high regard amongst Tajara, and in place of books the fanciful song-stories of traveling bards were one of the few ways the public could remove themselves from their lives.

Theatre was also equally important in the life of a pre-discovery Tajara. Given that, with the lack of books, there was little to keep your usual worker entertained, the ability to watch and enjoy a riveting drama or hilarious comedy was heaven. Theatres and performing halls can be found in almost every Tajaran village, and are often constructed to rival even the main seat of town council or government in architectural beauty. For example, the D'na'tel Hall in the Tajaran capital was one and a quarter larger than the seat of government prior to human sanctioned expansions. Dating back to the late Renaissance Era, it was constructed from high quality marble and many sculptures of characters and scenes from various popular Tajaran plays were meticulously hand-carved into the walls by sculptor Nasir Ka'nira.

However, literature itself - that is to say novels - have never been looked kindly upon by the Tajara public. Though this closed way of thinking is starting to shift with the greater introduction of literacy amongst Tajara as a whole, many elders still harbor bitter feelings about books in general. They were almost universally considered a symbol of oppression and luxury by pre-revolution Tajara, given the fact that only the nobility were taught en masse how to read, and that every family had it's own private expansive library that even learned peasants had to pay out of pocket to access. This led to a widespread destruction of much of historical Tajara text following the uprising, as revolutionaries took it upon themselves to purposely gather and burn whatever books they could after taking a noble stronghold.

=== Military ===

The military hardware of the People's Republic of Adhomai lands somewhere close to what humankind used in the early 1900s, though the transition to energy weapons has already been made. Clumsy overheating handguns and rifles that slowly fire long bolts of concentrated energy are used by high ranking soldiers or special operatives, but their durability is dubious in comparison to the mass-produced, single shot or bolt action rifles that the majority of Tajaran soldiers use. In recent years the People's Republic has largely replaced bolt action rifles with fully automatic Tsarrayut’yan rifles, however these suffer accuracy issues at longer ranges. Bayonets are heavily relied upon in close quarters combat rather than Tajaran model submachine guns, which are expensive in the eyes of the People's Republic and jam easily in the harsh terrain of Adhomai.
[[File:Williamsbrowning01.jpg|thumb||The Tui'ad "Icelance" laser rifle.]]
Heavy infantry weapons like heavy machine guns used to come in the form of heavy, hand cranked gatling emplacements with a heavy emphasis on frontal gun shielding. These HMG emplacements are extremely deadly in comparison to the slow firing rifles of foot soldiers, and are usually countered by Tajaran artillery or laser weaponry. Most squads of Tajara now carry a mixture of top loading magazine fed light machine guns or quicker firing belt fed LMGs.

Tajaran artillery is where the cunning of the People's Republic engineering shines, and many mountain ranges of Adhomai are lined with artillery guns the size of the mountains themselves. These weapons fire devastating artillery rounds capable of leveling small camps with a single shot, let alone a barrage. Artillery vehicles and mortar teams are almost always deployed in tandem with Tajaran infantry in order to shell enemy entrenchments and positions, and many Tajaran tacticians utilize artillery as their main killing force. These weapons are the pride of the People's Republic, and their nightmare if lost to enemy hands.

''For more information, see [[Tajaran Military Structures]]''

=== Education ===
Tajaran institutions for education are woefully behind their counterparts in other species. Historically, Njarir-Ahkran were often the only ones who became literate. Historians theorize this is tied to their alleged rise to nobility through their positions in early theological organizations. Officials from each faction agree that religious education has dominated most of Adhomai's academic history with heavy evidence from religious books which were largely able to survive the mass destruction of books by being sheltered in mosques. Disagreements among academics arise when discussing the evolution of primary schools, secondary schools, and universities. Academicians in the New Kingdom of Adhomai assert that these institutions began to rise thousands of years ago during the Adhomai Renaissance and downplay the role of the nobility's suppression of educating the masses. However intellectuals in the People's Republic of Adhomai and the Adhomai Liberation Army assert that these institutions were disingenuous social clubs at best and that schooling and formal education did not begin to arise until five hundred years prior. Hard information on the curriculum of pre-war institutions outside of theological institutions is difficult to find, however archaeological evidence tends to support arguments that there was a heavy focus on the arts- especially musical. Some artistic Hharar who lived before the war give accounts on nobles providing large patronage for painters such as in the modern sense with Al-Manq, but also for lavish concerts, operas, and ballets. Sculpting also came into prominence as evidenced by the intricate detail of various statues and gargoyle-like protrusions from an array of buildings in Nal'Tor and especially on the capital building in The People's Square: the aptly-named Steeple. Regardless of the details of pre-revolution educational institutions, the current face of Tajaran education outside of seminaries is primarily technical schools which focus on preparing young Tajara to work the various labor jobs around Adhomai.

''See also [[The Nal'tor College of Career Excellence]].''

=== Marriage and Relationships ===
Historically, the peasantry made due by uniting themselves as a workforce which has bred an intimate inter-person relationship among the families of most villages, towns, and cities. Regardless of the size of the population, pre-uprising Tajara were often well acquainted with families that may have lived on the other side of town. Arranged marriages were extremely common and were ways to improve relationships among families. However, this traditional practice has met with extreme criticism following post-uprising debates. The practice of arranged marriage was not feasible following the first revolution which effectively eliminated a generation of adult Tajara. This created a generation which had to largely create their own marriages, many of which passed on this emerging cultural norm to the next generation. Although permanent pairing of Tajara is often colloquially referred to as "marriage" due to humanizing influences, there are a handful of different technical terms for it depending on the religion of the Tajara involved. S'rand'marr worshipers are typically brought together in mosques by their local Brother of the Sun in a ceremony which symbolizes and glorifies S'rendarr and life. Their equivalent of Marriage is called "'''S'rendal'Matir'''" (The life of S'rendarr), named for the idea of continuing the life which the sun god S'rendarr celebrates. Tajara under the worship of Ma'ta'ke have a less celebratory and less ritualistic ceremony, instead having a simple meeting between families with a clergyman to proclaim the lovers "'''Zrrazhil Ekrratul'''" (Continuation of the families), named for the simple notion of propagating the blood of the families involved.

Because of the Tajara's history as a repressive, conservative species, they have not grown too open-minded or liberal - unlike humanity's progressive views for example. Overt displays of affection and especially homosexuality among Tajara are looked down on and treated as a deviancy. There exists discrimination and bias against other races of Tajara - particularly against Zhan-Khazan for their purported low intelligence and rebellious tendencies. As a result, Tajara generally avoid interbreeding between races. An extension of the racism which prevents Tajara from breeding outside of their race can be found in the general public's extreme revulsion to notions of relationships outside of the species, an act which is considered an intolerable fetish to most.

==History==

[[File:Adhomai2.png|thumb|alt=The Tajaran homeworld.|Adhomai was ravaged by warfare and more than forty million deaths have been recorded as a result of the Great War.]]

===Nobility and the Ancient Past===

For as long as most Tajara care to remember, Adhomai had always been under the rule of nobility. The most dated historical text that still exists in Tajaran possession dates back at least four thousand years and still talks about 'serving their masters', so many historians agree that the trend of blood rule is more deeply-routed in Tajaran existence than was previously considered.

The ancient past of the Tajara is poorly documented and historical texts are almost non-existent; meticulous combing and destruction of educational material by millennia of harsh rule resulted in total atrophy of most scientific arts in Tajaran society. Top Tajaran scholars in this day and age have theories that life on Adhomai. Little is known about Tajara civilization before '''2500 BCE''' Galactic Standard Time.

Tajara society and government in the '''2000 BCE''' era Galactic Standard Time was similar to human feudalism. Several towns, villages, or the rare city would be organized under a single Lord. Nobles of fiefs commonly collected together to make crucial decisions about the ownership or trade of lands. If agreements were not met and conflict between two lords was imminent, decisions would commonly be made through staged combat. In these trials, groups of peasants were equipped with matching weapons and faced with the task of killing off the opposition. These displays were considered a quality source of entertainment, usually in which nobles would come to an agreement on their previously unsettled differences -- before staying to watch the peasants slaughter one another. Peasants had little choice in these matters, and all dissidence was met harshly and fatally at the hands of the Nobles' Enforcers - trained agents (commonly of M'sai descent) who fought for the nobility of Adhomai in exchange for relative freedom. These Tajaran enforcers kept the peasants of Adhomai's lands repressed and powerless through shock and terror.

What is known for sure, however, is that tension and violence had slowly been increasing over hundreds of years between the populace and their fellow noble families.

Based upon limited information gleaned from literature and art that survived various purges, many Kingdoms across Adhomai had been violently replaced with highly centralized theocracies, which are first mentioned in historical texts in the '''1300 BCE''' era, with the religious states focused around the worship of the suns and their leaders as direct avatars of S'rendarr. The vast majority of Tajaran noble families stemmed from religious leaders with divine right to rule.

===Tensions Rise===

Tajara historians believe that global violence spilled out across the planet between the theocratic kingdoms and the other scattered noble families in the '''1500 BCE''' era. These religious leaders clashed and either pitted their followers against one another. The noble leaders continued to fight and inter-marry until the ruling families had become exclusively '''Njarir’Akhran'''. Over time, the nobility as it were slowly began to lose their religious inclination, adopting more traditional civil institutions and a relaxation of the church's control which gave way to state control. This indirectly created the '''Adhomai Renaissance''' in the '''1,100 BCE''' era. Religious worship of the noble families had been dropping steadily in conjunction with the lower influence they had upon the other nobility. It was this period that historians believe the overwhelming control of the noble families flourished and solidified into what it was prior to human contact.

Literature was heavily regulated from this point as the ruling Njarir’Akhran reacted harshly to the '''Adhomai Renaissance'''. Enlightened philosophers had taken advantage of the creation of the short-lived printing press in '''955 BCE''', who's blueprints and designs were quickly destroyed and would not be recovered until several hundred years later. The rise in literacy and philosophers questioning the very concept of "right to rule" was deemed dangerous to the health of noble rule. Scarce written literature the Adhomai Renaissance spawned sculptors, musicians, and artists. However, rather than their works being presented for public viewing, they were collected by noble families and only a handful were shown outside of their palaces for the peasantry to admire.

Following this era, tension between the nobility and the peasantry began to steadily increase, believed to have stemmed from increasingly harsh rulers and laws. Technological and cultural knowledge and breakthroughs had slowly begun to trickle down from the noble families to the peasantry. The blueprints for the '''printing press''' had managed to be smuggled out of a private noble library in '''173 CE''' and many underground libraries for the peasantry began to pop up in cities and towns across Adhomai. Eventually it became a capital crime for a peasant to even own a copy of an unapproved text.

Adhomai underwent a form of industrialization with the creation and proliferation of the steam engine in '''1226 CE'''. However this only forced the Adhomai peasants into harsh new labors digging in mines and working 18 hour days building rail lines for private use by the Njarir’Akhran nobility. Laws were soon enacted that banned any non-Njarir’Akhran from utilizing electricity or riding on trains.

This trend of noble's hoarding new technology or innovations at the expense of the peasants continued until human contact.

Thirty years prior to human discovery of Adhomai, the deep-seeded mistrust between peasants and nobles had reached an all time high. The Tajaran species was trapped in a technological bubble forced upon them by their nobility. At the height of their industrial revolution only a few years prior, the leadership at the time became increasingly wary of the unification of many Tajaran workers who demanded greater rights, seeing themselves in what could be accounted as another 'Renaissance' era and result in more 'enlightened' individuals straining their already crumbling control over the populace.

The realms of education, science, and luxury found themselves under severe restrictions, and your basic Tajara was forced into almost twenty hour work days with minimal time afforded for eating and sleeping on the job. Analysis of the noble houses proves that during this time in Tajaran history, the nobility had never been worth more in Sol credits than previously. This is largely attributed to the fact that rather than modernizing Adhomai the nobility had seen fit to confiscate and use these fruits of scientific thinking for themselves.

Automobiles are considered one of the best examples of this. The first automobile is recorded to have been created in '''2012 CE'''. Using a combustion engine much like primitive human vehicles, with extra anti-freezing measures and thick treads, one of the first fully functional automated cars had been produced by a collection of Tajaran engineers and scientists, at the behest of the nobility. These large creations were considered by many older Tajara to be a symbol of negligence and gluttony by their leaders. Workers were never provided with such things; they were forced to transport themselves through Adhomai's harsh winter conditions on foot or by using specially designed 'snow bicycles', regardless of how far away their place of work was.

Further restricting the rights of the individual Tajara was enacted by a furious nobility after several instances of violence against Njarir’Akhran, but specific information on these incidents has been lost. Legislation was introduced against 'workers unions' as well as any sort of illicit groups; a permit was required to form anything from hunting parties to agencies. In this whirlwhind of political turmoil, a fresh generation of Tajara were growing up, deprived of what most humans consider to be 'basic rights'. As they grew older and angrier, the nobility saw fit to continue tightening their control over their subjects until a civil war was almost inevitable. Like a powder keg ready to blow, only a single spark was needed to light the flame.

===Human Discovery===
This came in the form of human discovery in '''2418 CE'''. A Sol Alliance funded expedition into the Tajaran home system discovered the pre-space age species and their homeworld of Adhomai. Lush with untapped resources and potential workers, Adhomai was an attractive prospect for many human super corporations, especially NanoTrasen. Because of their slow technological progress, most of Adhomai's valuable minerals remained untapped by mining or drilling. It was due to this that several corporations attempted to insert themselves into the dealings of Adhomai.

However, the nobility felt incredibly threatened by what they considered 'intrusions' by humanity and completely refused them diplomatic access to their planet. The Alliance stepped in, initially unwilling to interfere in a pre-space age society and, reluctantly, the super corporations were forced to abandon their wishes to stake claims on Adhomai's resources - at least in the open. In the year '''2420 CE''', a group of Tajaran intellectuals - considered rebels by the state - were shuttled off-world by a still unknown entity. Given asylum in the Sol Alliance, they met and discussed much with human scientists and officials. Tensions between the Alliance and Tajaran nobility rose after such an event and they accused the humans of harboring terrorists.

Eventually, these rebels were returned to Adhomai with supplies and weapons. Fed with new ideals of personal freedom and 'rights afforded to all' by their influential human friends, the seeds of revolution were sowed among the Tajaran populace, spread by word of mouth. Workers, doctors, teachers, even soldiers that were questionably loyal to the nobility were swayed by these promises of freedom and equality. Meetings in the basements of dark taverns or barns were common, and relations between the nobility and their peasants were at the lowest ever recorded in Tajaran history.

===The Uprisings===

It took little more than a year for a formal uprising to be staged. On '''2421 CE''', after the nobility had captured one of the original Tajara that had been shuttled off world, he was sentenced to be publicly hanged by the neck in front of their peasants to show just how serious they were about keeping control. Ultimately, many historians believe this to be a highly egregious mistake. Rebels in the audience, armed with advanced off-world weapons, proceeded to open fire on loyalist forces and kill a nobleman in the process. This event, called the '''D'as'ral Massacre''' (so named for the city it took place in) by the nobility was all the excuse they needed to enact martial law.

[[File:Emplacements.jpg|thumb|alt=Gun emplacements.|Wartime photo capture of rebel artillery emplacements.]]

However, they found themselves in a cornered position. Weapons and supplies were being shipped in off-world by mysterious benefactors, and their collections of scientists and engineers had either fled to safety being noblemen themselves, or took up arms and joined the revolution. Without significant scientific presence to deconstruct or understand these new human weapons or support the war effort, the conflict resulted in a string of rebel victories that drew closer and closer to the capital cities of each providence. Fighting was extremely fierce and atrocities were recorded by both sides.

Among the noble families, the largest and nearly the most powerful was a dynasty called the 'Hadii'. Their castle was amongst the best defended in the region and the battle to take it was waged for six months of non-stop fighting. As it became increasingly clear to them that they were eventually going to be overrun, the Hadii struck a deal with the rebel leader; in return for complete immunity from the war, as well as persecution, they afforded the revolutionaries with unique tools and even blueprints of other families' castles, pointing out weak points and infiltration spots.

It was this turn coating that tipped the revolution in favor of the peasantry. Armed with this new information, they made use of radio systems previously restricted for nobility to methodically and ruthlessly end their uprising by murdering most of the noble families and whatever soldiers and civilians remained loyal to them. By '''2431 CE''' the revolution had finally come to an end with a total of more than '''92 million casualties''' with more than half of that being loyalist forces, and '''40 million civilian deaths'''. Many Tajaran cities and villages were utterly destroyed by vicious fighting as well as bombardment by uncaring nobles. A informal ceasefire was declared between the factions, though skirmishes were still common.
[[File:Anti-noble_Propaganda.jpg|200px|thumb|right|Famous People's Republic Propaganda painting which depicts a pouf noble walking a Tajaran worker like a pet.]]

===Outcome of the Revolution===

Following this total upheaval of Tajaran society, rebel leaders met with Hadii noblemen and discussed how to form a government, given that only the Hadii were experienced with ruling. Human corporations took express interest in this; the Hadii were one of the few noble families that saw profit in human stakes on Adhomai, and many back-room deals were made until ultimately the Hadii were placed at the head of Tajaran government in '''2432 CE''', and ushered in a new federal republic: '''The People's Republic of Adhomai'''. The Tajaran public was markedly distressed by this turn of the events, and fearing another uprising, human intervention again helped defuse the situation. The Hadii promised that it would not be like it was before.

NanoTrasen, suspected by many conspiracy theorists to be behind the funding and supplying of Tajara during the war, holds claim to most of Adhomai and has a monopoly over most of the planet's valuables. Collaboration between them, the Sol Alliance and the Jargon Federation has resulted in more technological advances in Tajaran society recently than ever before in their recorded history. Approval ratings for the current leadership rose in response.
[[File:21208e532f75dbdf919f48ff4ddac508.jpg|300px|thumb|right|Potrait of President Al'Mari Hadii, taken one week from his death and done in the [[Notable Tajara|Al'Manq style]].]]

However, serious problems remained. '''Rhagrrhuzau Hadii''' suddenly began to back out of the People's Republic's agreed upon business deals with NanoTrasen, all of which saw a massive amount of Tajaran natural resources exported. Citing humanity as greedy and destructive, '''Rhagrrhuzau Hadii''' made clear his intentions to make Adhomai independent until it was ready to take on the burden of interstellar politics.

===The Second Revolution===

The disagreements and hatred of the Hadii republican government had led to insurrection and treachery between Adhomai's major power figures since '''Rhagrrhuzau Hadii''''s new economic policies were revealed. Many Tajaran business contractors - just recently denied their ability to sell ludicrous amounts of natural resources and workers to the massive human megacorporation, NanoTrasen - felt threatened by the reforms of the Hadii government and its first President, '''Rhagrrhuzau Hadii'''. On '''2451 CE''', during a military parade, President Rhagrrhuzau was assassinated by a young Zhan-Khazan radical. A known secret service agent of the People's Republic, the radical was sentenced to death for his treachery, brought on by the violent tendencies of his Zhan-Khazan genetics. His brother and vice-president '''Njadrasanukii Hadii''' quickly assumed the office of the presidency and immediately passed brutal laws that punished Zhan-Khazans and 'subversive elements'. NanoTrasen was invited back to Adhomai and menial workers were sold en masse to NanoTrasen workplaces while the rights to the bountiful natural resources of Adhomai were sold off to NanoTrasen. Public hangings and firing squads became the norm once again.
[[File:Godblessalmarihadii.png|thumb|400px|left|Picture taken by the Adhomai Chronicle moments before the Assassination of Rhagrrhuzau Al'Mari Hadii. The single most defining moment of this generation of Tajara.]]

Many military generals that had fought for the Republic soon defected under the banner of the Adhomai Liberation Army, the leader of which being '''Rhagrrhuzau Hadii''''s old friend and ally, '''Halkiikijr Nated'Hakhan''', and Adhomai found itself embroiled in yet another global conflict that continues to this day. "His gun was on stun" became the rallying cry of Rhagrrhuzau's fiercest supporters, "Hadiists," as they alluded to how he not only left himself greatly vulnerable during the parade, but had even left his energy pistol on stun while he was assassinated.

===Adhomai Today===

The Tajaran home world has suffered plenty in the three decades since the end of the First Revolution. With the sudden injection of advanced technology into their relatively simple life, the discrepancy between modernized cities and outlying areas could not be more obvious. While the Tajaran capital boasts the most modern developments with sleek skyscrapers, advanced connections and phone lines, as well as hospitals and schools, the further you get from the larger cities, the more apparent it is that things are not quite so flashy. Expanding infrastructure remains difficult, as most public funds are seized for use by the military or used to repair infrastructure damaged by shelling or bombings.

There is a steady stream of money being fed into the People's Republic of Adhomai. NanoTrasen, as per it's agreement with the president, have set up mining and logging operations on Adhomai using the local work force for the most menial of tasks. In return, company funded clinics and schools are slowly being spread out and build in the needy areas. Tajaran resource operations are now all but nonexistent; the buildings that were once part of the nobility's small gathering efforts have now been refurbished and are being used by NanoTrasen.

Literacy has risen to its all time high on Adhomai, and with the assistance of the Alliance, teachers have been brought in from off world to educate the younger generation of Tajara. However, this number has begun to decline as the dangers of working on Adhomai are beginning to become common knowledge. Special establishments for older students have also been constructed to assist the elder generation in being brought to the same level of education, but NanoTrasen has not expressed significant interest in this; these people make up the brunt of their low-paid workforce and they want to ensure that they are kept that way.

There are still several proponents of revolution that oppose the current government, which has plunged the planet into another all-encompassing civil war that remains at a standstill today.

==Notable Information==

===Religion===
====S'rand'marr Worship====
''"By day and light of S'Rendarr, we live and bask in his warmth, happy and content. By the warmth and light of Messa, we cease breath and fall to death. Only by the love and harmony of both the Twin Gods and Sibling Suns do we live happily, and die the same. By the Twin Gods and Sibling Suns, S'Rendarr and Messa, the faithful ask for your blessing, and to please extend it to the non-faithful who do no wrong, and cast no sin."''

- The "First Prayer" of S'rand'marr Worship

There are a handful of faiths on Adhomai, but the majority religion is the worship of S'rendarr and Messa, the names of both suns in the Tajaran home system. Ancient Tajara were believed to worship the suns as gods, believing their light to be the only thing keeping the planet from freezing over entirely. Over time, this faith matured into a system of beliefs suited to the peasantry; looking down upon the acts of betraying your fellow worker and attempting to foster unity and understanding amongst its followers. It is believed by many that S'rendarr is the god of life and the day, as the bigger of the two suns, and he is associated with good happenings and is most often prayed to. Contrastingly, Messa, the blue sun, is the goddess of the night and death; whenever she eclipses S'rendarr, all followers partake in religious rituals that ask Messa to spare them from whatever ill tidings she may bring. The worship of the sun gods is dominated by an organization called the Parivara, meaning, the "Family." The head of the Parivara is Father Walid Al'qat who is based out of Sana Sahira, a holy city on the tallest mountain on Adhomai which roughly translates into the City of the Suns. The First Father of the Twin Gods was said to have made a direct link with the Gods, who gave him these laws that all of their faith should follow:

''"You shalt not harm another, faithful to the Suns or not. You shalt always show kindness to any and all. You shalt not covet the items of another faithful. You shalt not defile the body of one who now rests in Messa's Forever."''

Since the day these were declared in Sana Sahira, they have been considered the Law of the Suns. This location in the People's Republic places the Parivara in the precarious position of having to act favorably to the faction's government, however Father Walid Al'qat attempts to stay out of politics in order to avoid alienating any worshipers across borders. The Father of the Parivara is chosen by the Brothers of the Suns who serve as the priests and clergy of the faith. Devoted women of the faith can become Suns' Sisters, who take a vow of silence of silence, like the Gods themselves, and live in the Mosques devoted to the worship, tending to them in anyway needed, anything from cleaning to heavy manual labor repairing and replacing glass or furniture, to healing the Brothers, patrons and other Suns' Sisters. To cause harm to a Suns' Sister is said to be one of the most unholy things you can do in a place of worship, as they're meant to emulate the Gods themselves, silent, but strong and dependable.

====Ma'ta'ke====
The second largest religion is the worship of the Snow God Mata'ke and his cohort companion gods, which dates back to ancient Tajaran times. A figure of legend, Mata'ke is believed to have been the head of a hardy tribe of mountain dwellers which regularly came to the aid of other tribes which were constantly plagued by bandits and wild animals. He was revered as a fierce warrior capable of fighting a platoon of men by himself, but also as a kind soul for the records of his dealings with other tribes show understanding and kindness. He is upheld to be the ultimate Tajara- powerful, wise, and magnanimous. Followers of Mata'ke himself endeavor to emulate his grandeur, while others attempt to emulate the other gods.

In Tajaran mythology, the tribe of Mata'ke rose to the status of gods when they slew the King of the Rrak'narrr, who was also the lord and master of all Adhomai. Upon killing him, the various tribessmen all absorbed different aspects of its many powers, each becoming immortal. As the one who dealt the killing blow, and at the will of the dying Rrak'narrr's final wishes, Mata'ke absorbed the majority of the powers and became lord and master of all Adhomai. The tribe then decided that their former settlement was not befitting of their powers, and instead established themselves in a city of wonders at the "Edge of Adhomai" where they fend off malicious entities and protects all Tajara.

====Njarir-Ahkran Worship====
At one point, a religion was established heralding the nobility themselves as gods by certain devout loyalits, but this faith has all but been completely erased following the uprising. Individuals who were recorded to believe in or are suspected of being a member undergo persecution and even in some cases death sentences. With most loyalists either in hiding or killed during the uprising, and all places of worship destroyed, any intelligent Tajara would never admit to being, or attempt to defend, a member of this faith.

===Ethnicities===
There are four races of Tajara: the Hharar, the Zhan-Khazan, the Njarir-Ahkran and the M'sai. Each race has a common role which they play in society which their biological inclinations make them more suited for, as well as their own cultures which have formed from long histories of performing these roles in society. Tajara heavily stereotype each other based on race which is often a cause for conflict. As a result of these differences, there is a lot of racial tension between these various types of Tajara which was further exacerbated by differences in socioeconomic classes.

''For information about the ethnicities, their traits, and their cultures: see [[Tajaran Ethnicities]]''

==Factions in the Civil War==

The Adhomai Civil War has three main factions participating in the fighting.
[[File:Hadii.jpg|300px|thumb|right|Malik Hadii (Njadrasanukii Hadii), President of the People's Republic of Adhomai.]]
===[[File:PRA_Flag.png|30px]] People's Republic of Adhomai ===

Lead by President Njadrasanukii Hadii, the '''People’s Republic of Adhomai''' are considered the 'loyalist' faction on Adhomai and enjoy galactic recognition as '''the''' government of Adhomai. It claims to be the true keeper of Al’marii’s legacy. However, the PRA can be described as a Hadiist branch of Al’marii’s revolutionary ideology - that means putting the State at the top of a hierarchy of power. The PRA is a very centralized state, but in recent years has slowly been able to start making true its promises to bring revolution to the masses. With land reform, enfranchisement of women and peasantry, literacy initiatives, and the collectivization of farms and the means of production, the PRA is struggling to hold true to its radical ideals while an entrenched upper party stubbornly tries to hold onto power.

With a focus on expanding the Navy of Adhomai and ensuring greater prosperity for his supporters, Hadii has forced rapid modernization on the cities still in loyalist hands. The government's rule is marked by a lack of privacy, enthusiastic police and a pervasive secret police that leave privacy a nebulous concept to most Tajara. During the height of the war anyone suspected of supporting traitors or publicizing media critical of the government faced harsh retribution, but these practices are becoming less pervasive as wartime zealotry fades. The government is often accused of making deal with crime families in major cities to help maintain peace and get a cut of the underworld's profits. In addition, the Parliament under President Hadii is criticized for being nothing more than a puppet, providing a rubber stamp to the extremely centralized office of the president. However, life under the government, while not free, can often be stable and safe when away from the conflict zones. Under the Republic, Tajara have more opportunities than they have had historically, with the government investing heavily in its people. NanoTrasen continues to throw out large nets and bring in hundreds or even thousands of Tajara new employment opportunities in the galaxy as well as selling designs for ships and other space-faring aircraft to the People's Republic's Military. NanoTrasen is also accused of being very exploitative of Tajara laborers, but for many Tajara the company is their path to the adventure of the wider galaxy.

The sole political party of the PRA (of which all members of Parliament are members of) is the '''Parizahra Zhahrazjujz Tajara Akzatauzjauna Azahrazakahuz Hadii''', or Party of the Free Tajara under the Leadership of Hadii. Shortened to ''''the Party'''' for obvious reasons.

===[[File:DiamondALA.png|30px]] Adhomai Liberation Army | Democratic People's Republic of Adhomai ===
The most pervasive and successful rebellion came from a group calling themselves the '''Adhomai Libeation Army''', a group made up of Tajara from almost every walk of life. Opposing corporate claims on Tajaran soil and citing mismatched development and governmental negligence as the fault of humanity, they aim to "free Tajara from the new shackles imposed upon them by the corporate overlords and return Adhomai to a free, prosperous planet like our ancestors dreamed of." They named the nation they were fighting for the '''Democratic People's Republic of Adhomai'''.

During the height of the war, reality saw settlements liberated by the Liberation Army ruled by a military junta. Being a supporter of the loyalist government, or having been a collaborator, was grounds for immediate execution by firing squad. Villages often found their supplies seized by Liberation forces for the war effort, and the whole movement was a massive, tenacious military dictatorship under the absolute authority of '''Supreme Commander Halkiikir Na'ted'Akhan''', also known simply as Nated.

Following the release of their updated '''2459''' manifesto, the various regional civilian governments which formed under their rule were coalesced into '''The Democratic People's Republic of Adhomai.''' Authority is still highly decentralized. In January of '''2461''', a contested election saw Almrah Harrlala become Purrjar (or President in Basic). Contested by the military, the so-called Nated Supremacist Movement launched a putsch that was ultimately foiled by Nated himself, who appealed for the return of civilian government and then resigned his command.

The DPRA is now lead by '''Purrjar Almrah Harrlala''' who is struggling to transition what was once a militant insurgency movement, then an organized military, into a modern, democratic nation. With the help of Nated as a government minister going out to negotiate with ruling Juntas to voluntarily turn over power to civilian governments, the DPRA's future faces many fundamental changes. The Liberation Army and the DPRA does, for the most part, try to respect the basic rights of Tajara. Most Tajara under their rule don't need to worry about a secret police or being framed for a crime for civil disobedience. Criticizing the Liberation leadership is allowed, and many powerful figures laugh along with searing satire targeted at them.

Tajara from the DPRA are struggling to find recognition from the major powers of the galaxy. Its citizens (or dissidents) often must go through the dangerous path of being smuggled off planet with false visas and citizenship. In more recent times, DPRA citizens are being sponsored by Harrlala's government to go out into the galaxy openly, and to show the galaxy what Tajara can achieve on their own terms without being puppets of human megacorporations.

[[File:Ahdomai Political cities.png|300px|thumb|A map of modern-day Adhomai]]

===[[File:New Kingdom of Adhomai.png|30px]] New Kingdom of Adhomai===
The last major faction is the rebellious '''New Kingdom of Adhomai''', which seceded and declared itself a nation in 2450. The New Kingdom is ruled by a Njarir’Akhran noble line that survived the previous Revolution by remaining in hiding, owing to the efforts of their supporters. Ruled by ''' King Nazira Ka'rimah''' (Vahzirthaamro Azunja) specifically, he denounces both other factions in the civil war as illegitimate and himself as the only legitimate ruler of Adhomai. Supporters of the New Kingdom tend to be rare outside lands it controls. However, they believe strongly that the current republic on Adhomai was founded on genocide and unspeakable slaughters. The New Kingdom puts forth the ideology that Republicanism is bloodshed. The only way to return Adhomai to peace and prosperity is to learn from the mistakes of the ancient nobles and Republicans, and create a new noble dynasty. They believe this dynasty should rule as a constitutional monarchy in order to prevent abuses of power. In reality, this has proven very difficult, especially with the realities of war. Owning little territory in the north, the Kingdom's defenses are constantly besieged. The lofty titles of the nobles disguise the fact that most of the nobility of this new kingdom remain in squalor only marginally better than the peasants. Life is extremely difficult, and the Ka'rimah dynasty finds itself struggling to function with their limited constitutional powers and factional in-fighting between the military and the civilian government.

{{Navbox Tajara Lore}}
{{Navbox Lore}}
[[Category:Species]]
[[Category:Pages]]
[[Category:Tajara]]
''Human cat artwork belongs to Alexander Zavaliy, and artwork used for Al'Manq's portrait belongs to Eldar Zakirov. Al'Mari Hadii picture created by SleepyWolf''

Tajara

2019-05-02T05:26:25Z

Mofo1995: /* Factions in the Civil War */ Added NKA flag.

{{Navbox Lore}}
{{Navbox Tajara Lore}}
{{Infobox Species
|Species = Tajara
|Scientific = T. Sapiens
|Image = OldTajara.png
|System = S'rand'marr
|World = [[Adhomai]]
|Language = Siik'maas, Siik'Tajr, Nal'rasan, Ya'ssa, Delvahhi
|Politic = People's Republic of Adhomai,
Adhomai Liberation Army,
New Kingdom of Adhomai
}}
{{toc_right}}
== Overview ==

The Tajara (direct plural: Tajara – Tah-jaw-rah both singular and multiple) (adjective: Tajaran - Tah-jaw-ran) are a race of about 5.25 billion humanoids which possess markedly felinoid traits that include a semi-prehensile tail, a body covered in fur of varying shades and padded, digitigrade feet.

To apply to be Tajara, apply [http://aurorastation.org/forums/viewforum.php?f=28 here].

Additional information: [[Adhomai|Adhomai]] [[Notable Tajara]] [[Tajaran Military Structures]] [[Tajaran Ethnicities]]

==Heads of Staff==

Hharar and Njarir-Ahkran can be the following Heads of Staff:

* Head of Security
* Chief Medical Officer
* Head of Personnel
* Research Director
* Chief Engineer
* Internal Affairs Agent

M'sai can be the following Heads of Staff:
* Head of Security

== Mechanics ==

* Tajara can speak a number of unique languages, such as:
:- Siik'Maas. Use this in game by typing say ,j
:- Siik'Tajr. Use this in game by typing say ,w
:- Ya'ssa. Use this in game by typing say ,r
:- Nal'rasan. Only available to M'sai Tajara, use this in game by typing ,i
:- Delvahhi. Only available to Zhan-Khazan Tajara, use this in game by typing ,n
* All Tajara have claws, and will scratch with them instead of punching, dealing extra damage.
* Tajara can see much better in the dark than humans.
* Tajara are less vulnerable to harm from cold due to their fur, but more vulnerable to harm from heat.
* Tajara cannot use human gloves or shoes due to their claws and digitigrade limbs. They are only able to wear hardsuits and hardsuit helmets designed/modified for their Tajaran anatomy. They are able to wear 'softsuits' (such as non-hardsuit space suits, biosuits, and fire suits).
* Due to a long history of combined selective breeding and cultural factors, different Tajaran races have different physical qualities and attributes as well as levels of education. Visit the physiology sections of the [[Tajaran Ethnicities]] page for information about their differences.
=== Coloration ===

{| align:Center
|-
!Hharar group, usual coloration:
|[[File:H_BeaverBrown.png|300px|thumb|left|Beaver Brown (RGB 159, 139, 112).]]
|[[File:H_Kochiba.png|300px|thumb|left|Kochiba (RGB 107, 68, 35)]]
|[[File:H_Taupe.png|300px|thumb|left|Taupe (RGB 72, 60, 50)]]
|
|-
!Zhan-Khazan group, usual coloration:
|[[File:ZK_BlueGrey.png|300px|thumb|left|Blue-Grey (RGB 34, 37, 50)]]
|[[File:ZK_DarkGrey.png|300px|thumb|left|Dark Gray (RGB 30, 30, 30)]]
|[[File:ZK_Chocolate.png|300px|thumb|left|Chocolate (RGB 94, 38, 18)]]
|[[File:ZK_Black.png|300px|thumb|left|Black (RGB 0, 0, 0)]]
|
|-
!Njarir'Akhran group, usual coloration:
|[[File:NA_Orange.png|300px|thumb|left|Orange (RGB 238, 64, 0))]]
|[[File:NA_Cinammon.png|300px|thumb|left|Cinnamon (RGB 160, 82, 45)]]
|[[File:NA_Ruddy.png|300px|thumb|left|Ruddy (RGB 138, 54, 15)]]
|[[File:NA_Cream.png|300px|thumb|left|Cream (RGB 205, 175, 149)]]
|
|-
!M'sai group, usual coloration:
|[[File:M_White.png|300px|thumb|left|White (RGB 238, 223, 204)]]
|[[File:M_Ivory.png|300px|thumb|left|Ivory (RGB 205, 205, 192)]]
|[[File:M_Wheat.png|300px|thumb|left|Wheat (RGB 205, 186, 150)]]
|[[File:M_Silver.png|300px|thumb|left|Silver (RGB 192, 192, 192)]]
|}

== Biology ==
To the average human, the Tajara share many similarities with Earth felines; however, when looked at from a purely scientific perspective, this description is largely superficial. Unlike terrestrial felines, the Tajara are both omnivorous and bipedal. Their bodies are almost entirely covered in a thick coat of fur that is extremely good at insulating them from the extreme cold of Adhomai. The layer of body fat and fur is designed to trap body heat in an efficient manner. There are only a handful of areas where fur is not present, those being on the palm of their paws, the soles of their feet, and a number of various orifices as well as a small area around their eyes.

Occasionally, the fur around a Tajara's neck is known to grow into a shaggy 'mane' of sorts, giving them a distinct look not unlike a terran lion. This hair tends to be much stronger and a great deal more wiry than the rest of the fur on a Tajara's body. Some Tajara tend towards monochromatic bodies while others have multicolor or even calico fur patterns. These designs depend heavily on the genetics of the individual's parents, much like hair and eye color. Because of this, some parents are utterly incapable of producing multicolor children. Designs including flat colors, stripes, spots and most conceivable combinations have been recorded by scientists both Tajaran and human. A male Tajara is somewhere between 145 cm and 185 cm in height, while the mean body mass is between 55 kg and 90 kg. Females tend to range between 135 cm and 185 cm in height, with their own weight somewhere around 35 kg to 75 kg. As such, both their body weight and height is roughly comparable to the average human. A Tajaran fetus only takes six months to mature, and Tajaran children likewise mature rapidly, reaching the full extent of their growth by 15 or 16. This rapid maturation has a profound effect on the lifespan of Tajara, as only with modern medicine have Tajara reached ages above 70, with the oldest living Tajara being 84 years old. Most Tajara retire at age 60 when they are too old to work in any capacity.

===Tajaran Evolution===
The Tajara evolved as a predatory, cave-dwelling species upon their home planet of Adhomai, and as a result they have a pair of fairly large, well developed eyes that are forward set. These eyes are comparable to those of humans, but they are more effective in low-light situations due to the Tajaran ancestors having to hunt in dark cave tunnels. Tajaran eyes are set above a slightly elongated structure comprised of hard bone similar to a muzzle on terrestrial creatures. Their pupils are large and capable of contracting significantly faster than most other creatures, both sapient and otherwise. This allows for a considerable degree of low light vision, however they have a thin reflective layer which has the side-effect of appearing illuminated in the dark.

The Tajaran dental structure was at one point in their evolutionary history once geared for a carnivorous lifestyle, but has since evolved and shifted towards a more omnivorous role. Tajara have sharp, needle like teeth in the front of their jaw which are quite clearly geared to tear meat; the further along the jaw line one goes, teeth similar to human molars reside behind the sharp canines, evidence of the change to an omnivorous diet. Evolutionary biologists believe that predecessors to modern Tajara had rough tongues with few taste buds in order to facilitate eating raw meat. The contemporary species has evolved out of this a long time ago in conjunction with becoming omnivorous, and so they now have softer tongues with a full sense of taste. Atop their heads, Tajara have a pair of deft, normally erect ears that are capable of a wide range of motion. They can rotate to roughly ninety degrees, capable of even being able to fold back almost entirely onto the skull if needed.

===Extremities and Sleep Cycle===
Tajaran extremities, specifically their hands and feet have five digits, and are generally the same shape as human extremities. However, they are slightly stubbier in appearance, though still dexterous enough to be useful. Tajara employed in more professional roles such as engineers, architects, or other occupations that require dexterous manipulation often find themselves with filed down claws, reduced to a smooth end in order to allow easy usage of standard human based technology. This is a task that Tajara tend to do reluctantly, given that cutting too short is incredibly painful and will expose nerves to the air. Normally, these claws are non-retractable and grow from the fingertips, usually measuring around 1-2 centimeters.

The sleep cycles of the Tajaran species are one of their most scientifically curious features. A normal waking period is somewhere between thirty six and forty eight hours, with a subsequent twenty to twenty eight hours of sleep. Normally, the waking period is spotted with three to four fifteen minute naps in order to keep the Tajara refreshed and alert. This is universal on all worlds with Tajaran living upon them. Tajara are capable of great feats of intelligent, dedicated work but this is physically exhausting, which renders them utterly mentally and psychologically exhausted. Those that do not enter their sleep cycle properly may find themselves groggy, aggressive, paranoid and disoriented until their circadian rhythm is righted.

===Tajaran Build===
[[File:Cats.png|400px|thumb|right|An artist sketch of Tajaran dimorphism, builds and general stance.]]
In comparison to most other known species, the Tajaran body is designed to specifically be more flexible, lithe and slender despite their thick insulation. A handful of Tajaran ethnicities do not exhibit these traits and instead manifest increased muscle size, strength, or bulk. Tajara are sexually dimorphic; females have more elongated muzzles, shorter ears, as well as more petite forms, and their distribution of body fat is entirely different than that of a male. Females do not exhibit visible breasts until pregnancy, at which point they swell in order to provide for young. Males are in general taller, have broader shoulders, bigger hands and feet, and more pointed ears.

Tajara are built for the extremely low temperature environments that are incredibly common on Adhomai, giving them remarkable cold resistance. However, this gives them a tendency to overheat in more mild environments. To avoid this, most Tajara will dress lightly in warmer environments such as those on human installations or tropical worlds. Forgoing the usual layer-like clothing, these Tajara resign themselves to thin clothing. Those who find themselves confined to bio suit or radiation suit for extended periods of time will end up feeling extremely uncomfortable and perspiring heavily.

==Social==

Native Tajaran names are usually difficult for humans and other species to pronounce properly; as such, older Tajara prefer to take names (whereas young Tajara are given them at birth) that they find they themselves are able to pronounce and are also phonetically pleasing. For many, these are names derived from Arabic or Russian backgrounds, as they are the easiest for their inhuman mouths to pronounce. Traditionally, Tajaran names included the name of the dynasty they served, and some Tajara carry over this tradition and have their 'middle' name be their dynasty's name.

As with all other species who work in Human-centric environments. Tajara are expected and required to have passed a prerequisite test to test their comprehension of Tau-Ceti basic, the operating language of NanoTrasen and most transstellar corporations, in addition to most major sovereign entities. Admittedly the passing levels of these comprehension tests are quite low, but are high enough to ensure basic conversation between what will likely be a multi-species crew. However, private communication in Siik’Mas or Siik’tajr is not forbidden by NanoTrasen regulations and is often used to hold conversations between Tajara on the crew.

Though there are a variety of languages used by the Tajara, among the foremost of this vast plethora of languages is Siik’mas and Siik’tajr.

'''Siik'maas''' is theorized to have been the ancient language of the Tajara, the 'religious' language shared between most Tajara from their onset as a species. Despite Tajaran society evolving to a point where religious devotion became less encouraged, the universal service language used in all churches and worship sessions became the most common for Tajara and almost every Tajara knows how to speak it. It has been taught as the primary educational language amongst most Tajaran ethnicities since the Renaissance era and continues to be the most prevalent language on Adhomai since.

It is capable of being spoken by a learned human, as it is not as reliant on body language as Siik'tajr or the other native languages on Adhomai. However, just as Tau Ceti basic is difficult for Tajara to master given their muzzle structure, Siik'maas is the same to humans, since they lack the proper biology to perform certain inflections properly. Despite it focusing more on spoken word than others, some of the vocabulary requires subtle body movements that are challenging for humans to grasp, no less perform. Even if one were to learn these movements, they tend to be sluggish and slower, giving the speech a sort of 'drunken' feeling. Tajara speaking this over the radio often find themselves in similar positions.

Siik'maas is the federal language of the People's Republic of Adhomai. However, several groups of Tajara ranging from scholars to traditional followers of the old ways are attempting to revive older languages such as Nal'rasan, Delvahhi, Ya'ssa and other such languages.

'''Siik’tajr''' is the opposite of Siik’mas completely. A recent construction, it has seen more use recently following the overthrowing of the plutocracy. It was birthed from the necessity for a language that was difficult for law enforcers to understand, enabling revolutionaries to converse privately without having their conversations monitored or overheard. Revolutionary radicals have been a part of Adhomai's history for a long while, but were always small; however, when the Great War broke out, Siik'tajr saw widespread use by rebel forces during military operations similar to Navajo radio operators. It is a combination of Siik'mas and the more body language inclined Nal'rasan, a language traditionally used by hunters. It is not normally used in daily life due to its complexity, it is often maintained as a secondary language, especially for families who fought in the Great War.

Pro-human groups within Tajaran society have repeatedly attempted to push Cyrillic or Latin alphabets as 'easier to use' rather than the native Tajaran alphabet. However, the vast majority of Tajara use the old Siik alphabet and it is the federally enforced alphabet taught in schools, the original alphabet learned Tajara have been using for centuries. It has undergone certain modifications since the Great War to remove the influence of the plutocracy, and has made a widespread comeback with increasing literary levels among the Tajaran public.

Tajara have a strong biological inclination to roll the “R” sound, extending it. They also tend to refer to themselves in the third person perspective instead of the traditional first person ( “He has completed his work" instead of “I have completed my work") though Tajara who have spent a large amount of their lives in space or among other species may overcome this trait with great difficulty. Most Tajara will only speak to someone in the first person if it is someone they trust substantially. The occasional “slip up” can still be expected however, as being surrounded by a mostly Human crew can occasionally confuse them into using first person. The second person perspective is used in many regional dialects and does not imply any intimacy, however many Tajara prefer third person even in these cases as a preference. First person perspective is often used in the context of speeches or addresses to large populations in order enhance the rhetorical impact.

==Culture==

=== Fashion ===

Throughout Tajaran history, fashion has remained relatively simple. Extravagant vestments fabricated from silk and other high-quality animal hides were restricted exclusively to the nobility, and standard Tajaran peasantry had little time to choose their uniforms, usually donning overcoats made of rough fabric and patches of animal hide. The fluffier the design was, the wealthier a noble was considered.

Given the hardships of Tajaran life and the constant need to do work by hand, the peasantry came to favor practical, well insulated clothing rather than fanciful designs; they were also cheaper to weave, which made things easier on the weaver. Underwear usually came in the form of long-sleeved pants and a shirt typically woven from thick animal furs and plant fibers and is used as the inner most insulating layer. Then, a Tajara would overlay multiple garments to create several layers of insulation to stop the loss of body heat. Thick, full-length skirts, pants, and shirts were favored by the peasantry, all in dark colors to retain heat better. Typically pre-discovery and even post-discovery modern clothing consist of thermal underwear, pants for men or long, heavy skirts for women, with thick sweater-like shirts and fur cloaks.

The feared enforcers of the nobility wore great suits of armor designed to seal the user inside, creating an environment that was completely isolated from the harsh snows of Adhomai. Build for brute strength rather than comfort, the helmets of these suits made no room for Tajaran ears. These 'Enforcer Shells', as translated from Siik'maas, were usually brown or olive in color, with slit visors that masked the wearer's face.
[[File:Government_Officials.jpg|thumb||Typical Government Official wear.]]
Today, the Government Officials of the People's Republic of Adhomai are usually seen dressed in olive military fatigues, occasionally donning a commissar-styled cap. These caps are usually styled with small rosettes to signify authority. When in especially cold weather, officials usually layer on black trench coats and scarves rather than wearing the outfits of the lower class.

The lower and middle class of the Tajara are better heated by proxy, and can comfortably wear flat caps and long sleeved buttoned shirts for warmth when working in their factories rather than excessive garbs. When outside, typical Tajara will wear bomber jackets or fur coats with additional fur padding on the interior to better trap heat, paired with traditional slacks. Headwear for these working class citizens usually comes in the form of full head scarves to keep ears warm when in the wilderness, and standard soft and flat caps within cities.

=== Cuisine ===

Similarly, due to the cold temperatures of Adhomai, Tajara favor warming or hot food that can be consumed quickly before the freezing winds can cool the meal off. Porridges, soups, and chowders consisting of diced meat and vegetables for flavor was the usual meal of a working class Tajara, coupled with some bread and water or ale. Pre-industrial Tajara used to have community meals around bonfires to keep their food from cooling off too much, and almost all of their food source came in the form of porridges and oats. However, with the introduction of new technologies - such as higher quality insulation and home heating systems - Tajaran cuisine is being experimented with by chefs who are no longer restricted to compensating for the naturally low temperatures of Adhomai. Historically, culinary creations were reserved only for the nobility, who had better heated homes than the peasantry and more leeway was offered towards not having your meat turn blue in front of you.

===The Arts===

Of all arts, music is one of the most highly valued by Tajara. Stemming from the long-standing ban on most literature in their society, song and dance remained one of the only ways for Tajara to express themselves through words. Composers and musicians were traditionally held in high regard amongst Tajara, and in place of books the fanciful song-stories of traveling bards were one of the few ways the public could remove themselves from their lives.

Theatre was also equally important in the life of a pre-discovery Tajara. Given that, with the lack of books, there was little to keep your usual worker entertained, the ability to watch and enjoy a riveting drama or hilarious comedy was heaven. Theatres and performing halls can be found in almost every Tajaran village, and are often constructed to rival even the main seat of town council or government in architectural beauty. For example, the D'na'tel Hall in the Tajaran capital was one and a quarter larger than the seat of government prior to human sanctioned expansions. Dating back to the late Renaissance Era, it was constructed from high quality marble and many sculptures of characters and scenes from various popular Tajaran plays were meticulously hand-carved into the walls by sculptor Nasir Ka'nira.

However, literature itself - that is to say novels - have never been looked kindly upon by the Tajara public. Though this closed way of thinking is starting to shift with the greater introduction of literacy amongst Tajara as a whole, many elders still harbor bitter feelings about books in general. They were almost universally considered a symbol of oppression and luxury by pre-revolution Tajara, given the fact that only the nobility were taught en masse how to read, and that every family had it's own private expansive library that even learned peasants had to pay out of pocket to access. This led to a widespread destruction of much of historical Tajara text following the uprising, as revolutionaries took it upon themselves to purposely gather and burn whatever books they could after taking a noble stronghold.

=== Military ===

The military hardware of the People's Republic of Adhomai lands somewhere close to what humankind used in the early 1900s, though the transition to energy weapons has already been made. Clumsy overheating handguns and rifles that slowly fire long bolts of concentrated energy are used by high ranking soldiers or special operatives, but their durability is dubious in comparison to the mass-produced, single shot or bolt action rifles that the majority of Tajaran soldiers use. In recent years the People's Republic has largely replaced bolt action rifles with fully automatic Tsarrayut’yan rifles, however these suffer accuracy issues at longer ranges. Bayonets are heavily relied upon in close quarters combat rather than Tajaran model submachine guns, which are expensive in the eyes of the People's Republic and jam easily in the harsh terrain of Adhomai.
[[File:Williamsbrowning01.jpg|thumb||The Tui'ad "Icelance" laser rifle.]]
Heavy infantry weapons like heavy machine guns used to come in the form of heavy, hand cranked gatling emplacements with a heavy emphasis on frontal gun shielding. These HMG emplacements are extremely deadly in comparison to the slow firing rifles of foot soldiers, and are usually countered by Tajaran artillery or laser weaponry. Most squads of Tajara now carry a mixture of top loading magazine fed light machine guns or quicker firing belt fed LMGs.

Tajaran artillery is where the cunning of the People's Republic engineering shines, and many mountain ranges of Adhomai are lined with artillery guns the size of the mountains themselves. These weapons fire devastating artillery rounds capable of leveling small camps with a single shot, let alone a barrage. Artillery vehicles and mortar teams are almost always deployed in tandem with Tajaran infantry in order to shell enemy entrenchments and positions, and many Tajaran tacticians utilize artillery as their main killing force. These weapons are the pride of the People's Republic, and their nightmare if lost to enemy hands.

''For more information, see [[Tajaran Military Structures]]''

=== Education ===
Tajaran institutions for education are woefully behind their counterparts in other species. Historically, Njarir-Ahkran were often the only ones who became literate. Historians theorize this is tied to their alleged rise to nobility through their positions in early theological organizations. Officials from each faction agree that religious education has dominated most of Adhomai's academic history with heavy evidence from religious books which were largely able to survive the mass destruction of books by being sheltered in mosques. Disagreements among academics arise when discussing the evolution of primary schools, secondary schools, and universities. Academicians in the New Kingdom of Adhomai assert that these institutions began to rise thousands of years ago during the Adhomai Renaissance and downplay the role of the nobility's suppression of educating the masses. However intellectuals in the People's Republic of Adhomai and the Adhomai Liberation Army assert that these institutions were disingenuous social clubs at best and that schooling and formal education did not begin to arise until five hundred years prior. Hard information on the curriculum of pre-war institutions outside of theological institutions is difficult to find, however archaeological evidence tends to support arguments that there was a heavy focus on the arts- especially musical. Some artistic Hharar who lived before the war give accounts on nobles providing large patronage for painters such as in the modern sense with Al-Manq, but also for lavish concerts, operas, and ballets. Sculpting also came into prominence as evidenced by the intricate detail of various statues and gargoyle-like protrusions from an array of buildings in Nal'Tor and especially on the capital building in The People's Square: the aptly-named Steeple. Regardless of the details of pre-revolution educational institutions, the current face of Tajaran education outside of seminaries is primarily technical schools which focus on preparing young Tajara to work the various labor jobs around Adhomai.

''See also [[The Nal'tor College of Career Excellence]].''

=== Marriage and Relationships ===
Historically, the peasantry made due by uniting themselves as a workforce which has bred an intimate inter-person relationship among the families of most villages, towns, and cities. Regardless of the size of the population, pre-uprising Tajara were often well acquainted with families that may have lived on the other side of town. Arranged marriages were extremely common and were ways to improve relationships among families. However, this traditional practice has met with extreme criticism following post-uprising debates. The practice of arranged marriage was not feasible following the first revolution which effectively eliminated a generation of adult Tajara. This created a generation which had to largely create their own marriages, many of which passed on this emerging cultural norm to the next generation. Although permanent pairing of Tajara is often colloquially referred to as "marriage" due to humanizing influences, there are a handful of different technical terms for it depending on the religion of the Tajara involved. S'rand'marr worshipers are typically brought together in mosques by their local Brother of the Sun in a ceremony which symbolizes and glorifies S'rendarr and life. Their equivalent of Marriage is called "'''S'rendal'Matir'''" (The life of S'rendarr), named for the idea of continuing the life which the sun god S'rendarr celebrates. Tajara under the worship of Ma'ta'ke have a less celebratory and less ritualistic ceremony, instead having a simple meeting between families with a clergyman to proclaim the lovers "'''Zrrazhil Ekrratul'''" (Continuation of the families), named for the simple notion of propagating the blood of the families involved.

Because of the Tajara's history as a repressive, conservative species, they have not grown too open-minded or liberal - unlike humanity's progressive views for example. Overt displays of affection and especially homosexuality among Tajara are looked down on and treated as a deviancy. There exists discrimination and bias against other races of Tajara - particularly against Zhan-Khazan for their purported low intelligence and rebellious tendencies. As a result, Tajara generally avoid interbreeding between races. An extension of the racism which prevents Tajara from breeding outside of their race can be found in the general public's extreme revulsion to notions of relationships outside of the species, an act which is considered an intolerable fetish to most.

==History==

[[File:Adhomai2.png|thumb|alt=The Tajaran homeworld.|Adhomai was ravaged by warfare and more than forty million deaths have been recorded as a result of the Great War.]]

===Nobility and the Ancient Past===

For as long as most Tajara care to remember, Adhomai had always been under the rule of nobility. The most dated historical text that still exists in Tajaran possession dates back at least four thousand years and still talks about 'serving their masters', so many historians agree that the trend of blood rule is more deeply-routed in Tajaran existence than was previously considered.

The ancient past of the Tajara is poorly documented and historical texts are almost non-existent; meticulous combing and destruction of educational material by millennia of harsh rule resulted in total atrophy of most scientific arts in Tajaran society. Top Tajaran scholars in this day and age have theories that life on Adhomai. Little is known about Tajara civilization before '''2500 BCE''' Galactic Standard Time.

Tajara society and government in the '''2000 BCE''' era Galactic Standard Time was similar to human feudalism. Several towns, villages, or the rare city would be organized under a single Lord. Nobles of fiefs commonly collected together to make crucial decisions about the ownership or trade of lands. If agreements were not met and conflict between two lords was imminent, decisions would commonly be made through staged combat. In these trials, groups of peasants were equipped with matching weapons and faced with the task of killing off the opposition. These displays were considered a quality source of entertainment, usually in which nobles would come to an agreement on their previously unsettled differences -- before staying to watch the peasants slaughter one another. Peasants had little choice in these matters, and all dissidence was met harshly and fatally at the hands of the Nobles' Enforcers - trained agents (commonly of M'sai descent) who fought for the nobility of Adhomai in exchange for relative freedom. These Tajaran enforcers kept the peasants of Adhomai's lands repressed and powerless through shock and terror.

What is known for sure, however, is that tension and violence had slowly been increasing over hundreds of years between the populace and their fellow noble families.

Based upon limited information gleaned from literature and art that survived various purges, many Kingdoms across Adhomai had been violently replaced with highly centralized theocracies, which are first mentioned in historical texts in the '''1300 BCE''' era, with the religious states focused around the worship of the suns and their leaders as direct avatars of S'rendarr. The vast majority of Tajaran noble families stemmed from religious leaders with divine right to rule.

===Tensions Rise===

Tajara historians believe that global violence spilled out across the planet between the theocratic kingdoms and the other scattered noble families in the '''1500 BCE''' era. These religious leaders clashed and either pitted their followers against one another. The noble leaders continued to fight and inter-marry until the ruling families had become exclusively '''Njarir’Akhran'''. Over time, the nobility as it were slowly began to lose their religious inclination, adopting more traditional civil institutions and a relaxation of the church's control which gave way to state control. This indirectly created the '''Adhomai Renaissance''' in the '''1,100 BCE''' era. Religious worship of the noble families had been dropping steadily in conjunction with the lower influence they had upon the other nobility. It was this period that historians believe the overwhelming control of the noble families flourished and solidified into what it was prior to human contact.

Literature was heavily regulated from this point as the ruling Njarir’Akhran reacted harshly to the '''Adhomai Renaissance'''. Enlightened philosophers had taken advantage of the creation of the short-lived printing press in '''955 BCE''', who's blueprints and designs were quickly destroyed and would not be recovered until several hundred years later. The rise in literacy and philosophers questioning the very concept of "right to rule" was deemed dangerous to the health of noble rule. Scarce written literature the Adhomai Renaissance spawned sculptors, musicians, and artists. However, rather than their works being presented for public viewing, they were collected by noble families and only a handful were shown outside of their palaces for the peasantry to admire.

Following this era, tension between the nobility and the peasantry began to steadily increase, believed to have stemmed from increasingly harsh rulers and laws. Technological and cultural knowledge and breakthroughs had slowly begun to trickle down from the noble families to the peasantry. The blueprints for the '''printing press''' had managed to be smuggled out of a private noble library in '''173 CE''' and many underground libraries for the peasantry began to pop up in cities and towns across Adhomai. Eventually it became a capital crime for a peasant to even own a copy of an unapproved text.

Adhomai underwent a form of industrialization with the creation and proliferation of the steam engine in '''1226 CE'''. However this only forced the Adhomai peasants into harsh new labors digging in mines and working 18 hour days building rail lines for private use by the Njarir’Akhran nobility. Laws were soon enacted that banned any non-Njarir’Akhran from utilizing electricity or riding on trains.

This trend of noble's hoarding new technology or innovations at the expense of the peasants continued until human contact.

Thirty years prior to human discovery of Adhomai, the deep-seeded mistrust between peasants and nobles had reached an all time high. The Tajaran species was trapped in a technological bubble forced upon them by their nobility. At the height of their industrial revolution only a few years prior, the leadership at the time became increasingly wary of the unification of many Tajaran workers who demanded greater rights, seeing themselves in what could be accounted as another 'Renaissance' era and result in more 'enlightened' individuals straining their already crumbling control over the populace.

The realms of education, science, and luxury found themselves under severe restrictions, and your basic Tajara was forced into almost twenty hour work days with minimal time afforded for eating and sleeping on the job. Analysis of the noble houses proves that during this time in Tajaran history, the nobility had never been worth more in Sol credits than previously. This is largely attributed to the fact that rather than modernizing Adhomai the nobility had seen fit to confiscate and use these fruits of scientific thinking for themselves.

Automobiles are considered one of the best examples of this. The first automobile is recorded to have been created in '''2012 CE'''. Using a combustion engine much like primitive human vehicles, with extra anti-freezing measures and thick treads, one of the first fully functional automated cars had been produced by a collection of Tajaran engineers and scientists, at the behest of the nobility. These large creations were considered by many older Tajara to be a symbol of negligence and gluttony by their leaders. Workers were never provided with such things; they were forced to transport themselves through Adhomai's harsh winter conditions on foot or by using specially designed 'snow bicycles', regardless of how far away their place of work was.

Further restricting the rights of the individual Tajara was enacted by a furious nobility after several instances of violence against Njarir’Akhran, but specific information on these incidents has been lost. Legislation was introduced against 'workers unions' as well as any sort of illicit groups; a permit was required to form anything from hunting parties to agencies. In this whirlwhind of political turmoil, a fresh generation of Tajara were growing up, deprived of what most humans consider to be 'basic rights'. As they grew older and angrier, the nobility saw fit to continue tightening their control over their subjects until a civil war was almost inevitable. Like a powder keg ready to blow, only a single spark was needed to light the flame.

===Human Discovery===
This came in the form of human discovery in '''2418 CE'''. A Sol Alliance funded expedition into the Tajaran home system discovered the pre-space age species and their homeworld of Adhomai. Lush with untapped resources and potential workers, Adhomai was an attractive prospect for many human super corporations, especially NanoTrasen. Because of their slow technological progress, most of Adhomai's valuable minerals remained untapped by mining or drilling. It was due to this that several corporations attempted to insert themselves into the dealings of Adhomai.

However, the nobility felt incredibly threatened by what they considered 'intrusions' by humanity and completely refused them diplomatic access to their planet. The Alliance stepped in, initially unwilling to interfere in a pre-space age society and, reluctantly, the super corporations were forced to abandon their wishes to stake claims on Adhomai's resources - at least in the open. In the year '''2420 CE''', a group of Tajaran intellectuals - considered rebels by the state - were shuttled off-world by a still unknown entity. Given asylum in the Sol Alliance, they met and discussed much with human scientists and officials. Tensions between the Alliance and Tajaran nobility rose after such an event and they accused the humans of harboring terrorists.

Eventually, these rebels were returned to Adhomai with supplies and weapons. Fed with new ideals of personal freedom and 'rights afforded to all' by their influential human friends, the seeds of revolution were sowed among the Tajaran populace, spread by word of mouth. Workers, doctors, teachers, even soldiers that were questionably loyal to the nobility were swayed by these promises of freedom and equality. Meetings in the basements of dark taverns or barns were common, and relations between the nobility and their peasants were at the lowest ever recorded in Tajaran history.

===The Uprisings===

It took little more than a year for a formal uprising to be staged. On '''2421 CE''', after the nobility had captured one of the original Tajara that had been shuttled off world, he was sentenced to be publicly hanged by the neck in front of their peasants to show just how serious they were about keeping control. Ultimately, many historians believe this to be a highly egregious mistake. Rebels in the audience, armed with advanced off-world weapons, proceeded to open fire on loyalist forces and kill a nobleman in the process. This event, called the '''D'as'ral Massacre''' (so named for the city it took place in) by the nobility was all the excuse they needed to enact martial law.

[[File:Emplacements.jpg|thumb|alt=Gun emplacements.|Wartime photo capture of rebel artillery emplacements.]]

However, they found themselves in a cornered position. Weapons and supplies were being shipped in off-world by mysterious benefactors, and their collections of scientists and engineers had either fled to safety being noblemen themselves, or took up arms and joined the revolution. Without significant scientific presence to deconstruct or understand these new human weapons or support the war effort, the conflict resulted in a string of rebel victories that drew closer and closer to the capital cities of each providence. Fighting was extremely fierce and atrocities were recorded by both sides.

Among the noble families, the largest and nearly the most powerful was a dynasty called the 'Hadii'. Their castle was amongst the best defended in the region and the battle to take it was waged for six months of non-stop fighting. As it became increasingly clear to them that they were eventually going to be overrun, the Hadii struck a deal with the rebel leader; in return for complete immunity from the war, as well as persecution, they afforded the revolutionaries with unique tools and even blueprints of other families' castles, pointing out weak points and infiltration spots.

It was this turn coating that tipped the revolution in favor of the peasantry. Armed with this new information, they made use of radio systems previously restricted for nobility to methodically and ruthlessly end their uprising by murdering most of the noble families and whatever soldiers and civilians remained loyal to them. By '''2431 CE''' the revolution had finally come to an end with a total of more than '''92 million casualties''' with more than half of that being loyalist forces, and '''40 million civilian deaths'''. Many Tajaran cities and villages were utterly destroyed by vicious fighting as well as bombardment by uncaring nobles. A informal ceasefire was declared between the factions, though skirmishes were still common.
[[File:Anti-noble_Propaganda.jpg|200px|thumb|right|Famous People's Republic Propaganda painting which depicts a pouf noble walking a Tajaran worker like a pet.]]

===Outcome of the Revolution===

Following this total upheaval of Tajaran society, rebel leaders met with Hadii noblemen and discussed how to form a government, given that only the Hadii were experienced with ruling. Human corporations took express interest in this; the Hadii were one of the few noble families that saw profit in human stakes on Adhomai, and many back-room deals were made until ultimately the Hadii were placed at the head of Tajaran government in '''2432 CE''', and ushered in a new federal republic: '''The People's Republic of Adhomai'''. The Tajaran public was markedly distressed by this turn of the events, and fearing another uprising, human intervention again helped defuse the situation. The Hadii promised that it would not be like it was before.

NanoTrasen, suspected by many conspiracy theorists to be behind the funding and supplying of Tajara during the war, holds claim to most of Adhomai and has a monopoly over most of the planet's valuables. Collaboration between them, the Sol Alliance and the Jargon Federation has resulted in more technological advances in Tajaran society recently than ever before in their recorded history. Approval ratings for the current leadership rose in response.
[[File:21208e532f75dbdf919f48ff4ddac508.jpg|300px|thumb|right|Potrait of President Al'Mari Hadii, taken one week from his death and done in the [[Notable Tajara|Al'Manq style]].]]

However, serious problems remained. '''Rhagrrhuzau Hadii''' suddenly began to back out of the People's Republic's agreed upon business deals with NanoTrasen, all of which saw a massive amount of Tajaran natural resources exported. Citing humanity as greedy and destructive, '''Rhagrrhuzau Hadii''' made clear his intentions to make Adhomai independent until it was ready to take on the burden of interstellar politics.

===The Second Revolution===

The disagreements and hatred of the Hadii republican government had led to insurrection and treachery between Adhomai's major power figures since '''Rhagrrhuzau Hadii''''s new economic policies were revealed. Many Tajaran business contractors - just recently denied their ability to sell ludicrous amounts of natural resources and workers to the massive human megacorporation, NanoTrasen - felt threatened by the reforms of the Hadii government and its first President, '''Rhagrrhuzau Hadii'''. On '''2451 CE''', during a military parade, President Rhagrrhuzau was assassinated by a young Zhan-Khazan radical. A known secret service agent of the People's Republic, the radical was sentenced to death for his treachery, brought on by the violent tendencies of his Zhan-Khazan genetics. His brother and vice-president '''Njadrasanukii Hadii''' quickly assumed the office of the presidency and immediately passed brutal laws that punished Zhan-Khazans and 'subversive elements'. NanoTrasen was invited back to Adhomai and menial workers were sold en masse to NanoTrasen workplaces while the rights to the bountiful natural resources of Adhomai were sold off to NanoTrasen. Public hangings and firing squads became the norm once again.
[[File:Godblessalmarihadii.png|thumb|400px|left|Picture taken by the Adhomai Chronicle moments before the Assassination of Rhagrrhuzau Al'Mari Hadii. The single most defining moment of this generation of Tajara.]]

Many military generals that had fought for the Republic soon defected under the banner of the Adhomai Liberation Army, the leader of which being '''Rhagrrhuzau Hadii''''s old friend and ally, '''Halkiikijr Nated'Hakhan''', and Adhomai found itself embroiled in yet another global conflict that continues to this day. "His gun was on stun" became the rallying cry of Rhagrrhuzau's fiercest supporters, "Hadiists," as they alluded to how he not only left himself greatly vulnerable during the parade, but had even left his energy pistol on stun while he was assassinated.

===Adhomai Today===

The Tajaran home world has suffered plenty in the three decades since the end of the First Revolution. With the sudden injection of advanced technology into their relatively simple life, the discrepancy between modernized cities and outlying areas could not be more obvious. While the Tajaran capital boasts the most modern developments with sleek skyscrapers, advanced connections and phone lines, as well as hospitals and schools, the further you get from the larger cities, the more apparent it is that things are not quite so flashy. Expanding infrastructure remains difficult, as most public funds are seized for use by the military or used to repair infrastructure damaged by shelling or bombings.

There is a steady stream of money being fed into the People's Republic of Adhomai. NanoTrasen, as per it's agreement with the president, have set up mining and logging operations on Adhomai using the local work force for the most menial of tasks. In return, company funded clinics and schools are slowly being spread out and build in the needy areas. Tajaran resource operations are now all but nonexistent; the buildings that were once part of the nobility's small gathering efforts have now been refurbished and are being used by NanoTrasen.

Literacy has risen to its all time high on Adhomai, and with the assistance of the Alliance, teachers have been brought in from off world to educate the younger generation of Tajara. However, this number has begun to decline as the dangers of working on Adhomai are beginning to become common knowledge. Special establishments for older students have also been constructed to assist the elder generation in being brought to the same level of education, but NanoTrasen has not expressed significant interest in this; these people make up the brunt of their low-paid workforce and they want to ensure that they are kept that way.

There are still several proponents of revolution that oppose the current government, which has plunged the planet into another all-encompassing civil war that remains at a standstill today.

==Notable Information==

===Religion===
====S'rand'marr Worship====
''"By day and light of S'Rendarr, we live and bask in his warmth, happy and content. By the warmth and light of Messa, we cease breath and fall to death. Only by the love and harmony of both the Twin Gods and Sibling Suns do we live happily, and die the same. By the Twin Gods and Sibling Suns, S'Rendarr and Messa, the faithful ask for your blessing, and to please extend it to the non-faithful who do no wrong, and cast no sin."''

- The "First Prayer" of S'rand'marr Worship

There are a handful of faiths on Adhomai, but the majority religion is the worship of S'rendarr and Messa, the names of both suns in the Tajaran home system. Ancient Tajara were believed to worship the suns as gods, believing their light to be the only thing keeping the planet from freezing over entirely. Over time, this faith matured into a system of beliefs suited to the peasantry; looking down upon the acts of betraying your fellow worker and attempting to foster unity and understanding amongst its followers. It is believed by many that S'rendarr is the god of life and the day, as the bigger of the two suns, and he is associated with good happenings and is most often prayed to. Contrastingly, Messa, the blue sun, is the goddess of the night and death; whenever she eclipses S'rendarr, all followers partake in religious rituals that ask Messa to spare them from whatever ill tidings she may bring. The worship of the sun gods is dominated by an organization called the Parivara, meaning, the "Family." The head of the Parivara is Father Walid Al'qat who is based out of Sana Sahira, a holy city on the tallest mountain on Adhomai which roughly translates into the City of the Suns. The First Father of the Twin Gods was said to have made a direct link with the Gods, who gave him these laws that all of their faith should follow:

''"You shalt not harm another, faithful to the Suns or not. You shalt always show kindness to any and all. You shalt not covet the items of another faithful. You shalt not defile the body of one who now rests in Messa's Forever."''

Since the day these were declared in Sana Sahira, they have been considered the Law of the Suns. This location in the People's Republic places the Parivara in the precarious position of having to act favorably to the faction's government, however Father Walid Al'qat attempts to stay out of politics in order to avoid alienating any worshipers across borders. The Father of the Parivara is chosen by the Brothers of the Suns who serve as the priests and clergy of the faith. Devoted women of the faith can become Suns' Sisters, who take a vow of silence of silence, like the Gods themselves, and live in the Mosques devoted to the worship, tending to them in anyway needed, anything from cleaning to heavy manual labor repairing and replacing glass or furniture, to healing the Brothers, patrons and other Suns' Sisters. To cause harm to a Suns' Sister is said to be one of the most unholy things you can do in a place of worship, as they're meant to emulate the Gods themselves, silent, but strong and dependable.

====Ma'ta'ke====
The second largest religion is the worship of the Snow God Mata'ke and his cohort companion gods, which dates back to ancient Tajaran times. A figure of legend, Mata'ke is believed to have been the head of a hardy tribe of mountain dwellers which regularly came to the aid of other tribes which were constantly plagued by bandits and wild animals. He was revered as a fierce warrior capable of fighting a platoon of men by himself, but also as a kind soul for the records of his dealings with other tribes show understanding and kindness. He is upheld to be the ultimate Tajara- powerful, wise, and magnanimous. Followers of Mata'ke himself endeavor to emulate his grandeur, while others attempt to emulate the other gods.

In Tajaran mythology, the tribe of Mata'ke rose to the status of gods when they slew the King of the Rrak'narrr, who was also the lord and master of all Adhomai. Upon killing him, the various tribessmen all absorbed different aspects of its many powers, each becoming immortal. As the one who dealt the killing blow, and at the will of the dying Rrak'narrr's final wishes, Mata'ke absorbed the majority of the powers and became lord and master of all Adhomai. The tribe then decided that their former settlement was not befitting of their powers, and instead established themselves in a city of wonders at the "Edge of Adhomai" where they fend off malicious entities and protects all Tajara.

====Njarir-Ahkran Worship====
At one point, a religion was established heralding the nobility themselves as gods by certain devout loyalits, but this faith has all but been completely erased following the uprising. Individuals who were recorded to believe in or are suspected of being a member undergo persecution and even in some cases death sentences. With most loyalists either in hiding or killed during the uprising, and all places of worship destroyed, any intelligent Tajara would never admit to being, or attempt to defend, a member of this faith.

===Ethnicities===
There are four races of Tajara: the Hharar, the Zhan-Khazan, the Njarir-Ahkran and the M'sai. Each race has a common role which they play in society which their biological inclinations make them more suited for, as well as their own cultures which have formed from long histories of performing these roles in society. Tajara heavily stereotype each other based on race which is often a cause for conflict. As a result of these differences, there is a lot of racial tension between these various types of Tajara which was further exacerbated by differences in socioeconomic classes.

''For information about the ethnicities, their traits, and their cultures: see [[Tajaran Ethnicities]]''

==Factions in the Civil War==

The Adhomai Civil War has three main factions participating in the fighting.
[[File:Hadii.jpg|300px|thumb|right|Malik Hadii (Njadrasanukii Hadii), President of the People's Republic of Adhomai.]]
===[[File:PRA_Flag.png|30px]] People's Republic of Adhomai ===

Lead by President Njadrasanukii Hadii, the '''People’s Republic of Adhomai''' are considered the 'loyalist' faction on Adhomai and enjoy galactic recognition as '''the''' government of Adhomai. It claims to be the true keeper of Al’marii’s legacy. However, the PRA can be described as a Hadiist branch of Al’marii’s revolutionary ideology - that means putting the State at the top of a hierarchy of power. The PRA is a very centralized state, but in recent years has slowly been able to start making true its promises to bring revolution to the masses. With land reform, enfranchisement of women and peasantry, literacy initiatives, and the collectivization of farms and the means of production, the PRA is struggling to hold true to its radical ideals while an entrenched upper party stubbornly tries to hold onto power.

With a focus on expanding the Navy of Adhomai and ensuring greater prosperity for his supporters, Hadii has forced rapid modernization on the cities still in loyalist hands. The government's rule is marked by a lack of privacy, enthusiastic police and a pervasive secret police that leave privacy a nebulous concept to most Tajara. During the height of the war anyone suspected of supporting traitors or publicizing media critical of the government faced harsh retribution, but these practices are becoming less pervasive as wartime zealotry fades. The government is often accused of making deal with crime families in major cities to help maintain peace and get a cut of the underworld's profits. In addition, the Parliament under President Hadii is criticized for being nothing more than a puppet, providing a rubber stamp to the extremely centralized office of the president. However, life under the government, while not free, can often be stable and safe when away from the conflict zones. Under the Republic, Tajara have more opportunities than they have had historically, with the government investing heavily in its people. NanoTrasen continues to throw out large nets and bring in hundreds or even thousands of Tajara new employment opportunities in the galaxy as well as selling designs for ships and other space-faring aircraft to the People's Republic's Military. NanoTrasen is also accused of being very exploitative of Tajara laborers, but for many Tajara the company is their path to the adventure of the wider galaxy.

The sole political party of the PRA (of which all members of Parliament are members of) is the '''Parizahra Zhahrazjujz Tajara Akzatauzjauna Azahrazakahuz Hadii''', or Party of the Free Tajara under the Leadership of Hadii. Shortened to ''''the Party'''' for obvious reasons.

===[[File:DiamondALA.png|30px]] Adhomai Liberation Army | Democratic People's Republic of Adhomai ===
The most pervasive and successful rebellion came from a group calling themselves the '''Adhomai Libeation Army''', a group made up of Tajara from almost every walk of life. Opposing corporate claims on Tajaran soil and citing mismatched development and governmental negligence as the fault of humanity, they aim to "free Tajara from the new shackles imposed upon them by the corporate overlords and return Adhomai to a free, prosperous planet like our ancestors dreamed of." They named the nation they were fighting for the '''Democratic People's Republic of Adhomai'''.

During the height of the war, reality saw settlements liberated by the Liberation Army ruled by a military junta. Being a supporter of the loyalist government, or having been a collaborator, was grounds for immediate execution by firing squad. Villages often found their supplies seized by Liberation forces for the war effort, and the whole movement was a massive, tenacious military dictatorship under the absolute authority of '''Supreme Commander Halkiikir Na'ted'Akhan''', also known simply as Nated.

Following the release of their updated '''2459''' manifesto, the various regional civilian governments which formed under their rule were coalesced into '''The Democratic People's Republic of Adhomai.''' Authority is still highly decentralized. In January of '''2461''', a contested election saw Almrah Harrlala become Purrjar (or President in Basic). Contested by the military, the so-called Nated Supremacist Movement launched a putsch that was ultimately foiled by Nated himself, who appealed for the return of civilian government and then resigned his command.

The DPRA is now lead by '''Purrjar Almrah Harrlala''' who is struggling to transition what was once a militant insurgency movement, then an organized military, into a modern, democratic nation. With the help of Nated as a government minister going out to negotiate with ruling Juntas to voluntarily turn over power to civilian governments, the DPRA's future faces many fundamental changes. The Liberation Army and the DPRA does, for the most part, try to respect the basic rights of Tajara. Most Tajara under their rule don't need to worry about a secret police or being framed for a crime for civil disobedience. Criticizing the Liberation leadership is allowed, and many powerful figures laugh along with searing satire targeted at them.

Tajara from the DPRA are struggling to find recognition from the major powers of the galaxy. Its citizens (or dissidents) often must go through the dangerous path of being smuggled off planet with false visas and citizenship. In more recent times, DPRA citizens are being sponsored by Harrlala's government to go out into the galaxy openly, and to show the galaxy what Tajara can achieve on their own terms without being puppets of human megacorporations.

[[File:Ahdomai Political cities.png|300px|thumb|A map of modern-day Adhomai]]

===[[File:New Kingdom of Adhomai.png|30px]]New Kingdom of Adhomai===
The last major faction is the rebellious '''New Kingdom of Adhomai''', which seceded and declared itself a nation in 2450. The New Kingdom is ruled by a Njarir’Akhran noble line that survived the previous Revolution by remaining in hiding, owing to the efforts of their supporters. Ruled by ''' King Nazira Ka'rimah''' (Vahzirthaamro Azunja) specifically, he denounces both other factions in the civil war as illegitimate and himself as the only legitimate ruler of Adhomai. Supporters of the New Kingdom tend to be rare outside lands it controls. However, they believe strongly that the current republic on Adhomai was founded on genocide and unspeakable slaughters. The New Kingdom puts forth the ideology that Republicanism is bloodshed. The only way to return Adhomai to peace and prosperity is to learn from the mistakes of the ancient nobles and Republicans, and create a new noble dynasty. They believe this dynasty should rule as a constitutional monarchy in order to prevent abuses of power. In reality, this has proven very difficult, especially with the realities of war. Owning little territory in the north, the Kingdom's defenses are constantly besieged. The lofty titles of the nobles disguise the fact that most of the nobility of this new kingdom remain in squalor only marginally better than the peasants. Life is extremely difficult, and the Ka'rimah dynasty finds itself struggling to function with their limited constitutional powers and factional in-fighting between the military and the civilian government.

{{Navbox Tajara Lore}}
{{Navbox Lore}}
[[Category:Species]]
[[Category:Pages]]
[[Category:Tajara]]
''Human cat artwork belongs to Alexander Zavaliy, and artwork used for Al'Manq's portrait belongs to Eldar Zakirov. Al'Mari Hadii picture created by SleepyWolf''

User:Mofo1995

2019-05-02T05:25:30Z

Mofo1995: Added NKA map.

{{wip
|assign = Loow}}

{{Navbox Tajara Lore}}

'''I am the master of the cats.'''

[[File:Death of Sylvester.jpg]]

''Contact me with any questions about the following: [[Tajara]], [[Adhomai]], [[Notable Tajara]], [[Tajaran Military Structures]], [[The Nal'tor College of Career Excellence]], [[Tajaran Ethnicities]], [[Adhomai Economy]], [[Ma'ta'ke Gods]], [[S'rand'marr]], [[Timeline of Tajara]]''

== Scratch Pad Work:==

P'urrjar was born in 2173 to an architect's clerk and maid. Birthplace was a small harbor town called Mrrhmal on the eastern coast of Rasn'rr. Education was to become a Kraszaramalik. Attracted to military stories instead. In 2186 he became an aide-de-camp in the 3rd Alam'ard of Foot for the Archduke of Nal'Tor, an Alyad'almalik, after his mother petitioned her lord to accept him. A far richer lord than most of his neighbors on Rasn'rr, this lord had very large Alam'ards and furnished the infantry formations with support artillery batteries.
--------------------------------------------------------------------------------
During his time as an aide-de-camp, he was assigned to relay messages between the artillery batteries and the Alyad'almalik. He soon realized that dispersing the military between the Alam'ards in batteries was inefficient. After presenting deployment suggestions to his lord, the Alam'ards were rearranged so that the center of the Alyad'almalik's forces was an artillery Alam'ard with infantry alam'ards on the flanks and cavalry alam'ards on the far flanks. This was tested in a battle against the Das'nrra Empire by a coalition of memberstates to the Rasn'rr Empire on the northern coast of Rasn'rr across the channel. Massed artillery doctrine proved to be a paradigm shift which changed warfare.

== Plans:==
1.) Timeline of events from discovery of space aliens to 2459, setting the canon for the events of the first revolutionary war. <--- WIP

2.) Cities lore. Outlining the culture, architecture, and common professions of each city. <--- Regional lore is coming first, then this

3.) Elaborating on the various dance sensations on Adhomai according to region. <---- Maybe.

---4.) Canonizing cave-dwellers and tribes of cuddling cat people.--- NO way

You just lost the game.

== Helpful Maps ==
[[File:Ahdomai Political cities.png|825px|left]]
[[File:Geographical.png|825px|right|]]
[[File:AdhomaiAncientRegimesNames.png|825px|left]]

== Flags ==
[[File:PRA Flag.png]] [[File:DiamondALA.png]] [[File:New Kingdom of Adhomai.png]]

File:New Kingdom of Adhomai.png

2019-05-02T05:25:05Z

Mofo1995: NKA Map. The tree of liberty has gotta be watered wit da blood of commies

NKA Map. The tree of liberty has gotta be watered wit da blood of commies

User:Mofo1995

2019-05-02T05:24:07Z

Mofo1995: Added historical map

File:AdhomaiAncientRegimesNames.png

2019-05-02T05:18:25Z

Mofo1995: Map of Adhomai at the turn of the century.

Map of Adhomai at the turn of the century.

File:Trade Ship.jpg

2019-03-09T21:42:46Z

Mofo1995: Mofo1995 uploaded a new version of File:Trade Ship.jpg

A Tajaran trade ship.

Taken from a Screenshot in Sins of a Solar Empire, found here: http://sinsofasolarempire.wikia.com/wiki/TEC_Trade_ship

Tajara Space Capability

2018-11-27T21:10:02Z

Mofo1995:

{{wip
|assign = Loow}}
{{toc_right}}
[[File:Ships pew pew.png|350px|thumb|right|Organization of the PRA space forces.]]

== Blizzard Doctrine ==
In the early stages PRA had simply used old designs purchased from Nanotrasen, Sol Alliance, Elyra or the Frontier Alliances but very soon the PRA discovered these outdated and overpriced designs were near useless when dealing with anything bigger than a single pirate vessel as their guns could barely penetrate the armoring and shielding, having bled enough money through destroyed vessels a radical change came after a capture of 3 Civilian Transport ships by pirates, The Blizzard Doctrine was established.
The Blizzard Doctrine combines the best of PRA combined arms actions and DPRA guerilla warfare, the fast, small and aggressive craft is perfect for patrolling borders and interviewing while the Sentinel carriers provide them with much-needed support. Icelances and Headmasters are much less utilized, usually being kept in reserve unless a larger threat appears.

=== Kosmostrelki ===
The PRA has always been known with substituting quality with quantity, however, their doctrine had to be tweaked for space combat as their ships, cheap as they are, are still hard and expensive to replace for the government, this makes the Kosmostrelki one of the most trained troops in the PRA roster.
The Kosmostrelki are usually trained in Baghrar simply to instill a sense of discipline and because it’s an excellent way to learn balance in space. However their training shines in their ability to improvise on the fly, many anti-pirate actions have been saved with the creative use of duct tape, chewing gum and a pencil.
The talk among other troops is that the Kosmostrelki units have a high amount of deserters due to the nature of their job and how easy it is to run away into space, however, these statistics are unsupported.

== State Owned Civilian Ships ==
Non-combat ships are a common sight on the resource-rich Adhomai. However, no single Tajara whose citizenship is within PRA is allowed to privately own such a ship and instead, all ships are owned and the property of the PRA government. This demand does not apply to anyone outside of PRA zones of power. However, due to the fact that the PRA owns the biggest military fleet Tajara would be hard pressed to admit they're part of the NKA or DPRA, making the life of those two factions that much harder.
Foreign vessels face no such obligations and Nanotrasen mining vessels do not need to answer hailing at all.

=== Freighter ===
Tajara freighters are just like any other, big, square and with a powerful engine. However, they do stand out with one interesting feature, a powered emergency jettison. This prevents anyone from obtaining said cargo as it speeds off at incredible speeds into space. Denying the enemy valuable resources and booty. Skilled enough pilots are capable of launching said crates directly at their pursuers. (Pirates have to risk following cargo flying off at incredible speed and possibly spinning through space or following the ship.)

=== Transport ===
Civilian Transports are a rare sight in the star system, but they do exist. Combining powerful engines for a quick getaway with thick armoring, they easily outrun and outlast any raider in deep space. This has come at the cost of navigation and comfort as ventilations would provide unnecessary weak spots, this has led to numerous cases of heatstroke in these cramped ships.

=== Mining Jacks ===
A skipjack would usually be seen in the hands of smugglers but Tajara has developed an ingenious way of mining. Instead of using a large ship to destroy or land on an asteroid this small, one-pilot and pointed Jacks simply strip away a part of said asteroid and take it back to a mining station or a larger mother-vessel where is it processed. This enables them to mine even in very dangerous areas as they can quickly flee to a base.

=== Scrapper ===
The most common sight in Tajara space are scrappers, two or three crew ships which serve to magnetically grip any debris or damaged ships and tow them to a spaceyard, where they’re either scrapped or repaired. There is a rumor floating around about these horseshoe-shaped ships, that the crews steal orbiting craft with the crew still inside.

== State Owned Military Ships ==
Realizing that ship-combat is completely different from for example naval or ground combat, the PRA developed a unique doctrine titled “The Blizzard”, it is defined by quick hit and run attacks of smaller interceptors while larger ships stand back as fire support, softening the targets.
This has led to Tajara having probably the fastest but least durable fleet in the known space, perfect against pirates, mercenaries and other wild groups of space.

=== Fang ===
Fangs are one-pilot interceptor with practically zero shielding, armor and wielding ineffective weapons. Their design copied from Alliance corvettes saw frequent refits, most recently to fit the Blizzard doctrine these ships have been fitted with a number of cannons and small un-guided rockets for quick, brief and destructive hit and run attacks.

=== Snowstorm ===
The newest addition to the Tajaran roster, the Snowstorm is a two-crew, pilot and an operator, ship with curiously delicate and expensive technology. Employing a wide range of signal disrupting devices purchased from the Eridanian security companies, these ships are, at full power, capable of knocking out even the impressive Vaurca ships and Sol Destroyers with their hacking capabilities.

=== Icelance ===
A perfect reflection of Tajara doctrine, these ships are akin to artillery. Shaped like a rifle barrell this long tube of a ship actually packs quite a surprising punch.
The secret of the ship rests in its reflection of PRA infantry doctrine, artillery. Packing magnetic accelerators along its whole length the ship, packed with titanium rods, fires said rods at supersonic speeds. Impossible to shoot down by gunners due to their thin profile, undetectable by conventional point-defense and maximum impact force on a minimum area combine this into an extremely deadly weapon.
However with near zero armor, limited battery allowing about one shot per three minutes and limited speed this “space artillery” carries over it’s ground vulnerabilities.

=== Icelance GC-2 (Glacial Worm Type 2 variant)===
Of similar design yet completely different purpose, the Icelance GC-2 differs in one thing, main weapon.
With advancements in technology PRA scientists have perfected the art of frost, thus the GC-2 variant comes equipped with a molecule retarder commonly known as a “Freeze Ray”, the cannon works with temperatures the cold void of space could only hope to achieve, weakening the structure of outer armor and creating a layer of permafrost on shields, impeding the pilots visual access and forcing the shield to eventually crumble under the weight of the ice.
This design comes with the added benefit of straining the battery much less, making this design capable of firing multiple times rather than only once before it has to enter its downtime period.
This means that the GC-2 is usually employed in tandem with multiples of the original design.

=== Headmaster ===
The heaviest of the Tajara ships follow the Blizzard doctrine designed by PRA military and keeps its status as the lightest heavy ship ever designed, almost putting it among medium ships. This combination makes the cruiser immune to anything most pirates can field while being fast enough to catch up and begin firing. However, in a serious fight with a heavier ship, it would easily fold.

=== Sentinel ===
The Blizzard doctrine required a ship which could resupply the numerous Fangs and Energy consuming Snowstorms and thus Sentinel was designed.
Sentinel is a carrier ship used to refuel, rearm and repair smaller ships during a battle is the largest and bulkiest ships in the Tajara roster it was assumed that the Sentinel would be the primary target of enemy fire, in response the government spared no expense on this design. Boasting high armor, impressive shielding, point-defenses, and even Bluespace Disruptors purchased from Epsilon Eridani, this ship design takes pride in fielding the least damaged ships in Tajara history.
Of course, the ships are also slow and expensive to upkeep and so many crewmembers jokingly call them “moving space stations”.