From 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 24 Sep 2024 16:33:09 +0200 Subject: [PATCH 01/16] Modding CoC rewrite + simplification --- .../en.md | 67 ++++++------------- 1 file changed, 21 insertions(+), 46 deletions(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index 287bf3e4797b..c6b8e84b5445 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -4,58 +4,33 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines ## Behaviour and conduct -- The goal of modding is to help a mapper improve their work so that it can be pushed towards the [ranked](/wiki/Beatmap/Category#ranked) status if the mapper chooses to do so. If you're not interested in helping people, steer clear of the discussion to avoid *hurting them*. -- When modding, consider who the post is directed at, what you aim to achieve by posting and what response you expect to receive. This will ensure your best intentions are conveyed and your post is easy to understand. - - Don't shy away from new mappers and modders — these people are the ones who can benefit the most from your input! Be patient, understanding, and provide as much explanation as possible so that they can learn and improve more quickly - - If you're new yourself, don't be afraid to say so! This will allow more experienced community members to point you in the right direction. Everyone was new and in your position once! -- Treat others as you wish to be treated. People are more receptive to kind, helpful suggestions than hostile ones. Try to understand others' point-of-view rather than attack it — nobody likes to feel worthless, incompetent or stupid. If you are a masochist, assume that all others are not. -- If you wish to comment on or discuss a beatmap, go to that beatmap's [discussion page](/wiki/Beatmap_discussion) — not social media outlets, or the comment section, as it is unlikely your concerns will be heard by anyone with the power to address them appropriately. -- Personal attacks, hateful comments, misplaced joking, derailing the thread and general drama-initiation are not acceptable in any form and **will not be tolerated**. - -## Making a mod post - -So you downloaded a map and you've thought of some things you aren't happy with — now's the time to put your thoughts to words and help improve the map. But how can you get the mapper to see your point of view, test your suggestions and give you feedback? After all, no one likes feeling that their time has been wasted. - -- Before modding, ensure your intentions are good and you are focused on the task at hand. No one likes to receive a rude or lazy mod. -- When making suggestions, try to differentiate between what is intersubjectively / objectively bad or wrong, and what you simply dislike on a personal level. **All types of suggestion are fine as long as they are put forward accordingly**. - - **Objective Issues** - Prohibited by rulesets and must be fixed. - - **Intersubjective Issues** - Not prohibited by rulesets, but are agreed upon as being "wrong" by a majority of people. Should be fixed in most cases unless there are opposing intersubjective arguments with equal size, or if the mapper can exhaustively explain why they feel it is acceptable. - - **Subjective Issues** - Something that you believe or think on a personal level. Might become intersubjective if many people agree with it. -- **Unless the concept behind a beatmap is fundamentally flawed from the start**, modding should aim to improve the map **in its current design** - not force your own style upon it. If you truly believe the map has too many significant issues to address individually, try to give a general statement of why this is the case and what direction you think the map should go in to get back on track. -- When pointing out "issues", inspect each thoroughly and consider exactly what it is about the particular "thing" you dislike. Then, try to offer a potential solution or improvement and consider exactly how that suggestion will improve the map. If necessary, try multiple suggestions to see which work best — the more help you can offer the mapper, the better. - -Suggestions themselves should ideally consist of four main parts, though based on the experience of the mapper and/or your personal relationship to them, you may want to be more lenient: - -1. **A statement of the issue itself and where it can be found** - including a timestamp is a huge help so that the mapper can find the part in question quickly. -2. **A brief explanation of why this causes a problem** - this is essential in convincing a mapper to even consider your suggestion. Mappers are much more receptive to criticism and change when it's accompanied by clear, understandable and valid reasoning. -3. **One or more alternative suggestions, accompanied by explanations of how they address the problem(s)** - much like the above, explanation is key here. Even if you can convince the mapper that their current work can be improved, what makes your suggestion better than theirs, or anyone else's? -4. **The wording (or even language) used should take the mapper into consideration.** Are they a fluent English speaker? If not, stick to simple and easy-to-understand language. If you both speak the same language, by all means write in that language, but try to append an English summary of your mods and mod replies if possible, to ensure everyone stays on the same page. If necessary, support your suggestions with screenshots, illustrations, or even short video clips to help get your point across. - -There are any number of ways to present your mod post, so feel free to experiment, but try to keep the visuals simple and formatted in a way that it is easy for the mapper and others to work with. +- **The goal of modding is to help a mapper improve their work.** If you're not interested in helping people, steer clear of the discussion. +- **Consider what you're posting, why you're posting it, and who you're posting it to.** This will ensure your best intentions are conveyed and your post is easy to understand. + - **Don't shy away from new mappers and modders** — these people are the ones who can benefit the most from your input! Be patient, understanding, and provide as much explanation as possible so that they can learn and improve more quickly + - **If you're new yourself, don't be afraid to say so!** This will allow more experienced community members to point you in the right direction. Everyone was new and in your position once! +- **Treat others as you wish to be treated.** People are more receptive to kind, helpful suggestions than hostile ones. Stay on topic and keep away from personal attacks, hateful comments, and misplaced jokes to avoid derailing the thread. +- **Use the [discussion page](/wiki/Beatmap_discussion).** Discuss your suggestions with other community members. Otherwise, it is unlikely your concerns will be heard by anyone with the power to address them appropriately. ## Responding to a mod -Someone just posted some suggestions on your map, great! However, it doesn't simply end there. For the record, it's necessary to give a proper response for two major reasons. Firstly, so that future mods can be tailored more specifically to your concept or style, resulting in fewer unhelpful suggestions. Secondly, just as a mod post *helps you improve your mapping ability*, providing a detailed mod response helps the modder improve their modding ability, meaning they gain experience and can provide more helpful and detailed mods in the future. You never know who you may need to ask for a mod next time around! - -- Treat all suggestions as valid and equally important until you have thoroughly inspected and tested them — even minor stylistic changes or alternative viewpoints can help improve the quality of a beatmap -- As with making a mod post, be sure to explain yourself as much as possible. State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. -- When declining a suggestion, remain calm and professional, say what needs to be said in order to explain yourself and **leave it at that**. No matter how impolite, confusing or unhelpful the suggestion was, getting angry and responding with hostility, sarcasm, etc. will not help the situation. -- [Beatmap Nominators](/wiki/People/Beatmap_Nominators) (BN) and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) (NAT) members will review previous mods before placing any icons and may want to initiate or revisit discussions during their checks. Any assistance you can provide as to why you did or didn't do something takes very little effort, and could be a huge help to all parties later on. +It's necessary to give a proper response to a mod post. Not only will it make it easier for future mods to be tailored to your concept or style, but it will also help the modder improve their modding ability. -## Further exchange and discussion +In order for this exchange to be productive, it is important to consider the following: -Sometimes, a single mod and response isn't enough to bring all parties to agreement, or fully resolve an issue. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Alternatively, both parties might agree that although one option is better, it isn't the best option and could still be improved further with additional input. Continued feedback is the best way to improve a beatmap, so get people involved and talking to get as many different ideas, or see things from as many points of view as necessary. +- **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. +- **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. +- **Remain calm and professional.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. +- **Provide context.** By providing concise explanations on the mods you responded to, you make it easier for future modders, [Beatmap Nominators](/wiki/People/Beatmap_Nominators), and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) to revisit discussions during their checks. -- If you're unsure about something, ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. -- Still can't reach an agreement? Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team). Remember they are busy people, however! Should you realise there's a more suitable alternative to something you originally suggested, don't be afraid to put your pride aside - **sometimes being wrong can be far more valuable than being right**. -- **There is no such things as a "wrong" opinion** — it's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them, as you never know when it might be useful in the future. -- If you can't explain something through logic, you will not be able to explain it to them through violence either. Rather than continue a discussion that isn't progressing, walk away and try again with the next modder/mapper. -- When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. - -## Qualified beatmaps +## Further exchange and discussion -The [Qualified section](/wiki/Beatmap/Category#qualified) allows beatmaps to receive any final suggestions for change or improvement before reaching ranked status. When modding a qualified map, everything you consider "not minor" should **always** be mentioned — minor issues are also worth mentioning however, especially if they affect gameplay. If a qualified beatmap accumulates a significant number of minor issues, or if there is one or more major/unrankable issues, the beatmap should be disqualified so that fixes and improvements can be made before attempting requalification. +Sometimes, discussions will be drawn-out, and a single mod and response isn't enough to bring all parties to agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure. -If you're unsure on the nature of a potential problem, ask for other opinions or review previous mod posts to make sure the "issue" presented isn't something done intentionally by the mapper — if so, it will likely have been discussed already. If there has been no prior discussion, feel free to open one as if you were modding the map normally, and post a brief outline of your concerns. +Consider exploring the following solutions when an agreement cannot be reached: -**Note that it is the community's responsibility alone to report issues with qualified beatmaps**. It is not guaranteed that any BN or NAT member will actively check and disqualify beatmaps without being prompted to do so. +- **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. +- **Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. +- **Being wrong can be far more valuable than being right.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid to put your pride aside. +- **There are no wrong opinions** — it's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them, as you never know when it might be useful in the future. +- **Take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. +- **Report bad behaviour.** When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. From 15720c8412c858a202a7fd224d759b396b831074 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 24 Sep 2024 17:36:23 +0200 Subject: [PATCH 02/16] Outdated translations --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/es.md | 5 +++++ wiki/Rules/Code_of_conduct_for_modding_and_mapping/fr.md | 5 +++++ wiki/Rules/Code_of_conduct_for_modding_and_mapping/id.md | 5 +++++ wiki/Rules/Code_of_conduct_for_modding_and_mapping/ja.md | 5 +++++ wiki/Rules/Code_of_conduct_for_modding_and_mapping/ru.md | 5 +++++ 5 files changed, 25 insertions(+) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/es.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/es.md index d3ddf6844c6f..0a5140b946d2 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/es.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/es.md @@ -1,3 +1,8 @@ +--- +outdated_since: 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a +outdated_translation: true +--- + # Código de conducta para el modding y el mapping El **código de conducta para el modding y el mapping** es un conjunto de reglas y pautas que se aplican a todo el ecosistema del [modding](/wiki/Modding) y el [mapping](/wiki/Beatmapping) de osu! y a una extensión de las [reglas de la comunidad de osu!](/wiki/Rules) y los [criterios de clasificación generales](/wiki/Ranking_criteria). Para garantizar que las discusiones sobre el mapping y el modding en los hilos se lleven a cabo en un entorno constructivo, positivo y productivo, un código de conducta es crucial para que todos estén en sintonía. Al participar en el ecosistema del modding y el mapping, es obligatorio seguir este código de conducta. La mala conducta que viole estas reglas podría dar lugar a [sanciones impuestas a tu cuenta](/wiki/Silence). diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/fr.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/fr.md index bbc9e49a0832..373bcd3c52d3 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/fr.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/fr.md @@ -1,3 +1,8 @@ +--- +outdated_since: 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a +outdated_translation: true +--- + # Code de conduite pour le modding et le mapping Le **code de conduite pour le modding et le mapping** est un ensemble de règles et de lignes directrices qui s'appliquent à l'ensemble d'osu! concernant le [modding](/wiki/Modding) et le [mapping](/wiki/Beatmapping), et constitue une extension des [règles de la communauté d'osu!](/wiki/Rules). Afin de garantir que les discussions sur le mapping et le modding dans les discussions se déroulent dans un environnement constructif, positif et productif, un code de conduite est essentiel pour que tout le monde soit sur la même longueur d'onde. Lorsque vous participez au modding et au mapping, il est obligatoire de suivre ce code de conduite. Tout comportement contraire à ces règles peut entraîner des [sanctions sur votre compte](/wiki/Silence). diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/id.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/id.md index 32d46a3cbed7..bbe3b17fe74b 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/id.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/id.md @@ -1,3 +1,8 @@ +--- +outdated_since: 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a +outdated_translation: true +--- + # Kode etik dalam modding dan mapping **Kode Etik dalam Modding dan Mapping** adalah kumpulan dari beberapa aturan dan pedoman yang berlaku untuk seluruh aktivitas [modding](/wiki/Modding) dan [mapping](/wiki/Beatmapping) di dalam osu!, pedoman ini juga merupakan tambahan untuk [aturan komunitas osu!](/wiki/Rules) dan [Ranking Criteria](/wiki/Ranking_criteria). Kode etik memiliki peran penting untuk membuat semua orang tetap berada dalam topik pembahasan, memastikan diskusi modding dan mapping tetap berlangsung terkendali, konstruktif, positif dan produktif, kode etik perannya sangat penting untuk membuat semua orang tetap berada dalam topik pembahasan. Saat berpartisipasi dalam aktivitas modding dan mapping, kamu wajib mengikuti kode etik ini. [Sanksi akan dijatuhkan pada akunmu jika terbukti melakukan pelanggaran terhadap pedoman ini](/wiki/Silence). diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ja.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ja.md index 87c2c9189ea9..a9517a851484 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ja.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ja.md @@ -1,3 +1,8 @@ +--- +outdated_since: 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a +outdated_translation: true +--- + # ModdingとMappingにおける行動規範 **ModdingとMappingにおける行動規範**とは、osu!の[Mapping](/wiki/Beatmapping)と[Modding](/wiki/Modding)のエコシステム全体に適用されるルールとガイドラインからなる行動規範のことで、[コミュニティルール](/wiki/Rules)と[ランキング基準](/wiki/Ranking_criteria)の延長線上にあります。スレッドでのMappingとModdingの議論が、建設的かつ前向きで生産的な環境で行われるようにするため、全員が同じ規範を保つ必要があります。ModdingとMappingのエコシステムに参加する以上は、当規範に従わなければなりません。これらの規則を破ると[アカウントにペナルティが課される](/wiki/Silence)可能性があります。 diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ru.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ru.md index 99ecefa5cb19..e9a2170936c6 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ru.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/ru.md @@ -1,3 +1,8 @@ +--- +outdated_since: 3b36d38ae903933c6efab9e00637c7c3d3f6fe8a +outdated_translation: true +--- + # Кодекс поведения при моддинге и маппинге Данная статья — свод правил и рекомендаций, которые действуют в рамках всей экосистемы [маппинга](/wiki/Beatmapping) и [моддинга](/wiki/Modding) в osu!. Она является продолжением [правил сообщества](/wiki/Rules) и [общих критериев ранкинга](/wiki/Ranking_criteria). Приведённые ниже пункты необходимы для поддержания конструктивной, положительной и продуктивной атмосферы. Их необходимо соблюдать, а за их нарушение [могут наказать](/wiki/Silence). From 59c6013f65d273d358de7ad0952e1972070dc9f1 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 24 Sep 2024 20:28:19 +0200 Subject: [PATCH 03/16] Clayton review - I --- .../Code_of_conduct_for_modding_and_mapping/en.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index c6b8e84b5445..bba0925ad8d3 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -13,13 +13,9 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines ## Responding to a mod -It's necessary to give a proper response to a mod post. Not only will it make it easier for future mods to be tailored to your concept or style, but it will also help the modder improve their modding ability. - -In order for this exchange to be productive, it is important to consider the following: - - **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. -- **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. -- **Remain calm and professional.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. +- **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. +- **Remain calm.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. - **Provide context.** By providing concise explanations on the mods you responded to, you make it easier for future modders, [Beatmap Nominators](/wiki/People/Beatmap_Nominators), and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) to revisit discussions during their checks. ## Further exchange and discussion @@ -30,7 +26,7 @@ Consider exploring the following solutions when an agreement cannot be reached: - **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. - **Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. -- **Being wrong can be far more valuable than being right.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid to put your pride aside. +- **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid to put your pride aside. - **There are no wrong opinions** — it's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them, as you never know when it might be useful in the future. - **Take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. - **Report bad behaviour.** When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. From 60478a3a12b86ad5cdb3a20294311db73ef192d6 Mon Sep 17 00:00:00 2001 From: MChecaH <93517213+MChecaH@users.noreply.github.com> Date: Fri, 27 Sep 2024 10:40:08 +0200 Subject: [PATCH 04/16] Added usergroup abbreviations Co-authored-by: Antalf <101658120+osuAntalf@users.noreply.github.com> --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index bba0925ad8d3..4ac8bbad5cc1 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -16,7 +16,7 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines - **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. - **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. - **Remain calm.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. -- **Provide context.** By providing concise explanations on the mods you responded to, you make it easier for future modders, [Beatmap Nominators](/wiki/People/Beatmap_Nominators), and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) to revisit discussions during their checks. +- **Provide context.** By providing concise explanations on the mods you responded to, you make it easier for future modders, [Beatmap Nominators](/wiki/People/Beatmap_Nominators) (BN), and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) (NAT) to revisit discussions during their checks. ## Further exchange and discussion From bc2d2d8c6f5e557dfb1d724ed188f4afcf1cee02 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Fri, 27 Sep 2024 15:41:57 +0200 Subject: [PATCH 05/16] Added "New user approchability" bulletpoint --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index 4ac8bbad5cc1..19273377dab0 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -6,8 +6,7 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines - **The goal of modding is to help a mapper improve their work.** If you're not interested in helping people, steer clear of the discussion. - **Consider what you're posting, why you're posting it, and who you're posting it to.** This will ensure your best intentions are conveyed and your post is easy to understand. - - **Don't shy away from new mappers and modders** — these people are the ones who can benefit the most from your input! Be patient, understanding, and provide as much explanation as possible so that they can learn and improve more quickly - - **If you're new yourself, don't be afraid to say so!** This will allow more experienced community members to point you in the right direction. Everyone was new and in your position once! +- **Be approchable.** Discussions are open to all users. Everyone is welcome to participate, including those who are new to the community. Be patient, understanding, and provide as much explanation as necessary so that everyone can learn and improve more quickly. - **Treat others as you wish to be treated.** People are more receptive to kind, helpful suggestions than hostile ones. Stay on topic and keep away from personal attacks, hateful comments, and misplaced jokes to avoid derailing the thread. - **Use the [discussion page](/wiki/Beatmap_discussion).** Discuss your suggestions with other community members. Otherwise, it is unlikely your concerns will be heard by anyone with the power to address them appropriately. From 8b8be8cd25e152aab587921575b12ae35d778df8 Mon Sep 17 00:00:00 2001 From: MChecaH <93517213+MChecaH@users.noreply.github.com> Date: Fri, 27 Sep 2024 20:03:47 +0200 Subject: [PATCH 06/16] Modified intro to "Further exchange and discussion" --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index 19273377dab0..c3186cf08e0c 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -21,7 +21,7 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines Sometimes, discussions will be drawn-out, and a single mod and response isn't enough to bring all parties to agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure. -Consider exploring the following solutions when an agreement cannot be reached: +Consider the following guidelines when an agreement cannot be reached: - **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. - **Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. From 5f2658906e1008038d02064c52131daecc928c5e Mon Sep 17 00:00:00 2001 From: MChecaH Date: Fri, 27 Sep 2024 20:27:31 +0200 Subject: [PATCH 07/16] Changed verbal form on "Be open minded" point --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index c3186cf08e0c..a317b21fabc9 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -25,7 +25,7 @@ Consider the following guidelines when an agreement cannot be reached: - **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. - **Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. -- **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid to put your pride aside. +- **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid of putting your pride aside. - **There are no wrong opinions** — it's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them, as you never know when it might be useful in the future. - **Take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. - **Report bad behaviour.** When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. From 53eee0be91ce576f41a0eaba389ee300b836c7bc Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 1 Oct 2024 10:29:32 +0200 Subject: [PATCH 08/16] Added Maxus' suggestion --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index a317b21fabc9..e70ed10b25dc 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -19,7 +19,7 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines ## Further exchange and discussion -Sometimes, discussions will be drawn-out, and a single mod and response isn't enough to bring all parties to agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure. +Sometimes, discussions will be drawn-out, and a single mod and response isn't enough to bring all parties to agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure within a reasonable timeframe. Consider the following guidelines when an agreement cannot be reached: From 5cab4fef0c6c5b2cdd306d43656de7f169bfb912 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Sun, 6 Oct 2024 11:21:07 +0200 Subject: [PATCH 09/16] New, (hopefully) useful intro to responding to mods --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index e70ed10b25dc..dc822b754f84 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -12,6 +12,10 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines ## Responding to a mod +It is a mapper's responsibility to keep up with the latest discussions in their beatmaps. Ignoring suggestions or not responding to them in a timely manner can discourage other modders from participating in the discussion. + +When responding to someone's suggestions, it is important to consider the following: + - **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. - **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. - **Remain calm.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. From a16235830e4a608446c1fd7f8529bf2bc0a9cce8 Mon Sep 17 00:00:00 2001 From: MChecaH <93517213+MChecaH@users.noreply.github.com> Date: Tue, 8 Oct 2024 20:05:01 +0200 Subject: [PATCH 10/16] Clayton review 2 - Part 1 Co-authored-by: clayton --- .../Code_of_conduct_for_modding_and_mapping/en.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index dc822b754f84..45e7a20866f6 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -17,19 +17,19 @@ It is a mapper's responsibility to keep up with the latest discussions in their When responding to someone's suggestions, it is important to consider the following: - **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. -- **Explain yourself as much as possible.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. +- **Explain yourself clearly.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. - **Remain calm.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. -- **Provide context.** By providing concise explanations on the mods you responded to, you make it easier for future modders, [Beatmap Nominators](/wiki/People/Beatmap_Nominators) (BN), and [Nomination Assessment Team](/wiki/People/Nomination_Assessment_Team) (NAT) to revisit discussions during their checks. +- **Provide context.** By providing all relevant information in your responses to mods, you make it easier for future modders to understand the discussion. ## Further exchange and discussion -Sometimes, discussions will be drawn-out, and a single mod and response isn't enough to bring all parties to agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure within a reasonable timeframe. +Sometimes, discussions will be drawn out, and a single mod and response isn't enough to bring all parties to an agreement. Perhaps the mapper doesn't agree with a suggestion, and the modder isn't satisfied with their response. Ideally, all discussions should find closure within a reasonable timeframe. Consider the following guidelines when an agreement cannot be reached: - **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. -- **Ask someone with more experience, such as a member of [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. +- **Ask someone with more experience, such as a member of the [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. - **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid of putting your pride aside. -- **There are no wrong opinions** — it's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them, as you never know when it might be useful in the future. +- **There are no wrong opinions.** It's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them. - **Take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. - **Report bad behaviour.** When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. From 4eb071ad977f14d877825d1ec9c06c4ccf0878e0 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 8 Oct 2024 20:08:34 +0200 Subject: [PATCH 11/16] Clayton review 2 - Part 2 --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index 45e7a20866f6..c1cb8f617cb1 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -1,6 +1,6 @@ # Code of conduct for modding and mapping -The **code of conduct for modding and mapping** is a set of rules and guidelines that apply to the entirety of the osu! [modding](/wiki/Modding) and [mapping](/wiki/Beatmapping) ecosystem and an extension to the [osu! community rules](/wiki/Rules) and [general ranking criteria](/wiki/Ranking_criteria). In order to ensure that mapping and modding discussions in threads take place in a constructive, positive and productive environment, a code of conduct is crucial to get everyone on the same page. When participating in the modding and mapping ecosystem, it is mandatory to follow this code of conduct. Misconduct that violates these rules might lead to [penalties issued to your account](/wiki/Silence). +The **code of conduct for modding and mapping** is a set of rules and guidelines that apply to the entirety of the osu! [modding](/wiki/Modding) and [mapping](/wiki/Beatmapping) ecosystem and an extension to the [osu! community rules](/wiki/Rules). In order to ensure that mapping and modding discussions in threads take place in a constructive, positive and productive environment, a code of conduct is crucial to get everyone on the same page. When participating in the modding and mapping ecosystem, it is mandatory to follow this code of conduct. Misconduct that violates these rules might lead to [penalties issued to your account](/wiki/Silence). ## Behaviour and conduct @@ -29,7 +29,6 @@ Consider the following guidelines when an agreement cannot be reached: - **Ask if you're unsure about something.** Ask the person in question to explain what they meant. They should be more than willing to explain things to you in more detail. - **Ask someone with more experience, such as a member of the [BN](/wiki/People/Beatmap_Nominators) or [NAT](/wiki/People/Nomination_Assessment_Team).** While they are busy people, they should be able to help you reach an agreement. -- **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid of putting your pride aside. -- **There are no wrong opinions.** It's up to the mapper and modders to come to an agreement in a civil manner. Try to understand alternative points of view rather than attack them. -- **Take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. +- **Be open minded.** If you realise there's a more suitable alternative to something you originally suggested, don't be afraid of putting your pride aside. There are no wrong opinions, so try to understand alternative points of view rather than attack them. +- **If things are getting heated, take a break.** It is important to be at a right state of mind when discussing something. If you can't explain something through logic, you will not be able to explain it to them through violence either. - **Report bad behaviour.** When things look to be getting out of hand, or if the discussion is struggling to stay on topic, [call a moderator](/wiki/Reporting_bad_behaviour). Don't contribute to the problem by continuing to post. From 7a5819732edbf24aa4bc4716d9b96c26f25d3264 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 8 Oct 2024 20:10:39 +0200 Subject: [PATCH 12/16] Solves cyndifusic's open comment --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index c1cb8f617cb1..a428edda8c23 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -17,7 +17,7 @@ It is a mapper's responsibility to keep up with the latest discussions in their When responding to someone's suggestions, it is important to consider the following: - **Treat all suggestions as valid and equally important.** Don't draw hasty conclusions about the validity of a suggestion without properly assessing it. -- **Explain yourself clearly.** State what you changed, and if you didn't accept the suggestion for some reason, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. +- **Explain yourself clearly.** State what you changed, and if you disagree with a suggestion, explain why and what you did instead. This will not only help the modder to learn, but also allow future mods to be tailored to your concept or style. - **Remain calm.** Say what needs to be said in order to explain yourself and leave it at that. No matter how unhelpful the suggestion was, responding with hostility, sarcasm, etc. will not help the situation. - **Provide context.** By providing all relevant information in your responses to mods, you make it easier for future modders to understand the discussion. From f3e64d9310aced263507482347ce19c3941b6be4 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Tue, 8 Oct 2024 20:16:14 +0200 Subject: [PATCH 13/16] Potential fix to the latest open comment --- wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md index a428edda8c23..2e6c1e6c8279 100644 --- a/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md +++ b/wiki/Rules/Code_of_conduct_for_modding_and_mapping/en.md @@ -4,7 +4,7 @@ The **code of conduct for modding and mapping** is a set of rules and guidelines ## Behaviour and conduct -- **The goal of modding is to help a mapper improve their work.** If you're not interested in helping people, steer clear of the discussion. +- **The goal of modding is to help a mapper improve their work.** If you're not interested in helping people or fostering a healthy discourse, steer clear of the discussion. - **Consider what you're posting, why you're posting it, and who you're posting it to.** This will ensure your best intentions are conveyed and your post is easy to understand. - **Be approchable.** Discussions are open to all users. Everyone is welcome to participate, including those who are new to the community. Be patient, understanding, and provide as much explanation as necessary so that everyone can learn and improve more quickly. - **Treat others as you wish to be treated.** People are more receptive to kind, helpful suggestions than hostile ones. Stay on topic and keep away from personal attacks, hateful comments, and misplaced jokes to avoid derailing the thread. From 58cfc74dcd956a25bec4906427498b408e4b4646 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Wed, 9 Oct 2024 09:51:59 +0200 Subject: [PATCH 14/16] Links fix. Will be changed again in future PRs. --- wiki/Guides/Common_modding_mistakes/en.md | 2 +- wiki/Modding/Forum_modding/en.md | 2 +- wiki/Modding/en.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/wiki/Guides/Common_modding_mistakes/en.md b/wiki/Guides/Common_modding_mistakes/en.md index 7d11127dccaf..f788119a26ea 100644 --- a/wiki/Guides/Common_modding_mistakes/en.md +++ b/wiki/Guides/Common_modding_mistakes/en.md @@ -165,7 +165,7 @@ learn how to map first and then I can mod this properly this map would look great in the trash can ``` -**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) when modding for a better modding environment for everyone. +**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) when modding for a better modding environment for everyone. --- diff --git a/wiki/Modding/Forum_modding/en.md b/wiki/Modding/Forum_modding/en.md index 0e8c077048e2..80ee3bf64821 100644 --- a/wiki/Modding/Forum_modding/en.md +++ b/wiki/Modding/Forum_modding/en.md @@ -99,7 +99,7 @@ In the forum-based modding system, a lot of actions were manual, which often led The changes required to address most common issues were initiated on [April 26, 2013](https://osu.ppy.sh/community/forums/topics/129625), when [peppy](/wiki/People/peppy) presented the idea of the [new modding system](/wiki/Beatmap_discussion) (later known as *Modding v2*). On [August 21, 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), a new category, [Qualified](/wiki/Beatmap/Category#qualified), was added. Qualified would serve as a buffer between pending and ranked beatmaps and allow for more smooth unranks. In addition to that, a new team, [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*), was assembled to check qualified beatmaps and control the ranking process. -Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: +Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: - [April 11, 2016](https://osu.ppy.sh/community/forums/topics/442285): Beatmap discussions were enabled for two beatmaps and made available for public testing. - [February 1, 2017](https://osu.ppy.sh/community/forums/topics/552250): After several more months of development based on collected feedback, the next version of the discussion system was enabled for another, larger set of beatmaps. diff --git a/wiki/Modding/en.md b/wiki/Modding/en.md index 8e930e38ee8f..6a6096f71b0f 100644 --- a/wiki/Modding/en.md +++ b/wiki/Modding/en.md @@ -27,7 +27,7 @@ To mod a beatmap, start by downloading the most up-to-date version and opening i When you come across an issue, select any relevant hit objects, then use the copy shortcut (`Ctrl` + `C`) to copy their timestamp information as text. On the beatmap's discussion, paste (`Ctrl` + `V`) any applicable timestamps and your feedback. The `Timeline` tab is used for issues regarding specific parts of a beatmap, the `General (This difficulty)` tab is used for feedback on larger sections of a beatmap, and the `General (All difficulties)` tab is used for issues applicable to all difficulties of a beatmap. -All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) for more details on how to format mod posts. +All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) for more details on how to behave on mod posts. Beatmappers regularly provide [kudosu](/wiki/Modding/Kudosu) to mod posts that they consider helpful by clicking the *thumbs up* vote button. This statistic is tracked on an individual's profile and is referenced when applying to join the [Beatmap Nominators](/wiki/People/Beatmap_Nominators). From e64a0a653aef87559e030fb632eb950e0dd72758 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Wed, 9 Oct 2024 10:15:30 +0200 Subject: [PATCH 15/16] Revert previous commit. Will modify the wiki redirects instead. This reverts commit 58cfc74dcd956a25bec4906427498b408e4b4646. --- wiki/Guides/Common_modding_mistakes/en.md | 2 +- wiki/Modding/Forum_modding/en.md | 2 +- wiki/Modding/en.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/wiki/Guides/Common_modding_mistakes/en.md b/wiki/Guides/Common_modding_mistakes/en.md index f788119a26ea..7d11127dccaf 100644 --- a/wiki/Guides/Common_modding_mistakes/en.md +++ b/wiki/Guides/Common_modding_mistakes/en.md @@ -165,7 +165,7 @@ learn how to map first and then I can mod this properly this map would look great in the trash can ``` -**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) when modding for a better modding environment for everyone. +**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) when modding for a better modding environment for everyone. --- diff --git a/wiki/Modding/Forum_modding/en.md b/wiki/Modding/Forum_modding/en.md index 80ee3bf64821..0e8c077048e2 100644 --- a/wiki/Modding/Forum_modding/en.md +++ b/wiki/Modding/Forum_modding/en.md @@ -99,7 +99,7 @@ In the forum-based modding system, a lot of actions were manual, which often led The changes required to address most common issues were initiated on [April 26, 2013](https://osu.ppy.sh/community/forums/topics/129625), when [peppy](/wiki/People/peppy) presented the idea of the [new modding system](/wiki/Beatmap_discussion) (later known as *Modding v2*). On [August 21, 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), a new category, [Qualified](/wiki/Beatmap/Category#qualified), was added. Qualified would serve as a buffer between pending and ranked beatmaps and allow for more smooth unranks. In addition to that, a new team, [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*), was assembled to check qualified beatmaps and control the ranking process. -Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: +Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: - [April 11, 2016](https://osu.ppy.sh/community/forums/topics/442285): Beatmap discussions were enabled for two beatmaps and made available for public testing. - [February 1, 2017](https://osu.ppy.sh/community/forums/topics/552250): After several more months of development based on collected feedback, the next version of the discussion system was enabled for another, larger set of beatmaps. diff --git a/wiki/Modding/en.md b/wiki/Modding/en.md index 6a6096f71b0f..8e930e38ee8f 100644 --- a/wiki/Modding/en.md +++ b/wiki/Modding/en.md @@ -27,7 +27,7 @@ To mod a beatmap, start by downloading the most up-to-date version and opening i When you come across an issue, select any relevant hit objects, then use the copy shortcut (`Ctrl` + `C`) to copy their timestamp information as text. On the beatmap's discussion, paste (`Ctrl` + `V`) any applicable timestamps and your feedback. The `Timeline` tab is used for issues regarding specific parts of a beatmap, the `General (This difficulty)` tab is used for feedback on larger sections of a beatmap, and the `General (All difficulties)` tab is used for issues applicable to all difficulties of a beatmap. -All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) for more details on how to behave on mod posts. +All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) for more details on how to format mod posts. Beatmappers regularly provide [kudosu](/wiki/Modding/Kudosu) to mod posts that they consider helpful by clicking the *thumbs up* vote button. This statistic is tracked on an individual's profile and is referenced when applying to join the [Beatmap Nominators](/wiki/People/Beatmap_Nominators). From 5e86d52e1ceed8d9e8c5e799aecccd892066a5c7 Mon Sep 17 00:00:00 2001 From: MChecaH Date: Wed, 9 Oct 2024 10:23:28 +0200 Subject: [PATCH 16/16] Fixed redirects manually. Not worth adding in the YAML, will be changed. --- wiki/Guides/Common_modding_mistakes/en.md | 2 +- wiki/Guides/Common_modding_mistakes/es.md | 2 +- wiki/Guides/Common_modding_mistakes/fr.md | 2 +- wiki/Guides/Common_modding_mistakes/id.md | 2 +- wiki/Guides/Common_modding_mistakes/zh.md | 2 +- wiki/Modding/Forum_modding/en.md | 2 +- wiki/Modding/Forum_modding/es.md | 2 +- wiki/Modding/Forum_modding/fr.md | 2 +- wiki/Modding/Forum_modding/id.md | 2 +- wiki/Modding/en.md | 2 +- wiki/Modding/es.md | 2 +- wiki/Modding/fr.md | 2 +- wiki/Modding/id.md | 2 +- wiki/Modding/ja.md | 2 +- wiki/Modding/ru.md | 2 +- wiki/Modding/tr.md | 2 +- wiki/Modding/zh.md | 2 +- 17 files changed, 17 insertions(+), 17 deletions(-) diff --git a/wiki/Guides/Common_modding_mistakes/en.md b/wiki/Guides/Common_modding_mistakes/en.md index 7d11127dccaf..f788119a26ea 100644 --- a/wiki/Guides/Common_modding_mistakes/en.md +++ b/wiki/Guides/Common_modding_mistakes/en.md @@ -165,7 +165,7 @@ learn how to map first and then I can mod this properly this map would look great in the trash can ``` -**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) when modding for a better modding environment for everyone. +**Refrain from making rude or sarcastic remarks when modding.** This sort of behaviour is what would eventually get you [silenced](/wiki/Silence), and not something others would end up liking you for. Be sure to always follow the [Code of Conduct](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) when modding for a better modding environment for everyone. --- diff --git a/wiki/Guides/Common_modding_mistakes/es.md b/wiki/Guides/Common_modding_mistakes/es.md index 36ede67de3d0..e33e13dac627 100644 --- a/wiki/Guides/Common_modding_mistakes/es.md +++ b/wiki/Guides/Common_modding_mistakes/es.md @@ -165,7 +165,7 @@ aprende a mapear y entonces podré modearlo correctamente este mapa se vería increible en la basura ``` -**Evita ser grosero o sarcástico cuando modeas.** Esta conducta acabará dejándote [silenciado](/wiki/Silence), y no es algo que a otras personas les guste leer. Asegúrate de seguir el [código de conducta](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#cómo-hacer-una-publicación-de-un-mod) cuando modeas para mantener un ambiente de modding positivo para todos. +**Evita ser grosero o sarcástico cuando modeas.** Esta conducta acabará dejándote [silenciado](/wiki/Silence), y no es algo que a otras personas les guste leer. Asegúrate de seguir el [código de conducta](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) cuando modeas para mantener un ambiente de modding positivo para todos. --- diff --git a/wiki/Guides/Common_modding_mistakes/fr.md b/wiki/Guides/Common_modding_mistakes/fr.md index 828bcbd0ea6e..897a2c7562e4 100644 --- a/wiki/Guides/Common_modding_mistakes/fr.md +++ b/wiki/Guides/Common_modding_mistakes/fr.md @@ -169,7 +169,7 @@ Apprends d'abord à faire du mapping et ensuite je pourrai modder ça correcteme ce mapping serait parfait dans une poubelle ``` -**S'abstenir de faire des remarques grossières ou sarcastiques lors du modding.** C'est ce genre de comportement qui vous vaudra d'être [réduit au silence](/wiki/Silence), et ce n'est pas quelque chose que les autres finiront par apprécier. Assurez-vous de toujours suivre le [Code de conduite](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#créer-un-mod-post) lorsque vous moddez pour un meilleur environnement de modding pour tout le monde. +**S'abstenir de faire des remarques grossières ou sarcastiques lors du modding.** C'est ce genre de comportement qui vous vaudra d'être [réduit au silence](/wiki/Silence), et ce n'est pas quelque chose que les autres finiront par apprécier. Assurez-vous de toujours suivre le [Code de conduite](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) lorsque vous moddez pour un meilleur environnement de modding pour tout le monde. --- diff --git a/wiki/Guides/Common_modding_mistakes/id.md b/wiki/Guides/Common_modding_mistakes/id.md index 2f648b61339e..242367d36417 100644 --- a/wiki/Guides/Common_modding_mistakes/id.md +++ b/wiki/Guides/Common_modding_mistakes/id.md @@ -169,7 +169,7 @@ belajar dulu cara nge-map yang benar sana, baru nanti saya bisa mod map kamu den map ini akan terlihat bagus di kotak sampah ``` -**Jangan membuat pernyataan yang kasar atau sarkastik pada saat memberikan mod**. Tindakan seperti ini akan membuatmu ter-[*silence*](/wiki/Silence) dan tidak disukai oleh para pengguna lainnya. Pastikan untuk selalu mengikuti [kode etik yang berlaku](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#membuat-postingan-mod) pada saat memberikan mod demi menciptakan lingkungan modding yang lebih nyaman bagi semua. +**Jangan membuat pernyataan yang kasar atau sarkastik pada saat memberikan mod**. Tindakan seperti ini akan membuatmu ter-[*silence*](/wiki/Silence) dan tidak disukai oleh para pengguna lainnya. Pastikan untuk selalu mengikuti [kode etik yang berlaku](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) pada saat memberikan mod demi menciptakan lingkungan modding yang lebih nyaman bagi semua. --- diff --git a/wiki/Guides/Common_modding_mistakes/zh.md b/wiki/Guides/Common_modding_mistakes/zh.md index 892e789105e9..5d0562cdc151 100644 --- a/wiki/Guides/Common_modding_mistakes/zh.md +++ b/wiki/Guides/Common_modding_mistakes/zh.md @@ -165,7 +165,7 @@ 人太菜，白给都不要，倒贴都扶不起 ``` -**在摸图时，不要发表粗鲁、讽刺或攻击他人的言论。** 这样的行为甚至能导致你被禁言，而且并不会讨人喜欢。在摸图时一定要遵守[行为准则](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#摸图和留言)，给大家创造一个良好的摸图环境。 +**在摸图时，不要发表粗鲁、讽刺或攻击他人的言论。** 这样的行为甚至能导致你被禁言，而且并不会讨人喜欢。在摸图时一定要遵守[行为准则](/wiki/Rules/Code_of_conduct_for_modding_and_mapping)，给大家创造一个良好的摸图环境。 --- diff --git a/wiki/Modding/Forum_modding/en.md b/wiki/Modding/Forum_modding/en.md index 0e8c077048e2..80ee3bf64821 100644 --- a/wiki/Modding/Forum_modding/en.md +++ b/wiki/Modding/Forum_modding/en.md @@ -99,7 +99,7 @@ In the forum-based modding system, a lot of actions were manual, which often led The changes required to address most common issues were initiated on [April 26, 2013](https://osu.ppy.sh/community/forums/topics/129625), when [peppy](/wiki/People/peppy) presented the idea of the [new modding system](/wiki/Beatmap_discussion) (later known as *Modding v2*). On [August 21, 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), a new category, [Qualified](/wiki/Beatmap/Category#qualified), was added. Qualified would serve as a buffer between pending and ranked beatmaps and allow for more smooth unranks. In addition to that, a new team, [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*), was assembled to check qualified beatmaps and control the ranking process. -Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: +Afterwards, the beatmap discussion system and the [code of conduct for modding and mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) were developed and made available to restructure modding and make it a more enjoyable experience for everyone involved: - [April 11, 2016](https://osu.ppy.sh/community/forums/topics/442285): Beatmap discussions were enabled for two beatmaps and made available for public testing. - [February 1, 2017](https://osu.ppy.sh/community/forums/topics/552250): After several more months of development based on collected feedback, the next version of the discussion system was enabled for another, larger set of beatmaps. diff --git a/wiki/Modding/Forum_modding/es.md b/wiki/Modding/Forum_modding/es.md index bbd59017d5e7..0c2244186104 100644 --- a/wiki/Modding/Forum_modding/es.md +++ b/wiki/Modding/Forum_modding/es.md @@ -101,7 +101,7 @@ En el sistema de modding basado en los foros, muchas acciones eran manuales, lo Los cambios necesarios para abordar los problemas más comunes se iniciaron el [26 de abril de 2013](https://osu.ppy.sh/community/forums/topics/129625), cuando [peppy](/wiki/People/peppy) presentó la idea del [nuevo sistema de modding](/wiki/Beatmap_discussion) (más tarde conocido como *Modding v2*). El [21 de agosto de 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), se añadió una nueva categoría, [calificados](/wiki/Beatmap/Category#qualified). La categoría calificados serviría de puente entre los beatmaps pendientes y los clasificados y permitiría unas desclasificaciones más fluidas. Además de eso, se formó un nuevo equipo, el [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*), para verificar los beatmaps calificados y controlar el proceso de clasificación. -Posteriormente, se desarrollaron el sistema de las discusiones de beatmaps y el [código de conducta para el modding y el mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#cómo-hacer-una-publicación-de-un-mod), que se pusieron a disposición de los usuarios para reestructurar el modding y convertirlo en una experiencia más agradable para todos los implicados: +Posteriormente, se desarrollaron el sistema de las discusiones de beatmaps y el [código de conducta para el modding y el mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping), que se pusieron a disposición de los usuarios para reestructurar el modding y convertirlo en una experiencia más agradable para todos los implicados: - [11 de abril de 2016](https://osu.ppy.sh/community/forums/topics/442285): Se activaron las discusiones de beatmaps para dos beatmaps y se pusieron a disposición para pruebas públicas. - [1 de febrero de 2017](https://osu.ppy.sh/community/forums/topics/552250): Después de varios meses más de desarrollo basado en los comentarios recopilados, se activó la siguiente versión del sistema de discusiones para otro conjunto mayor de beatmaps. diff --git a/wiki/Modding/Forum_modding/fr.md b/wiki/Modding/Forum_modding/fr.md index d71db3e1c20f..f8b98ac29ecf 100644 --- a/wiki/Modding/Forum_modding/fr.md +++ b/wiki/Modding/Forum_modding/fr.md @@ -101,7 +101,7 @@ Dans le système de modding basé sur le forum, de nombreuses actions étaient m Les modifications nécessaires pour résoudre les problèmes les plus courants ont été initiées le [26 avril 2013](https://osu.ppy.sh/community/forums/topics/129625), lorsque [peppy](/wiki/People/peppy) a présenté l'idée du [nouveau système de modding](/wiki/Beatmap_discussion) (connu ensuite sous le nom de *Modding v2*). Le [21 août 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), une nouvelle catégorie, [qualifiée](/wiki/Beatmap/Category#qualified), a été ajoutée. La catégorie servirait de tampon entre les beatmaps en attente et les beatmaps classés et permettrait des déranks plus fluides. De plus, une nouvelle équipe, la [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*), a été créée pour vérifier les beatmaps qualifiés et contrôler le processus de classement. -Ensuite, le système de discussion des beatmap et le [code de conduite pour le modding et le mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#créer-un-mod-post) ont été développés et mis à disposition pour restructurer le modding et en faire une expérience plus agréable pour toutes les personnes impliquées : +Ensuite, le système de discussion des beatmap et le [code de conduite pour le modding et le mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) ont été développés et mis à disposition pour restructurer le modding et en faire une expérience plus agréable pour toutes les personnes impliquées : - [11 avril 2016](https://osu.ppy.sh/community/forums/topics/442285) : Les discussions sur les beatmaps ont été activées pour deux beatmaps et mises à disposition pour les tests publics. - [1er février 2017](https://osu.ppy.sh/community/forums/topics/552250) : Après plusieurs mois supplémentaires de développement sur la base des commentaires recueillis, la version suivante du système de discussion a été activée pour un autre ensemble plus important de beatmaps. diff --git a/wiki/Modding/Forum_modding/id.md b/wiki/Modding/Forum_modding/id.md index 7acb910ada47..c3a453421474 100644 --- a/wiki/Modding/Forum_modding/id.md +++ b/wiki/Modding/Forum_modding/id.md @@ -101,7 +101,7 @@ Dalam praktiknya, sistem modding berbasis forum cenderung rawan terhadap berbaga Perubahan-perubahan dibutuhkan untuk menyelesaikan masalah-masalah umum dimulai pada [26 April 2013](https://osu.ppy.sh/community/forums/topics/129625), saat [peppy](/wiki/People/peppy) mempresentasikan ide mengenai [sistem modding baru](/wiki/Beatmap_discussion) (yang nanti dikenal sebagai *Modding v2*). Pada [21 Agustus 2014](https://osu.ppy.sh/home/news/2014-08-21-restructuring-of-the-bat), kategori beatmap [Qualified](/wiki/Beatmap/Category#qualified) ditambahkan. Qualified menjadi penyangga antara beatmap pending dan ranked untuk membuat proses unrank menjadi lebih halus. Sebagai tambahan, tim [Quality Assurance Team](/wiki/People/Quality_Assurance_Team) (*QAT*) dibentuk untuk mengecek beatmap yang qualified dan mengontrol proses ranking. -Setelah itu, sistem diskusi beatmap dan [kode etik dalam modding dan mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#membuat-postingan-mod) dikembangkan dan dirilis untuk merestrukturisasi modding dan menjadikan modding lebih menyenangkan untuk semua yang terlibat: +Setelah itu, sistem diskusi beatmap dan [kode etik dalam modding dan mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) dikembangkan dan dirilis untuk merestrukturisasi modding dan menjadikan modding lebih menyenangkan untuk semua yang terlibat: - [11 April 2016](https://osu.ppy.sh/community/forums/topics/442285): Diskusi beatmap diaktifkan untuk dua beatmap dan tersedia untuk dites oleh publik. - [1 Februari 2017](https://osu.ppy.sh/community/forums/topics/552250): Setelah beberapa pengembangan berdasarkan umpan balik yang diterima, versi lanjutan sistem diskusi beatmap tersedia untuk publik dan lebih banyak beatmap. diff --git a/wiki/Modding/en.md b/wiki/Modding/en.md index 8e930e38ee8f..ff5893ecba5c 100644 --- a/wiki/Modding/en.md +++ b/wiki/Modding/en.md @@ -27,7 +27,7 @@ To mod a beatmap, start by downloading the most up-to-date version and opening i When you come across an issue, select any relevant hit objects, then use the copy shortcut (`Ctrl` + `C`) to copy their timestamp information as text. On the beatmap's discussion, paste (`Ctrl` + `V`) any applicable timestamps and your feedback. The `Timeline` tab is used for issues regarding specific parts of a beatmap, the `General (This difficulty)` tab is used for feedback on larger sections of a beatmap, and the `General (All difficulties)` tab is used for issues applicable to all difficulties of a beatmap. -All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) for more details on how to format mod posts. +All mod posts should address what the issue is, why it is an issue, and how to fix it. See the [Code of Conduct for Modding and Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) for more details on how to format mod posts. Beatmappers regularly provide [kudosu](/wiki/Modding/Kudosu) to mod posts that they consider helpful by clicking the *thumbs up* vote button. This statistic is tracked on an individual's profile and is referenced when applying to join the [Beatmap Nominators](/wiki/People/Beatmap_Nominators). diff --git a/wiki/Modding/es.md b/wiki/Modding/es.md index 85c8a0db9e85..91ffdbbc0736 100644 --- a/wiki/Modding/es.md +++ b/wiki/Modding/es.md @@ -27,7 +27,7 @@ Para modear un beatmap, empieza descargando la versión más reciente y abriendo Cuando te encuentres con un problema, selecciona todos los objetos relevantes, luego usa el atajo de copiar (`Ctrl` + `C`) para copiar la información de la línea de tiempo como texto. En la discusión del beatmap, pega (`Ctrl` + `V`) la información de la línea de tiempo y tus comentarios. La pestaña `Línea de tiempo` se usa para problemas relacionados con partes específicas de un beatmap, la pestaña `General (nombre de la dificultad)` se usa para comentarios sobre secciones más grandes de un beatmap, y la pestaña `General (Todas las dificultades)` se usa para problemas aplicables a todas las dificultades de un beatmap. -Todos las publicaciones de mods deben indicar cuál es el problema, por qué es un problema y cómo solucionarlo. Consulta el [código de conducta para el modding y el mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#cómo-hacer-una-publicación-de-un-mod) para obtener más información sobre el formato de las publicaciones de mods. +Todos las publicaciones de mods deben indicar cuál es el problema, por qué es un problema y cómo solucionarlo. Consulta el [código de conducta para el modding y el mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) para obtener más información sobre el formato de las publicaciones de mods. Los mappers suelen dar [kudosu](/wiki/Modding/Kudosu) a los mods que consideren útiles haciendo clic en el icono de *pulgar hacia arriba*. Esta estadística se rastrea en el perfil del usuario y se usa como referencia al solicitar el ingreso a los [Beatmap Nominators](/wiki/People/Beatmap_Nominators). diff --git a/wiki/Modding/fr.md b/wiki/Modding/fr.md index e533d67e8855..97c695e8e00f 100644 --- a/wiki/Modding/fr.md +++ b/wiki/Modding/fr.md @@ -27,7 +27,7 @@ Pour modder une beatmap, commencez par télécharger la version la plus récente Lorsque vous rencontrez un problème, sélectionnez tous les objets pertinents, puis utilisez le raccourci de copie (`Ctrl` + `C`) pour copier leurs informations d'horodatage en tant que texte. Sur la discussion d'une beatmap, collez (`Ctrl` + `V`) les horodatages applicables et vos commentaires. L'onglet `Chronologie` est utilisé pour les problèmes concernant des parties spécifiques d'une beatmap, l'onglet `Général (cette difficulté)` est utilisé pour les commentaires sur de plus grandes sections d'une beatmap, et l'onglet `Général (Toutes les difficultés)` est utilisé pour les problèmes applicables à toutes les difficultés d'une beatmap. -Tous les messages de mods doivent traiter de la nature du problème, de sa raison d'être et de la manière de le résoudre. Voir le [Code de conduite pour le modding et le mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#créer-un-mod-post) pour plus de détails sur la mise en forme des messages de mod. +Tous les messages de mods doivent traiter de la nature du problème, de sa raison d'être et de la manière de le résoudre. Voir le [Code de conduite pour le modding et le mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) pour plus de détails sur la mise en forme des messages de mod. Les mappeurs fournissent régulièrement des [kudosu](/wiki/Modding/Kudosu) aux messages des moddeurs qu'ils considèrent comme utiles en cliquant sur le bouton de vote "like". Cette statistique est enregistrée sur le profil de l'utilisateur et est référencée lors de la demande d'adhésion aux [Beatmap Nominators](/wiki/People/Beatmap_Nominators). diff --git a/wiki/Modding/id.md b/wiki/Modding/id.md index fdb476723f4f..cb9bfd8900c5 100644 --- a/wiki/Modding/id.md +++ b/wiki/Modding/id.md @@ -27,7 +27,7 @@ Untuk melakukan mod pada sebuah beatmap, mulailah dengan mengunduh versi terbaru Saat kamu menemukan masalah, pilih objek hit tersebut, lalu gunakan pintasan salin (`Ctrl` + `C`) untuk menyalin informasi dari timestamp sebagai teks. Pada diskusi beatmap, tempel (`Ctrl` + `V`) timestamp sekaligus umpan balik dari kamu. Tab `Timeline` digunakan untuk masalah yang berkaitan dengan bagian tertentu dari sebuah beatmap, tab `Umum (Tingkat kesulitan ini)` digunakan untuk umpan balik pada bagian yang lebih besar dari sebuah beatmap, dan tab `Umum (Semua tingkat kesulitan)` digunakan untuk masalah yang berlaku untuk semua tingkat kesulitan pada sebuah beatmap. -Semua postingan mod harus membahas apa saja masalahnya, mengapa itu menjadi masalah, dan bagaimana cara memperbaikinya. Lihat [Kode Etik dalam Modding dan Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#membuat-postingan-mod) untuk detail lebih lanjut tentang cara membuat format postingan mod. +Semua postingan mod harus membahas apa saja masalahnya, mengapa itu menjadi masalah, dan bagaimana cara memperbaikinya. Lihat [Kode Etik dalam Modding dan Mapping](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) untuk detail lebih lanjut tentang cara membuat format postingan mod. Beatmapper biasanya memberikan [kudosu](/wiki/Modding/Kudosu) ke postingan mod yang mereka anggap berguna dengan mengeklik tombol *jempol*. Statistik ini dapat dilacak pada profil setiap pengguna dan menjadi rujukan saat melamar untuk bergabung dengan [Beatmap Nominator](/wiki/People/Beatmap_Nominators). diff --git a/wiki/Modding/ja.md b/wiki/Modding/ja.md index 58521da96882..33ecece63c22 100644 --- a/wiki/Modding/ja.md +++ b/wiki/Modding/ja.md @@ -31,7 +31,7 @@ Modするには、まず該当ビートマップを最新のバージョンに 不自然な箇所を見つけたら、そのオブジェクトを選択し、コピー(Ctrl + C)して投稿画面(もしくはメモ帳など)に貼り付け(Ctrl + V)ます。そして、なぜ不自然に思ったのかの理由を一緒に書いてください。`タイムライン`タブはビートマップの特定の部分に関する問題、`一般(難易度名)`タブは特定の難易度に関する問題、`一般(すべての難易度)`タブはすべての難易度に一貫した問題がある場合に使われます。 -指摘する場合は、どこが不自然なのか、なぜそれが不自然に思ったのか、どのように修正すればより良くなるのかを言う必要があります。詳しくは、[ModdingとMappingにおける行動規範](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#mod投稿)を参照してください。 +指摘する場合は、どこが不自然なのか、なぜそれが不自然に思ったのか、どのように修正すればより良くなるのかを言う必要があります。詳しくは、[ModdingとMappingにおける行動規範](/wiki/Rules/Code_of_conduct_for_modding_and_mapping)を参照してください。 mapperは定期的に、役に立ったMod投稿に賛成票を入れることで、[kudosu](/wiki/Modding/Kudosu)を与えることができます。kudosuは、[ビートマップノミネーター](/wiki/People/Beatmap_Nominators)(BN)への参加を申請する際に使用されます。 diff --git a/wiki/Modding/ru.md b/wiki/Modding/ru.md index 84c97f543c43..29a3ef60c095 100644 --- a/wiki/Modding/ru.md +++ b/wiki/Modding/ru.md @@ -27,7 +27,7 @@ Если вы обнаружили проблему, выделите в редакторе относящиеся к ней объекты, а затем скопируйте их таймкод, нажав `Ctrl` + `C`. Вставьте этот таймкод на странице обсуждения карты в одну из вкладок, нажав `Ctrl` + `V`, и напишите после него свои мысли и идеи. Если замечание связано с конкретными частями сложности, оставьте его на вкладке `Timeline`, если с обширными участками или всей сложностью в целом — на вкладке `General (This difficulty)`, а для вещей, применимых ко всем сложностям в карте, используйте вкладку `General (All difficulties)`. -Все моды должны явно указывать, что именно является недостатком, почему это — недостаток, и как его исправить. Более подробно о том, как оформлять мод-посты, написано в статье «[Нормы поведения в моддинге и маппинге](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#написание-модов)». +Все моды должны явно указывать, что именно является недостатком, почему это — недостаток, и как его исправить. Более подробно о том, как оформлять мод-посты, написано в статье «[Нормы поведения в моддинге и маппинге](/wiki/Rules/Code_of_conduct_for_modding_and_mapping)». Если маппер посчитал мод полезным, он может выдать его автору [кудосу](/wiki/Modding/Kudosu), нажав на *большой палец вверх* справа от поста. Число полезных модов показано в профиле каждого игрока на вкладке `modding`; оно учитывается в случае подачи заявки в группу [номинаторов](/wiki/People/Beatmap_Nominators). diff --git a/wiki/Modding/tr.md b/wiki/Modding/tr.md index 6955afce07b1..71256c093d2e 100644 --- a/wiki/Modding/tr.md +++ b/wiki/Modding/tr.md @@ -27,7 +27,7 @@ Bir beatmap setini modlamak için, en güncel sürümü indirerek ve onun [tart Bir sorun ile karşı karşıya geldiğinizde, ilgili vuruş objelerini seçin, ardından zaman damgası bilgisini metin olarak kopyalamak için kopyalama kısayolunu (`Ctrl` + `C`) kullanın. Beatmapin tartışma kısmında, mevcut zaman damgalarını yapıştırın (`Ctrl` + `V`) ve geri bildirimlerinizi ekleyin. `Zaman Çizgisi` sekmesi beatmapin spesifik kısımlarını ile ilgili sorunlar için kullanılır, `Genel (Bu zorluk)` sekmesi beatmapin daha geniş kısımlarına geri bildirim bırakmak için kullanılır, ve `Genel (Tüm zorluklar)` ise beatmap setinin tüm zorluklarını ilgilendiren sorunlar için kullanılır. -Tüm mod gönderileri sorunun ne olduğunu, bunun neden bir sorun yarattığını, ve nasıl çözülmesi gerektiğini ele almalıdır. Mod gönderilerinin nasıl düzenlendiği hakkında daha fazla detay için [Modlama ve Mapleme Etik Çalışma Kurallarına](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#making-a-mod-post) bakınız. +Tüm mod gönderileri sorunun ne olduğunu, bunun neden bir sorun yarattığını, ve nasıl çözülmesi gerektiğini ele almalıdır. Mod gönderilerinin nasıl düzenlendiği hakkında daha fazla detay için [Modlama ve Mapleme Etik Çalışma Kurallarına](/wiki/Rules/Code_of_conduct_for_modding_and_mapping) bakınız. Beatmapperlar yardımcı olduğunu düşündükleri mod gönderilerine *yukarı baş parmak* oy butonuna tıklayarak sık sık [kudosu](/wiki/Modding/Kudosu) sağlarlar. Bu istatistik her bir bireyin profilinde tutulur ve [Beatmap Aday Göstericilere](/wiki/People/Beatmap_Nominators) katılmak için başvururken referans alınır. diff --git a/wiki/Modding/zh.md b/wiki/Modding/zh.md index 4faa08a55968..2b4869da2464 100644 --- a/wiki/Modding/zh.md +++ b/wiki/Modding/zh.md @@ -27,7 +27,7 @@ 当你发现了谱面内存在的问题，选择问题所在的这些物件，按下复制快捷键（`Ctrl` + `C`），游戏能自动获得它们所在的时间戳并保存在剪贴板内。转至谱面讨论页，粘贴（`Ctrl` + `V`）这些时间戳并填写反馈建议即可。讨论页的`时间轴`标签页用于粘贴与难度内某一特定部分有关的问题，`常规（此难度）`标签页用于粘贴与此难度整体相关的问题，`常规（所有难度）`标签页用于粘贴整张谱面内可能存在的问题。 -所有的摸图贴都应指出问题是什么，为什么它会成为问题，以及问题的解决方法。参见：[行为准则：摸图与作图](/wiki/Rules/Code_of_conduct_for_modding_and_mapping#摸图和留言)。 +所有的摸图贴都应指出问题是什么，为什么它会成为问题，以及问题的解决方法。参见：[行为准则：摸图与作图](/wiki/Rules/Code_of_conduct_for_modding_and_mapping)。 发出请求的谱师通常需要给已参考并应用至谱面的摸图帖*点赞*，此时，摸图员就能得到 [kudosu](/wiki/Modding/Kudosu)。kudosu 会在主页统计数量、追踪来源，并作为申请加入[谱面审核员 (BN)](/wiki/People/Beatmap_Nominators) 的一个重要参考指标。