This suggestion is fucking greatNozhomi wrote:
Could we have maybe a button to hide resolved issues as map owner ? It would resolve this easily.
This suggestion is fucking greatNozhomi wrote:
Could we have maybe a button to hide resolved issues as map owner ? It would resolve this easily.
I believe this is furthering mapping bias and making a less of a reason to help others become better at mapping. Granted there are bad comments here and there, but good comments still overwhelm those, so I don't believe this the best direction to face. Most of the time all of the attention from common people would be taken away by those respected mapper.hi-mei wrote:
Basically, there are people whos very experienced (Shiirn, Okorin, Natsu etc) and there are people who just spams their opinions without any knowledge in mapping.
Yea it sounds a bit uh... unfair but as a mapper (and trust me, its the case for any prominent mapper) sometimes I wanna see only specific person's opinon, instead of scrolling thru the entire thread of mods that might be useless.
idk newer modders can even get downvoted now for bad comments sooooabraker wrote:
I believe this is furthering mapping bias and making a less of a reason to help others become better at mapping. Granted there are bad comments here and there, but good comments still overwhelm those, so I don't believe this the best direction to face. Most of the time all of the attention from common people would be taken away by those respected mapper.hi-mei wrote:
Basically, there are people whos very experienced (Shiirn, Okorin, Natsu etc) and there are people who just spams their opinions without any knowledge in mapping.
Yea it sounds a bit uh... unfair but as a mapper (and trust me, its the case for any prominent mapper) sometimes I wanna see only specific person's opinon, instead of scrolling thru the entire thread of mods that might be useless.
Nozhomi wrote:
Could we have maybe a button to hide resolved issues as map owner ? It would resolve this easily.
You can filter to resolved or pending, but the issue is nonetheless scrolling through resolved stuff to see what is going on, how is the mapper responding to mods and what could general concerns be from modders.Nozhomi wrote:
Could we have maybe a button to hide resolved issues as map owner ? It would resolve this easily.MaridiuS wrote:
Think noffy was referring to the idea of scrolling through 100 random points that nobody will really care about. If some issue on the lines of "spacing too big here" was resolved, it means it's not relevant in the map anymore, and we're forced to scroll through multiple posts of these kind. Therefore no reason for the modder to point it out or care about that post while it takes valuable space, compared to an old ~13pixel line. Add 30 of those and it becomes hellish.
pkhg wrote:
also theres a way to edit descriptions currently. u just have to search for it on your post history
pkhg wrote:
ya ik but im just pointing that out as a placeholder like what u did for metadata posts
hi-mei wrote:
oh boys, there are people getting 10kds per maps set XD
@peppy can you please change the Kudosu thing to come from "resolved" but not "upvoted" instead?
people gonna abuse that for sure
What's the use for this? It's not gonna prevent hype spamming anyways. I feel like this is just wasting everyone's time even more.peppy wrote:
- hype only possible after user has played through the beatmap (need client support)
Wait really? - Why do I have to determine if a map deserves a hype by playing through it now? What if the map is a 10 min marathon? Do I have to play through the whole thing to just give a map I believe deserves a hype to get rank? I hope that won't be the case lolBOUYAAA wrote:
What's the use for this? It's not gonna prevent hype spamming anyways. I feel like this is just wasting everyone's time even more.peppy wrote:
- hype only possible after user has played through the beatmap (need client support)
Why is hype even mendatory i don't get it.
Hailie wrote:
I really don't agree with this new KD system whatsoever - I can even get kds from my own map which doesn't make sense...
Hailie wrote:
Apparently I can go straight to someone's map and downvote a modder's mod and take away their kd from it (I tried it on a random map and one of my maps - oh course I remove the downvote after that lol)
I think that is... pretty dumb and that just goes back to my point of why I believe the mapper should determine if a mod deserves a kds once more because that just cause even more abusive issues
it was added recentlycococolaco wrote:
Quite minor but it would be nice to see who has favorited your map
LowAccuracySS wrote:
I think the main concern I have about this entire thing is the fact that it's being forced when it's not complete- I think 90% of the complaints that we currently have are mainly due to the incomplete nature of mv2. I don't know though, that's just my opinion based on what I've seen. As for suggestions, most of what's been mentioned I agree with, including changing beatmap descriptions post-rank. I don't see how abuse can occur here, and I would like to see examples (if possible)
Anyway, just my two cents. Modding with mv2 is straight to the point and easy, I just worry about the set owner and GDers more
I agree with only about GD mappers. Current system has no function for GD mappers. For now, host is checking all GD mappers respond and check resolved. It's too unproductive.LowComboFC wrote:
Would also like to add a small detail for the cons (well, it's basically a suggestion); the map(set) host should be able to mark one's point as either accepted or denied instead of just "resolved". Otherwise, why do we colour our mod replies in v1? They're way easier to distinguish and it would be a cool (and helpful for some) detail to have plus it isn't that hard to implement.
Furthermore, something a bit more complex but one that could prove VERY useful and should be more compatible with v2 rather than v1: Give permission to GDers to do what I mentioned above on their own diffs. The host could give permission for the GDers to do so in their diffs, and each diff's permissions should be seperated so (example:) the GDer doesn't accept/deny a point in another diff they haven't mapped etc.. This is a bit more complex to do but I'm confident it's going to be more compatible with v2. The GDers updating their own diff could also be a thing but I'm not sure how that would work.
I believe modding v2 has much potential, and as long as it's made a bit more intuitive to use it'll be quite a good step for the modding scene.
Kawashiro wrote:
LowComboFC wrote:
Would also like to add a small detail for the cons (well, it's basically a suggestion); the map(set) host should be able to mark one's point as either accepted or denied instead of just "resolved". Otherwise, why do we colour our mod replies in v1? They're way easier to distinguish and it would be a cool (and helpful for some) detail to have plus it isn't that hard to implement.
Furthermore, something a bit more complex but one that could prove VERY useful and should be more compatible with v2 rather than v1: Give permission to GDers to do what I mentioned above on their own diffs. The host could give permission for the GDers to do so in their diffs, and each diff's permissions should be seperated so (example:) the GDer doesn't accept/deny a point in another diff they haven't mapped etc.. This is a bit more complex to do but I'm confident it's going to be more compatible with v2. The GDers updating their own diff could also be a thing but I'm not sure how that would work.
I believe modding v2 has much potential, and as long as it's made a bit more intuitive to use it'll be quite a good step for the modding scene.
I agree with only about GD mappers. Current system has no function for GD mappers. For now, host is checking all GD mappers respond and check resolved. It's too unproductive.
MaridiuS wrote:
alright, popping is now a thing, though a bit different, check undiscussed at the OP.
Changing description via the new site is also available, though not sure if it's posssible to do when a map is ranked.
ThisKawashiro wrote:
When I mod a map which already received many mods, Mapper sometimes already resolved some issues what i want to suggest without any more discusses. For now, only writer and mapper can reopen resolved issues. But I think this is blocking the way to others to join the discussion which is already resolved. For example, If someone suggested what i want to suggest and mapper rejected and check "resolved" icon, then nobody (except mapper and writer) can't show his own suggestion again.
I strongly think others (not a writer or mapper) should be able to reopen discussions which already resolved.
If people repeat the same issues in different mods, it's maybe the meaning that this issue have to be fixed?FiddleBlue wrote:
The point of modding v2 is to simplify issues so that people don't repeat the same thing in another discussion. So anyone should be able to open resolved discussion. Mappers will most likely organize by pending rather than all, so the additional mod given is likely to not be seen.
Or we can simply just add more to the discussion to what the initial modder has missed, like he didn't offer suggestions or didn't explain really well.Pachiru wrote:
If people repeat the same issues in different mods, it's maybe the meaning that this issue have to be fixed?FiddleBlue wrote:
The point of modding v2 is to simplify issues so that people don't repeat the same thing in another discussion. So anyone should be able to open resolved discussion. Mappers will most likely organize by pending rather than all, so the additional mod given is likely to not be seen.
To me upvote/downvote is not as similar as repeating the same thing in different person's mod, cause text mod have more impact than just clicking on a button.
MaridiuS wrote:
ConsIssues that only seem to be curent
- Polishing the mod is not as viable, there's no way to prepare a mod beforehand with osu! resources. Nothing is wrong with doing live modding, not an issue.
- In the current system modding is considered as a secondary involvement, people are much more known for being mappers or players, but rarely is a user known for being a good modder. The new system puts modders all mixed up, so others viewing the thread won't be able to comprehend the value of one modder, in fact, with all the posts mixed up so much, I doubt anybody will be looking over mods unless the timestamp says that something was already mentioned. This means no one will be able to take notice on a specific modder, therefore... rip modder pride. This is planned for future implementation, but is a large hurdle.
Clearing other smaller ones is higher priority.- There is no formatting. We can have linebreaks, this has been somewhat addressed.
- Seems like there is a lot of unused space than it needs to be. ~Noffy. Personally I think at some point it is handy, but removing a little bit white space would be more fitting as I won't be required to scroll a lot down for just one discussion on a post. Peppy has confirmed that mv2 is being redesigned, expect a more compact version in the future.
- GDers can't post their updates in the thread so you don't have a history of them if people wanted to ever look back for changes. Still an issue
- Some mappers like to reply to mods first before applying it, so after answering a mod and mark it as resolved, keeping a track later would be a pain. Mappers still fix stuff locally on their system, not really an issue to begin with.
- New reward system is literally a con No clear way to solve this for now.
- Hype system is also a con This has been addressed in many ways, much better now.
- Character limit... Currently in case I need to write a huge paragraph, I will have to break it down into adding more into responses of the initial post, which is just a pain imo. So imo I think character limit could have a higher cap? I already told you in Akitoshi's server that being concise and simple is a skill. If you're really stuck then use multiple timestamps or comments. Having over 500 characters is spammy and defeats the purpose of v2.
Improvement suggestions
- Currently you can't view activity on mv2 on old site. On new site you can, but it's mega spammy. They are working on compressing mv2 kudosu history here
- Currently, if a difficulty changes beatmap number due to being renamed, or deleted and added back between uploads, all points made on it disappear into an abyss. Renaming does not delete info. Deleting + readding is rare.
- Is there no limit per kudosu on a mapset yet? Why? Kudosu for 30 minute marathons should not be the same as tv size.
- You can't see the listing of currently nominated maps. This is still a major issue.
- Writing box is impractical, it's height is too small, covering about 2 and a half rows. Scrolling goes to like 1.5 rows and I get to skip text basically on longer posts. I think making it by default to be higher, or simply make it follow your preference of its height is the way to go, because the current chosen box is too small for any editing conventions. This is fixed.
- Make it available to filter per modder and per timeline. I am pretty sure many people would prefer that, I cant imagine myself browsing mapthreads on modv2 in it's current state. Especially the "resolved" issues. Filters are planned.