Lore Staff Guidelines - Revision history

Datamatt: update to lore writers github perms

2025-10-31T21:14:12Z

update to lore writers github perms

← Older revision		Revision as of 21:14, 31 October 2025
Line 3:		Line 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.		* '''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.
	* When submitting content to the wiki, '''you are still bound to the [[Wiki Staff Guidelines]].'''		* When submitting content to the wiki, '''you are still bound to the [[Wiki Staff Guidelines]].'''
			* Lore Writers have a say on pull requests on the Github related to their lore area, which must be approved or denied by the Lore Writer in an explicit '''comment or approval''' on the pull request. This privilege should not be abused, and it may be overruled by the Maintainers and the Head Developers if they deem it necessary.

	== Whitelist Management ==		== Whitelist Management ==

Triogenix at 02:37, 11 April 2025

2025-04-11T02:37:43Z

← Older revision		Revision as of 02:37, 11 April 2025
Line 185:		Line 185:
	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 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.		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 or deputy lorewriter 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.		Under normal circumstances Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. In the event of a lore writer vacancy and applications for that vacancy being open for a period longer than one month, if there are no applicants during that timeframe, the loremaster may appoint deputies to that department, should there be deputy applicants that would normally be the writers decision. However, Loremasters may not open deputy applications without first opening writer applications and waiting for a one-month period. 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 ===

Triogenix: updated to reflect the changes to event award rules, as well as additions to rules/regulations regarding the inclusion of player characters in official lore

2024-04-29T23:29:45Z

updated to reflect the changes to event award rules, as well as additions to rules/regulations regarding the inclusion of player characters in official lore

← Older revision		Revision as of 23:29, 29 April 2024
Line 134:		Line 134:

	==== Event Awards ====		==== Event Awards ====
	Awards are considered ~~anything~~ that represents a noting of a certain action during events by the lore team. Commonly, this is done in the form of medals or a plaque. Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items, except those given to the Horizon as a whole.		Awards are considered any in-game way that represents a noting of a certain action, broad or specific, during events by the lore team. Commonly, this is done in the form of medals or a plaque. Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items, except those given to the Horizon as a whole.

			Unique awards are for the purposes of this section, defined as any awards which mention a player character's name.

	For specific/special awards, the following rules apply;		For specific/special awards, the following rules apply;

	1) Any ~~specific/special~~ awards given to player characters cannot be an in-round item. ~~It should be made clear to players that~~ custom ~~item requests for any specific/special award~~ will be immediately denied. ~~The~~ only ~~exception to this is during~~ rounds where ~~it was decided~~ to ~~run an award ceremony~~ in~~-game~~.		1) Any unique awards given to player characters cannot be an in-round item during standard rounds. Any request for unique awards as custom items will be immediately denied. Awards may only be used in (event) rounds where the use of awards has been explicitly permitted in the event description (such as award ceremonies). This permission can come with certain restrictions (i.e. the usage of dress uniforms/formal clothing together with the award) This rule does not apply to signed items.

			1a) Writers may include mention of specific/special awards and the player characters which received them in articles, at the discretion of the LTA, but may not include this on any lore wiki page, outside of arc summaries.

	2) The reasoning behind the ~~specific/special~~ award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain.		2) The reasoning behind the unique award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain.

	3) The reasoning mentioned in number 2 must also not be ~~related~~ to fighting ~~or combat~~ in any way. ~~Specific/special~~ awards may be handed out for something like exceptional planning and organization, but not for destroying a mech.		3) The reasoning mentioned in number 2 must also not be directly tied to combat or fighting in any way. Unique awards may be handed out for something like exceptional planning and organization, but not for destroying a mech.

	4) ~~Specific/special~~ awards may only be given to player characters with the express permission of the LTA.		4) Unique awards may only be given to player characters with the express permission of the LTA. Furthermore, Head Administrators reserve the right to deny any awards on the grounds of failing to meet the highest standards of roleplay.

	5) These rules do not apply to NPCs or Event Characters, only to player characters.		5) These rules do not apply to NPCs or Event Characters, only to player characters.

	6) Specific/special awards from corporations must also be approved by the Lead CCIA Agent.		6) Specific/special awards from corporations must also be approved by the Lead CCIA Agent.

			=== Recognition of Player Characters in Official Lore ===
			For the purposes of this section, official lore is defined as anything written by members of the lore team, and posted to either the official galactic news database, or published on the Aurora Wiki.

			1) Player characters should only be recognized in official lore if they influence the course of an IC development, and player characters should never be mentioned otherwise.

			2) Lore Writers are '''strictly forbidden from including their own, or other members of the Lore Team’s characters in any official Lore'''. Furthermore, Lore Writers are restricted from creating IC developments which would inevitably create lore that features their characters, or other members of the Lore Team’s characters.

			3) Approval from the LTA is required before recognizing any player character in official lore.

			3a) All recognition of a player character must be removed from official lore should the attached player be permanently banned from the server.

			4) The Administration Team, through the Head Administrators, reserves the right to mandate the removal of recognition from a player character in official lore, should they believe they do not conduct themselves appropriately in character, or if a character’s player does not conduct themselves appropriately.

			5) The Lore Team must strive to recognize a wide variety of characters and players in official lore, by;

			5a) Ensuring the potential for obtaining recognition is available to all players who play in events.

			5b) Ensuring a character is never recognized more than two times.

			5c) Endeavour that a player never has one of their characters recognized more than twice within a short time frame. The definition of that time frame is at the discretion of the LTA.

			6) Player characters cannot be recognized if they are being recognized for something that has a large impact on the overall setting, and instead be contributed to the Horizon crew. An example would be a player character being recognized for discovering a new phoron deposit, or doing something extremely significant for an arc.

			7) When recognizing player characters, writers should ensure that recognition is limited to articles, and rarely put onto non-arc wiki pages. As an example, a character saves a dog from a house which is on fire, and this is mentioned in an article, but would not be mentioned on the wiki entry for that house’s location.

	== Lore Team Expectations and Staffing ==		== Lore Team Expectations and Staffing ==

Triogenix: /* Event Arcs */

2024-04-14T22:02:59Z

Event Arcs

← Older revision		Revision as of 22:02, 14 April 2024
Line 97:		Line 97:
	* Major Event Arcs must be presented in the Lore Staff Section of the Forums, to be approved by Loremasters after a review period. This presentation should take place during a major event arc that would be preceding it, as mentioned above.		* Major Event Arcs must be presented in the Lore Staff Section of the Forums, to be approved by Loremasters after a review period. This presentation should take place during a major event arc that would be preceding it, as mentioned above.
	** In addition to the Loremaster review and stamp of approval, Major Event Arcs should be discussed amongst the entire team in regards to their impact. If possible, other teams should incorporate some of the impact of an arc into their own lore, in order to make the setting feel more alive.		** In addition to the Loremaster review and stamp of approval, Major Event Arcs should be discussed amongst the entire team in regards to their impact. If possible, other teams should incorporate some of the impact of an arc into their own lore, in order to make the setting feel more alive.
			** Both the Head Developers and LTA reserve the right to request changes or alterations to proposed arcs and may deny arcs at their discretion.
	* Events follow the server’s canonicity rules, as outlined [https://wiki.aurorastation.org/index.php?title=Lore_Team_Rules_and_Regulations#CANONICAL_DEATHS_IN_EVENTS%3A below].		* Events follow the server’s canonicity rules, as outlined [https://wiki.aurorastation.org/index.php?title=Lore_Team_Rules_and_Regulations#CANONICAL_DEATHS_IN_EVENTS%3A below].
	* When Scheduling an Event; the forum calendar post should follow [https://forums.aurorastation.org/events/event/1-event-template/ this format].		* When Scheduling an Event; the forum calendar post should follow [https://forums.aurorastation.org/events/event/1-event-template/ this format].
			** The Event Scale section must be filled out with one of the following intensity; Low, Medium, High, or Extreme.
			*** Furthermore, the LTA and Head Developers have the final say as to what an event's intensity classification is or should be.
			* Any arc that would see the running of a high or extreme intensity event must also see that the event specifically is approved by the LTA and Head Developers before the arc proposal being presented on the forums.
			** This should be done by the relevant team creating a rough draft of the arc, including the reasoning for why an extreme intensity event should be run, and how it will improve the arc.
	*All event arc proposals must follow these rules;		*All event arc proposals must follow these rules;
	** [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/#comment-153462 This is the format for event arc proposal forum posts], the long description is a google doc, shared via link to anyone who access the link.		** [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/#comment-153462 This is the format for event arc proposal forum posts], the long description is a google doc, shared via link to anyone who access the link.
Line 108:		Line 113:
	** By the time everything has been entered into the appropriate fields, [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 the document should look something like this.]		** By the time everything has been entered into the appropriate fields, [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 the document should look something like this.]
	* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled as per the respective rules.		* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled as per the respective rules.

			==== Event Intensity Scale ====
			This is for internal use by the lore team, lore team administration, and head developers to help classify where on the intensity scale a proposed event should fall. These are guidelines, with the LTA and Head Developers having the final say on event intensities.

			* Low Intensity - There is no external threat to the crew that can cause physical or mental harm.

			* Medium Intensity - An external threat that can cause physical or mental harm is present, however it is easily overcome by the crew, and during overcoming it, or should the crew fail to overcome it, there will be a minimal loss of life or risk of injury among player characters.

			* High Intensity - An external threat that can cause physical or mental harm is present and overcoming will be difficult. During overcoming it, or should the crew fail to overcome it, there will be a moderate loss of life or risk of injury among player characters

			* Extreme Intensity - An external threat that can cause physical or mental harm is present, and the main focus of the event. During overcoming it, or should the crew fail to overcome it, there will be a high loss of life or risk of injury among player characters.

	==== Canonical Deaths in Events ====		==== Canonical Deaths in Events ====

Triogenix: /* Event Awards */

2024-03-24T01:07:58Z

Event Awards

← Older revision		Revision as of 01:07, 24 March 2024
Line 124:		Line 124:
	1) Any specific/special awards given to player characters cannot be an in-round item. It should be made clear to players that custom item requests for any specific/special award will be immediately denied. The only exception to this is during rounds where it was decided to run an award ceremony in-game.		1) Any specific/special awards given to player characters cannot be an in-round item. It should be made clear to players that custom item requests for any specific/special award will be immediately denied. The only exception to this is during rounds where it was decided to run an award ceremony in-game.

	2) The reasoning behind the specific/special award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain ~~to accomplish something~~.		2) The reasoning behind the specific/special award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain.

	3) The reasoning mentioned in number 2 must also not be related to fighting or combat in any way. Specific/special awards may be handed out for something like exceptional planning and organization, but not for destroying a mech.		3) The reasoning mentioned in number 2 must also not be related to fighting or combat in any way. Specific/special awards may be handed out for something like exceptional planning and organization, but not for destroying a mech.

Triogenix: /* Event Awards */

2024-03-24T01:07:26Z

Event Awards

← Older revision		Revision as of 01:07, 24 March 2024
Line 118:		Line 118:

	==== Event Awards ====		==== Event Awards ====
	Awards are considered anything that represents a noting of a certain action during events by the lore team. Commonly, this is done in the form of medals or a plaque. Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items.		Awards are considered anything that represents a noting of a certain action during events by the lore team. Commonly, this is done in the form of medals or a plaque. Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items, except those given to the Horizon as a whole.

	For specific/special awards, the following rules apply;		For specific/special awards, the following rules apply;

	1) Any specific/special awards given to player characters cannot be an in-round item. It should be made clear to players that custom item requests for any specific/special award will be immediately denied.		1) Any specific/special awards given to player characters cannot be an in-round item. It should be made clear to players that custom item requests for any specific/special award will be immediately denied. The only exception to this is during rounds where it was decided to run an award ceremony in-game.

	2) The reasoning behind the specific/special award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain to accomplish something.		2) The reasoning behind the specific/special award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain to accomplish something.

Triogenix: /* Event Awards */

2024-03-24T01:03:13Z

Event Awards

← Older revision		Revision as of 01:03, 24 March 2024
Line 118:		Line 118:

	==== Event Awards ====		==== Event Awards ====
	Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items.		Awards are considered anything that represents a noting of a certain action during events by the lore team. Commonly, this is done in the form of medals or a plaque. Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items.

	For specific/special awards, the following rules apply;		For specific/special awards, the following rules apply;

Triogenix: /* Event Rules and Regulations */

2024-03-24T01:01:12Z

Event Rules and Regulations

← Older revision		Revision as of 01:01, 24 March 2024
Line 116:		Line 116:

	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.		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.

			==== Event Awards ====
			Participation awards that apply to all characters during an event or awards given to the Horizon's crew as a whole can be given at the discretion of the relevant event manager and their team. However, such awards cannot be in-round items or custom items.

			For specific/special awards, the following rules apply;

			1) Any specific/special awards given to player characters cannot be an in-round item. It should be made clear to players that custom item requests for any specific/special award will be immediately denied.

			2) The reasoning behind the specific/special award has to be for how something was accomplished, not just accomplishing something. This reasoning must also meet the highest OOC standards of roleplay, for example, no awards for characters who ignored pain to accomplish something.

			3) The reasoning mentioned in number 2 must also not be related to fighting or combat in any way. Specific/special awards may be handed out for something like exceptional planning and organization, but not for destroying a mech.

			4) Specific/special awards may only be given to player characters with the express permission of the LTA.

			5) These rules do not apply to NPCs or Event Characters, only to player characters.

			6) Specific/special awards from corporations must also be approved by the Lead CCIA Agent.

	== Lore Team Expectations and Staffing ==		== Lore Team Expectations and Staffing ==

MattAtlas: remove the defunct rule on the deputy loremaster handling the lore master's breaches of conduct

2024-01-04T13:52:19Z

remove the defunct rule on the deputy loremaster handling the lore master's breaches of conduct

← Older revision		Revision as of 13:52, 4 January 2024
Line 2:		Line 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.		* '''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.
	* '''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.		* '''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.
	* '''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.
	* When submitting content to the wiki, '''you are still bound to the [[Wiki Staff Guidelines]].'''		* When submitting content to the wiki, '''you are still bound to the [[Wiki Staff Guidelines]].'''

La Villa Strangiato: La Villa Strangiato moved page Lore Team Rules and Regulations to Lore Staff Guidelines: Naming consistency

2024-01-01T19:46:01Z

La Villa Strangiato moved page Lore Team Rules and Regulations to Lore Staff Guidelines: Naming consistency

← Older revision	Revision as of 19:46, 1 January 2024
(No difference)