ow, awesome work
Davin Fortune wrote:
When making suggestions, try to differentiate between what is intersubjectively or objectively bad or wrong, and what you simply dislike on a personal level.
Well when the mapper see the map with the structure, he/she says fine but when player play it and say it's bad, and suggest it. Isn't it just like a subjective stuff? Not necessarily. As a modder you need to testplay the map, along with the patterns to make sure it plays well. If something still goes through then the player only need to explain why it plays bad and give a possible(?) solution. Even if there is no possible solution given, we can make decision by following the explanation.
between me and various osu!mania mappers, i keep giving a damn warn many times about :Unless the concept behind a beatmap is fundamentally flawed from the start, modding should aim to improve the map in it’s current design - not force your own style upon it.
People are currently using this as an excuse to stop technical maps (such as HW's) from getting qualified, and I feel like the wording on this doesn't really specify that it's pointed at mapsets from new mappers and mappers that don't really know what they are doing. I think that the first part of the sentence could make it clearer about what kinds of map we're directing this toLoctav wrote:
- Unless the concept behind a beatmap is fundamentally flawed from the start, modding should aim to improve the map in it’s current design - not force your own style upon it.
Loctav wrote:
- Unless the concept behind a beatmap is fundamentally flawed from the start, modding should aim to improve the map in
it’sits current design - not force your own style upon it.
Agreed. I think, if the modder is capable of writing English, but for example chooses to mod in their foreign native language instead, they should write a short summary of core parts of the mod, and the mapper should do it as well when replying to the mod in that same native language to give a short summary on what was changed. This is especially important on the modder's part when an IRC mod is in question, since it's really hard to tell what is conveyed in those messages if they're of foreign language, and sometimes it can be quite important information to see what was already discussed and what the mapper's opinion on that is.Wafu wrote:
I still think the same about the language, but nobody discussed that at all, so I don't see why it is the same.
ALL BNs speak English and are obligate to check if any mods aren't missing a kudosu. It's good if you use a language that makes more sense to the mapper, but one of them should make a conclusion about what was changed and what wasn't changed in English - maybe something important was ignored and maybe we aren't even aware if that mod warrants a kudosu. I think it's quite quality-killer if you want to qualify/bubble a map that has all mods of a language you don't understand. Sometimes I'm surprised what mapper ignored and could improve the map a lot, but nobody will point it out in this case.
All BNs are competent in English, but you can't reasonably expect every mapper/modder in the entire community to be so. I could include an additional request to "provide a summary of main points upon request", but I feel the onus is as much on the BN to seek out that information if they desire it, as well as the mapper/modder. As with any aspect of mapping, you are encouraged to seek help from someone with experience if there are parts of the beatmap thread you don't understand or want more information on - either from the mapper/modder or another team member who is competent.Wafu wrote:
I still think the same about the language, but nobody discussed that at all, so I don't see why it is the same.
ALL BNs speak English and are obligate to check if any mods aren't missing a kudosu. It's good if you use a language that makes more sense to the mapper, but one of them should make a conclusion about what was changed and what wasn't changed in English - maybe something important was ignored and maybe we aren't even aware if that mod warrants a kudosu. I think it's quite quality-killer if you want to qualify/bubble a map that has all mods of a language you don't understand. Sometimes I'm surprised what mapper ignored and could improve the map a lot, but nobody will point it out in this case.
I did consider adding this, but felt it would be too difficult to work in in a simple way (i.e. without covering several hundred possibilities) that fit the idea of this guide. Once the foundation of [Problem > Explanation > Suggestion] is understood, clarity via formatting will develop over time. The theme of "give to others what you would like to receive" should encourage people to put effort into making their mod posts understandable and accessible.J1NX1337 wrote:
I think one thing that helps with the modder's approach when writing mods is to properly organize the mod structure, with for example lists and perhaps some square brackets for headers or bold/colored text for highlighting. It helps make the mods more comprehensible and more enjoyable to read for the mapper and everyone involved. It's not exactly essential of course but to my experience, it does convey a better feeling of the mod in general. It seems more proper, nice and less lazy because of the extra bit of effort put into it, I suppose. It doesn't of course mean that everyone who doesn't bother with aforementioned things or cleanliness made a bad mod though, definitely up to the modder.
Everyone feels this way at times, but you have to remember that modding is a voluntary activity, often with little "reward". People are far more likely to mod what they like, for whom they like, when they like; either because they find it more enjoyable, or they can be more sure of what to expect and hence, what to look for, making the process easier. Some people don't like to leave their comfort zone, and that's fine - they can still make a positive contribution from there, and may yet open up in time. osu! is a diverse community, so the chances of you not being able to find anyone who shares the same preferences as you are slim. Keep mapping/modding/discussing/etc. and you'll meet new people, make friends and be able to gain experience and improve together!Annika Flina wrote:
I'm not too good with words, so please bear with me here.
When I was looking through the mod queues, I noticed quite a few modding queues saying that they will only mod certain genres and/or songs that they like. I got rejected many times trying to get mods for my first map becuse the modders "didn't like my song".
While I understand that every person has their own preferences, I feel that modders should be able to step out of their comfort zone and be open to all genres of music presented to them by the mappers.
If the modder doesn't know how to mod a certain genre, that's okay. But rejecting a map just because they don't like the song is not something I think is acceptable, especially if the modder doesn't take into account the quality of the map presented to them.
Though I'm still new to mapping and modding, I feel that having modders be open to all genres of music would help mappers get more mods, and the modders would gain even more valuable knowledge on modding.
What do you guys think?