From 00efe8af054f90aa94e4c8e880d7dc8807752e10 Mon Sep 17 00:00:00 2001 From: Southpaw Date: Sat, 31 Aug 2024 20:40:50 +0100 Subject: [PATCH 01/12] Remove RSS feed (so last decade) --- src/pages/feed.xml.js | 25 ------------------------- 1 file changed, 25 deletions(-) delete mode 100644 src/pages/feed.xml.js diff --git a/src/pages/feed.xml.js b/src/pages/feed.xml.js deleted file mode 100644 index 7bab519c..00000000 --- a/src/pages/feed.xml.js +++ /dev/null @@ -1,25 +0,0 @@ -import rss from "@astrojs/rss"; - -const postImportResult = import.meta.glob("./en/blog/**/*.md", { eager: true }); -const posts = Object.values(postImportResult); - -// TODO(apple): Multiple feeds, one per language (RSS doesn't support multi-language feeds). -// That would be too easy. -export const GET = () => - rss({ - // `` field in output xml - title: "The Quilt Project", - // `<description>` field in output xml - description: "The mod-loader that cares.", - // base URL for RSS <item> links - site: import.meta.env.SITE, - // list of `<item>`s in output xml - items: posts.map((post) => ({ - link: post.url, - title: post.frontmatter.title, - pubDate: post.frontmatter.date, - description: post.compiledContent(), - })), - // (optional) inject custom xml - customData: `<language>en-us</language>`, - }); From 8d70366af37010e392c6d95bbf5fb805828cc94e Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sat, 31 Aug 2024 20:50:59 +0100 Subject: [PATCH 02/12] Remove API GUI (APIs are for computers, geez) --- src/pages/api.astro | 37 ------------------------------------- 1 file changed, 37 deletions(-) delete mode 100644 src/pages/api.astro diff --git a/src/pages/api.astro b/src/pages/api.astro deleted file mode 100644 index a918cd4b..00000000 --- a/src/pages/api.astro +++ /dev/null @@ -1,37 +0,0 @@ ---- -import Base from "@layouts/Base.astro"; -import swaggerCss from "swagger-ui/dist/swagger-ui.css?raw"; -import swaggerDarkCss from "../styles/swagger-dark.css?raw"; ---- - -<script> - const swaggerUiNode = document.getElementById('swagger-ui'); - if (swaggerUiNode) { - import('swagger-ui').then(({ default: renderSwagger }) => { - window.ui = renderSwagger({ - url: '/api/openapi.yaml', - domNode: swaggerUiNode, - deepLinking: true, - }); - }); - } -</script> -<style is:inline> - pre.version { - background-color: inherit !important; - } -</style> -<style is:inline set:html={swaggerCss}></style> -<style is:inline set:html={swaggerDarkCss}></style> - -<Base content={{title: "Quilt API Index", description: "Index for the Quilt Website API"}}> - <div id="swagger-ui"></div> - - <noscript> - <article class="message is-danger"> - <div class="message-body"> - <p>Javascript is required to view this page</p> - </div> - </article> - </noscript> -</Base> From 6970cf628f7b09ea8d329b47a849a334287441bc Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sat, 31 Aug 2024 21:00:59 +0100 Subject: [PATCH 03/12] Remove home page (it's just a lame redirect) --- src/pages/index.astro | 5 ----- 1 file changed, 5 deletions(-) delete mode 100644 src/pages/index.astro diff --git a/src/pages/index.astro b/src/pages/index.astro deleted file mode 100644 index f7bbc443..00000000 --- a/src/pages/index.astro +++ /dev/null @@ -1,5 +0,0 @@ ---- -import Redirect from "@layouts/Redirect.astro"; ---- - -<Redirect href="/en" /> From c59184fc695de34212e73854ba80e776fbf4104d Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sat, 31 Aug 2024 22:39:08 +0100 Subject: [PATCH 04/12] Remove template mod generator (the youth are too reliant on technology) --- src/pages/en/usage/generator.mdx | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 src/pages/en/usage/generator.mdx diff --git a/src/pages/en/usage/generator.mdx b/src/pages/en/usage/generator.mdx deleted file mode 100644 index 0d1c9de4..00000000 --- a/src/pages/en/usage/generator.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -permalink: /usage/generator -title: Mod Generator -description: Generate a ready to use mod template -layout: /src/layouts/Generator.astro ---- \ No newline at end of file From dac83ea3cc3cf555b53dbd168b7549457816d5d9 Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sat, 31 Aug 2024 22:54:27 +0100 Subject: [PATCH 05/12] Delete ARCHITECTURE.md (we're programmers, not architects) --- ARCHITECTURE.md | 73 ------------------------------------------------- 1 file changed, 73 deletions(-) delete mode 100644 ARCHITECTURE.md diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md deleted file mode 100644 index 36da3ead..00000000 --- a/ARCHITECTURE.md +++ /dev/null @@ -1,73 +0,0 @@ -# Architecture of This Site - -Contributors should also familiarize themselves with the architecture of this repository, which is best done by taking a look at the folder structure: - -``` -src/ - components/ - atoms/ - parts/ - setpieces/ - data/ - team/ - layouts/ - locales/ - en/ - zh/ - ... - pages/ - util/ -public/ - assets/ - favicon/ -``` - -## Source (`src/`) - -This folder contains all of the code and content of the site. -As a rule of thumb, you should put all non-assets here. - -### Components (`src/components/`) - -The components folder contains components, which are divided into three kinds—atoms, parts and setpieces. - -Atoms (available under `@atoms`) are simple, reusable components that follow the Unix philosophy—do one thing, and do one thing well. -They are practically found everywhere, often used as a building block of pages, parts, setpieces, and so on. Examples of atoms include buttons and messages. - -Parts (`@parts`) are more complex components than atoms, and are often specialized for one purpose or for a single page—for example, the grid of launchers in the install page is a single part, which consists of several `InstallerButton`s, which are atoms. - -Setpieces (`@setpieces`) are very complex structures that typically provide a large chunk of functionality of a page, such as the navbar, the footer and the sidebar. -These gigantic components are intended to be used alone in pages, and not in other components. - -### Data (`src/data/`, `@data`) - -The data folder contains some TypeScript files for storing some common variables used throughout the site, such as links, account names, localization settings, etc. - -### Layouts (`src/layouts/`, `@layouts`) - -This folder contains every layout of the site, used by all pages of the site. Nothing much to say about that. - -### Locales (`src/locales/`) - -This folder contains the translated strings used in the site. Under this folder, each locale gets its own folder—`en/` for English, `zh/` for Chinese, etc. -Under that, you will see a bunch of `.flt` files—they are [Fluent](https://projectfluent.org) files, parsed and substituted into the site. - -It is worth noting that most of the site's text doesn't get translated this way—as you will see, we only use Fluent for short and common strings. -Long paragraphs of text remain in Astro and Markdown files, which need to be translated as Astro and Markdown files. - -### Pages (`src/pages/`) - -Pretty self-explanatory—the main content of this site. Edit this section if you're looking to add content, to fix a typo, etc. - -### Utilities (`src/util`, `@util`) - -This folder contains a bunch of TypeScript files containing common functions for doing tasks like localizing paths, getting the edit date of a page, fetching launcher updates, etc. - -## Public (`public/`) - -This folder stores assets that can be included in the built site *verbatim*—these files are not processed at all while building—good for images, processed stylesheets, favicons, and more! - -Minutiae: -- Note that in the built site, the assets stored here are directly placed under the root path: for example, a file at `public/image.png` should be accessed with the path `/image.png`. -- Files under `public/assets/css/` are currently precompiled from SCSS files from the `quilt-bulma` package. This may change in the future! -- We currently bundle a CSS/WebFonts copy of Font Awesome 6 Free under `public/assets/fontawesome/` as a fallback option for users who have disabled JavaScript. This again, may change in the future. From 6f9e8b806981c95c55ec069ef55142b38d859414 Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sat, 31 Aug 2024 23:09:45 +0100 Subject: [PATCH 06/12] Remove code of conduct (I don't have a good reason for this one) --- src/pages/en/community/code-of-conduct.mdx | 81 ---------------------- 1 file changed, 81 deletions(-) delete mode 100644 src/pages/en/community/code-of-conduct.mdx diff --git a/src/pages/en/community/code-of-conduct.mdx b/src/pages/en/community/code-of-conduct.mdx deleted file mode 100644 index 6e8c8192..00000000 --- a/src/pages/en/community/code-of-conduct.mdx +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Code of Conduct -description: Learn about Quilt's community spaces, and what we expect of our users. -layout: /src/layouts/Page.astro ---- - -Like many communities, our policies are based on a Code of Conduct. Please make sure you read it before making use of -our spaces, as it provides a set of behavioral guidelines that we expect everyone to adhere to. - -## Notes - -This Code of Conduct applies to anyone that makes use of a space managed by the Quilt team. **Not having read the Code of Conduct is not a valid excuse for breaking it,** and all members of the community will be held to this standard. - -While we try to go into detail with our examples, it's impossible to cover every possible situation in one document. In general, treat others how you wish to be treated -- if you wouldn't like to be treated in a particular way, don't treat others like that either! - -This Code of Conduct is the basis for [our rules](/en/community). We require that all community members read both this document, and the rules document. - -<hr /> - -## Our Pledge - -We as community members, contributors, and team members pledge to make participation in our community a harassment-free experience for everyone, regardless of age, culture, ethnicity, gender identity & expression, nationality, physical or mental disabilities or differences (regardless of intensity), politics, race, religion, sex, sexual orientation, socio-economic status or subcultural affiliation. - -We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community, and we are committed to promoting these concepts. - -## Our Standards - -We expect the members of our community to participate in a positive, authentic and deliberate way. Consideration, respect and empathy are key when it comes to building and supporting a healthy community, and we request that our members exercise this through their actions. - -Please take into account that online communities bring people together from many different cultures and backgrounds. It's important to understand that sometimes the combination of cultural differences and online interaction can lead to misunderstandings. - -Examples of behavior that contributes to a positive environment for our community include: - -- Demonstrating empathy, patience and kindness toward other people -- Being respectful of differing opinions, viewpoints, and experiences -- Giving and gracefully accepting constructive feedback -- Respecting others' personal choices, even when they don't line up with yours -- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience -- Focusing on what is best not just for us as individuals, but for the overall community - -Examples of unacceptable behavior include: - -- The use of sexualized language or imagery, and sexual attention or advances of any kind -- Trolling, insulting or derogatory comments -- Personal or political attacks -- Threats of violence, or violent acts towards others -- Public or private harassment -- Intentionally dead-naming or misgendering others -- Publishing others' private information, such as a physical or email address, without their explicit permission ("doxxing") -- Gatekeeping others' access to mental health or accessibility tools -- Advocating for, or encouraging, any unacceptable forms of behavior -- Other conduct which could reasonably be considered inappropriate - -## Enforcement Responsibilities - -Community team members are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. - -If a community member engages in behavior violating this Code of Conduct, the members of the community team may take any action they deem appropriate. Actions may range from a simple warning to the most drastic: permanent removal from the community, exclusion from any interaction, and loss of all rights in the community. - -## Scope - -This Code of Conduct applies within all community spaces (both online and offline), as well as when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. - -This Code of Conduct applies to all projects, repositories and community spaces that are managed by Quilt, regardless of whether or not the use of this code is explicitly called out. We also reserve the right to retroactively enforce this Code of Conduct when community members violate it in spaces not managed by Quilt. - -## Reporting a Problem - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the Quilt community team directly on Discord, either via private message or the ModMail bot. If your report concerns a specific community team member or group of community team members, please send your report to a team member that is not part of the report, or a member of the administrative board. - -All complaints will be reviewed and investigated promptly and fairly, and all team members are obligated to respect the privacy and security of the reporter of any incident. - -## Changes & Feedback - -It is likely that this Code of Conduct will need additions, modifications and other improvements. Online culture changes, new views and sensitivities emerge which need to be taken into account. To that end, we reserve the right to update this Code of Conduct at any time, pending feedback from the community when possible. - -We always welcome feedback and suggestions. If you'd like to provide either, feel free to [open an issue on GitHub](https://github.com/QuiltMC/quiltmc.org/issues)! - -## Attribution - -This Code of Conduct is a heavily modified version of the [Contributor Covenant version 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), with inspiration and examples taken from the [JetBrains Open Source and Community Code of Conduct](https://confluence.jetbrains.com/display/ALL/JetBrains+Open+Source+and+Community+Code+of+Conduct), [Microsoft Open Source Code of Conduct](https://microsoft.github.io/codeofconduct) and -[Open Source Design Code of Conduct](https://opensourcedesign.net/code-of-conduct). From c56a6f06ded520e29e474752493b40ed3356f72c Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 09:43:05 +0100 Subject: [PATCH 07/12] Remove instructions to install the vanilla launcher (we are modders here) --- src/pages/en/install/client.mdx | 79 --------------------------------- 1 file changed, 79 deletions(-) delete mode 100644 src/pages/en/install/client.mdx diff --git a/src/pages/en/install/client.mdx b/src/pages/en/install/client.mdx deleted file mode 100644 index 5a652298..00000000 --- a/src/pages/en/install/client.mdx +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: "Install: Client" -permalink: /install/client - -layout: /src/layouts/InstallPage.astro -platformKey: platform-client -website: "https://www.minecraft.net/en-us/download" - -hasDownloads: true ---- - -import InstallerVersion from "@parts/install/InstallerVersion.astro"; -import MavenInstallerButton from "@atoms/MavenInstallerButton.astro"; -import { Icon } from "astro-icon/components" - -Before getting started, you'll need to make sure you download a copy of the Quilt installer. - -The **Universal** download will work on any computer with Java 17 or later properly installed -- but if you're on Windows, and you'd rather just use the Java installation that comes with Minecraft, then you can use the **Windows** download. - -If you're not sure which to pick, use the **Universal** download. If you need to update your Java version, we recommend downloading it from [Eclipse Adoptium](https://adoptium.net/temurin/releases/?version=17). - -<div class="field is-horizontal"> - <InstallerVersion /> - - <div class="field-body"> - <div class="field"> - <div class="control buttons"> - <MavenInstallerButton arch="java-universal" title="Universal (.jar)" icon="cib:java" class_="button is-primary" /> - <MavenInstallerButton arch="windows-x86_64" title="Windows (.exe)" icon="cib:windows" class_="button" /> - - <div class="dropdown is-right is-hoverable"> - <div class="dropdown-trigger"> - <button class="button" aria-haspopup="true" aria-controls="dropdown-menu"> - <span class="icon is-small"> - <Icon name="mdi:dots-vertical"/> - </span> - - <span>More</span> - </button> - </div> - - <div class="dropdown-menu" id="dropdown-menu" role="menu"> - <div class="dropdown-content"> - <MavenInstallerButton arch="windows-aarch64" title="Windows (.exe, ARM64)" icon="cib:windows" class_="dropdown-item" /> - <MavenInstallerButton arch="windows-i686" title="Windows (.exe, 32-bit)" icon="cib:windows" class_="dropdown-item" /> - </div> - </div> - </div> - </div> - </div> - </div> -</div> - -Once you have a copy of the Quilt installer downloaded, follow these steps: - -1. If you haven't already, download a copy of the Minecraft launcher [from the Minecraft website](https://www.minecraft.net/en-us/download), and install it -2. If you have the Minecraft launcher open, close it before continuing -3. Find the Quilt installer you downloaded and run it -4. Ensure that you have the **Client** tab selected -5. Select the versions of Minecraft and Quilt Loader you wish to install -6. Click the **Install** button - -Assuming you left the **Generate profile** box checked, you'll notice that a new Quilt installation will have been created for you. Otherwise, you can click on the **Installations** tab at the top and create a new one, picking the new Quilt entry from the **Version** dropdown. - -That's all there is to it - install some mods, launch your new installation, and have fun playing! - -# Installing Mods - -Installing mods is a fairly simple process: - -1. Download the mods you'd like to install -2. Open the Minecraft Launcher and click on the **Installations** tab -3. Hover your mouse cursor over the Quilt installation you'd like to add mods to -4. Click on the button that looks like a folder icon -5. In the folder that opens, create a folder named `mods` if one doesn't already exist -6. Copy your mod files into the `mods/` folder -7. Ensure you have also added the **Quilted Fabric API/Quilt Standard Libraries** bundle, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) or [on Modrinth](https://modrinth.com/mod/qsl) - -Launch your installation, and the mods should be available immediately. If you run into any issues, please take a look at the [troubleshooting page](/en/usage/troubleshooting), or [join us on Discord](https://discord.quiltmc.org) to ask for support! From 76b832e92756f7a30f76c8458ee652c14c98da31 Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 16:54:55 +0100 Subject: [PATCH 08/12] Remove known incompatibilities page (will be replaced by unknown incompatibilities) --- src/pages/en/usage/known-incompatibilities.mdx | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 src/pages/en/usage/known-incompatibilities.mdx diff --git a/src/pages/en/usage/known-incompatibilities.mdx b/src/pages/en/usage/known-incompatibilities.mdx deleted file mode 100644 index 94d9d861..00000000 --- a/src/pages/en/usage/known-incompatibilities.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -permalink: /usage/ -title: Known Incompatibilities -description: See all the known incompatibilities with Quilt in this page. -layout: /src/layouts/KnownIncompatibilities.astro ---- From e183d3fb8eb235dba2574938c4d435dca653562b Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 19:12:14 +0100 Subject: [PATCH 09/12] Remove rules (we have transcended them) --- src/pages/en/community/rules.mdx | 131 ------------------------------- 1 file changed, 131 deletions(-) delete mode 100644 src/pages/en/community/rules.mdx diff --git a/src/pages/en/community/rules.mdx b/src/pages/en/community/rules.mdx deleted file mode 100644 index 8b6ffe14..00000000 --- a/src/pages/en/community/rules.mdx +++ /dev/null @@ -1,131 +0,0 @@ ---- -title: Rules -description: Quilt's core rules, which build upon the Code of Conduct to provide a set of concrete guidelines for behaviour. -layout: /src/layouts/Page.astro ---- - -We expect everyone that makes use of any Quilt community spaces to adhere to the following rules. If you have any questions or suggestions, please feel free to contact a member of the community team or ask your question in the `#discord-meta` channel. - -**Remember:** Ignorance of our rules is not an excuse for breaking them. You are responsible for educating yourself on how every community you join expects you to behave, and "I didn't know that was in the rules" will never be a valid excuse. - -#### 1) Follow our Code of Conduct and NSFW content policy - -Make sure you read and follow [our Code of Conduct](/en/community/code-of-conduct), which outlines what we expect from you and is the basis for these rules. It's important that you read and understand the Code of Conduct, and the rules on this page -- feel free to contact a community team member if you need any clarification. - -Additionally, be sure to read and follow [our NSFW and Sexual Content policy](/en/community/nsfw-policy), which explains what types of content, media and related behaviour we do and don't allow. - -That said, remember that there will sometimes be situations that are difficult to fit into the Code of Conduct at a glance. In these cases, please contact a member of the community team for clarification. - -#### 2) Follow Discord's Rules - -In all community spaces, everyone must also follow the Discord [Community Guidelines](https://discord.com/guidelines) and [Terms of Service](https://discord.com/terms). - -These aren't just good to follow as a general rule of thumb -- this is also a requirement when operating a large community on Discord, especially if that community is aiming to be partnered or verified. - -#### 3) Try to speak English - -The world is a big place, and many people will have a different native language. The common language in our community is English, but we understand that not everyone speaks English at the same level. - -If you're not a native English speaker, please try to speak English to the best of your ability. Don't worry if you need to use a translation tool, or if your English isn't great -- we won't make fun of you, and we'll help you figure out the right words if you get stuck. - -#### 4) Listen to & respect all community team members - -The community team is here to support the community, keep it running smoothly, and ensure that it remains safe and friendly. In order to allow us to do our jobs, we need you to cooperate with us. - -Essentially, please take requests from community team members seriously and listen when a team member asks you to do something. If you have a problem with what a team member is asking you to do, we advise that you step away from the situation and send a private message to another team member. - -#### 5) Keep all projects legal, legitimate & appropriate - -While anyone may make use of the Quilt toolchain in accordance with the licenses applied to each project, all projects developed or promoted **in all Quilt community spaces** must meet the following criteria: - -- Projects must not be malicious -- which includes (but is not limited to) malware, mods that include backdoors, mods that modify Quilt in an attempt to hide themselves from servers they connect to, or mods that harass specific people or groups of people (for example, by automatically kicking them from servers with the mod installed) -- Projects must not be sexualized, hateful or otherwise inappropriate in nature, and this also applies to all code and project assets posted for any purpose -- Projects must not break laws, including copyright laws -- this includes piracy tools (including mods that use projects like `youtube-dl` for in-game music streaming) and hacked clients, as well as projects that fail to adhere to the licenses of other projects to the best of their ability -- Projects must not break the Terms of Service or EULA of any organization, including (but not limited to) Mojang, Microsoft, Discord (including their ban on exploits and hacks) and any other community platforms we use -- Projects must not hide their functionality and should be upfront with what they do -- however, projects with unfinished documentation or benign "Easter eggs" do not violate this rule -- Projects must not make use of exploits in order to provide their functionality -- this is required by the [Discord Terms of Service](https://discord.com/terms) (among others), and is widely considered to be a problematic thing to do - -#### 6) Don't spam, and don't advertise outside the showcase channels - -We provide a number of channels for showcasing and informing users about your Quilt-related projects. Outside of these channels, we will not tolerate advertising or any other form of spam. In particular, posting large numbers of images or lines of text together can be particularly disruptive, and we'd prefer you make use of a pastebin site or image uploading site when sharing a lot of text or images. - -We may remove links to other Discord servers, communities and projects at our discretion if we feel like they've been posted inappropriately, rather than to start or contribute to a discussion. - -#### 7) Follow the given channel topic, and don't derail a discussion - -Most of our channels are strictly on-topic, and we expect our users to take note of a channel's topic and stick to it. We understand that conversations may span multiple topics and move onto something else, but we may ask you to move if a conversation leaves the scope of a channel's topic. - -Additionally, when entering a channel with an active discussion, please be mindful of that discussion and do not try to derail it (by talking over it, for example). We have multiple general (off-topic) channels you can use if a channel is busy. - -#### 8) When requesting help, specify your mappings (and other useful, relevant info) - -If you're working on a mod and asking for help in one of our many help channels, **make sure you specify what mappings you're using**. We recommend creating a thread, and putting the mappings in the thread name -- you can use these abbreviations to ensure everyone's on the same page: - -- `MCP` -- MCP/Forge mappings -- `MM` -- Mojang Mappings -- `QM` -- Quilt Mappings (The default for Quilt) -- `YM` -- Yarn Mappings (The default for Fabric) - -An example thread title could be `YM | Entity pathing` or `[MM] Negative Enchants`. That said, we understand that quick questions may be more suited to direct discussion in the channels -- in those cases, **make sure you're clear about which mappings you're using**. You can also make use of the `:mcp:`, `:mm:`, `:qm:` and `:ym:` (or `:yarn:`) emoji if you'd like to. - -Ultimately, it's _your_ responsibility to ensure that it's as easy as possible to help you with your questions. The less work it takes for someone to understand your problem, the more likely you are to get a quick response! To that end, we also recommend you specify other useful information with your question -- such as **the version of Minecraft you're working with**, **error logs** and **relevant code snippets**. - -#### 9) Don't import drama or controversy from other communities - -We aim to be a safe place for everyone -- regardless of their background, identity, or other defining trait. In order to do this, it's important that people are allowed to interact without having to worry about controversies from the wider modding community that they may be seeking refuge from. - -Additionally, we expect a certain level of professionalism from our members. For both of these reasons, discussion of drama or controversies from other communities is banned -- including the numerous controversies that have unfolded within other spaces in the wider modding community. - -If you'd like to discuss these controversies with other users, start a DM group or join a community that's designed to handle that discussion. - -<hr /> - -### Non-message mediums - -Do not change your avatar, nickname, username or custom/rich status to try to evade an infraction, or to attack or harass any user or group. If you'd like to appeal an infraction, please send a private message to any community team member. - -#### Nicknames - -All nicknames must adhere to the rules above, in addition to the following rules: -1. Nicknames must be easy to read, especially by a screen-reader (eg: no Zalgo or otherwise hard to read non-ascii characters, with the exception of non-Latin names) -2. Nicknames cannot be intentionally confusing or misleading - impersonation is stricly forbidden, as well as using similar looking nicknames to be intentionally confusing -3. Nicknames must have some readable characters (eg: no "empty" nicknames) - -We reserve the right to change or reset nicknames that are infringing those rules, or designed to place you higher in the member list in community spaces that have one, which is known as "hoisting". As always, the moderator has the final call as to whether a nickname infringe those rules or not. You are free to appeal this decision. - -#### Avatars - -All avatars must adhere to the rules above. Additionally, avatars depicting weapons (e.g. knives, firearms), objectionable or Not Safe For Work (NSFW) content are disallowed, as well as fully-transparent avatars or avatars that appear to be fully-transparent by matching the platform's background color. This also applies to PluralKit member avatars. - -#### Custom/Rich Statuses - -All user statuses must adhere to the rules above. In particular, we don't want to see objectionable or <abbr title="Not Safe For Work">NSFW</abbr> emoji, the advertising of sketchy or <abbr title="Not Safe For Work">NSFW</abbr> websites, or hateful sentiment. - -### Reporting - -To report rule-breaking behavior on Discord, mention the **@Moderators** role directly in the channel, and a community team member will be along as soon as they can be. You can also send a private message to the **@ModMail** bot, which will open a thread that any currently available community team member can respond to. - -Alternatively, you can send a private message directly to any community team member, or otherwise contact the community team using the relevant contact methods for the given community space. - -If your report concerns a community team member, please send a private message directly to a different member of the community team or a member of the administrative board. All private reports will be treated with confidentiality. - -### Enforcement - -Our community team members have multiple tools at their disposal when dealing with those who violate the rules, including the following: - -- Verbally/textually warning or correcting users -- Forcibly changing a user's nickname -- Temporarily muting users -- Temporarily or permanently removing users from the community (kicking, tempbanning, banning) - -Each situation is unique, and will be assessed on a case-by-case basis. All actions taken in response to rule-breaking behavior is done at the discretion of the community team member in question -- however, we will take feedback from the community if its members are not happy with how things were resolved. - -Appeals for community bans on Discord are handled via the **@ModMail** bot, and banned users are automatically sent an invite to a special server that exists for them to be able to send a private message to **@ModMail**. We advise that anyone appealing an infraction approaches their appeal with civility and respect, addressing the infraction reason and, if they agree with the infraction, considering the severity of what they did and what they may be able to do to rectify it. - -Appeals made for lesser infractions may result in a more significant infraction if the person appealing fails to approach their appeal with respect, or attempts to abuse the community team members or appeals process. - -#### Moderation Guidelines - -Moderation is a complicated subject at best, and it requires a lot of nuances and difficult decision-making. While it's impossible to enumerate every possible situation (and some situations will not suit our documentation), we've done our best to explain how we come to a decision, and what we expect from our community team. - -For more information on this, feel free to read [our moderation guidelines](/en/staff/moderation). If you have any feedback on this document, feel free to contact us! From 0ae9af323ffda2a7219df3a1493238807d2bddd5 Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 19:30:27 +0100 Subject: [PATCH 10/12] Delete writing.mdx (most people can already write...?) --- src/pages/en/staff/outreach/writing.mdx | 206 ------------------------ 1 file changed, 206 deletions(-) delete mode 100644 src/pages/en/staff/outreach/writing.mdx diff --git a/src/pages/en/staff/outreach/writing.mdx b/src/pages/en/staff/outreach/writing.mdx deleted file mode 100644 index f8a05e39..00000000 --- a/src/pages/en/staff/outreach/writing.mdx +++ /dev/null @@ -1,206 +0,0 @@ ---- -title: Writing Guidelines -description: Tips and best-practices for writing content on the site. -authors: - - gdude2002 - - pluie - - "[object Object]" -layout: /src/layouts/StaffDocument.astro ---- - -import Message from "@atoms/Message.astro"; - -import TabBar from "@atoms/tabs/TabBar.astro"; -import TabBarLink from "@atoms/tabs/TabBarLink.astro"; -import TabContent from "@atoms/tabs/TabContent.astro"; -import TabGroup from "@atoms/tabs/TabGroup.astro"; - -<Message title="Warning: Migration" style="danger"> - -**This document has completely changed.** As we have migrated from Jekyll to [Astro](https://astro.build), writing documents is now a vastly different process. Please contact [pluie](https://github.com/pluiedev) (`pluie#9105`) or [[object Object]](https://github.com/obj-obj) (`[object Object]#7105`) if you need any help writing new articles and these new guidelines aren't enough. Thanks for your patience! - -</Message> - -{/* -<TabGroup id="test-group"> - <TabBar> - <TabBarLink name="First Tab" tab="one"></TabBarLink> - <TabBarLink name="Second Tab" tab="two"></TabBarLink> - </TabBar> - - <TabContent tab="one"> - First tab content - </TabContent> - - <TabContent tab="two"> - Second tab content - </TabContent> -</TabGroup> -*/} - -Writing work can be tricky at times, and Quilt doesn't have a large group of professional writers on hand for advice. This document is intended to be a set of guidelines, tips, and tricks to use when writing documents, articles, blog posts, and other written content for the site. - -## Editors & Setup - -Using [Visual Studio Code](https://code.visualstudio.com) or [VSCodium](https://vscodium.com) is recommended. When opening the site with VSCode, you should see a popup in the bottom right asking if you want to install some recommended extensions. If you don't see it, you can also type `@recommended` into the extensions searchbar: - -<img src="/assets/img/writing/recommended-extensions.jpg" width="300" /> - -## Spelling, Punctuation & Grammar - -This goes without saying, but proper spelling and grammar is fairly important. That said, nobody is perfect and there are tools out there that make everyone's lives easier. The use of one is highly recommended, even if you usually have excellent spelling and grammar -- everyone makes mistakes! - -- [LanguageTool](https://languagetool.org) remains one of the best tools available for this, even the free version. VSCode with [the LTeX extension](https://marketplace.visualstudio.com/items?itemName=valentjn.vscode-ltex) -- or IntelliJ IDEA -- is an easy way to use LanguageTool. -- [Grammarly](https://www.grammarly.com) exists as an alternative, but LanguageTool's open-source approach tends to result in a more trustable tool. - -A somewhat formal tone in your writing is also recommended, but there's absolutely no need to completely avoid an informal approach. The site even supports emojis (<kbd>Meta</kbd> + <kbd>.</kbd>), if that's something you're into. 🥔 - -It's also worth thinking a little about punctuation -- you can use `-` for a hyphen, with `--` and `---` existing for progressively longer dashes. If you're looking to join to words together (like-this), use a single hyphen. To break apart a sentence -- like this -- use two dashes. - -## Front Matter - -A front matter block must be placed at the top of every document or page that's written for the site. It takes the form of a block of YAML surrounded by triple dashes (`---`), and should contain _at least_ a `title` and `layout` property. - -```yaml ---- -title: This is the title of the page or blog post. -layout: /src/layouts/Page.astro ---- -``` - -Pages that don't contain a `layout` property in the front matter will be output as plain HTML (no sidebar, no styling, nothing). Below are some front matter properties: - -- `layout` -- Layouts are in the `/src/pages` directory. Most of the pages either use `/src/layouts/Page.astro` (for pages, such as About, Community, etc.) and `/src/layouts/Post.astro` (for blog posts). The Install section of the site uses a different set of layouts (`/src/layouts/Install.astro` for the main page and `/src/layouts/InstallPage.astro` for the launcher pages). - -- `draft` -- If you're working on something that needs to be committed but not visible to the public on the site, you can set this to `true`. - -More information on this can be found in [the Astro documentation](https://docs.astro.build/en/guides/markdown-content). - -### Author Information - -Author information can be specified using the `authors` property in the front matter: - -```yaml ---- -authors: - - person-one - - person-two ---- -``` - -### Components - -To use any components that require importing, you'll need to be in a `.mdx` file instead of a `.md` file. There's no difference between the Markdown in these two filetypes, so you can just rename any existing Markdown file. - -#### Messages - -`Message` -- this allows you to create a Message, as shown below. Messages are essentially boxes that draw attention to a specific block of text. - -<div class="columns"> - <div class="column"> - ##### Example - - ```astro - import Message from "@atoms/Message.astro"; - - <Message style="success"> - This message has no title, but it has the "success" styling. - </Message> - - <Message title="Title goes here" style="danger"> - This message has a title, and the "danger" styling. - </Message> - ``` - - </div> - - <div class="column"> - ##### Result - - <Message style="success"> - This message has no title, but it has the "success" styling. - </Message> - - <Message title="Title goes here" style="danger"> - This message has a title, and the "danger" styling. - </Message> - - </div> - -</div> - -#### Columns - -Columns aren't particularly complex. Columns on this site will collapse nicely for mobile users, with the leftmost column showing first. Here's an example to show how to use them: - -##### Example - -```astro -<div class="columns"> - <div class="column"> - <Message> - This is column 1. - </Message> - </div> - <div class="column"> - <Message> - This is column 2. - </Message> - </div> -</div> -``` - -##### Result - -<div class="columns"> - <div class="column"> - <Message>This is column 1.</Message> - </div> - <div class="column"> - <Message>This is column 2.</Message> - </div> -</div> - -# Articles, Documents and Pages - -When working on non-blog content, it's worth keeping the following points in mind. - -## Front Matter (Pages) - -For non-blog content, the following front matter properties may be useful: - -- `description` -- This is the page's meta description that will be shown in search engines and on social media. If you skip this, then the site's default description will be used instead. - -# Blog Posts - -As writing blog posts is somewhat different from writing an article or document, you'll need to do the following things **in addition to the requirements for any other type of page**: - -- Include a date in the post's front matter. -- Include author information in the post's front matter, [as detailed above](#author-information). -- Define an excerpt in your post - -For more information on these concepts, please see the following sections. - -## Front Matter (Blog) - -For blog posts, you need to include a `date` field in the front matter, which should be in a standard ISO format (For example, `2022-05-07 4:30:00 -00:00`). This is required for all blog posts, as the site relies on it for post ordering and to display metadata. - -## Excerpts - -Excerpts are meant to be a summary of what's in a blog post. **Every blog post must have an excerpt** -- failing to provide one will make the entire post be used as the excerpt, which is definitely not what you want. - -Typically, excerpts are generated from the first couple of paragraphs in a post. Using the special HTML comment `<!-- MORE -->` will mark all content above it as the excerpt. - -One approach would be to write a summary at the top of an article, mark it as the excerpt and add a horizontal rule to split it from the rest of the page content: - -```markdown -A summary of the post goes here. - -<!-- MORE --> - ---- - -The actual post content starts here. -``` - -There are many ways to approach this, of course -- it's best left to the creative liberty of whoever's writing the post, so this is just a suggestion. From f7cd7f754ebfa34fcd6bb88d4496ff6a8e49a734 Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 19:50:42 +0100 Subject: [PATCH 11/12] Revert "Remove rules (we have transcended them)" This reverts commit e183d3fb8eb235dba2574938c4d435dca653562b. --- src/pages/en/community/rules.mdx | 131 +++++++++++++++++++++++++++++++ 1 file changed, 131 insertions(+) create mode 100644 src/pages/en/community/rules.mdx diff --git a/src/pages/en/community/rules.mdx b/src/pages/en/community/rules.mdx new file mode 100644 index 00000000..8b6ffe14 --- /dev/null +++ b/src/pages/en/community/rules.mdx @@ -0,0 +1,131 @@ +--- +title: Rules +description: Quilt's core rules, which build upon the Code of Conduct to provide a set of concrete guidelines for behaviour. +layout: /src/layouts/Page.astro +--- + +We expect everyone that makes use of any Quilt community spaces to adhere to the following rules. If you have any questions or suggestions, please feel free to contact a member of the community team or ask your question in the `#discord-meta` channel. + +**Remember:** Ignorance of our rules is not an excuse for breaking them. You are responsible for educating yourself on how every community you join expects you to behave, and "I didn't know that was in the rules" will never be a valid excuse. + +#### 1) Follow our Code of Conduct and NSFW content policy + +Make sure you read and follow [our Code of Conduct](/en/community/code-of-conduct), which outlines what we expect from you and is the basis for these rules. It's important that you read and understand the Code of Conduct, and the rules on this page -- feel free to contact a community team member if you need any clarification. + +Additionally, be sure to read and follow [our NSFW and Sexual Content policy](/en/community/nsfw-policy), which explains what types of content, media and related behaviour we do and don't allow. + +That said, remember that there will sometimes be situations that are difficult to fit into the Code of Conduct at a glance. In these cases, please contact a member of the community team for clarification. + +#### 2) Follow Discord's Rules + +In all community spaces, everyone must also follow the Discord [Community Guidelines](https://discord.com/guidelines) and [Terms of Service](https://discord.com/terms). + +These aren't just good to follow as a general rule of thumb -- this is also a requirement when operating a large community on Discord, especially if that community is aiming to be partnered or verified. + +#### 3) Try to speak English + +The world is a big place, and many people will have a different native language. The common language in our community is English, but we understand that not everyone speaks English at the same level. + +If you're not a native English speaker, please try to speak English to the best of your ability. Don't worry if you need to use a translation tool, or if your English isn't great -- we won't make fun of you, and we'll help you figure out the right words if you get stuck. + +#### 4) Listen to & respect all community team members + +The community team is here to support the community, keep it running smoothly, and ensure that it remains safe and friendly. In order to allow us to do our jobs, we need you to cooperate with us. + +Essentially, please take requests from community team members seriously and listen when a team member asks you to do something. If you have a problem with what a team member is asking you to do, we advise that you step away from the situation and send a private message to another team member. + +#### 5) Keep all projects legal, legitimate & appropriate + +While anyone may make use of the Quilt toolchain in accordance with the licenses applied to each project, all projects developed or promoted **in all Quilt community spaces** must meet the following criteria: + +- Projects must not be malicious -- which includes (but is not limited to) malware, mods that include backdoors, mods that modify Quilt in an attempt to hide themselves from servers they connect to, or mods that harass specific people or groups of people (for example, by automatically kicking them from servers with the mod installed) +- Projects must not be sexualized, hateful or otherwise inappropriate in nature, and this also applies to all code and project assets posted for any purpose +- Projects must not break laws, including copyright laws -- this includes piracy tools (including mods that use projects like `youtube-dl` for in-game music streaming) and hacked clients, as well as projects that fail to adhere to the licenses of other projects to the best of their ability +- Projects must not break the Terms of Service or EULA of any organization, including (but not limited to) Mojang, Microsoft, Discord (including their ban on exploits and hacks) and any other community platforms we use +- Projects must not hide their functionality and should be upfront with what they do -- however, projects with unfinished documentation or benign "Easter eggs" do not violate this rule +- Projects must not make use of exploits in order to provide their functionality -- this is required by the [Discord Terms of Service](https://discord.com/terms) (among others), and is widely considered to be a problematic thing to do + +#### 6) Don't spam, and don't advertise outside the showcase channels + +We provide a number of channels for showcasing and informing users about your Quilt-related projects. Outside of these channels, we will not tolerate advertising or any other form of spam. In particular, posting large numbers of images or lines of text together can be particularly disruptive, and we'd prefer you make use of a pastebin site or image uploading site when sharing a lot of text or images. + +We may remove links to other Discord servers, communities and projects at our discretion if we feel like they've been posted inappropriately, rather than to start or contribute to a discussion. + +#### 7) Follow the given channel topic, and don't derail a discussion + +Most of our channels are strictly on-topic, and we expect our users to take note of a channel's topic and stick to it. We understand that conversations may span multiple topics and move onto something else, but we may ask you to move if a conversation leaves the scope of a channel's topic. + +Additionally, when entering a channel with an active discussion, please be mindful of that discussion and do not try to derail it (by talking over it, for example). We have multiple general (off-topic) channels you can use if a channel is busy. + +#### 8) When requesting help, specify your mappings (and other useful, relevant info) + +If you're working on a mod and asking for help in one of our many help channels, **make sure you specify what mappings you're using**. We recommend creating a thread, and putting the mappings in the thread name -- you can use these abbreviations to ensure everyone's on the same page: + +- `MCP` -- MCP/Forge mappings +- `MM` -- Mojang Mappings +- `QM` -- Quilt Mappings (The default for Quilt) +- `YM` -- Yarn Mappings (The default for Fabric) + +An example thread title could be `YM | Entity pathing` or `[MM] Negative Enchants`. That said, we understand that quick questions may be more suited to direct discussion in the channels -- in those cases, **make sure you're clear about which mappings you're using**. You can also make use of the `:mcp:`, `:mm:`, `:qm:` and `:ym:` (or `:yarn:`) emoji if you'd like to. + +Ultimately, it's _your_ responsibility to ensure that it's as easy as possible to help you with your questions. The less work it takes for someone to understand your problem, the more likely you are to get a quick response! To that end, we also recommend you specify other useful information with your question -- such as **the version of Minecraft you're working with**, **error logs** and **relevant code snippets**. + +#### 9) Don't import drama or controversy from other communities + +We aim to be a safe place for everyone -- regardless of their background, identity, or other defining trait. In order to do this, it's important that people are allowed to interact without having to worry about controversies from the wider modding community that they may be seeking refuge from. + +Additionally, we expect a certain level of professionalism from our members. For both of these reasons, discussion of drama or controversies from other communities is banned -- including the numerous controversies that have unfolded within other spaces in the wider modding community. + +If you'd like to discuss these controversies with other users, start a DM group or join a community that's designed to handle that discussion. + +<hr /> + +### Non-message mediums + +Do not change your avatar, nickname, username or custom/rich status to try to evade an infraction, or to attack or harass any user or group. If you'd like to appeal an infraction, please send a private message to any community team member. + +#### Nicknames + +All nicknames must adhere to the rules above, in addition to the following rules: +1. Nicknames must be easy to read, especially by a screen-reader (eg: no Zalgo or otherwise hard to read non-ascii characters, with the exception of non-Latin names) +2. Nicknames cannot be intentionally confusing or misleading - impersonation is stricly forbidden, as well as using similar looking nicknames to be intentionally confusing +3. Nicknames must have some readable characters (eg: no "empty" nicknames) + +We reserve the right to change or reset nicknames that are infringing those rules, or designed to place you higher in the member list in community spaces that have one, which is known as "hoisting". As always, the moderator has the final call as to whether a nickname infringe those rules or not. You are free to appeal this decision. + +#### Avatars + +All avatars must adhere to the rules above. Additionally, avatars depicting weapons (e.g. knives, firearms), objectionable or Not Safe For Work (NSFW) content are disallowed, as well as fully-transparent avatars or avatars that appear to be fully-transparent by matching the platform's background color. This also applies to PluralKit member avatars. + +#### Custom/Rich Statuses + +All user statuses must adhere to the rules above. In particular, we don't want to see objectionable or <abbr title="Not Safe For Work">NSFW</abbr> emoji, the advertising of sketchy or <abbr title="Not Safe For Work">NSFW</abbr> websites, or hateful sentiment. + +### Reporting + +To report rule-breaking behavior on Discord, mention the **@Moderators** role directly in the channel, and a community team member will be along as soon as they can be. You can also send a private message to the **@ModMail** bot, which will open a thread that any currently available community team member can respond to. + +Alternatively, you can send a private message directly to any community team member, or otherwise contact the community team using the relevant contact methods for the given community space. + +If your report concerns a community team member, please send a private message directly to a different member of the community team or a member of the administrative board. All private reports will be treated with confidentiality. + +### Enforcement + +Our community team members have multiple tools at their disposal when dealing with those who violate the rules, including the following: + +- Verbally/textually warning or correcting users +- Forcibly changing a user's nickname +- Temporarily muting users +- Temporarily or permanently removing users from the community (kicking, tempbanning, banning) + +Each situation is unique, and will be assessed on a case-by-case basis. All actions taken in response to rule-breaking behavior is done at the discretion of the community team member in question -- however, we will take feedback from the community if its members are not happy with how things were resolved. + +Appeals for community bans on Discord are handled via the **@ModMail** bot, and banned users are automatically sent an invite to a special server that exists for them to be able to send a private message to **@ModMail**. We advise that anyone appealing an infraction approaches their appeal with civility and respect, addressing the infraction reason and, if they agree with the infraction, considering the severity of what they did and what they may be able to do to rectify it. + +Appeals made for lesser infractions may result in a more significant infraction if the person appealing fails to approach their appeal with respect, or attempts to abuse the community team members or appeals process. + +#### Moderation Guidelines + +Moderation is a complicated subject at best, and it requires a lot of nuances and difficult decision-making. While it's impossible to enumerate every possible situation (and some situations will not suit our documentation), we've done our best to explain how we come to a decision, and what we expect from our community team. + +For more information on this, feel free to read [our moderation guidelines](/en/staff/moderation). If you have any feedback on this document, feel free to contact us! From f1c0676858b31d3d971a3200ca10679d8b24783d Mon Sep 17 00:00:00 2001 From: Southpaw <git@southpaw1496.dev> Date: Sun, 1 Sep 2024 20:02:44 +0100 Subject: [PATCH 12/12] Revert "Revert "Remove rules (we have transcended them)"" This reverts commit f7cd7f754ebfa34fcd6bb88d4496ff6a8e49a734. --- src/pages/en/community/rules.mdx | 131 ------------------------------- 1 file changed, 131 deletions(-) delete mode 100644 src/pages/en/community/rules.mdx diff --git a/src/pages/en/community/rules.mdx b/src/pages/en/community/rules.mdx deleted file mode 100644 index 8b6ffe14..00000000 --- a/src/pages/en/community/rules.mdx +++ /dev/null @@ -1,131 +0,0 @@ ---- -title: Rules -description: Quilt's core rules, which build upon the Code of Conduct to provide a set of concrete guidelines for behaviour. -layout: /src/layouts/Page.astro ---- - -We expect everyone that makes use of any Quilt community spaces to adhere to the following rules. If you have any questions or suggestions, please feel free to contact a member of the community team or ask your question in the `#discord-meta` channel. - -**Remember:** Ignorance of our rules is not an excuse for breaking them. You are responsible for educating yourself on how every community you join expects you to behave, and "I didn't know that was in the rules" will never be a valid excuse. - -#### 1) Follow our Code of Conduct and NSFW content policy - -Make sure you read and follow [our Code of Conduct](/en/community/code-of-conduct), which outlines what we expect from you and is the basis for these rules. It's important that you read and understand the Code of Conduct, and the rules on this page -- feel free to contact a community team member if you need any clarification. - -Additionally, be sure to read and follow [our NSFW and Sexual Content policy](/en/community/nsfw-policy), which explains what types of content, media and related behaviour we do and don't allow. - -That said, remember that there will sometimes be situations that are difficult to fit into the Code of Conduct at a glance. In these cases, please contact a member of the community team for clarification. - -#### 2) Follow Discord's Rules - -In all community spaces, everyone must also follow the Discord [Community Guidelines](https://discord.com/guidelines) and [Terms of Service](https://discord.com/terms). - -These aren't just good to follow as a general rule of thumb -- this is also a requirement when operating a large community on Discord, especially if that community is aiming to be partnered or verified. - -#### 3) Try to speak English - -The world is a big place, and many people will have a different native language. The common language in our community is English, but we understand that not everyone speaks English at the same level. - -If you're not a native English speaker, please try to speak English to the best of your ability. Don't worry if you need to use a translation tool, or if your English isn't great -- we won't make fun of you, and we'll help you figure out the right words if you get stuck. - -#### 4) Listen to & respect all community team members - -The community team is here to support the community, keep it running smoothly, and ensure that it remains safe and friendly. In order to allow us to do our jobs, we need you to cooperate with us. - -Essentially, please take requests from community team members seriously and listen when a team member asks you to do something. If you have a problem with what a team member is asking you to do, we advise that you step away from the situation and send a private message to another team member. - -#### 5) Keep all projects legal, legitimate & appropriate - -While anyone may make use of the Quilt toolchain in accordance with the licenses applied to each project, all projects developed or promoted **in all Quilt community spaces** must meet the following criteria: - -- Projects must not be malicious -- which includes (but is not limited to) malware, mods that include backdoors, mods that modify Quilt in an attempt to hide themselves from servers they connect to, or mods that harass specific people or groups of people (for example, by automatically kicking them from servers with the mod installed) -- Projects must not be sexualized, hateful or otherwise inappropriate in nature, and this also applies to all code and project assets posted for any purpose -- Projects must not break laws, including copyright laws -- this includes piracy tools (including mods that use projects like `youtube-dl` for in-game music streaming) and hacked clients, as well as projects that fail to adhere to the licenses of other projects to the best of their ability -- Projects must not break the Terms of Service or EULA of any organization, including (but not limited to) Mojang, Microsoft, Discord (including their ban on exploits and hacks) and any other community platforms we use -- Projects must not hide their functionality and should be upfront with what they do -- however, projects with unfinished documentation or benign "Easter eggs" do not violate this rule -- Projects must not make use of exploits in order to provide their functionality -- this is required by the [Discord Terms of Service](https://discord.com/terms) (among others), and is widely considered to be a problematic thing to do - -#### 6) Don't spam, and don't advertise outside the showcase channels - -We provide a number of channels for showcasing and informing users about your Quilt-related projects. Outside of these channels, we will not tolerate advertising or any other form of spam. In particular, posting large numbers of images or lines of text together can be particularly disruptive, and we'd prefer you make use of a pastebin site or image uploading site when sharing a lot of text or images. - -We may remove links to other Discord servers, communities and projects at our discretion if we feel like they've been posted inappropriately, rather than to start or contribute to a discussion. - -#### 7) Follow the given channel topic, and don't derail a discussion - -Most of our channels are strictly on-topic, and we expect our users to take note of a channel's topic and stick to it. We understand that conversations may span multiple topics and move onto something else, but we may ask you to move if a conversation leaves the scope of a channel's topic. - -Additionally, when entering a channel with an active discussion, please be mindful of that discussion and do not try to derail it (by talking over it, for example). We have multiple general (off-topic) channels you can use if a channel is busy. - -#### 8) When requesting help, specify your mappings (and other useful, relevant info) - -If you're working on a mod and asking for help in one of our many help channels, **make sure you specify what mappings you're using**. We recommend creating a thread, and putting the mappings in the thread name -- you can use these abbreviations to ensure everyone's on the same page: - -- `MCP` -- MCP/Forge mappings -- `MM` -- Mojang Mappings -- `QM` -- Quilt Mappings (The default for Quilt) -- `YM` -- Yarn Mappings (The default for Fabric) - -An example thread title could be `YM | Entity pathing` or `[MM] Negative Enchants`. That said, we understand that quick questions may be more suited to direct discussion in the channels -- in those cases, **make sure you're clear about which mappings you're using**. You can also make use of the `:mcp:`, `:mm:`, `:qm:` and `:ym:` (or `:yarn:`) emoji if you'd like to. - -Ultimately, it's _your_ responsibility to ensure that it's as easy as possible to help you with your questions. The less work it takes for someone to understand your problem, the more likely you are to get a quick response! To that end, we also recommend you specify other useful information with your question -- such as **the version of Minecraft you're working with**, **error logs** and **relevant code snippets**. - -#### 9) Don't import drama or controversy from other communities - -We aim to be a safe place for everyone -- regardless of their background, identity, or other defining trait. In order to do this, it's important that people are allowed to interact without having to worry about controversies from the wider modding community that they may be seeking refuge from. - -Additionally, we expect a certain level of professionalism from our members. For both of these reasons, discussion of drama or controversies from other communities is banned -- including the numerous controversies that have unfolded within other spaces in the wider modding community. - -If you'd like to discuss these controversies with other users, start a DM group or join a community that's designed to handle that discussion. - -<hr /> - -### Non-message mediums - -Do not change your avatar, nickname, username or custom/rich status to try to evade an infraction, or to attack or harass any user or group. If you'd like to appeal an infraction, please send a private message to any community team member. - -#### Nicknames - -All nicknames must adhere to the rules above, in addition to the following rules: -1. Nicknames must be easy to read, especially by a screen-reader (eg: no Zalgo or otherwise hard to read non-ascii characters, with the exception of non-Latin names) -2. Nicknames cannot be intentionally confusing or misleading - impersonation is stricly forbidden, as well as using similar looking nicknames to be intentionally confusing -3. Nicknames must have some readable characters (eg: no "empty" nicknames) - -We reserve the right to change or reset nicknames that are infringing those rules, or designed to place you higher in the member list in community spaces that have one, which is known as "hoisting". As always, the moderator has the final call as to whether a nickname infringe those rules or not. You are free to appeal this decision. - -#### Avatars - -All avatars must adhere to the rules above. Additionally, avatars depicting weapons (e.g. knives, firearms), objectionable or Not Safe For Work (NSFW) content are disallowed, as well as fully-transparent avatars or avatars that appear to be fully-transparent by matching the platform's background color. This also applies to PluralKit member avatars. - -#### Custom/Rich Statuses - -All user statuses must adhere to the rules above. In particular, we don't want to see objectionable or <abbr title="Not Safe For Work">NSFW</abbr> emoji, the advertising of sketchy or <abbr title="Not Safe For Work">NSFW</abbr> websites, or hateful sentiment. - -### Reporting - -To report rule-breaking behavior on Discord, mention the **@Moderators** role directly in the channel, and a community team member will be along as soon as they can be. You can also send a private message to the **@ModMail** bot, which will open a thread that any currently available community team member can respond to. - -Alternatively, you can send a private message directly to any community team member, or otherwise contact the community team using the relevant contact methods for the given community space. - -If your report concerns a community team member, please send a private message directly to a different member of the community team or a member of the administrative board. All private reports will be treated with confidentiality. - -### Enforcement - -Our community team members have multiple tools at their disposal when dealing with those who violate the rules, including the following: - -- Verbally/textually warning or correcting users -- Forcibly changing a user's nickname -- Temporarily muting users -- Temporarily or permanently removing users from the community (kicking, tempbanning, banning) - -Each situation is unique, and will be assessed on a case-by-case basis. All actions taken in response to rule-breaking behavior is done at the discretion of the community team member in question -- however, we will take feedback from the community if its members are not happy with how things were resolved. - -Appeals for community bans on Discord are handled via the **@ModMail** bot, and banned users are automatically sent an invite to a special server that exists for them to be able to send a private message to **@ModMail**. We advise that anyone appealing an infraction approaches their appeal with civility and respect, addressing the infraction reason and, if they agree with the infraction, considering the severity of what they did and what they may be able to do to rectify it. - -Appeals made for lesser infractions may result in a more significant infraction if the person appealing fails to approach their appeal with respect, or attempts to abuse the community team members or appeals process. - -#### Moderation Guidelines - -Moderation is a complicated subject at best, and it requires a lot of nuances and difficult decision-making. While it's impossible to enumerate every possible situation (and some situations will not suit our documentation), we've done our best to explain how we come to a decision, and what we expect from our community team. - -For more information on this, feel free to read [our moderation guidelines](/en/staff/moderation). If you have any feedback on this document, feel free to contact us!