Delta-V Wiki - User contributions [en]

Content Removal

2026-10-11T15:55:37Z

DV vapetastic: /* In order to remove content, You must: */

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

=== '''In order to remove content, You must:''' ===
* Make a list of issues with the content

*Announce the planned removal of the content, including a date, and its issues - For classifications of "Major Content" only

*Create a community feedback post regarding the removal, the issues, and a specific date of removal.

* Establish a deadline for action (Removal or Replacement)

=== Appropriate Deadlines: ===
* 1 week - minor to moderate content (Sprites, Mechanical balances, Items, Machines, Etc)

* 2 weeks - Major content (Gamemodes, Roles, Multiple minor/moderate content items as a "bundle"** Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process

If Community feedback for removal is overwhelmingly negative, Content Review is required to seek approval of both the Interim Team lead and the Project Management Team before finalizing removal.

Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).'' Project Management and Maintainers will have final say on removal via author request, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

<nowiki>**</nowiki> Bundles are considered any content that includes more than 1 item. Some examples include superweapons or the improvised armory. Bundles do not include items that require specific parts to function, such as "blunderbuss" and "Blunderbuss ammo", as an example.

Direction Guidelines

2026-10-09T18:03:13Z

DV vapetastic:

{{DISPLAYTITLE:Content Review Guidelines}}
{{DISPLAYTITLE:Content Review Guidelines}}

{{Important|Title=Under Construction|Note=This policy is currently under construction. All current documents are subject to change.|Image=engineer.png|Color=#c44f00}}

'''Interim CR Conduct Policy'''

This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers. Any PR author is also subject to these policies when interacting with Reviewers. If this policy is broken by a PR author, this can result in a denial of the PR, a suspension of access, or removal from the codebase.'''

==== '''Approach to Content Review''' ====

# Reviewers are expected to approach the process of content review with awareness of any personal biases regarding relevant subjects to the review, and should make those biases known to other Reviewers.
# Reviewers should, even acknowledging biases, endeavor to approach the process of content review in an objective manner, and with the goal of achieving constructive dialogue and consensus (if possible) on the PR being reviewed.
# Reviewers should utilize the Content Review bot (the "Raised Issue" system) and should have a generalized understanding of how the system functions and its appropriate use.
# Reviewers should have a basic understanding of how PR submission works, including basic GitHub operations (pull requests, merges, etc), and should be reasonably up to date on the current state of Space Station 14 (the game, its mechanics, how systems function in play, etc).
# Reviewers should focus on discrete issues when conducting content review, rather than making generalized statements ("I don't vibe with this," "This PR doesn't feel right," etc).
# Reviewers should read the PR, ask questions of other reviewers or the PR author if necessary, and develop and articulate a stance on the PR.

==== '''Behavior & Conflict of Interest''' ====

# '''Staff ''cannot'' act as Reviewers for their own PRs.''' ''This includes but is not limited to: voting in favor of the PR, triaging the PR, or finalizing reviews of their own PR. Staff who are PR Authors are permitted to advocate, represent, clarify, and generally engage in conversation with Reviewers, as is normal for PR Authors; however, extended lawyering or attempts to use "soft power" (influence due to staff position, etc) can result in the Staff PR Author's access to the discussion being limited or denied, or the PR being denied by the Interm CR Team.''
# '''Bullying, toxic statements, condescension, or "talking down" to others by Reviewers is not allowed.''' ''This applies to Community Members, PR Authors, or other Reviewers. If Reviewers engage in any of the above behavior, or violate the Staff Policy in the course of Interim CR work, they may have access to the discussion restricted or denied by the Interim CR Head or Moderation Staff. Repeated instances of the above behavior may lead to removal from the Interim CR Team at the discretion of High Command (as outlined in the Head Staff Voting Policy).''
# '''Reviewers are encouraged to employ their expertise in discussion, but also to respect the expertise of other Reviewers in turn.''' ''Attempts to "correct" or otherwise dismiss the arguments of others in an offhand manner (i.e., one not backed by evidence/explanation) may be considered toxic behavior and may result in consequences as outlined above.''

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Interim Team lead to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in either the #public-content-review or the #private-content-review forum channels. The Senior Content Reviewer who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a vote. Content Review's take place with a raised issue system. If you have an issue with something in the PR, you should raise an issue using the Content Review bot using the small guide below:

# Send a message outlining your issue with the PR.
# Hover over the message.
# Hover over <code>Apps</code>.
# Hover over <code>Delta-V Bot</code>.
# Click on <code>Raise Issue</code>. The message you send will be pinned and viewable by entering the command <code>/cr issue overview</code>. With every reminder message sent by the bot, the ratio of issues and overrules will be displayed. The same way is done to overrule issues.

If an issue is not addressed, it must wait until the end of a review period. At the end of a review, the Senior Content Reviewer who initiated review, will tally both issues and overrides, and then determine whether the issues will prevent a PR from being merged. This includes requesting changes, applying a test merge, approving the PR as is, or denying the PR. This can be overridden by the Content Director at any time.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

== Upstream Merges ==

Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. This may be changed or removed at any time by any head of development (IE Head Mapper, Head Maintainer)

Direction Guidelines

2026-10-09T16:14:05Z

DV vapetastic: /* Upstream Merges */

{{DISPLAYTITLE:Content Review Guidelines}}
{{DISPLAYTITLE:Content Review Guidelines}}

{{Important|Title=Under Construction|Note=This policy is currently under construction. All current documents are subject to change.|Image=engineer.png|Color=#c44f00}}

'''Interim CR Conduct Policy'''

This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers.'''

==== '''Approach to Content Review''' ====

# Reviewers are expected to approach the process of content review with awareness of any personal biases regarding relevant subjects to the review, and should make those biases known to other Reviewers.
# Reviewers should, even acknowledging biases, endeavor to approach the process of content review in an objective manner, and with the goal of achieving constructive dialogue and consensus (if possible) on the PR being reviewed.
# Reviewers should utilize the Content Review bot (the "Raised Issue" system) and should have a generalized understanding of how the system functions and its appropriate use.
# Reviewers should have a basic understanding of how PR submission works, including basic GitHub operations (pull requests, merges, etc), and should be reasonably up to date on the current state of Space Station 14 (the game, its mechanics, how systems function in play, etc).
# Reviewers should focus on discrete issues when conducting content review, rather than making generalized statements ("I don't vibe with this," "This PR doesn't feel right," etc).
# Reviewers should read the PR, ask questions of other reviewers or the PR author if necessary, and develop and articulate a stance on the PR.

==== '''Behavior & Conflict of Interest''' ====

# '''Staff ''cannot'' act as Reviewers for their own PRs.''' ''This includes but is not limited to: voting in favor of the PR, triaging the PR, or finalizing reviews of their own PR. Staff who are PR Authors are permitted to advocate, represent, clarify, and generally engage in conversation with Reviewers, as is normal for PR Authors; however, extended lawyering or attempts to use "soft power" (influence due to staff position, etc) can result in the Staff PR Author's access to the discussion being limited or denied, or the PR being denied by the Interm CR Team.''
# '''Bullying, toxic statements, condescension, or "talking down" to others by Reviewers is not allowed.''' ''This applies to Community Members, PR Authors, or other Reviewers. If Reviewers engage in any of the above behavior, or violate the Staff Policy in the course of Interim CR work, they may have access to the discussion restricted or denied by the Interim CR Head or Moderation Staff. Repeated instances of the above behavior may lead to removal from the Interim CR Team at the discretion of High Command (as outlined in the Head Staff Voting Policy).''
# '''Reviewers are encouraged to employ their expertise in discussion, but also to respect the expertise of other Reviewers in turn.''' ''Attempts to "correct" or otherwise dismiss the arguments of others in an offhand manner (i.e., one not backed by evidence/explanation) may be considered toxic behavior and may result in consequences as outlined above.''

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Interim Team lead to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in either the #public-content-review or the #private-content-review forum channels. The Senior Content Reviewer who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a vote. Content Review's take place with a raised issue system. If you have an issue with something in the PR, you should raise an issue using the Content Review bot using the small guide below:

# Send a message outlining your issue with the PR.
# Hover over the message.
# Hover over <code>Apps</code>.
# Hover over <code>Delta-V Bot</code>.
# Click on <code>Raise Issue</code>. The message you send will be pinned and viewable by entering the command <code>/cr issue overview</code>. With every reminder message sent by the bot, the ratio of issues and overrules will be displayed. The same way is done to overrule issues.

If an issue is not addressed, it must wait until the end of a review period. At the end of a review, the Senior Content Reviewer who initiated review, will tally both issues and overrides, and then determine whether the issues will prevent a PR from being merged. This includes requesting changes, applying a test merge, approving the PR as is, or denying the PR. This can be overridden by the Content Director at any time.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

== Upstream Merges ==

Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. This may be changed or removed at any time by any head of development (IE Head Mapper, Head Maintainer)

Direction Guidelines

2026-10-09T16:01:45Z

DV vapetastic:

{{DISPLAYTITLE:Content Review Guidelines}}
{{DISPLAYTITLE:Content Review Guidelines}}

{{Important|Title=Under Construction|Note=This policy is currently under construction. All current documents are subject to change.|Image=engineer.png|Color=#c44f00}}

'''Interim CR Conduct Policy'''

This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers.'''

==== '''Approach to Content Review''' ====

# Reviewers are expected to approach the process of content review with awareness of any personal biases regarding relevant subjects to the review, and should make those biases known to other Reviewers.
# Reviewers should, even acknowledging biases, endeavor to approach the process of content review in an objective manner, and with the goal of achieving constructive dialogue and consensus (if possible) on the PR being reviewed.
# Reviewers should utilize the Content Review bot (the "Raised Issue" system) and should have a generalized understanding of how the system functions and its appropriate use.
# Reviewers should have a basic understanding of how PR submission works, including basic GitHub operations (pull requests, merges, etc), and should be reasonably up to date on the current state of Space Station 14 (the game, its mechanics, how systems function in play, etc).
# Reviewers should focus on discrete issues when conducting content review, rather than making generalized statements ("I don't vibe with this," "This PR doesn't feel right," etc).
# Reviewers should read the PR, ask questions of other reviewers or the PR author if necessary, and develop and articulate a stance on the PR.

==== '''Behavior & Conflict of Interest''' ====

# '''Staff ''cannot'' act as Reviewers for their own PRs.''' ''This includes but is not limited to: voting in favor of the PR, triaging the PR, or finalizing reviews of their own PR. Staff who are PR Authors are permitted to advocate, represent, clarify, and generally engage in conversation with Reviewers, as is normal for PR Authors; however, extended lawyering or attempts to use "soft power" (influence due to staff position, etc) can result in the Staff PR Author's access to the discussion being limited or denied, or the PR being denied by the Interm CR Team.''
# '''Bullying, toxic statements, condescension, or "talking down" to others by Reviewers is not allowed.''' ''This applies to Community Members, PR Authors, or other Reviewers. If Reviewers engage in any of the above behavior, or violate the Staff Policy in the course of Interim CR work, they may have access to the discussion restricted or denied by the Interim CR Head or Moderation Staff. Repeated instances of the above behavior may lead to removal from the Interim CR Team at the discretion of High Command (as outlined in the Head Staff Voting Policy).''
# '''Reviewers are encouraged to employ their expertise in discussion, but also to respect the expertise of other Reviewers in turn.''' ''Attempts to "correct" or otherwise dismiss the arguments of others in an offhand manner (i.e., one not backed by evidence/explanation) may be considered toxic behavior and may result in consequences as outlined above.''

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Interim Team lead to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in either the #public-content-review or the #private-content-review forum channels. The Senior Content Reviewer who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a vote. Content Review's take place with a raised issue system. If you have an issue with something in the PR, you should raise an issue using the Content Review bot using the small guide below:

# Send a message outlining your issue with the PR.
# Hover over the message.
# Hover over <code>Apps</code>.
# Hover over <code>Delta-V Bot</code>.
# Click on <code>Raise Issue</code>. The message you send will be pinned and viewable by entering the command <code>/cr issue overview</code>. With every reminder message sent by the bot, the ratio of issues and overrules will be displayed. The same way is done to overrule issues.

If an issue is not addressed, it must wait until the end of a review period. At the end of a review, the Senior Content Reviewer who initiated review, will tally both issues and overrides, and then determine whether the issues will prevent a PR from being merged. This includes requesting changes, applying a test merge, approving the PR as is, or denying the PR. This can be overridden by the Content Director at any time.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

== Upstream Merges ==

Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. This may be changed or removed at any time by any head of development

Direction Guidelines

2026-10-07T14:48:18Z

DV vapetastic: added under construction

{{DISPLAYTITLE:Content Review Guidelines}}
{{DISPLAYTITLE:Content Review Guidelines}}

{{Important|Title=Under Construction|Note=This policy is currently under construction. All current documents are subject to change.|Image=engineer.png|Color=#c44f00}}

=== Overview ===
This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

== Content Review Policy ==
Any portion of the Content Review Policy can be suspended, or overridden by the Content Director at any time.

1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.

2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.

3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

4. Using the "Raised Issue" system, Content Reviewers must have a generalized understanding of how to use this system

5. Content Reviewers cannot override issues on their own PR. The author is allowed to advocate, represent, clarify, and generally engage in conversation.

6. Extended lawyering of PR Reviews is not allowed. Reviewers should focus on raising an issue, asking questions, and choosing a stance.

7. Only Senior Content Reviewers may triage or finalize decisions regarding a PR with the standard review policy.

8. No Content Reviewer may triage or end reviews for their own PR.

9. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Content Director or Senior CR's to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in either the #public-content-review or the #private-content-review forum channels. The Senior Content Reviewer who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a vote. Content Review's take place with a raised issue system. If you have an issue with something in the PR, you should raise an issue using the Content Review bot using the small guide below:

# Send a message outlining your issue with the PR.
# Hover over the message.
# Hover over <code>Apps</code>.
# Hover over <code>Delta-V Bot</code>.
# Click on <code>Raise Issue</code>. The message you send will be pinned and viewable by entering the command <code>/cr issue overview</code>. With every reminder message sent by the bot, the ratio of issues and overrules will be displayed. The same way is done to overrule issues.

If an issue is not addressed, it must wait until the end of a review period. At the end of a review, the Senior Content Reviewer who initiated review, will tally both issues and overrides, and then determine whether the issues will prevent a PR from being merged. This includes requesting changes, applying a test merge, approving the PR as is, or denying the PR. This can be overridden by the Content Director at any time.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

== Upstream Merges ==

Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. This may be changed or removed at any time by any head of development

Gorlex

2026-09-20T22:41:07Z

DV vapetastic:

=== This page is in progress ===

Redspace Cloning was developed in secret by Interdyne. Redspace Cloning, due to its cheap nature, resulted in cloned individuals having genetic deformities that gave enhanced combat and quick reflexes while genetically damaging the user's frontal lobes, particularly the area known as "Broca's Area". Its quirks had not been fully ironed out before Gorlex partnered with Interdyne. After 6 months of the partnership and Gorlex fulfilling its contractual obligations, over 80% of Its workforce had been cloned.

Due to their close connections to Cybersun Industries, and their own reservations with Nanotrasen's expansion into the private military space, Gorlex became a founding member of the Syndicate. They now form the sword of the coalition, accepting a hefty paycheck from the Syndicate's collective funding for the trouble. The Marauders are an elite force trained and employed by Gorlex, and cause a lot of trouble for Nanotrasen via coordinated strikes on their stations. The deadliest of the Gorlex operatives are the elite of the elite: The Nuclear Operatives, named for their main method of attack: Nuclear Warfare.

While they are an elite force, the Marauders are often poorly disciplined, which has led to Cybersun embedding officers into Gorlex strike teams to maintain discipline within the ranks and keep them on target. This has created an osmosis of ideas throughout the Syndicate, and many motifs originally associated with the Gorlex Marauders have become commonly associated with the entire organisation. This includes, but is not limited to, their blood-red colour scheme, their iconic snake logo (adapted for syndicate use), and, in many ways, their ruthlessness. This has flowed both ways, and the Marauders have learned some new tricks from their allies, like sourcing newer, more powerful weaponry from {IN PROGRESS} or adopting the combat stimulants used by the Tyger Cooperative.

Delta V Lore

2026-09-16T03:26:12Z

DV vapetastic:

= Table of Contents =
Documents below were authored by: ''Vapetastic, Porto, ConfusedLemon, FangsakaCharlie, Grasstype, Bonktrauma, AeraAulin, Einkusprigestoast, Greenster, Bellwether, Exile and Malfatto.''

{{Important|Title=Under Construction|Note=Delta V's Lore is currently under construction. All current documents are subject to change.|Image=engineer.png|Color=#c44f00}}

{{Lore Menu}}

History of Sol and Earth

2026-09-16T03:24:59Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present.|Image=engineer.png|Color=#c44f00}}

=== '''Background''' ===
In the year 2053, small reservoirs of plasma (Also known as Phoron) were discovered on the moon. This highly volatile substance was the catalyst that kicked-off humanity’s age of space exploration by allowing Faster-Than-Light travel. Soon enough, humans had spread out to the far corners of the Milky Way galaxy, colonizing thousands of planets. Mega-Corporations began to surface as the powerhouses of multiple star systems, using their immense wealth to subjugate and exploit the natives and weak colonies of underdeveloped and recently colonized planets to further their own agendas. Many of these Mega-Corporations established themselves as sovereign entities, akin to an earthly autocracy with its own systems of government, security, and justice.

{{Lore Menu}}

History of Sol and Earth

2026-09-10T16:31:14Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

=== '''Background''' ===
In the year 2053, small reservoirs of plasma (Also known as Phoron) were discovered on the moon. This highly volatile substance was the catalyst that kicked-off humanity’s age of space exploration by allowing Faster-Than-Light travel. Soon enough, humans had spread out to the far corners of the Milky Way galaxy, colonizing thousands of planets. Mega-Corporations began to surface as the powerhouses of multiple star systems, using their immense wealth to subjugate and exploit the natives and weak colonies of underdeveloped and recently colonized planets to further their own agendas. Many of these Mega-Corporations established themselves as sovereign entities, akin to an earthly autocracy with its own systems of government, security, and justice.

{{Lore Menu}}

Kosanikaan Confederation

2026-09-10T16:27:51Z

DV vapetastic: /* Kosanikaan Confederation (KCO) */

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

== '''Kosanikaan Confederation (KCO)''' ==
Thanks to advances in science in the last 400 years, voting has never been easier. While the '''Kosanikaan Confederation''' has largely autonomous sectors, these sectors count votes straight from a connection of neural implants given to every citizen upon reaching the legal voting age. This allows them to vote straight from their mind, usually without a second thought.

The '''Kosanikaan Confederation''' is quite unique in its modernized voting practices, and this allows for its citizens to prosper in the nation. Meritocracy is highly valued, and its citizens usually go above and beyond due to their high national fervor. The '''KCO''' focuses on protecting its interests in its local domestic region, and is considered a minor faction in a galaxy of “big players”.

The '''KCO''' has no requirements for citizenship other than receiving a voting implant. [[History of the Delta Sector#Nanotrasen|Nanotrasen]] suspects that these implants can be used to monitor and conduct surveillance on individuals, however through extensive {REDACTED BY ORDER OF CC} subjects were unrecoverable and no data of substance was collected to prove these suspicions.

{{Lore Menu}}

Terragov

2026-09-10T16:15:42Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

== '''TerraGov, Sol’s Current Leadership''' ==
'''TerraGov''' was established in 2200 After a major faction within the '''[[United Nations Armed Forces|UNAF]]''' decided that the armed forces should not be leading the people. '''TerraGov''' was founded on a Democratic Republic, with only “Empowered Citizens” being allowed to vote. Representatives are selected based on Age of the Voter, with each 3 year span receiving a selection of representatives, all the way to 160 Years of age. This is not based on Cryogenic age, and only Biological age.

'''TerraGov’s''' Website describes “Empowered Citizens” as those that have committed service to '''TerraGov’s''' cause in some capacity, and have done so for at least 10 years. It also details that Citizens may only be granted Empowerment through an application, however applications are currently closed until 2586 due to “Maximum Capacity Reached”.

'''TerraGov''' is lead by the '''TerraGov''' Senior Senate, which is currently listed at 1,890 members, This Senate makes decisions similar to an Executive branch of government. The Junior Senate is listed at 3,256 members, and is charged with daily operations, finances, and legislative action. Each law must pass both the Junior and Senior Senate to be approved. Junior Senators are eligible for the Senior Senate upon reaching 130 Years of age with a minimum of 50 years of Service within the senate or GalPol.

=== The GBPI and GalPol ===
In 2196 after multiple corporate CEO's and other leadership roles were being targetted by an unknown organization, the [[United Nations Armed Forces|UNAF]] formed the Galactic Bureau of Police and Investigations as a formal Investigative body for crimes that happened within Sol. The GBPI was given complete control and authority over Civilian Crimes, which the UNAF labelled as crimes committed outside of military service, and outside of warfare.

In 2201 after the first official Senate conference by Terragov, the GBPI was officially recognized by the civilian government, and was given a massive uptake in funding by the civilian government, as well as private funding from benefactors Including [[Nanotrasen]] and the [[Betelgeuse Consortium]]. After the funding increase, the GBPI established its first GalPol presence outside of Sol and the surrounding systems on a station on Nouvelle Montreal, the capital of the [[Betelgeuse Consortium]].

In 2202 [[Nanotrasen]] Central Command issued direct orders to its security and specialized response forces that GalPol agents and officers are now the primary authority of Space Law, and that any documented major crimes against [[Nanotrasen]] will be reported automatically to GalPol. [[Nanotrasen]] continued to hold its own hearings, trials, and even punishments. Nanotrasen and the GBPI have maintained a multi-century long history of Cooperation and Involvment. <code>Some say that Nanotrasen's closest ally isnt a corporation or nation, it's the GBPI.</code>{{Lore Menu}}

Terragov

2026-09-10T16:11:01Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

== '''TerraGov, Sol’s Current Leadership''' ==
'''TerraGov''' was established in 2200 After a major faction within the '''[[United Nations Armed Forces|UNAF]]''' decided that the armed forces should not be leading the people. '''TerraGov''' was founded on a Democratic Republic, with only “Empowered Citizens” being allowed to vote. Representatives are selected based on Age of the Voter, with each 3 year span receiving a selection of representatives, all the way to 160 Years of age. This is not based on Cryogenic age, and only Biological age.

'''TerraGov’s''' Website describes “Empowered Citizens” as those that have committed service to '''TerraGov’s''' cause in some capacity, and have done so for at least 10 years. It also details that Citizens may only be granted Empowerment through an application, however applications are currently closed until 2586 due to “Maximum Capacity Reached”.

'''TerraGov''' is lead by the '''TerraGov''' Senior Senate, which is currently listed at 1,890 members, This Senate makes decisions similar to an Executive branch of government. The Junior Senate is listed at 3,256 members, and is charged with daily operations, finances, and legislative action. Each law must pass both the Junior and Senior Senate to be approved. Junior Senators are eligible for the Senior Senate upon reaching 130 Years of age with a minimum of 50 years of Service within the senate or GalPol.

=== The GBPI and GalPol ===
In 2196 after multiple corporate CEO's and other leadership roles were being targetted by an unknown organization, the [[United Nations Armed Forces|UNAF]] formed the Galactic Bureau of Police and Investigations as a formal Investigative body for crimes that happened within Sol. The GBPI was given complete control and authority over Civilian Crimes, which the UNAF labelled as crimes committed outside of military service, and outside of warfare.

In 2201 after the first official Senate conference by Terragov, the GBPI was officially recognized by the civilian government, and was given a massive uptake in funding by the civilian government, as well as private funding from benefactors Including [[Nanotrasen]] and the [[Betelgeuse Consortium]]. After the massive funding increase from the civilian government and private benefactors, the GBPI established its first GalPol presence outside of Sol and the surrounding systems on a station on Nouvelle Montreal, the capital of the [[Betelgeuse Consortium]].

In 2202 [[Nanotrasen]] Central Command issued direct orders to its security and specialized response forces that GalPol agents and officers are now the primary authority of Space Law, and that any documented major crimes against [[Nanotrasen]] will be reported automatically to GalPol. [[Nanotrasen]] continued to hold its own hearings, trials, and even punishments. Nanotrasen and the GBPI have maintained a multi-century long history of Cooperation and Involvment. <code>Some say that Nanotrasen's closest ally isnt a corporation or nation, it's the GBPI.</code>{{Lore Menu}}

Kosanikaan Confederation

2026-09-10T15:43:23Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

== '''Kosanikaan Confederation (KCO)''' ==
Thanks to advances in science in the last 400 years, voting has never been easier. While the '''Kosanikaan Confederation''' has largely autonomous sectors, these sectors count votes straight from a connection of neural implants given to every citizen upon reaching the legal voting age. This allows them to vote straight from their mind, usually without a second thought.

The '''Kosanikaan Confederation''' is quite unique in its modernized voting practices, and this allows for its citizens to prosper in the nation. Meritocracy is highly valued, and its citizens usually go above and beyond due to their high national fervor. The '''KCO''' does protect its national interests in their domestic region highly, and is considered a minor faction in a galaxy of “big players”.

The '''KCO''' has no requirements for citizenship other than receiving a voting implant. [[History of the Delta Sector#Nanotrasen|Nanotrasen]] suspects that these implants can be used to monitor and conduct surveillance on individuals, however through extensive {REDACTED BY ORDER OF CC} subjects were unrecoverable.

{{Lore Menu}}

Betelgeuse Consortium

2026-09-10T15:43:05Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

== '''Betelgeuse Consortium (BGC)''' ==
A long history of trade, oppression and profit tells the story of the '''Betelgeuse Consortium'''. Descendants of Old Terran colonists, the '''Betelgeuse''' system was a vital system for trade, settled in between most major settled systems. Throughout the chaos of old colonial wars, executives have mostly seized power in '''Nouvelle Montreal''', the capital of the '''BGC''' and its surrounding planets and systems.

While the board isnt popular with its rule, its economic power cannot be denied. Many trade stations owe their profits to the '''BGC''' and have been largely “bought out”. Dissidence in the '''BGC''' is overshadowed by the nations extreme propaganda system. According to the Board of Directors, everyone is happy and healthy within the '''BGC'''.

With Interstellar trade, the '''BGC''' has one major factor to it's participation, Medical Research and Technology. The '''BGC''' is known as the “Powerhouse” of the Medical field, with the most advanced Cybernetic and Healing technologies being marked as proprietary '''BGC''' Technology. [[History of the Delta Sector#Nanotrasen|Nanotrasen]] regularly trades and purchases these items from '''BGC'''.

{{Lore Menu}}

History of Sol and Earth

2026-09-10T15:42:10Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

=== '''Background''' ===
In the year 2053, small reservoirs of plasma (Also known as Phoron) were discovered on the moon. This highly volatile substance was the catalyst that kicked-off humanity’s age of space exploration. Soon enough, humans had spread out to the far corners of the galaxy, colonizing thousands of planets. Mega-Corporations began to surface as the powerhouses of multiple star systems, using their immense wealth to subjugate and exploit the natives of underdeveloped planets to further their own agendas. Many of these Mega-Corporations established themselves as sovereign entities, akin to an earthly autocracy with its own systems of government, security, and justice.

{{Lore Menu}}

Nanotrasen

2026-09-10T15:41:42Z

DV vapetastic:

{{Important|Title=Under Construction|Note=This page is currently under construction, Watch your step as safety hazards may be present|Image=engineer.png|Color=#c44f00}}

==== '''NanoTrasen (NT)''' ====
What started out as a relatively small and humble organization tasked by the United Nations in 2055 with exploration and discovery had bolstered itself into possibly the largest single entity in the known galaxy. Using cut-throat business tactics they easily dominated their competition, absorbing many rival corporations into their ranks. They remain the dominant superpower in the research, development, and exploration sectors.

NT is a primarily "Plasma / Phoron" mining company that stumbled upon the noosphere and psionics research. Epistemics was haphazardly created for this,

NT while being the "Discoverer" (Another faction actually discovered and has had this for a while, so think christopher columbus style discovery) Has tried to hide this with "Phoron" and artifact research.

The reason we have artifacts is from an ancient psionic powered race that is originally from the region, but has been seen on the galactic scale.

NT is a notable bad employer, but tries to treat workers in the delta sector rather well due to the massively important psionic research going on on those stations.

Skirt rules, cut corners, overall the cheapest route is the best route.

== '''Nanotrasen''' ==
'''Nanotrasen''' is the dominant megacorporation of the universe. While ostensibly bowing to '''[[Terragov]]''', '''Nanotrasen''' separately controls multiple galaxies, holds a monopoly over Plasma research, Laser technology, [[History of the Delta Sector#Psionics|'''Psionic''' '''technology''']], and dozens if not hundreds of other industries through a combination of sheer resources, underhanded tactics, and in some cases outright corporate war. There are multiple different stories for '''Nanotrasen’s''' origin, however in the hundreds of years since it’s founding along with the immense, bloated, almost unknowable size the only confirmed details are that '''Nanotrasen''' started as a small company on earth, and was one of the main drivers of the space race that led to the colonization of the universe.

{{Lore Menu}}

Template:Lore Menu

2026-09-10T15:08:17Z

DV vapetastic:

{| class="wikitable mw-collapsible" width=100% style="font-size: 95%"
|-
! colspan=2 style="font-size: 95%; border: 2px solid #000000" | [[Delta V Lore]]
|-
| style="width:24%; text-align:right; background: #630813; border: 2px solid #000000" | '''Historical Documents'''
| style="border: 2px solid #000000" | [[History of Sol and Earth]] · [[United Nations of Earth]] · [[United Nations Armed Forces]] · [[History of the Delta Sector]]
|-
| style="text-align:right; background: #132c5e; border: 2px solid #000000" | '''Minor Nations'''
| style="border: 2px solid #000000" | [[The Free Sapient Charter]] · [[The Wesk'Rir Nation]] · [[Betelgeuse Consortium]] · [[Kosanikaan Confederation]]
|-
| style="text-align:right; background: #3258a6; border: 2px solid #000000" | '''Major Nations'''
| style="border: 2px solid #000000" | [[Terragov]] · [[Tengoku Commonwealth]] · [[Theocratic Monarchy of Verdanova]]
|-
| style="text-align:right; background: #014a41; border: 2px solid #000000" | '''Minor Corporations'''
| style="border: 2px solid #000000" | [[Gorlex]] · [[Donk Company]] · [[MI13]] · [[Tyger Dynamics]]
|-
| style="text-align:right; background: #018c7c; border: 2px solid #000000" | '''Major Corporations'''
| style="border: 2px solid #000000" | [[Nanotrasen]] · [[Interdyne]] · [[Cybersun]]
|-
| style="text-align:right; background: #a12a47; border: 2px solid #000000" | '''Clans and Cults'''
| style="border: 2px solid #000000" | [[Cosmic Cult]] · [[Clockwork Cult]] · [[Spider Clan]]
|-
| style="text-align:right; background: #360101; border: 2px solid #000000" | '''Languages'''
| style="border: 2px solid #000000" | [[Terran]] · [[Freelang]] · [[Celestial Verdanic]] · [[Consortium Trade Standard]] · [[Tengokun Military Standard]] · [[Neurovox]]
|}<noinclude>

== Usage ==
Navigational template for the [[Delta V Lore|Lore]] category. Includes an automatic categorization of the page into said category. To use it, write:

<pre>
{{Lore Menu}}
</pre>

[[Category:Templates]]
</noinclude>
<includeonly>[[Category:Lore]]</includeonly>

Delta V Lore

2026-09-09T19:57:32Z

DV vapetastic:

Gorlex

2026-09-09T19:39:11Z

DV vapetastic: Created page with "=== This page is in progress === Nanotrasen stations commonly have nuclear devices onboard in case of two scenarios, an infestation of the blob which is now suspected to be extinct, or the station had rebelled and the responding SRT/ERT have declared the station unsaveable and chosen to scuttle it instead. This system had a failsafe of premature detonation, it had no software to arm the device loaded onto it. Instead the software to arm it was stored inside of a NAD (n..."

=== This page is in progress ===

Nanotrasen stations commonly have nuclear devices onboard in case of two scenarios, an infestation of the blob which is now suspected to be extinct, or the station had rebelled and the responding SRT/ERT have declared the station unsaveable and chosen to scuttle it instead. This system had a failsafe of premature detonation, it had no software to arm the device loaded onto it. Instead the software to arm it was stored inside of a NAD (nuclear authentication disk). This was commonly kept on the captain or head of security. Alongside this failsafe a code was also required to arm it, this was only given to the station if asked for or when the stations automated systems detected a blob infestation. Unfortunately the machine that randomized the codes to the nuclear devices was not truly random, and after heavy research into Redspace, the Syndicate gained access to codes to Nanotrasen's nuclear devices.

Upon initiating a nuclear raid on a site, the marauders would enter into the drop pod and launch themselves at the station, crashing a hole through the station and blitzkrieging the nuclear disk to quickly activate the nuclear device.

Upon grabbing the disk and activation, nuclear operatives are trained to defend the nuclear bomb until it detonates to prevent defusion.

This strategy only works because of Interdyne's newest medical research, cloning.

Cloning was developed around the same time as the Gorlex Marauders was formed, although its quirks weren't fully ironed out yet resulting in the clone Marauders having genetic deformities. These deformities were ironed out after the third drop pod attack was done. But the marauders had actually stated that they liked some of the new bodies the cloning pods created. This would create the species known as Felinid, Harpy, and Rodentia. Interdyne would research these deformities and create a gene therapy procedure to allow customers to become one of these species.

Interdyne

2026-09-09T19:38:39Z

DV vapetastic:

== The origins of Interdyne Pharmaceuticals ==
Interdyne Pharmaceuticals was founded on Mars in the year 2046, being made of split off employees from the now defunct Freelight chemicals after an incident where executives cut bonuses from 94% of workers. Leading to a mass exodus from the company.

Their founders Izzy Norman, Terry Elman, Richard Din, Yancy Norman were four mid level chemical researchers that knew each other personally and participated in the Freelight mass exodus, eventually coming together to create a better company than their old bosses. Starting out as a local producer of Diethylamine and EZ Nutriment to prove that they can produce basic chemicals. Their one and only investor was a highly private man named Edward, who suggested the name INTERDYNE for their company upon investing, which was agreed to become the name of the company.

=== A foothold on Mars ===
Until 2102 Interdyne focused on producing chemicals for the growing hydroponics industry on mars, as its Major locations acted as a “space truckstop” for travelers needing mid journey refuels on food and water while heading to the outer Sol system.

In this time period they also discovered and patented Unstable Mutagen as a much quicker way of getting desired traits on crops that was considerably cheaper then GMO processes, gaining massive success from its sale across the industry.

Through the boost of funds coming from the selling of Unstable Mutagen, Interdyne would spread throughout the Sol system creating more research labs. A majority of these labs would be secret bases in the asteroid belt. Nanotrasen “accidentally” destroyed a decent portion of the labs while performing mining operations in the belt, Interdyne claims that this wasn’t a so-called accident but was a deliberate corporate sabotage of Interdyne research sites, thus beginning the rivalry between the two companies.

=== The cold war of Deceit ===
Interdyne is the first recorded company that sent agents into Nanotrasen to sabotage and steal corporate items, specifically the Hypospray that Nanotrasen had accidentally designed when creating a fuel pump system for their newest Micro Satellite Re-alignment Engines. A large shipment of Hyposprays designated for their newest created ERT division was considered missing upon arriving to the cargo depot, and upon reviewing camera footage and cargo hauler route coordinates, investigators pinned the crate to be lost in the asteroid belt, causing Nanotrasen to become suspicious of corporate sabotage caused by Interdyne. This began the official cold war between Interdyne and Nanotrasen.

The cold war primarily focused on taking blueprints/recipes for secret projects the other was working on, reverse engineering it and then claiming their company had made it first. Both companies began to withold patenting their secret technology so the other couldn’t copy it and use it in secret.

During the cold war, both Interdyne and Nanotrasen began to collect allies. Interdyne did so through corporate deals and contracts, Nanotrasen through buyouts and lobbying.

Interdynes corporate deals primarily working with Cybersun, Donk Co, MI13, and Tyger Dynamics. While Nanotrasen began lobbying local planet governments to only use Nanotrasen provided items for their government. In an effort to limit Interdyne from expanding further, while also beginning to buy out smaller companies. A company of note was a lunar based AI and robot based company named Tadashi Industries, which is how Nanotrasen got its station AI cores and Cyborg helpers.

Interdyne began to reinforce ties between their partnered corporations, forming what we know as today as the Syndicate.

After years of warfare between Nanotrasen and the Syndicate. Nanotrasen developed technology that allowed bluespace artillery be put onto shuttle craft, allowing them to fire and quickly leave the area before the Syndicate Defense Forces could locate and use a drop pod to raid the shuttle.

=== Terragov's Intervention ===
Shortly after the development of the portable bluespace artillery pieces, TerraGov stepped in and issued an ultimatum “Stop the pointless war, or both of you will be destroyed”. This caused the corporate war to end abruptly, and without either corporation feeling satisfied with the results of the war. After this ultimatum, Both companies dialed back its own efforts against eachother, and began the old measures of deceit and undercover operations.

=== Chemical & Biological Weaponry ===
This continued how it did before, sabotage, double agents, and assassinations. Interdyne developed a multitude of new chemicals, mainly Vestine.

Vestine’s original creation is highly classified, its production is as you guessed highly classified. Its believed to be able to create advanced combat chemicals and biological weapons. Best known for Hyperzine, a combat stimulant able to keep soldiers fighting when they’re more dead than alive. Its second most known use is in the suspected creation of the Romerol virus, Originally created to act as a way to revert rotting using Vestine, it had the adverse effect of creating “zombies”. Which is now used as a biological weapon that cannot be easily traced to Interdyne, or their agents.

{{Lore Menu}}

Spider Clan

2026-09-09T17:50:02Z

DV vapetastic:

=== Origins of the Spider Clan ===
The origins of the Spider Clan have faded over time, with rumors stating they came from a Yakuza on earth sometime in the 22nd century, others suggest they come from an extremist faction of arachnids. The origin of the Spider Clan will most likely never come to light unless you become one of its higher ranks.

The spider clan is a name given by TerraGov to the faction, as the true name is only known by initiated members of the Spider Clan and is a closely guarded secret. Alongside TerraGov giving the Spider Clan its unofficial name, it’s also given it the label of a neutral faction within the galaxy, having no known base on any world or any known station hosting its faction.

They are primarily known for creating two things, the gene editing required to create Oni’s and their so called Space Ninjas. Both of these came from the same project, to create a super soldier worthy of handling anything the Spider Clan needed doing. Oni’s were also found to be a highly sought after genetic modification by humans, a watered down version of the gene edit can be found and purchased by anyone willing to pay.

The Space Ninjas became their main focus, having highly advanced suits capable of long term stealth in a compact package, and having capabilities to mass produce weapons for the cost of a decent amount of power. Alongside portable, reliable teleportation that uses no bluespace crystals.

The first confirmed spotting of a Space Ninja was in 2196 being caught briefly turning off their stealth capabilities to confront a high ranking Donk Co. executive before executing them. They were not originally linked to the spider clan until 2258 when the Spider Clan officially denounced the Syndicate for their stealing of technology and betrayal of the Spider Clan.

As of today, the Spider Clan is a secretive faction that has advanced stealth technology, holds many grudges, and intends to repay their grudges in blood or deception. Nanotrasen sees the Spider Clan as a faction that consistently steals research, but also shares a common enemy with the Syndicate.

{{Lore Menu}}

Spider Clan

2026-09-09T17:49:41Z

DV vapetastic:

=== Origins of the Spider Clan ===
The origins of the Spider Clan have faded over time, with rumors stating they came from a Yakuza on earth sometime in the 22nd century, others suggest they come from an extremist faction of arachnids. The origin of the Spider Clan will most likely never come to light unless you become one of its higher ranks.

The spider clan is a name given by TerraGov to the faction, as the true name is only known by initiated members of the Spider Clan and is a closely guarded secret. Alongside TerraGov giving the Spider Clan its unofficial name, it’s also given it the label of a neutral faction within the galaxy, having no known base on any world or any known station hosting its faction.

They are primarily known for creating two things, the gene editing required to create Oni’s and their so called Space Ninjas. Both of these came from the same project, to create a super soldier worthy of handling anything the Spider Clan needed doing. Oni’s were also found to be a highly sought after genetic modification by humans, a watered down version of the gene edit can be found and purchased by anyone willing to pay.

The Space Ninjas became their main focus, having highly advanced suits capable of long term stealth in a compact package, and having capabilities to mass produce weapons for the cost of a decent amount of power. Alongside portable, reliable teleportation that uses no bluespace crystals.

The first confirmed spotting of a space ninja was in 2196 being caught briefly turning off their stealth capabilities to confront a high ranking Donk Co. executive before executing them. They were not originally linked to the spider clan until 2258 when the Spider Clan officially denounced the Syndicate for their stealing of technology and betrayal of the Spider Clan.

As of today, the Spider Clan is a secretive faction that has advanced stealth technology, holds many grudges, and intends to repay their grudges in blood or deception. Nanotrasen sees the Spider Clan as a faction that consistently steals research, but also shares a common enemy with the Syndicate.

{{Lore Menu}}

Spider Clan

2026-09-09T17:41:31Z

DV vapetastic:

The origin of the Spiderclan has faded over time, with rumors stating they came from a Yakuza on the TerraGov cradle of earth, others suggest they come from an extremist faction of arachnids. The origin of the Spiderclan will most likely never come to light unless you are one of its higher ranks.

The spider clan is a name given by TerraGov to the faction, as the true name is only known by initiated members of the Spiderclan and is a closely guarded secret.
Alongside TerraGov giving the Spiderclan its unofficial name, it’s also given it the label of a neutral faction within the galaxy, having no known base on any world or any known space station hosting its faction. They are primarily known for creating two things, the gene editing required to create Oni’s and their space ninjas.
Both of these came from the same project, to create a super soldier worthy of handling anything the Spiderclan needed doing. Oni’s were also found to be a highly sought after genetic modification by humans, a dimmed down version of the gene edit can be found and purchased by anyone willing to pay.
The space ninjas were their main focus, having highly advanced suits capable of long term stealth in a compact package, and having capabilities to mass produce weapons for the cost of a decent amount of power. Alongside portable, reliable teleportation that uses no bluespace crystals.

The first confirmed spotting of a space ninja was in 2489 being caught briefly turning off their stealth capabilities to confront a high ranking Donk Co executive before executing them. They were not originally linked to the spider clan until 2534 when the Spiderclan officially denounced the syndicate for their stealing of technology and betrayal of the Spiderclan. Relations grew thin, while Nanotrasen and Terragov prepared for a cold or fullscale war between the two partys. While a fullscale war has never been noticed by Nanotrasen or TerraGov, they haven't confirmed that a cold war isn’t happening as well.

As of today, the Spiderclan is a secretive faction that have advanced stealth technology and holds many grudges and intends to repay their grudges in blood and deception.
Nanotrasen sees the Spiderclan as a faction that has messed with them before, but also shares a common enemy with the syndicate.

{{Lore Menu}}

Spider Clan

2026-09-09T17:41:17Z

DV vapetastic: Created page with "The origin of the Spiderclan has faded over time, with rumors stating they came from a Yakuza on the TerraGov cradle of earth, others suggest they come from an extremist faction of arachnids. The origin of the Spiderclan will most likely never come to light unless you are one of its higher ranks. The spider clan is a name given by TerraGov to the faction, as the true name is only known by initiated members of the Spiderclan and is a closely guarded secret. Alongside Te..."

Interdyne

2026-09-09T17:22:10Z

DV vapetastic:

== The origins of Interdyne Pharmaceuticals ==
Interdyne Pharmaceuticals was founded on Mars in the year 2046, being made of split off employees from the now defunct Freelight chemicals after an incident where executives cut bonuses from 94% of workers. Leading to a mass exodus from the company.

Their founders Izzy Norman, Terry Elman, Richard Din, Yancy Norman were four mid level chemical researchers that knew each other personally and participated in the Freelight mass exodus, eventually coming together to create a better company than their old bosses. Starting out as a local producer of Diethylamine and EZ Nutriment to prove that they can produce basic chemicals. Their one and only investor was a highly private man named Edward, who suggested the name INTERDYNE for their company upon investing, which was agreed to become the name of the company.

=== A foothold on Mars ===
Until 2102 Interdyne focused on producing chemicals for the growing hydroponics industry on mars, as its Major locations acted as a “space truckstop” for travelers needing mid journey refuels on food and water while heading to the outer Sol system.

In this time period they also discovered and patented Unstable Mutagen as a much quicker way of getting desired traits on crops that was considerably cheaper then GMO processes, gaining massive success from its sale across the industry.

Through the boost of funds coming from the selling of Unstable Mutagen, Interdyne would spread throughout the Sol system creating more research labs. A majority of these labs would be secret bases in the asteroid belt. Nanotrasen “accidentally” destroyed a decent portion of the labs while performing mining operations in the belt, Interdyne claims that this wasn’t a so-called accident but was a deliberate corporate sabotage of Interdyne research sites, thus beginning the rivalry between the two companies.

=== The cold war of Deceit ===
Interdyne is the first recorded company that sent agents into Nanotrasen to sabotage and steal corporate items, specifically the Hypospray that Nanotrasen had accidentally designed when creating a fuel pump system for their newest Micro Satellite Re-alignment Engines. A large shipment of Hyposprays designated for their newest created ERT division was considered missing upon arriving to the cargo depot, and upon reviewing camera footage and cargo hauler route coordinates, investigators pinned the crate to be lost in the asteroid belt, causing Nanotrasen to become suspicious of corporate sabotage caused by Interdyne. This began the official cold war between Interdyne and Nanotrasen.

The cold war primarily focused on taking blueprints/recipes for secret projects the other was working on, reverse engineering it and then claiming their company had made it first. Both companies began to withold patenting their secret technology so the other couldn’t copy it and use it in secret.

During the cold war, both Interdyne and Nanotrasen began to collect allies. Interdyne did so through corporate deals and contracts, Nanotrasen through buyouts and lobbying.

Interdynes corporate deals primarily working with Cybersun, Donk Co, MI13, and Tyger Dynamics. While Nanotrasen began lobbying local planet governments to only use Nanotrasen provided items for their government. In an effort to limit Interdyne from expanding further, while also beginning to buy out smaller companies. A company of note was a lunar based AI and robot based company named Tadashi Industries, which is how Nanotrasen got its station AI cores and Cyborg helpers.

Interdyne began to reinforce ties between their partnered corporations, forming what we know as today as the Syndicate.

Nanotrasen stations commonly have nuclear devices onboard in case of two scenarios, an infestation of the blob which is now suspected to be extinct, or the station had rebelled and the responding SRT/ERT have declared the station unsaveable and chosen to scuttle it instead. This system had a failsafe of premature detonation, it had no software to arm the device loaded onto it. Instead the software to arm it was stored inside of a NAD (nuclear authentication disk). This was commonly kept on the captain or head of security. Alongside this failsafe a code was also required to arm it, this was only given to the station if asked for or when the stations automated systems detected a blob infestation. Unfortunately the machine that randomized the codes to the nuclear devices was not truly random, and after heavy research into Redspace, the Syndicate gained access to codes to Nanotrasen's nuclear devices.

Upon initiating a nuclear raid on a site, the marauders would enter into the drop pod and launch themselves at the station, crashing a hole through the station and blitzkrieging the nuclear disk to quickly activate the nuclear device.

Upon grabbing the disk and activation, nuclear operatives are trained to defend the nuclear bomb until it detonates to prevent defusion.

This strategy only works because of Interdyne's newest medical research, cloning.

Cloning was developed around the same time as the Gorlex Marauders was formed, although its quirks weren't fully ironed out yet resulting in the clone Marauders having genetic deformities. These deformities were ironed out after the third drop pod attack was done. But the marauders had actually stated that they liked some of the new bodies the cloning pods created. This would create the species known as Felinid, Harpy, and Rodentia. Interdyne would research these deformities and create a gene therapy procedure to allow customers to become one of these species.

Eventually Nanotrasen would develop technology that allowed bluespace artillery be put onto shuttle craft, allowing them to fire and quickly leave the area before the Syndicate Defense Forces could locate and use a drop pod to raid the shuttle.

=== Terragov's Intervention ===
Shortly after the development of the portable bluespace artillery pieces, TerraGov stepped in and issued an ultimatum “Stop the pointless war, or both of you will be destroyed”. This caused the corporate war to end abruptly, and without either corporation feeling satisfied with the results of the war. After this ultimatum, Both companies dialed back its own efforts against eachother, and began the old measures of deceit and undercover operations.

=== Chemical & Biological Weaponry ===
This continued how it did before, sabotage, double agents, and assassinations. Interdyne developed a multitude of new chemicals, mainly Vestine.

Vestine’s original creation is highly classified, its production is as you guessed highly classified. Its believed to be able to create advanced combat chemicals and biological weapons. Best known for Hyperzine, a combat stimulant able to keep soldiers fighting when they’re more dead than alive. Its second most known use is in the suspected creation of the Romerol virus, Originally created to act as a way to revert rotting using Vestine, it had the adverse effect of creating “zombies”. Which is now used as a biological weapon that cannot be easily traced to Interdyne, or their agents.

{{Lore Menu}}

Interdyne

2026-09-09T17:21:52Z

DV vapetastic: /* A foothold on Mars */

== The origins of Interdyne Pharmaceuticals ==
Interdyne Pharmaceuticals was founded on Mars in the year 2046, being made of split off employees from the now defunct Freelight chemicals after an incident where executives cut bonuses from 94% of workers. Leading to a mass exodus from the company.

Their founders Izzy Norman, Terry Elman, Richard Din, Yancy Norman were four mid level chemical researchers that knew each other personally and participated in the Freelight mass exodus, eventually coming together to create a better company than their old bosses. Starting out as a local producer of Diethylamine and EZ Nutriment to prove that they can produce basic chemicals. Their one and only investor was a highly private man named Edward, who suggested the name INTERDYNE for their company upon investing, which was agreed to become the name of the company.

=== A foothold on Mars ===
Until 2102 Interdyne focused on producing chemicals for the growing hydroponics industry on mars, as its Major locations acted as a “space truckstop” for travelers needing mid journey refuels on food and water while heading to the outer Sol system.

In this time period they also discovered and patented Unstable Mutagen as a much quicker way of getting desired traits on crops that was considerably cheaper then GMO processes, gaining massive success from its sale across the industry.

Through the boost of funds coming from the selling of Unstable Mutagen, Interdyne would spread throughout the Sol system creating more research labs. A majority of these labs would be secret bases in the asteroid belt. Nanotrasen “accidentally” destroyed a decent portion of the labs while performing mining operations in the belt, Interdyne claims that this wasn’t a so-called accident but was a deliberate corporate sabotage of Interdyne research sites, thus beginning the rivalry between the two companies.

=== The cold war of Deceit ===
Interdyne is the first recorded company that sent agents into Nanotrasen to sabotage and steal corporate items, specifically the Hypospray that Nanotrasen had accidentally designed when creating a fuel pump system for their newest Micro Satellite Re-alignment Engines. A large shipment of Hyposprays designated for their newest created ERT division was considered missing upon arriving to the cargo depot, and upon reviewing camera footage and cargo hauler route coordinates, investigators pinned the crate to be lost in the asteroid belt, causing Nanotrasen to become suspicious of corporate sabotage caused by Interdyne. This began the official cold war between Interdyne and Nanotrasen.

The cold war primarily focused on taking blueprints/recipes for secret projects the other was working on, reverse engineering it and then claiming their company had made it first. Both companies began to withold patenting their secret technology so the other couldn’t copy it and use it in secret.

During the cold war, both Interdyne and Nanotrasen began to collect allies. Interdyne did so through corporate deals and contracts, Nanotrasen through buyouts and lobbying.

Interdynes corporate deals primarily working with Cybersun, Donk Co, MI13, and Tyger Dynamics. While Nanotrasen began lobbying local planet governments to only use Nanotrasen provided items for their government. In an effort to limit Interdyne from expanding further, while also beginning to buy out smaller companies. A company of note was a lunar based AI and robot based company named Tadashi Industries, which is how Nanotrasen got its station AI cores and Cyborg helpers.

Interdyne began to reinforce ties between their partnered corporations, forming what we know as today as the Syndicate.

Nanotrasen stations commonly have nuclear devices onboard in case of two scenarios, an infestation of the blob which is now suspected to be extinct, or the station had rebelled and the responding SRT/ERT have declared the station unsaveable and chosen to scuttle it instead. This system had a failsafe of premature detonation, it had no software to arm the device loaded onto it. Instead the software to arm it was stored inside of a NAD (nuclear authentication disk). This was commonly kept on the captain or head of security. Alongside this failsafe a code was also required to arm it, this was only given to the station if asked for or when the stations automated systems detected a blob infestation. Unfortunately the machine that randomized the codes to the nuclear devices was not truly random, and after heavy research into Redspace, the Syndicate gained access to codes to Nanotrasen's nuclear devices.

Upon initiating a nuclear raid on a site, the marauders would enter into the drop pod and launch themselves at the station, crashing a hole through the station and blitzkrieging the nuclear disk to quickly activate the nuclear device.

Upon grabbing the disk and activation, nuclear operatives are trained to defend the nuclear bomb until it detonates to prevent defusion.

This strategy only works because of Interdyne's newest medical research, cloning.

Cloning was developed around the same time as the Gorlex Marauders was formed, although its quirks weren't fully ironed out yet resulting in the clone Marauders having genetic deformities. These deformities were ironed out after the third drop pod attack was done. But the marauders had actually stated that they liked some of the new bodies the cloning pods created. This would create the species known as Felinid, Harpy, and Rodentia. Interdyne would research these deformities and create a gene therapy procedure to allow customers to become one of these species.

Eventually Nanotrasen would develop technology that allowed bluespace artillery be put onto shuttle craft, allowing them to fire and quickly leave the area before the Syndicate Defense Forces could locate and use a drop pod to raid the shuttle.

=== Terragov's Intervention ===
Shortly after the development of the portable bluespace artillery pieces, TerraGov stepped in and issued an ultimatum “Stop the pointless war, or both of you will be destroyed”. This caused the corporate war to end abruptly, and without either corporation feeling satisfied with the results of the war. After this ultimatum, Both companies dialed back its own efforts against eachother, and began the old measures of deceit and undercover operations.

=== Chemical & Biological Weaponry ===
This continued how it did before, sabotage, double agents, and assassinations. Interdyne developed a multitude of new chemicals, mainly Vestine.

Vestine’s original creation is highly classified, its production is as you guessed highly classified. Its believed to be able to create advanced combat chemicals and biological weapons. Best known for Hyperzine, a combat stimulant able to keep soldiers fighting when they’re more dead than alive. Its second most known use is in the suspected creation of the Romerol virus, Originally created to act as a way to revert rotting using Vestine, it had the adverse effect of creating “zombies”. Which is now used as a biological weapon that cannot be easily traced to Interdyne, or their agents.

Interdyne

2026-09-09T17:07:22Z

DV vapetastic: Created page with "== The origins of Interdyne Pharmaceuticals == Interdyne Pharmaceuticals was founded on Mars in the year 2046, being made of split off employees from the now defunct Freelight chemicals after an incident where executives cut bonuses from 94% of workers. Leading to a mass exodus from the company. Their founders Izzy Norman, Terry Elman, Richard Din, Yancy Norman were four mid level chemical researchers that knew each other personally and participated in the Freelight ma..."

== The origins of Interdyne Pharmaceuticals ==
Interdyne Pharmaceuticals was founded on Mars in the year 2046, being made of split off employees from the now defunct Freelight chemicals after an incident where executives cut bonuses from 94% of workers. Leading to a mass exodus from the company.

Their founders Izzy Norman, Terry Elman, Richard Din, Yancy Norman were four mid level chemical researchers that knew each other personally and participated in the Freelight mass exodus, eventually coming together to create a better company than their old bosses. Starting out as a local producer of Diethylamine and EZ Nutriment to prove that they can produce basic chemicals. Their one and only investor was a highly private man named Edward, who suggested the name INTERDYNE for their company upon investing, which was agreed to become the name of the company.

=== A foothold on Mars ===
Until 2102 Interdyne focused on producing chemicals for the growing hydroponics industry on mars, as its Major locations acted as a “space truckstop” for travelers needing mid journey refuels on food and water while heading to the outer Sol system.

In this time period they also discovered and patented Unstable Mutagen as a much quicker way of getting desired traits on crops that was considerably cheaper then GMO processes, gaining massive success from its sale across the industry.

Through the boost of funds coming from the selling of Unstable Mutagen, interdyne would spread throughout the Sol system creating more research labs. A majority of these labs would be secret bases in the asteroid belt. Nanotrasen would “accidentally” destroy a decent portion of the labs while performing mining operations in the belt, Interdyne claims that this wasn’t a so-called accident but was a deliberate corporate sabotage of Interdyne research sites, thus beginning the rivalry between the two companies.

=== The cold war of Deceit ===
Interdyne would be the first recorded company to begin to send agents into Nanotrasen to sabotage and steal corporate items, specifically the Hypospray Nanotrasen had accidentally designed when creating a fuel pump system for their newest rocket engines. A large shipment of Hyposprays designated for their newest created ERT division was considered missing upon arriving to the cargo depot, and upon reviewing camera footage and cargo hauler route coordinates pinned the crate to be lost in the asteroid belt, causing Nanotrasen to become suspicious of corporate sabotage caused by Interdyne. This began the official cold war between Interdyne and Nanotrasen.

This cold war would primarily focus on taking blueprints/recipes for secret projects the other was working on, reverse engineering it and then claiming their company had made it first. Both companies would withold patenting their secret technology so the other couldn’t copy it and use it in secret.

During this cold war both Interdyne and Nanotrasen began to collect allies, Interdyne through corporate deals and contracts, and Nanotrasen through buyouts and lobbying.

Interdynes corporate deals with other corporations would become a proto version of the syndicate, working with Cybersun, Donk Co, Waffle company, and possibly more. While Nanotrasen would lobbying local planet governments to only use Nanotrasen provided items for their government. In an effort to limit Interdyne from expanding further, while also beginning to buy out smaller companies. a company of note was a lunar based AI and robot based company named Tadashi industries, which is how Nanotrasen got its station AI cores and Cyborg helpers.

Interdyne began to reinforce ties between their partnered corporations, forming what we know as today as the Syndicate.

Nanotrasen stations commonly have nuclear devices onboard in case of two scenarios, an infestation of the blob which is now suspected to be extinct, or the station had rebelled and the responding SRT/ERT have declared the station unsaveable and chosen to scuttle it instead. This system had a failsafe of premature detonation, it had no software to arm the device loaded onto it. Instead the software to arm it was stored inside of a NAD (nuclear authentication disk). This was commonly kept on the captain or head of security. Alongside this failsafe a code was also required to arm it, this was only given to the station if asked for or when the stations automated systems detected a blob infestation. Unfortunately the machine that randomized the codes to the nuclear devices was not truly random, and after heavy research into Redspace, the Syndicate gained access to codes to Nanotrasen's nuclear devices.

Upon initiating a nuclear raid on a site, the marauders would enter into the drop pod and launch themselves at the station, crashing a hole through the station and blitzkrieging the nuclear disk to quickly activate the nuclear device.

Upon grabbing the disk and activation, nuclear operatives are trained to defend the nuclear bomb until it detonates to prevent defusion.

This strategy only works because of Interdyne's newest medical research, cloning.

Cloning was developed around the same time as the Gorlex Marauders was formed, although its quirks weren't fully ironed out yet resulting in the clone Marauders having genetic deformities. These deformities were ironed out after the third drop pod attack was done. But the marauders had actually stated that they liked some of the new bodies the cloning pods created. This would create the species known as Felinid, Harpy, and Rodentia. Interdyne would research these deformities and create a gene therapy procedure to allow customers to become one of these species.

Eventually Nanotrasen would develop technology that allowed bluespace artillery be put onto shuttle craft, allowing them to fire and quickly leave the area before the Syndicate Defense Forces could locate and use a drop pod to raid the shuttle.

=== Terragov's Intervention ===
Shortly after this development of the portable bluespace artillery pieces, TerraGov stepped in and issued an ultimatum to both groups. “Stop the pointless war, or both of you will be destroyed”. This caused the outright war to end abruptly, and without either corporation feeling satisfied with the results of the war. This began the current day cold war that NanoTrasen and the syndicate has.

=== Chemical & Biological Weaponry ===
The current cold war continued how it did before, sabotage, double agents, and assassinations. But Interdyne developed a multitude of new chemicals, mainly Vestine.

Vestine’s original creation is highly classified, its production is as you guessed highly classified. Its believed to be able to create advanced combat chemicals and biological weapons. Best known for Hyperzine, a combat stimulant able to keep soldiers fighting when they’re more dead than alive. Its second most known use is in the suspected creation of the Romerol virus, Originally created to act as a way to revert rotting using Vestine, it had the adverse effect of creating “zombies”. Which is now used as a biological weapon that cannot be easily traced to Interdyne, or their agents.

Theocratic Monarchy of Verdanova

2026-09-09T16:53:19Z

DV vapetastic:

== '''Theocratic Monarchy of Verdanova''' ==
The humble world of Saõ Pedro is now a bustling hub of churches, cathedrals and ceremonies. Following traditions dating back centuries. The world was colonized by old Portuguese Colonists attempting to safeguard their culture from its possible extinction, the inhabitants of this world have now reinforced these traditions. A monarchy was established to rule over the planet, soon expanding further outward into the void. Saõ Pedro is the home of His most celestial majesty, '''King Pedro XII''', who is worshipped as a living god among his people. People have often referred to this as Celestialism. Known as a '''His Most Celestial Majesty''' or '''The Sage King''', King Pedro XII is a staunch supporter of The Church of Celestialism.

'''The Theocratic Monarchy of Verdanova''' is not a great power among the nations in the void, but they do have a pivotal role in safeguarding trade routes. These trade routes are enforced by the '''Provincial Protection Corps'''. Better known as the '''PPC''', its attempts to safeguard trade routes have made the '''TMV''' a favored customer among most corporations.

The '''TMV''' hosts a moderate number of worlds, with billions of sapients living under the monarchy. Sapients are not discriminated against, as the '''Celestial King''' marks all of them as subjects of the throne, rather than conforming to one race.

'''Verdanova''' was founded in the '''Pleiades Cluster''' (often referred to as the Seven Sisters, or The Gateway), with their capital in the system of '''Alcyone'''. With multiple habitable planets within this cluster, '''Verdanova''' has successfully expanded to the entire cluster.

Due to the clusters close location to Sol and thus [[Terragov|TerraGov]], '''Verdanova''' has become a major logistical powerhouse, and makes most of it's income hauling and trading goods between Sol and the “Outer Rim” Colonies and Companies.

[[History of the Delta Sector#Nanotrasen|Nanotrasen]] frequently Commissions '''Verdanovan''' '''Vessels''' and Captains for transportation and guidance when flying through or to harsh systems.

'''Verdanovans''' are required to be indoctrinated into the “Church of Celestialism”. While [[History of the Delta Sector#Nanotrasen|Nanotrasen]] has limited information on the church, it is widely suspected that this Church performs multiple psionic experiments on persons of the church.

While [[History of the Delta Sector#Nanotrasen|Nanotrasen]] has documented the first true contact with Psionic powers, once this was shared with multiple “Allied factions” approximately 90% of the '''Verdanovan''' population were documented as “New” hosts to multiple psyonic powers.

'''Verdanovan''' priests suggest that “their people are accepted by the gods, and in return are granted extreme powers that no other shall ever experience”.

After {REDACTED BY ORDER OF CC}, it was found that '''Verdanovan''' Psionic hosts are capable of sharing this so called “'''Divinity'''” with others, and can even bless a Psionic host to allow their powers to grow, or upgrade.

{{Lore Menu}}

Theocratic Monarchy of Verdanova

2026-09-09T16:51:14Z

DV vapetastic:

== '''Theocratic Monarchy of Verdanova''' ==
The humble world of Saõ Pedro is now a bustling hub of churches, cathedrals and ceremonies. Following traditions dating back centuries. The world was colonized by old Portuguese Colonists attempting to safeguard their culture from its possible extinction, the inhabitants of this world have now reinforced these traditions. A monarchy was established to rule over the planet, soon expanding further outward into the void. Saõ Pedro is the home of His most celestial majesty, '''King Pedro XII''', who is worshipped as a living god among his people. People have often referred to this as Celestialism. Known as a '''His Most Celestial Majesty''' or '''The Sage King''', King Pedro XII is a staunch supporter of The Church of Psionics.

'''The Theocratic Monarchy of Verdanova''' is not necessarily a great power among the nations in the void, but they do have a pivotal role in safeguarding trade routes. These trade routes are enforced by the '''Provincial Protection Corps'''. Better known as the '''PPC''', its attempts to safeguard trade routes have made the '''TMV''' a favored customer among most corporations.

The '''TMV''' hosts a moderate number of worlds, with millions of sapients living under the monarchy. Sapients are not discriminated against, as the '''Celestial King''' marks all of them as subjects of the throne, rather than conforming to one race.

'''Verdanova''' was founded in the '''Pleiades Cluster''' (often referred to as the Seven Sisters, or The Gateway), with their capital in the system of '''Alcyone'''. With multiple habitable planets within this cluster, '''Verdanova''' has successfully expanded to the entire cluster.

Due to the clusters close location to Sol and thus [[Terragov|TerraGov]], '''Verdanova''' has become a major logistical powerhouse, and makes most of it's income hauling and trading goods between Sol and the “Outer Rim” Colonies and Companies.

[[History of the Delta Sector#Nanotrasen|Nanotrasen]] frequently Commissions '''Verdanovan''' '''Vessels''' and Captains for transportation and guidance when flying through or to harsh systems.

'''Verdanovans''' are required to be indoctrinated into the “Church of Psionics”. While [[History of the Delta Sector#Nanotrasen|Nanotrasen]] has limited information on the church, it is widely suspected that this Church performs multiple experiments on persons of the church.

While [[History of the Delta Sector#Nanotrasen|Nanotrasen]] has documented the first true contact with Psionic powers, once this was shared with multiple “Allied factions” approximately 90% of the '''Verdanovan''' population were documented as “New” hosts to multiple psyonic powers.

'''Verdanovan''' priests suggest that “their people are accepted by the gods, and in return are granted extreme powers that no other shall ever experience”.

After {REDACTED BY ORDER OF CC}, it was found that '''Verdanovan''' Psionic hosts are capable of sharing this so called “'''Divinity'''” with others, and can even bless a Psionic host to allow their powers to grow, or upgrade.

{{Lore Menu}}

Betelgeuse Consortium

2026-09-09T16:49:25Z

DV vapetastic:

== '''Betelgeuse Consortium (BGC)''' ==
A long history of trade, oppression and profit tells the story of the '''Betelgeuse Consortium'''. Descendants of Old Terran colonists, the '''Betelgeuse''' system was a vital system for trade, settled in between most major settled systems. Throughout the chaos of old colonial wars, executives have mostly seized power in '''Nouvelle Montreal''', the capital of the '''BGC''' and its surrounding planets and systems.

While the board isnt popular with its rule, its economic power cannot be denied. Many trade stations owe their profits to the '''BGC''' and have been largely “bought out”. Dissidence in the '''BGC''' is overshadowed by the nations extreme propaganda system. According to the Board of Directors, everyone is happy and healthy within the '''BGC'''.

With Interstellar trade, the '''BGC''' has one major factor to it's participation, Medical Research and Technology. The '''BGC''' is known as the “Powerhouse” of the Medical field, with the most advanced Cybernetic and Healing technologies being marked as proprietary '''BGC''' Technology. [[History of the Delta Sector#Nanotrasen|Nanotrasen]] regularly trades and purchases these items from '''BGC'''.

{{Lore Menu}}

The Free Sapient Charter

2026-09-09T16:49:11Z

DV vapetastic:

== '''The Free Sapient Charter''' ==
'''The Free Sapient Charter''' is lead by a '''[[Playable Species#Thaven|Thaven]]''' named “''Freedom Be-Thy-Birthright''”. Originally founded on a slaver ship named ''The Unbowed'', carrying thousands of poor souls bound for unknown destinations to be illegally auctioned off away from '''[[Terragov|TerraGov’s]]''' prying eyes.

'''The Free Sapient Charter''' was founded upon the believe that freedom is a right to everyone. There are no jails, no laws, and most importantly everything can be aqqcuired by freedom in some way shape or form.

The Unbowed was overtaken by ''Freedom Be-Thy-Birthright'', and “Landed” on Vorn VII, many lightyears away from inhabited space.

'''The Free Sapient Charter''' Capital is on Vorn VII, located in the [[History of the Delta Sector|Delta V sector]], and shortly after colinization, the system was renamed to “''The Hope of Life''”. It's Capital City is named “''Trust and Honor''”

Not much is known about the '''Free Sapient Charter''', However they are a frequent visitor to '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' and [[Terragov|TerraGov]] Facilities. [[History of the Delta Sector#Nanotrasen|Nanotrasen]] has begun “courting” this particular group in hopes to absorb “The Hope of Life” into it's conglomerate of Stations within the [[History of the Delta Sector|Delta V sector]].

With most planets in “''The'' ''Hope of Life''” system being habitable by most lifeforms, [[History of the Delta Sector#Nanotrasen|'''Nanotrasen''']] has made it their top priority to align themselves with this faction and appease them by any means necessary.

While many talks have been made, '''The Free Sapient Charter''' has allowed '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' to construct one singular planetary station, however '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' has not began shipments to this system due to security concerns.

Due to [[History of the Delta Sector#Nanotrasen|'''Nanotrasen'''<nowiki/>'s]] succsessful naval defense networks, the syndicate and it's conglomerates have no information or ability to reach “''The'' ''Hope of Life”''. Due to {REDACTED BY ORDER OF CC} '''The Free Sapient Charter''' has no wishes to align themselves with the syndicate, and outright despises them.

{{Lore Menu}}

Nanotrasen

2026-09-09T16:48:59Z

DV vapetastic:

==== '''NanoTrasen (NT)''' ====
What started out as a relatively small and humble organization tasked by the United Nations in 2055 with exploration and discovery had bolstered itself into possibly the largest single entity in the known galaxy. Using cut-throat business tactics they easily dominated their competition, absorbing many rival corporations into their ranks. They remain the dominant superpower in the research, development, and exploration sectors.

== '''Nanotrasen''' ==
'''Nanotrasen''' is the dominant megacorporation of the universe. While ostensibly bowing to '''[[Terragov]]''', '''Nanotrasen''' separately controls multiple galaxies, holds a monopoly over Plasma research, Laser technology, [[History of the Delta Sector#Psionics|'''Psionic''' '''technology''']], and dozens if not hundreds of other industries through a combination of sheer resources, underhanded tactics, and in some cases outright corporate war. There are multiple different stories for '''Nanotrasen’s''' origin, however in the hundreds of years since it’s founding along with the immense, bloated, almost unknowable size the only confirmed details are that '''Nanotrasen''' started as a small company on earth, and was one of the main drivers of the space race that led to the colonization of the universe.

{{Lore Menu}}

History of the Delta Sector

2026-09-09T16:48:45Z

DV vapetastic:

== '''Origins of the Delta Sector''' ==
The '''Delta Sector''' was originally known as the Nexus. Named as such by the [[History of the Delta Sector#The Wizard’s Federation|'''Wizard’s Federation''']] who discovered the sector. They found that out of the known universe, the '''Delta Sector''' was where the veil between realspace and the '''[[History of the Delta Sector#The Noosphere|Noosphere]]''' was weakest. While they were able to keep it’s existence secret for 200 years, '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' eventually managed to discover it through {REDACTED BY ORDER OF CC} . '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' had already been doing research into developing '''[[History of the Delta Sector#Psionics|psionics]]''' as a way to get an advantage in their war with the syndicate, but without knowledge of their origin or nature progress had been slow. In the Nexus, they saw opportunity. War broke out, and while the [[History of the Delta Sector#The Wizard’s Federation|Wizard's Federation]] fought fiercely, {REDACTED BY ORDER OF CC}. Research stations were built in their place and the Nexus was renamed to the '''Delta Sector'''.

== '''Psionics''' ==
'''Psionics''' are various powers and abilities who draw their origin from the '''[[History of the Delta Sector#Noosphere|Noosphere]]'''. Psychic powers, miracles and blessings of faith, and even spells such as those used by the wizards are all types of psionics manifested differently and developed through a different lens. There are other schools of '''Psionics''' to be found as well, such as Fire Manipulation; However, these are poorly understood and haven’t been officially classified as of yet.

One of the main things understood about '''psionics''' is that once someone has gained the ability to wield them, almost all powers depend upon the wielder’s strength of will. It is commonly believed that they manifest by the wielder forming a piece of the '''[[History of the Delta Sector#Noosphere|noosphere]]''' according to their desires and effectively “overwriting” reality with their will. However, a strong will is '''not''' an indicator of one’s capability to cast a psionic power. What determines who is and is not psionic is unfortunately still not understood, only that some species such as the [[Playable Species#Kitsune|Kitsune]] or the Ifrit are typically psionic or more likely to develop psionics.

== '''The Noosphere''' ==
The '''Noosphere''' has gone by many names and has been described as many things. A Collective Unconscious, a Psychic energy field, a separate plane of reality entirely, the coalesced dreams of mortals... The exact nature of the '''Noosphere''' is unknown, beyond the fact that it is a place that you can go into, and that it is the source of most supernatural phenomena. Multiple factions, most recently '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''', have attempted to tap into its power to turn the tides of corporate war into their favor. However its influence was felt long before the corporations turned their attention towards it. It was only with '''[[History of the Delta Sector#Nanotrasen|Nanotrasen’s]]''' research into it that someone attempted to understand it scientifically.

== '''The Wizard’s Federation''' ==
The '''Wizard’s Federation''' was one of the first to observe the phenomenon known as '''[[History of the Delta Sector#Psionics|Psionics]]'''. As it is with power, many years passed and those in charge slowly became corrupt. Study became less for how to keep the universe safe, and more for increasing their own power. Arrogance became commonplace. Though some wizards chose to stay true to their ideals, the council who held leadership became blinded by their own power. This was, perhaps, the reason for the fall of the '''[[History of the Delta Sector#Origin of the Delta Sector|Nexus]]'''. While many wizards sought to defend it for their own power, a mix of in-fighting and just as many wizards seeing it’s loss as a rightful kick in the teeth to the archmages all but signed their loss in the war. The '''Wizards Federation''' was fully wiped out in 2410 by '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]'''. It is not documented why [[History of the Delta Sector#Nanotrasen|Nanotrasen]] actively warred against this faction however some say {REDACTED BY ORDER OF CC} is to blame.

{{Lore Menu}}

Nanotrasen

2026-09-09T16:48:02Z

DV vapetastic:

United Nations of Earth

2026-09-09T16:46:56Z

DV vapetastic:

== '''Unified Earth Administration (UEA)''' ==
In order to consolidate and organize the new age of space travel, the combined countries of '''Earth under the United Nations''' formed what is known as the '''Unified Earth Administration''' in 2100, a single entity tasked with the governance of both planet Earth and its off-world colonies such as the Lunar Refueling Depot and the Europa Scientific Research Colony. The '''UEA''' operates as an electoral democracy with representatives elected from each of the sovereign countries on Earth. While the countries continue to govern themselves individually, they all fall under the '''UEA’s''' policies and laws.

In 2156, after major infighting and a 10 year long legislative gridlock across the '''UEA''' Senate and Judiciary Council, the '''[[United Nations Armed Forces|UNAF]]''' commandeered control over Sol and it's colonies, leading to a major collapse of the '''UEA''' and it's leadership.

It is believed that major corporations such as '''Donk Co.''' and '''Cybersun''' and {REDACTED BY ORDER OF CC} assisted the [[United Nations Armed Forces|UNAF]] in establishing control after the '''UEA''' Senate attempted to pass a 60% Space Corporation tax across all colonies, <code>however many believe this is just a conspiracy.</code>

{{Lore Menu}}

History of Sol and Earth

2026-09-09T16:46:42Z

DV vapetastic:

History of Sol and Earth

2026-09-09T16:45:37Z

DV vapetastic:

History of Sol and Earth

2026-09-09T16:11:37Z

DV vapetastic: Created page with "=== '''Background''' === In the year 2053, small reservoirs of plasma (Also known as Phoron) were discovered on the moon. This highly volatile substance was the catalyst that kicked-off humanity’s age of space exploration. Soon enough, humans had spread out to the far corners of the galaxy, colonizing thousands of planets. Mega-Corporations began to surface as the powerhouses of multiple star systems, using their immense wealth to subjugate and exploit the natives of u..."

=== '''Background''' ===
In the year 2053, small reservoirs of plasma (Also known as Phoron) were discovered on the moon. This highly volatile substance was the catalyst that kicked-off humanity’s age of space exploration. Soon enough, humans had spread out to the far corners of the galaxy, colonizing thousands of planets. Mega-Corporations began to surface as the powerhouses of multiple star systems, using their immense wealth to subjugate and exploit the natives of underdeveloped planets to further their own agendas. Many of these Mega-Corporations established themselves as sovereign entities, akin to an earthly autocracy with its own systems of government, security, and justice.

==== '''NanoTrasen (NT)''' ====
What started out as a relatively small and humble organization tasked by the United Nations in 2055 with exploration and discovery had bolstered itself into possibly the largest single entity in the known galaxy. Using cut-throat business tactics they easily dominated their competition, absorbing many rival corporations into their ranks. They remain the dominant superpower in the research, development, and exploration sectors.

Template:Lore Menu

2026-09-09T16:07:46Z

DV vapetastic:

{| class="wikitable mw-collapsible" width=100% style="font-size: 95%"
|-
! colspan=2 style="font-size: 95%; border: 2px solid #000000" | [[Delta V Lore]]
|-
| style="width:24%; text-align:right; background: #630813; border: 2px solid #000000" | '''Historical Documents'''
| style="border: 2px solid #000000" | [[History of Sol and Earth]] · [[United Nations of Earth]] · [[United Nations Armed Forces]] · [[History of the Delta Sector]]
|-
| style="text-align:right; background: #132c5e; border: 2px solid #000000" | '''Minor Nations'''
| style="border: 2px solid #000000" | [[The Free Sapient Charter]] · [[The Wesk'Rir Nation]] · [[Betelgeuse Consortium]] · [[Kosanikaan Confederation]]
|-
| style="text-align:right; background: #3258a6; border: 2px solid #000000" | '''Major Nations'''
| style="border: 2px solid #000000" | [[Terragov]] · [[Tengoku Commonwealth]] · [[Theocratic Monarchy of Verdanova]]
|-
| style="text-align:right; background: #014a41; border: 2px solid #000000" | '''Minor Corporations'''
| style="border: 2px solid #000000" | [[Gorlex]] · [[Donk Company]] · [[MI13]] · [[Tyger Dynamics]]
|-
| style="text-align:right; background: #018c7c; border: 2px solid #000000" | '''Major Corporations'''
| style="border: 2px solid #000000" | [[Nanotrasen]] · [[Interdyne]] · [[Cybersun]]
|-
| style="text-align:right; background: #360101; border: 2px solid #000000" | '''Clans and Cults'''
| style="border: 2px solid #000000" | [[Cosmic Cult]] · [[Clockwork Cult]] · [[Spider Clan]]
|}<noinclude>

== Usage ==
Navigational template for the [[Delta V Lore|Lore]] category. Includes an automatic categorization of the page into said category. To use it, write:

<pre>
{{Lore Menu}}
</pre>

[[Category:Templates]]
</noinclude>
<includeonly>[[Category:Lore]]</includeonly>

History of the Delta Sector

2026-09-09T16:05:40Z

DV vapetastic:

== '''Origin of the Delta Sector''' ==
The '''Delta Sector''' was originally known as the Nexus. Named as such by the [[History of the Delta Sector#The Wizard’s Federation|'''Wizard’s Federation''']] who discovered the sector. They found that out of the known universe, the '''Delta Sector''' was where the veil between realspace and the '''[[History of the Delta Sector#The Noosphere|Noosphere]]''' was weakest. While they were able to keep it’s existence secret for 200 years, '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' eventually managed to discover it through {REDACTED BY ORDER OF CC} . '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' had already been doing research into developing '''[[History of the Delta Sector#Psionics|psionics]]''' as a way to get an advantage in their war with the syndicate, but without knowledge of their origin or nature progress had been slow. In the Nexus, they saw opportunity. War broke out, and while the [[History of the Delta Sector#The Wizard’s Federation|Wizard's Federation]] fought fiercely, {REDACTED BY ORDER OF CC}. Research stations were built in their place and the Nexus was renamed to the '''Delta Sector'''.

== '''Psionics''' ==
'''Psionics''' are various powers and abilities who draw their origin from the '''[[History of the Delta Sector#Noosphere|Noosphere]]'''. Psychic powers, miracles and blessings of faith, and even spells such as those used by the wizards are all types of psionics manifested differently and developed through a different lens. There are other schools of '''Psionics''' to be found as well, such as Fire Manipulation; However, these are poorly understood and haven’t been officially classified as of yet.

One of the main things understood about '''psionics''' is that once someone has gained the ability to wield them, almost all powers depend upon the wielder’s strength of will. It is commonly believed that they manifest by the wielder forming a piece of the '''[[History of the Delta Sector#Noosphere|noosphere]]''' according to their desires and effectively “overwriting” reality with their will. However, a strong will is '''not''' an indicator of one’s capability to cast a psionic power. What determines who is and is not psionic is unfortunately still not understood, only that some species such as the [[Playable Species#Kitsune|Kitsune]] or the Ifrit are typically psionic or more likely to develop psionics.

== '''The Noosphere''' ==
The '''Noosphere''' has gone by many names and has been described as many things. A Collective Unconscious, a Psychic energy field, a separate plane of reality entirely, the coalesced dreams of mortals... The exact nature of the '''Noosphere''' is unknown, beyond the fact that it is a place that you can go into, and that it is the source of most supernatural phenomena. Multiple factions, most recently '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''', have attempted to tap into its power to turn the tides of corporate war into their favor. However its influence was felt long before the corporations turned their attention towards it. It was only with '''[[History of the Delta Sector#Nanotrasen|Nanotrasen’s]]''' research into it that someone attempted to understand it scientifically.

== '''Nanotrasen''' ==
'''Nanotrasen''' is the dominant megacorporation of the universe. While ostensibly bowing to '''[[Terragov]]''', '''Nanotrasen''' separately controls multiple galaxies, holds a monopoly over Plasma research, Laser technology, [[History of the Delta Sector#Psionics|'''Psionic''' '''technology''']], and dozens if not hundreds of other industries through a combination of sheer resources, underhanded tactics, and in some cases outright corporate war. There are multiple different stories for '''Nanotrasen’s''' origin, however in the hundreds of years since it’s founding along with the immense, bloated, almost unknowable size the only confirmed details are that '''Nanotrasen''' started as a small company on earth, and was one of the main drivers of the space race that led to the colonization of the universe.

== '''The Wizard’s Federation''' ==
The '''Wizard’s Federation''' was one of the first to observe the phenomenon known as '''[[History of the Delta Sector#Psionics|Psionics]]'''. As it is with power, many years passed and those in charge slowly became corrupt. Study became less for how to keep the universe safe, and more for increasing their own power. Arrogance became commonplace. Though some wizards chose to stay true to their ideals, the council who held leadership became blinded by their own power. This was, perhaps, the reason for the fall of the '''[[History of the Delta Sector#Origin of the Delta Sector|Nexus]]'''. While many wizards sought to defend it for their own power, a mix of in-fighting and just as many wizards seeing it’s loss as a rightful kick in the teeth to the archmages all but signed their loss in the war. The '''Wizards Federation''' was fully wiped out in 2410 by '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]'''. It is not documented why [[History of the Delta Sector#Nanotrasen|Nanotrasen]] actively warred against this faction however some say {REDACTED BY ORDER OF CC} is to blame.

{{Lore Menu}}

Delta V Lore

2026-09-09T16:04:45Z

DV vapetastic:

= Table of Contents =
All documents below were authored by: ''Vapetastic, Porto, ConfusedLemon, FangsakaCharlie, Grasstype, Bonktrauma, AeraAulin, Einkusprigestoast, Greenster, Bellwether, Exile, and Malfatto''

{{Lore Menu}}

History of the Delta Sector

2026-09-08T21:25:26Z

DV vapetastic:

== '''Origin of the Delta Sector''' ==
The '''Delta Sector''' was originally known as the Nexus. Named as such by the [[History of the Delta Sector#The Wizard’s Federation|'''Wizard’s Federation''']] who discovered the sector. They found that out of the known universe, the '''Delta Sector''' was where the veil between realspace and the '''[[History of the Delta Sector#The Noosphere|Noosphere]]''' was weakest. While they were able to keep it’s existence secret for 200 years, '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' eventually managed to discover it through {REDACTED BY ORDER OF CC} . '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''' had already been doing research into developing '''[[History of the Delta Sector#Psionics|psionics]]''' as a way to get an advantage in their war with the syndicate, but without knowledge of their origin or nature progress had been slow. In the Nexus, they saw opportunity. War broke out, and while the [[History of the Delta Sector#The Wizard’s Federation|Wizard's Federation]] fought fiercely, {REDACTED BY ORDER OF CC}. Research stations were built in their place and the Nexus was renamed to the '''Delta Sector'''.

== '''Psionics''' ==
'''Psionics''' are various powers and abilities who draw their origin from the '''[[History of the Delta Sector#Noosphere|Noosphere]]'''. Psychic powers, miracles and blessings of faith, and even spells such as those used by the wizards are all types of psionics manifested differently and developed through a different lens. There are other schools of '''Psionics''' to be found as well, such as Fire Manipulation; However, these are poorly understood and haven’t been officially classified as of yet.

One of the main things understood about '''psionics''' is that once someone has gained the ability to wield them, almost all powers depend upon the wielder’s strength of will. It is commonly believed that they manifest by the wielder forming a piece of the '''[[History of the Delta Sector#Noosphere|noosphere]]''' according to their desires and effectively “overwriting” reality with their will. However, a strong will is '''not''' an indicator of one’s capability to cast a psionic power. What determines who is and is not psionic is unfortunately still not understood, only that some species such as the [[Playable Species#Kitsune|Kitsune]] or the Ifrit are typically psionic or more likely to develop psionics.

== '''The Noosphere''' ==
The '''Noosphere''' has gone by many names and has been described as many things. A Collective Unconscious, a Psychic energy field, a separate plane of reality entirely, the coalesced dreams of mortals... The exact nature of the '''Noosphere''' is unknown, beyond the fact that it is a place that you can go into, and that it is the source of most supernatural phenomena. Multiple factions, most recently '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]''', have attempted to tap into its power to turn the tides of corporate war into their favor. However its influence was felt long before the corporations turned their attention towards it. It was only with '''[[History of the Delta Sector#Nanotrasen|Nanotrasen’s]]''' research into it that someone attempted to understand it scientifically.

== '''Nanotrasen''' ==
'''Nanotrasen''' is the dominant megacorporation of the universe. While ostensibly bowing to '''[[Terragov]]''', '''Nanotrasen''' separately controls multiple galaxies, holds a monopoly over Plasma research, Laser technology, [[History of the Delta Sector#Psionics|'''Psionic''' '''technology''']], and dozens if not hundreds of other industries through a combination of sheer resources, underhanded tactics, and in some cases outright corporate war. There are multiple different stories for '''Nanotrasen’s''' origin, however in the hundreds of years since it’s founding along with the immense, bloated, almost unknowable size the only confirmed details are that '''Nanotrasen''' started as a small company on earth, and was one of the main drivers of the space race that led to the colonization of the universe.

== '''The Wizard’s Federation''' ==
The '''Wizard’s Federation''' was one of the first to observe the phenomenon known as '''[[History of the Delta Sector#Psionics|Psionics]]'''. As it is with power, many years passed and those in charge slowly became corrupt. Study became less for how to keep the universe safe, and more for increasing their own power. Arrogance became commonplace. Though some wizards chose to stay true to their ideals, the council who held leadership became blinded by their own power. This was, perhaps, the reason for the fall of the '''[[History of the Delta Sector#Origin of the Delta Sector|Nexus]]'''. While many wizards sought to defend it for their own power, a mix of in-fighting and just as many wizards seeing it’s loss as a rightful kick in the teeth to the archmages all but signed their loss in the war. The '''Wizards Federation''' was fully wiped out in 2410 by '''[[History of the Delta Sector#Nanotrasen|Nanotrasen]]'''. It is not documented why [[History of the Delta Sector#Nanotrasen|Nanotrasen]] actively warred against this faction however some say {REDACTED BY ORDER OF CC} is to blame.

{{Lore Menu}}

United Nations of Earth

2026-09-08T21:19:52Z

DV vapetastic:

United Nations of Earth

2026-09-08T21:19:22Z

DV vapetastic:

== '''Unified Earth Administration (UEA)''' ==
In order to consolidate and organize the new age of space travel, the combined countries of '''Earth under the United Nations''' formed what is known as the '''Unified Earth Administration''' in 2100, a single entity tasked with the governance of both planet Earth and its off-world colonies such as the Lunar Refueling Depot and the Europa Scientific Research Colony. The '''UEA''' operates as an electoral democracy with representatives elected from each of the sovereign countries on Earth. While the countries continue to govern themselves individually, they all fall under the '''UEA’s''' policies and laws.

In 2156 after major infighting and a 10 year long legislative gridlock across the '''UEA''' Senate and Judiciary Council, the '''[[United Nations Armed Forces|UNAF]]''' commandeered control over Sol and it's colonies, leading to a major collapse of the '''UAE''' and it's leadership.

It is believed that major corporations such as '''Donk Co.''' and '''Cybersun''' and {REDACTED BY ORDER OF CC} assisted the [[United Nations Armed Forces|UNAF]] in establishing control after the '''UEA''' Senate attempted to pass a 60% Space Corporation tax across all colonies, <code>however many believe this is just a conspiracy.</code>

{{Lore Menu}}

Template:Lore Menu

2026-09-08T20:52:15Z

DV vapetastic: Lore expansions

{| class="wikitable mw-collapsible" width=100% style="font-size: 95%"
|-
! colspan=2 style="font-size: 95%; border: 2px solid #000000" | [[Delta V Lore]]
|-
| style="width:24%; text-align:right; background: #630813; border: 2px solid #000000" | '''Historical Documents'''
| style="border: 2px solid #000000" | [[History of the Delta Sector]] · [[United Nations of Earth]] · [[United Nations Armed Forces]]
|-
| style="text-align:right; background: #132c5e; border: 2px solid #000000" | '''Minor Nations'''
| style="border: 2px solid #000000" | [[The Free Sapient Charter]] · [[The Wesk'Rir Nation]] · [[Betelgeuse Consortium]] · [[Kosanikaan Confederation]]
|-
| style="text-align:right; background: #3258a6; border: 2px solid #000000" | '''Major Nations'''
| style="border: 2px solid #000000" | [[Terragov]] · [[Tengoku Commonwealth]] · [[Theocratic Monarchy of Verdanova]]
|-
| style="text-align:right; background: #014a41; border: 2px solid #000000" | '''Minor Corporations'''
| style="border: 2px solid #000000" | [[Gorlex]] · [[Donk Company]] · [[MI13]] · [[Tyger Dynamics]]
|-
| style="text-align:right; background: #018c7c; border: 2px solid #000000" | '''Major Corporations'''
| style="border: 2px solid #000000" | [[Nanotrasen]] · [[Interdyne]] · [[Cybersun]]
|-
| style="text-align:right; background: #360101; border: 2px solid #000000" | '''Clans and Cults'''
| style="border: 2px solid #000000" | [[Cosmic Cult]] · [[Clockwork Cult]] · [[Spider Clan]]
|}<noinclude>

== Usage ==
Navigational template for the [[Delta V Lore|Lore]] category. Includes an automatic categorization of the page into said category. To use it, write:

<pre>
{{Lore Menu}}
</pre>

[[Category:Templates]]
</noinclude>
<includeonly>[[Category:Lore]]</includeonly>

Event Policy

2026-09-07T17:46:10Z

DV vapetastic:

''This policy refers to Administrators and Curators, Unless otherwise specified.''

1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.

2. '''Never''' '''use a “smite” against a player character that is in round.''' This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. '''Events should be allowed to play out at their own pace.''' Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.


4. '''Events must meet or exceed our MRP Standard.''' Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.

5. '''Events must not feature staff-level ghost roles such as SRT unless directly authorized by a Head of Staff.''' These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.

6. '''Events should never portray ''NanoTrasen'' or ''Central Command'' as directly antagonistic to the crew.''' While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.

7. '''Events should not disrupt the balance of the round.''' Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.

8. '''Event roles should be reserved for players.''' Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''more than 5 minutes''', the eventing staff member may join the queue .

9. '''aGhosts are welcome to take any ghost roles.''' Refer to the previous rule regarding roles you have spawned.

10. '''Do not test unknown commands on the game servers.''' All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.

11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

12. '''Any spawned CC character going to the station, must be armed by security on station.''' If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.

= Event Categories =

* '''Low Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' or above without approval.
Low impact events either:
* Do not interact with players in a meaningful way
* Are a direct response to a player request or interaction, and do not affect the round to a greater degree
-> Such as responding to faxes or answering prayers

* '''Medium Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' with approval from a '''Curator'''. '''Game Administrators''' / '''Curators''' without approval. '''Senior Curators''' / '''Senior Administrators''' and above do not need approval.
Medium impact events either
* Considerable affect players or the round without derailing the round, round-removing
players, or taking significant resources and manpower from departments.
* Add a new gamerule unlikely to cause significant effect on players or the round
* Are a direct response to a player request or interaction that affects the round to a considerable degree.
-> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''High Impact''' - Following the mandatory notice and when approved by a '''Senior Curator''' or above.
High impact events either:
* Heavily affect players or the round, possibly derailing the round, round-removing
players, or taking significant resources and manpower from departments
* Add a new gamemode, causing significant effect on players or the round
* Are a direct response to a player request or interaction that results in a High Impact event.
-> Some Examples include setting the game mode or spawning multiple round ending antagonists

⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & *approved* in the event log prior to running these events, unless otherwise authorized by at least *2 Senior Curators, or 1 Head of Staff*. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

== Exceptions to event policy ==

1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.

1a. '''Staff are permitted to spawn in Central Command characters for the purposes of teaching or training new crew specifically on arrivals station (transit hub) .''' any character spawned, must be deleted when the "new player" leaves the arrivals station.

2. '''Staff are permitted to create ghost bars.''' Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC, all radio's must be removed.

3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. '''Staff are permitted to Spawn ERT following the chart listed below.''' Any exceptions require approval from a Senior Administrator/Senior Curator or above.

[[File:ERT chart.jpg|thumb]]

= Epsilon Procedure =

''In the event that Epsilon is or will be needed, Permission is required by a HEAD OF STAFF or SENIOR CURATOR. If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Event Policy

2026-09-07T17:44:42Z

DV vapetastic: /* Exceptions to event policy */

''This policy refers to Administrators and Curators, Unless otherwise specified.''

1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.

2. '''Never''' '''use a “smite” against a player character that is in round.''' This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. '''Events should be allowed to play out at their own pace.''' Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.


4. '''Events must meet or exceed our MRP Standard.''' Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.

5. '''Events must not feature staff-level ghost roles such as SRT unless directly authorized by a Head of Staff.''' These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.

6. '''Events should never portray ''NanoTrasen'' or ''Central Command'' as directly antagonistic to the crew.''' While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.

7. '''Events should not disrupt the balance of the round.''' Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.

8. '''Event roles should be reserved for players.''' Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''more than 5 minutes''', the eventing staff member may join the queue .

9. '''aGhosts are welcome to take any ghost roles.''' Refer to the previous rule regarding roles you have spawned.

10. '''Do not test unknown commands on the game servers.''' All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.

11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

12. '''Any spawned CC character going to the station, must be armed by security on station.''' If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.

= Event Categories =

* '''Low Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' or above without approval.
Low impact events either:
* Do not interact with players in a meaningful way
* Are a direct response to a player request or interaction, and do not affect the round to a greater degree
-> Such as responding to faxes or answering prayers

* '''Medium Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' with approval from a '''Curator'''. '''Game Administrators''' / '''Curators''' without approval. '''Senior Curators''' / '''Senior Administrators''' and above do not need approval.
Medium impact events either
* Considerable affect players or the round without derailing the round, round-removing
players, or taking significant resources and manpower from departments.
* Add a new gamerule unlikely to cause significant effect on players or the round
* Are a direct response to a player request or interaction that affects the round to a considerable degree.
-> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''High Impact''' - Following the mandatory notice and when approved by a '''Senior Curator''' or above.
High impact events either:
* Heavily affect players or the round, possibly derailing the round, round-removing
players, or taking significant resources and manpower from departments
* Add a new gamemode, causing significant effect on players or the round
* Are a direct response to a player request or interaction that results in a High Impact event.
-> Some Examples include setting the game mode or spawning multiple round ending antagonists

⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & *approved* in the event log prior to running these events, unless otherwise authorized by at least *2 Senior Curators, or 1 Head of Staff*. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

== Exceptions to event policy ==

1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.

1a. '''Staff are permitted to spawn in Central Command characters for the purposes of teaching or training new crew specifically on arrivals station (transit hub) .''' any character spawned, must be deleted when the "new player" leaves the arrivals station.

2. '''Staff are permitted to create ghost bars.''' Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC

3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. '''Staff are permitted to Spawn ERT following the chart listed below.''' Any exceptions require approval from a Senior Administrator/Senior Curator or above.

[[File:ERT chart.jpg|thumb]]

= Epsilon Procedure =

''In the event that Epsilon is or will be needed, Permission is required by a HEAD OF STAFF or SENIOR CURATOR. If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Event Policy

2026-09-07T17:37:45Z

DV vapetastic: Deathsquad change

''This policy refers to Administrators and Curators, Unless otherwise specified.''

1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.

2. '''Never''' '''use a “smite” against a player character that is in round.''' This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. '''Events should be allowed to play out at their own pace.''' Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.


4. '''Events must meet or exceed our MRP Standard.''' Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.

5. '''Events must not feature staff-level ghost roles such as SRT unless directly authorized by a Head of Staff.''' These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.

6. '''Events should never portray ''NanoTrasen'' or ''Central Command'' as directly antagonistic to the crew.''' While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.

7. '''Events should not disrupt the balance of the round.''' Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.

8. '''Event roles should be reserved for players.''' Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''more than 5 minutes''', the eventing staff member may join the queue .

9. '''aGhosts are welcome to take any ghost roles.''' Refer to the previous rule regarding roles you have spawned.

10. '''Do not test unknown commands on the game servers.''' All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.

11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

12. '''Any spawned CC character going to the station, must be armed by security on station.''' If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.

= Event Categories =

* '''Low Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' or above without approval.
Low impact events either:
* Do not interact with players in a meaningful way
* Are a direct response to a player request or interaction, and do not affect the round to a greater degree
-> Such as responding to faxes or answering prayers

* '''Medium Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' with approval from a '''Curator'''. '''Game Administrators''' / '''Curators''' without approval. '''Senior Curators''' / '''Senior Administrators''' and above do not need approval.
Medium impact events either
* Considerable affect players or the round without derailing the round, round-removing
players, or taking significant resources and manpower from departments.
* Add a new gamerule unlikely to cause significant effect on players or the round
* Are a direct response to a player request or interaction that affects the round to a considerable degree.
-> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''High Impact''' - Following the mandatory notice and when approved by a '''Senior Curator''' or above.
High impact events either:
* Heavily affect players or the round, possibly derailing the round, round-removing
players, or taking significant resources and manpower from departments
* Add a new gamemode, causing significant effect on players or the round
* Are a direct response to a player request or interaction that results in a High Impact event.
-> Some Examples include setting the game mode or spawning multiple round ending antagonists

⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & *approved* in the event log prior to running these events, unless otherwise authorized by at least *2 Senior Curators, or 1 Head of Staff*. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

== Exceptions to event policy ==

1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.

2. '''Staff are permitted to create ghost bars.''' Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC

3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. '''Staff are permitted to Spawn ERT following the chart listed below.''' Any exceptions require approval from a Senior Administrator/Senior Curator or above.

[[File:ERT chart.jpg|thumb]]

= Epsilon Procedure =

''In the event that Epsilon is or will be needed, Permission is required by a HEAD OF STAFF or SENIOR CURATOR. If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Reviewing Content With Ethos

2026-08-21T23:16:53Z

DV vapetastic: /* Checks and Balances */

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator and/or content of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to review in High Command that is viewable by staff.''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead. If a reversal / decision is made by High Command that goes ''against'' CR's decision, there should be a detailed explanation as to why, as well as addressing any major concerns that were brought up during the CR process by reviewers.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)

Reviewing Content With Ethos

2026-08-21T23:15:22Z

DV vapetastic: /* Checks and Balances */

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator and/or content of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to publicly review in High Command.''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead. If a reversal / decision is made by High Command that goes ''against'' CR's decision, there should be a detailed explanation as to why, as well as addressing any major concerns that were brought up during the CR process by reviewers.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)