Developer Guidelines - Revision history

Datamatt: add the Head Spriter as an official role

2025-08-24T19:02:26Z

add the Head Spriter as an official role

← Older revision		Revision as of 19:02, 24 August 2025
Line 6:		Line 6:
	* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.		* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.
	* When the Maintainer Discussion label is applied, the maintainer or developer will post their reason for doing so on the PR. They will then immediately bring the PR to the maintainers' attention, who will try to discuss it within two weeks. If this time period has passed without you being notified of an outcome, feel free to remind the Maintainers about your PR.		* When the Maintainer Discussion label is applied, the maintainer or developer will post their reason for doing so on the PR. They will then immediately bring the PR to the maintainers' attention, who will try to discuss it within two weeks. If this time period has passed without you being notified of an outcome, feel free to remind the Maintainers about your PR.
			==Head Spriter==
			* The Head Spriter is responsible for writing up and enforcing '''spriting and art direction for the server''' as a whole with the Head Developers and Maintainers.
			* The Head Spriter is responsible for enforcing said spriting and art direction if necessary, whether that be through required changes on GitHub or otherwise.
			* The Head Spriter is responsible for coordinating spriting and art efforts on development projects.
	[[Category:Staff Guidelines]]		[[Category:Staff Guidelines]]

MattAtlas: edit the maintainer discussion rule

2024-12-11T09:31:39Z

edit the maintainer discussion rule

← Older revision		Revision as of 09:31, 11 December 2024
Line 5:		Line 5:
	* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.		* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.
	* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.		* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.
	* When the Maintainer Discussion label is applied, the maintainer or developer will post their reason for doing so on the PR. They will then immediately bring the PR to the maintainers' attention, who will discuss it within two weeks.		* When the Maintainer Discussion label is applied, the maintainer or developer will post their reason for doing so on the PR. They will then immediately bring the PR to the maintainers' attention, who will try to discuss it within two weeks. If this time period has passed without you being notified of an outcome, feel free to remind the Maintainers about your PR.
	[[Category:Staff Guidelines]]		[[Category:Staff Guidelines]]

MattAtlas: maintainer discussion tag guideline

2024-06-24T10:11:02Z

maintainer discussion tag guideline

← Older revision		Revision as of 10:11, 24 June 2024
Line 5:		Line 5:
	* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.		* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.
	* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.		* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.
			* When the Maintainer Discussion label is applied, the maintainer or developer will post their reason for doing so on the PR. They will then immediately bring the PR to the maintainers' attention, who will discuss it within two weeks.
	[[Category:Staff Guidelines]]		[[Category:Staff Guidelines]]

La Villa Strangiato: category

2024-01-01T19:48:41Z

MattAtlas at 13:36, 1 January 2024

2024-01-01T13:36:05Z

← Older revision		Revision as of 13:36, 1 January 2024
Line 2:		Line 2:
	* Developers are expected to regularly review pull requests. Our Github does not function without regular reviews. You are also expected to be somewhat thorough with reviewing pull requests - errors are fine, but you should still put effort into it.		* Developers are expected to regularly review pull requests. Our Github does not function without regular reviews. You are also expected to be somewhat thorough with reviewing pull requests - errors are fine, but you should still put effort into it.
	* You are not expected to review pull requests the contents of which you do not understand or cannot review. A spriter who can only sprite, for instance, is not expected to review a complex backend pull request.		* You are not expected to review pull requests the contents of which you do not understand or cannot review. A spriter who can only sprite, for instance, is not expected to review a complex backend pull request.
	Developers are expected to be active if submitting regular balance-related pull requests. Doing only back-end work does not require a high activity level, but repeatedly submitting balance pull requests while not being up-to-date with the game and its culture will lead to a review of your position.		* Developers are expected to be active if submitting regular balance-related pull requests. Doing only back-end work does not require a high activity level, but repeatedly submitting balance pull requests while not being up-to-date with the game and its culture will lead to a review of your position.
	* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.		* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.
	* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.		* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.

MattAtlas at 13:35, 1 January 2024

2024-01-01T13:35:59Z

← Older revision		Revision as of 13:35, 1 January 2024
Line 1:		Line 1:
	* Developers should not use their powers in-game outside of testing areas like the Thunderdome unless specifically required or asked to. You should always defer to a maintainer or administrator if one is present.		* Developers should not use their powers in-game outside of testing areas like the Thunderdome unless specifically required or asked to. You should always defer to a maintainer or administrator if one is present. If no maintainers or administrators are present and there is a game-breaking bug or a similar problem, you are allowed to fix it, though you should still be careful. Your actions will be your own responsibility.
	~~* *~~ If no maintainers or administrators are present and there is a game-breaking bug or a similar problem, you are allowed to fix it, though you should still be careful. Your actions will be your own responsibility.
	* Developers are expected to regularly review pull requests. Our Github does not function without regular reviews. You are also expected to be somewhat thorough with reviewing pull requests - errors are fine, but you should still put effort into it.		* Developers are expected to regularly review pull requests. Our Github does not function without regular reviews. You are also expected to be somewhat thorough with reviewing pull requests - errors are fine, but you should still put effort into it.
	* You are not expected to review pull requests the contents of which you do not understand or cannot review. A spriter who can only sprite, for instance, is not expected to review a complex backend pull request.		* You are not expected to review pull requests the contents of which you do not understand or cannot review. A spriter who can only sprite, for instance, is not expected to review a complex backend pull request.

MattAtlas: initial rules

2024-01-01T13:35:46Z

initial rules

New page

* Developers should not use their powers in-game outside of testing areas like the Thunderdome unless specifically required or asked to. You should always defer to a maintainer or administrator if one is present.
* * If no maintainers or administrators are present and there is a game-breaking bug or a similar problem, you are allowed to fix it, though you should still be careful. Your actions will be your own responsibility.
* Developers are expected to regularly review pull requests. Our Github does not function without regular reviews. You are also expected to be somewhat thorough with reviewing pull requests - errors are fine, but you should still put effort into it.
* You are not expected to review pull requests the contents of which you do not understand or cannot review. A spriter who can only sprite, for instance, is not expected to review a complex backend pull request.
Developers are expected to be active if submitting regular balance-related pull requests. Doing only back-end work does not require a high activity level, but repeatedly submitting balance pull requests while not being up-to-date with the game and its culture will lead to a review of your position.
* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.
* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.

← Older revision		Revision as of 19:48, 1 January 2024
Line 5:		Line 5:
	* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.		* The Feedback Required tag may be applied by any developer at their discretion, but it should not be used for trivial changes. It should be used when a pull request is controversial enough to justify a forum thread.
	* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.		* The Maintainer Discussion tag may be applied by any developer at their discretion, but it should only be used for changes that would have a large effect on the server, its gameplay or its setting.
			[[Category:Staff Guidelines]]