Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Short-term hype improvements #1954

Closed
peppy opened this issue Dec 11, 2017 · 14 comments
Closed

Short-term hype improvements #1954

peppy opened this issue Dec 11, 2017 · 14 comments

Comments

@peppy
Copy link
Sponsor Member

peppy commented Dec 11, 2017

As discussed on discord, let's adjust hype in an attempt to make it more relevant.

  • Each user has a limited supply of hype (5 per month to start)
  • Hype can only be used after playing through a difficulty from a beatmap set.
  • Reduce hype required for nomination to 5.
@Xinnoh
Copy link

Xinnoh commented Dec 12, 2017

The amount of hype you can give out should be correlated with kudosu obtained
Modders tend to look at more maps that are rankable quality, they will give hype to a lower percentage of maps they see.
Also incentivises kudosu,

@peppy
Copy link
Sponsor Member Author

peppy commented Dec 12, 2017

That's the eventual goal

@nanaya
Copy link
Collaborator

nanaya commented Dec 12, 2017

Hype can only be used after playing through a difficulty from a beatmap set.

I thought plays of pending maps aren't recorded?

@peppy
Copy link
Sponsor Member Author

peppy commented Dec 12, 2017

Yeah, going to be adding that just for this. I'll get back to you when that's ready to go.

@NoffyNoffeh
Copy link
Contributor

I feel like this would lead to maps being more hyped/pushed at the start of a month than the end of a month due to people having/running out of hypes to give. There should be some way to stagger the limited hype distribution, such as a user will receive their hypes on the same day of the month that they registered, rather than everybody getting it at the beginning of the month.

@tastystew
Copy link

maybe getting x (1?) per week, with a maximum of y (6?) 'stored'?

@peppy
Copy link
Sponsor Member Author

peppy commented Dec 13, 2017

it shouldn't be based on calendar months. it would just be last x days.

@Loctav
Copy link

Loctav commented Dec 13, 2017

I agree with distributing the available "hype points" in shorter iterations than a month and implement a cap of how much you can have at once (like tastystew proposed), in order to avoid most hype being only given out to beatmaps at the end/start of the month or end/start of the x days, leaving the riverbed dry in the middle of a larger block of days.

@Tarrasky
Copy link

"after playing" this means just play or pass the map?
This looks kinda strange since you dont need exactly play the map to argue if the map deserve be hyped in your opinion, maybe the option "after playing or modded a difficulty" looks more logical.

@Xinnoh
Copy link

Xinnoh commented Dec 14, 2017

"After playing" does not work for everyone, and excludes modders that don't play well. I only check maps with trackpad, as bringing a mouse/tablet around with me is a hassle. To hype stuff, I'd be forced to play random normal/hard diffs which don't nearly represent the set as much as insane/expert.
Adding say, 5 mods/discussions to the set should also allow me to hype the map. I would have had to take an in-depth look at it to create the comments.

@IOExceptionOsu
Copy link

Imo if you don't play the map, I'd have a hard time trusting that you know whether it's a good map or not. Looking at it can find out practical ranking problems but ultimately it's still a lot different from actually playing it

@Xinnoh
Copy link

Xinnoh commented Dec 14, 2017

I've spent the last 6 months doing exactly that when nominating. Not being able to play something does not inhibit the ability to judge a set's playability when you do it for long periods of time.

@nekodex
Copy link
Collaborator

nekodex commented Dec 22, 2017

Points 1 and 3 have been addressed. Point 2 however requires client-side changes that have not yet been done, marking as blocked for now.

@peppy peppy closed this as completed Dec 26, 2017
@peppy
Copy link
Sponsor Member Author

peppy commented Dec 26, 2017

Closing for now. We'll review this in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants