Skip to content

Instantly share code, notes, and snippets.

@Ephemeralis
Created February 2, 2018 05:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Ephemeralis/b253dedf2fd87bbb6c154e483d449f2a to your computer and use it in GitHub Desktop.
Save Ephemeralis/b253dedf2fd87bbb6c154e483d449f2a to your computer and use it in GitHub Desktop.

What makes a beatmap's track inappropriate for osu!?

With a wide variety of music available, most tracks will be fine for use in osu!, providing that they are not:

  • Intensely explicit, suggestive, or otherwise extremely confrontational in regards to shocking, obscene or highly sexual content
  • Glorifying, promoting or otherwise encouraging suicide, murder, or self-harm
  • Promoting racial tension or division
  • Extremely and unbearably loud or excessively clipped

Tracks with explicit lyrics can still be used so long as they do not overtly violate the criteria above.

They will need to be identified by a line in the beatmap's description reflecting the sensitive nature of the content. They must also not have the preview point of the map set to a portion of the song that widely broadcasts said explicit content.

I have an explicit track that I'd like to map, how do I know if it's okay?

This is a mildly complicated issue and what is acceptable for one person is often not for another.

To address this, roughly apply a variant of the 20% rule - is more than 20% of your track's lyrical content a direct reference to something explicit, suggestive, or otherwise controversial?

If so, or if approaching the case, you may want to consider mapping something else. It probably isn't okay.

Any track that is highly intense or shocking in any manner as described in the three criteria above is not allowed regardless of what percentage of its content falls under the classification.

What determines "highly intense" should be abundantly obvious to a large selection of random people.

What happens if my track isn't okay?

Any beatmap containing a disallowed track will be removed from the BSS.

All users are given a three submission leeway before penalties are handed out due to the uncertain nature of this rule.

Having any map of yours ranked will restore a 'charge' of the leeway to a maximum of three.

Each time your submission is removed, you will be afforded an explanation by the presiding member of the QAT or GMT responsible for the removal with reasoning justifying the removal.

You may contest this with them via PM if you so wish, or seek the opinions of others to substantiate your claim to the track's suitability. If you still cannot find common ground on this front, your claim may be escalated to a consensus vote among the current QAT, who will collectively decide if your track is acceptable or not.

After the leeway has passed, users who continually choose to upload inappropriate tracks will face a 42hr infringement.

@Okorin
Copy link

Okorin commented Feb 4, 2018

My comment from the thread:

  • make the 3 submission leeway one, if they dont get it after one they dont get it after having one thing slapped and explained to them why
  • mention that if you're not sure contact the GMT / QAT before uploading

@Naxesss
Copy link

Naxesss commented Feb 8, 2018

  • The 20% rule is likely a point that would cause debate, especially due to explicit content not being considered just black or white. Where would time start and end for each instance of explicit/suggestive/controversial language, how does context play into this, etc. In the end it may just cause more confusion than it clears up because of it's arbitrary and vague nature. In general, a way to make this clearer is providing examples of inappropriate/appropriate songs as points of reference, in order to stay consistent in judgement, although this has it's own share of problems I'd imagine.
  • The three submission leeway should probably take into account people intentionally breaking it every time they rank a map for the fun of testing the limits. Three is also quite a high number, preferably it would at least take into account the magnitude of the offense if anything, and if that ends up being too complicated then see oko's point above regarding this.

@JBHyperion
Copy link

Creating some kind of usercase system to keep track of inappropriate uploads (to the total "allowed" limit of three) would require needless additional overhead, and just encourages people testing the limits instead of actually asking, which is what we want them to do.

I'm fine with giving a one-warning C&D before dumping instant silences if that's a fairer way to do things though.

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