wiki/Beatmap_discussion/en.md ADDED
@@ -0,0 +1,166 @@
1
+ ---
2
+ tags:
3
+ - beatmap discussions
4
+ - modding V2
5
+ - MV2
6
+ ---
7
+
8
+ <!-- TODO: the interface has changed quite a bit. this whole article should be rechecked to make sure it all makes sense still -->
9
+
10
+ # Beatmap discussion
11
+
12
+ *See also: [Modding v1](/wiki/Modding/Forum_modding)*
13
+
14
+ **Beatmap discussion** (also known as *Modding v2*) is a system to manage and simplify the process of [modding](/wiki/Modding). It aims to provide a clear and understandable interface, where the improvement of a beatmap is in focus. When a beatmap is [submitted](/wiki/Submission), a discussion page is automatically created alongside the beatmap info page. When the beatmap is updated, the discussion page will be updated as well. The discussion page can be reached by clicking on the `Discussion` button on the info page. The beatmap discussion page consists of a few elements (from top-to-bottom):
15
+
16
+ - Mode selection
17
+ - Beatmap header
18
+ - Difficulty menu
19
+ - Sorting options
20
+ - Visual timeline
21
+ - Beatmap status
22
+ - Modding tabs
23
+ - Submission field
24
+ - Discussions
25
+
26
+ You can follow along with our images from [this beatmap](https://osu.ppy.sh/beatmapsets/924551/discussion) to get familiar with beatmap discussions or try opening a discussion page yourself!
27
+
28
+ ## Quick-start
29
+
30
+ It is important to keep a few things in mind to use beatmap discussion pages effectively:
31
+
32
+ - Choose the correct mode and difficulty you wish to mod.
33
+ - Select the proper section you are submitting your mod to.
34
+ - **Only post one issue at a time.** Do not submit multiple issues in a single post.
35
+ - Check to see if the issue has already been addressed when the similar post warning pops up.
36
+ - If you like the beatmap, consider hyping it to push it closer to nomination.
37
+
38
+ ## Mode selection
39
+
40
+ ![](img/mode-selection.png "Mode selection")
41
+
42
+ Mode selection changes the [game mode](/wiki/Game_mode) you are modding. It is only possible to select a game mode if the beatmap has a difficulty of that game mode. This is only used with beatmaps that contain multiple game modes; otherwise, it will default to the mapped game mode.
43
+
44
+ ## Beatmap header
45
+
46
+ *For information about setting metadata, see: [Song Setup ยง Song and Map Metadata](/wiki/Client/Beatmap_editor/Song_Setup#song-and-map-metadata)*
47
+
48
+ ![](img/beatmap-header.png "Beatmap header")
49
+
50
+ The beatmap header displays the title and artist provided in the [beatmap editor](/wiki/Client/Beatmap_editor). Clicking the beatmap header will navigate back to the info page.
51
+
52
+ ## Difficulty menu
53
+
54
+ ![](img/difficulty-menu.png "Difficulty menu")
55
+
56
+ You can select different [difficulties](/wiki/Beatmap/Difficulty) through the dropdown menu. This will show all currently available difficulties, along with older, deleted ones that have had suggestions/problems. The number that appears besides a difficulty's name is the number of unresolved posts on that specific difficulty. It is important to double-check this menu before submitting any mods.
57
+
58
+ ## Sorting options
59
+
60
+ ![](img/sorting-options.jpg "For your sorting needs")
61
+
62
+ Sorting options change the way beatmap discussions are viewed. When an option is chosen, it changes both the modding timeline and the modding section to only include the selected type of post. This is especially useful for seeing pending posts on a discussion page. Different options include:
63
+
64
+ - `Mine` shows your own posts
65
+ - `Notes` shows any notes by the mapper or [Beatmap Nominators](/wiki/People/The_Team/Beatmap_Nominators)
66
+ - `Resolved` shows resolved posts
67
+ - `Pending` shows pending posts
68
+ - `Praises` shows praise and hype posts
69
+ - `All` shows all posts
70
+
71
+ ## Visual timeline
72
+
73
+ ![](img/visual-timeline.jpg "Mod posts spread out on the timeline")
74
+
75
+ The visual timeline displays all of the mods made for a difficulty which use a timestamp. Clicking on any of these will scroll down to the mod posted at that timestamp. Note that any filtering options will change what is displayed here. The visual timeline is a useful tool for seeing how much a beatmap has been modded at a glance. A tightly packed timeline would mean that a beatmap has received a lot of attention already. The selected difficulty's settings are also displayed on the top-right of the visual timeline. From left-to-right these describe a difficulty's `Length`, `BPM`, `Circle Count` and `Slider Count`.
76
+
77
+ ## Beatmap status
78
+
79
+ ![](img/beatmap-status.jpg "Contains important information!")
80
+
81
+ The beatmap status bar shows everything relevant to a beatmap's spot in the [Beatmap Ranking Procedure](/wiki/Beatmap_ranking_procedure). This includes:
82
+
83
+ - Hype train
84
+ - General info
85
+ - Watch/Unwatch buttons
86
+ - Beatmap Page button
87
+
88
+ ### Hype train
89
+
90
+ The hype train tracks how many [hypes](/wiki/Beatmap/Hype) a mapset has received. Once 5 hypes have been achieved, the beatmap can be nominated by [Beatmap Nominators](/wiki/People/The_Team/Beatmap_Nominators). Hypes can only be given by going to the `General (All Difficulties)` tab, as it will not work through the `General` or the `Timeline` tabs. Clicking the `Hype` button will automatically move you to the correct tab.
91
+
92
+ ### Nomination status
93
+
94
+ The nomination status bar tracks a beatmap's nominations. Once a beatmap has received two nominations it will be [qualified](/wiki/Beatmap/Category#qualified)
95
+
96
+ ### General info
97
+
98
+ General info shows the creator of the beatmap, the submission date and the date it was last updated. [Status changes](/wiki/Beatmap), such as a beatmap getting Ranked, Loved or Graveyarded, are also considered updates and will be displayed here.
99
+
100
+ ### Watch/Unwatch
101
+
102
+ The `Watch` and `Unwatch` buttons allow for following/unfollowing the developments of a beatmap. If a beatmap is followed, new posts and replies on that beatmap's discussion page will create notifications on osu!web. Subscriptions can be managed through the [modding watchlist](https://osu.ppy.sh/beatmapsets/watches), which can be found through the home page menu.
103
+
104
+ ### Beatmap page
105
+
106
+ The `Beatmap Page` button will navigate to a beatmap's info page. This can also be done by clicking on the [beatmap header](#beatmap-header).
107
+
108
+ ## Modding tabs
109
+
110
+ ![](img/modding-tabs.jpg "Modding tabs.")
111
+
112
+ Modding happens through three tabs, which separate posts of different types and split them up into readable formats. Additionally, a fourth tab logs all changes. The number beside each tab describes the amount of posts in it.
113
+
114
+ `General (All difficulties)` shows posts that apply to all difficulties. Common posts in this tab include metadata, notes and discussion on the beatmap as a whole.
115
+
116
+ `General (This difficulty)` shows posts that only apply to the currently selected difficulty. Common posts in this tab include beatmap settings, recurring issues and general discussion on the selected difficulty.
117
+
118
+ `Timeline` shows posts at specific points of a difficulty according to the first timestamp placed. Every post in this tab must include a timestamp to be posted. Any timestamps later on will have no influence on post order.
119
+
120
+ `History` logs all changes to a discussion page in chronological order. Changes are colour-coded with green being resolved posts and status changes, red being new problems after nomination, and blue being everything else. Clicking on any reference number will jump to the specific post. This tab is not used while modding, but is useful for [Beatmap Nominators](/wiki/People/The_Team/Beatmap_Nominators) and other staff to check issues.
121
+
122
+ ## Submission field
123
+
124
+ ![](img/submission-field.jpg "Where mods are written.")
125
+
126
+ The submission field is where [mods](/wiki/Modding) are written. Once written, the mod must be submitted to the discussion page. This can be done by pressing one of the three type buttons; `Praise`, `Suggestion` or `Problem`.
127
+
128
+ `Praise` is used for praise and encouragement. `Suggestion` is used for posts which aren't directly in conflict with any rules. `Problem` is used for posts which are in direct conflict with the [Ranking Criteria](/wiki/Ranking_Criteria), or which are considered intersubjectively wrong. Once a button is pressed the mod will be submitted to the discussion page.
129
+
130
+ If you post in the `Timeline` tab, you must include a timestamp in your post. If your timestamp is close to another mod, you will have to confirm that it doesn't address the issue you are currently submitting. **Check each post before checking the box!** It might be beneficial to `Pin` the modding field while checking other issues. Enabling the pin will allow the submission field to scroll with you.
131
+
132
+ ## Discussions
133
+
134
+ ![](img/discussions.jpg "Where the discussion takes place!")
135
+
136
+ Discussions are where posts from the [submission field](#submission-field) are placed once submitted. Users visiting a discussion page can see posts made by all other users, and will be able to participate in discussion on posts. This is done by clicking the `Respond` or `Reply` buttons below a post and writing a response. After finishing a response, pressing `Enter` or clicking `Reply` will submit it to the discussion.
137
+
138
+ The beatmap creator and authors of modposts have the ability to close issues with the `Mark as Resolved` button. This marks the issue has having been dealt with to other users and removes it from the `Pending` [sorting option](#sorting-options). Modposts can be reopened by any user by adding further replies to a post and clicking `Reply and Reopen`. This is used when modders stumble upon closed issues which have not been fixed fully, or a topic needs further discussion.
139
+
140
+ ### Discussions sorting
141
+
142
+ Discussions can be sorted through with the buttons below the `Discussions` title. Initially, `Timeline` tab posts will be sorted chronologically based on the first timestamp provided. `General (All difficulties)` and `General (This difficulty)` posts will be sorted by last update. Note that any selected [sorting options](#sorting-options) will change what is displayed here as well. Other buttons at the top of the discussion field which change how discussions are viewed include `Collapse all` and `Expand all` which will show/hide posts respectively.
143
+
144
+ ### Thumbs up/down
145
+
146
+ If a modpost was helpful [Kudosu!](/wiki/Modding/Kudosu) can be given. This can be done by anyone except the post creator by giving the post a thumbs up. This is useful for modders as Kudosu! is needed for entry into the [Beatmap Nominators](/wiki/People/The_Team/Beatmap_Nominators). If this feature is abused, [BN](/wiki/People/The_Team/Beatmap_Nominators), [NAT](/wiki/People/The_Team/Nomination_Assessment_Team), and [GMT](/wiki/People/The_Team/Global_Moderation_Team) members can give a thumbs down to deny any Kudosu! given. If the abuse is done maliciously a penalty can also be given to abusers.
147
+
148
+ ### Discussion timeline
149
+
150
+ The timeline to the left of a discussion shows the timestamp the post addresses. This is only available in the `Timeline` section. Otherwise the discussion timeline will be left blank.
151
+
152
+ ### Tags
153
+
154
+ Tags display [important roles](/wiki/People/The_Team) below a users name. Only roles relevant for the beatmap discussion are shown. These include `MAPPER`, `BN`, `NAT`, `GMT`, and `DEV` members who have more options than a regular user looking at a discussion page.
155
+
156
+ ### Formatting tools
157
+
158
+ Owners of a post on a discussion page can use formatting tools to make usage more painless. This includes permalinks, edits and deletions.
159
+
160
+ `Permalink` grabs a direct link to a post. This will show up as a reference number (e.g. `#1234567`) to other users, which can be clicked to quickly move to the referenced post. This is especially useful when referencing issues across modposts.
161
+
162
+ `Edit` allows a user to edit their submission in case of mistakes. This is not intended to be used for replying to messages. Create a new reply instead.
163
+
164
+ `Delete` allows the submitter to remove their submission in case of severe mistakes. This feature is disabled for posts with discussion on them to hinder deletions caused by heated discussion.
165
+
166
+ <!--TODO: insert lots of links-->