Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Content Removal: Difference between revisions

From Delta-V Wiki
Vape (talk | contribs)
No edit summary
Vape (talk | contribs)
Requested Changes to policy
Line 10: Line 10:
* Make a list of issues with the content
* Make a list of issues with the content


*Create a Design Document that addresses these issues. <small>If Content Review cannot do this, it should be stated on the issue page in github.</small>  
*Announce the planned removal of the content, including a date, and its issues - <small>For classifications of "Major Content" only, see below</small>


*Present the issues and design solutions to the community via the Design Document
*Create a community feedback post regarding the removal, the issues, and a specific date of removal.


* Establish a deadline for action (Removal or Replacement)
* Establish a deadline for action (Removal or Replacement)
Line 19: Line 19:




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


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


* 4 weeks - Major content (Gamemodes, Roles, Etc)
Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process.


Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process. 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).''
If Community feedback for removal is overwhelmingly negative, Content Review is required to seek approval of both the Content Director and the Project Management Team before finalizing removal.


The Content Director and Maintainers will have final say, 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.''
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).'' The Content Director 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.''

Revision as of 12:15, 8 May 2026

Content Removal Policy

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, see below
  • 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 Content Director 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). The Content Director 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.