Lore Staff Guidelines - История изменений

>Triogenix: /* Event Arcs */

2024-04-14T22:02:59Z

Event Arcs

← Предыдущая версия		Версия от 01:02, 15 апреля 2024
Строка 97:		Строка 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.
Строка 108:		Строка 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

← Предыдущая версия		Версия от 04:07, 24 марта 2024
Строка 124:		Строка 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

← Предыдущая версия		Версия от 04:07, 24 марта 2024
Строка 118:		Строка 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

← Предыдущая версия		Версия от 04:03, 24 марта 2024
Строка 118:		Строка 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

← Предыдущая версия		Версия от 04:01, 24 марта 2024
Строка 116:		Строка 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

← Предыдущая версия		Версия от 16:52, 4 января 2024
Строка 2:		Строка 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

← Предыдущая версия	Версия от 22:46, 1 января 2024
(нет различий)

>La Villa Strangiato: category

2024-01-01T19:45:10Z

>La Villa Strangiato: re-adds news articles, adds new page to old page for archival purposes

2024-01-01T19:44:14Z

re-adds news articles, adds new page to old page for archival purposes

Внесённые изменения

>MattAtlas: Replaced content with "Superseded by https://wiki.aurorastation.org/index.php?title=Lore_Staff_Guidelines."

2024-01-01T14:33:38Z

Replaced content with "Superseded by https://wiki.aurorastation.org/index.php?title=Lore_Staff_Guidelines."

Внесённые изменения

← Предыдущая версия		Версия от 22:45, 1 января 2024
Строка 1:		Строка 1:


	== General Guidelines ==		== General Guidelines ==
	* '''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.
Строка 137:		Строка 135:

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

			[[Category:Staff Guidelines]]