From 794d113ce958e0703238c609e8711e3e3e07ec4c Mon Sep 17 00:00:00 2001 From: rubenwardy Date: Sat, 23 Apr 2022 14:39:07 +0100 Subject: [PATCH] Fix list formatting in policy and guidance --- app/flatpages/policy_and_guidance.md | 33 +++++++++++++++++----------- 1 file changed, 20 insertions(+), 13 deletions(-) diff --git a/app/flatpages/policy_and_guidance.md b/app/flatpages/policy_and_guidance.md index 98627e6a..4fab1263 100644 --- a/app/flatpages/policy_and_guidance.md +++ b/app/flatpages/policy_and_guidance.md @@ -48,7 +48,7 @@ but still has value. Note that this doesn't mean that you should add a thing you started working on yesterday, it's worth adding all the basic stuff to make your package useful. -You should make sure to mark Work in Progress stuff as such in the "maintenance status" column, +You should make sure to mark Work in Progress stuff as such in the "maintenance status" column, as this will help advise players. Adding non-player facing mods, such as libraries and server tools, is perfectly fine @@ -155,21 +155,28 @@ Doing so may result in temporary or permanent suspension from ContentDB. ## 7. Screenshots -1. Screenshots must not violate copyright. You should have the rights to the screenshot. -2. Screenshots should not be misleading, e.g. do not use idealized mockups or blender concept renders if they do not accurately reflect in-game appearance. -3. Screenshots should depict the actual content of the package in some way, i.e. no "off-topic" images. -4. Content that is prominently displayed or "focal" should be either present in, or interact with, the package in some way. - These can include things in other packages if they have a dependency relationship (either way), or if the submitted - package in some way enhances, extends, or alters that content. +1. Screenshots must not violate copyright. You should have the rights to the screenshot. + +2. Screenshots should not be misleading, e.g. do not use idealized mockups or blender concept renders if they do not accurately reflect in-game appearance. + +3. Screenshots should depict the actual content of the package in some way, i.e. no "off-topic" images. + +4. Content that is prominently displayed or "focal" should be either present in, or interact with, the package in some way. + These can include things in other packages if they have a dependency relationship (either way), or if the submitted + package in some way enhances, extends, or alters that content. + + Unrelated package content can be allowed to show what the package content will look like in a typical/realistic game scene, + but should be "in the background" only as far as possible. - Unrelated package content can be allowed to show what the package content will look like in a typical/realistic game scene, - but should be "in the background" only as far as possible. 5. Screenshots must only contain content appropriate for the Content Warnings of the package. -6. Images should be MOSTLY in-game screenshots. Some alterations are okay, such as collages, added text, - some reasonable compositing. Logo/brochure images are allowed but should NOT be the cover image. - Don't just use one of the textures from the package; show it in-situ as it actually looks in the game. -9. Packages should have a screenshot when reasonably applicable. +6. Images should be MOSTLY in-game screenshots. Some alterations are okay, such as collages, added text, + some reasonable compositing. Logo/brochure images are allowed but should NOT be the cover image. + + Don't just use one of the textures from the package; show it in-situ as it actually looks in the game. + +9. Packages should have a screenshot when reasonably applicable. + 10. Screenshots should be of reasonable dimensions. We recommend using 1920x1080.