forum

Plini - Paper Moon

posted
Total Posts
70
show more
Topic Starter
Zhuriel

Kagetsu wrote:

it might be true that 110 bpm is the original one for this song (i actually checked the tab before popping this) however, 11/8 is unsupported by the game so you will have to transcribe 11/8 to more simple time signatures (11/8 is "faster" hence why the current timing doesn't work)

Ranking Criteria wrote:

  1. Uninherited (red) Timing Sections should be used to accurately map the song's timing. They should synchronize to the beats of the song as accurately as possible and use the correct time signature whenever possible. If an incorrect time signature would last for more than 2 bars, add another timing section to fix it.(...)
while the game does not support 11/8, there is nothing unrankable in the way i've timed it according to this piece of wording in the rc as a) it is not possible to use the correct time signature and b) no incorrect time signature lasts for more than one bar.

Kagetsu wrote:

it's not about following an official number, but rather to make things work within the game limits.
things work quite well within the game's limits as-is, the tempo is correct and all the downbeats are in the right place. you can argue that not all the emphasis structure of the 11/8 matches up with the game metronome but that is a rather minor issue, not noticable in gameplay and probably also is the case in a few other examples, such as altale which uses a 3/4 instead of a 6/8 resulting in completely different subdivisions implied in the metronome to those actually used in the song.
Kagetsu

Zhuriel wrote:

while the game does not support 11/8, there is nothing unrankable in the way i've timed it according to this piece of wording in the rc as a) it is not possible to use the correct time signature and b) no incorrect time signature lasts for more than one bar.
that's the problem though. since it isn't possible to set the correct time signature, you should find a better way to represent that signature, (which in this case, would be by doubling the bpm). the current timing is actually an issue, because the metronome doesn't correctly synchronize to the song beats.
frukoyurdakul
I'm having a concern of one other part though, instead of the 11/8 section.

05:19:837 - I don't think this is flat 4/4. I haven't came up with a solution yet but I think that section needs to be fixed as well.
Secondly, the part after that kiai is also wrong (because of the similiar rhythms.) And here is what I've found:

You need a metronome reset on 05:38:874 - 05:46:074 - 05:53:274 - 06:00:474 - those 4 points. The guitar and the drums, and the rest of the structure of the music supports these resets. It will also fix the NC beats, which currently is the case.
squirrelpascals

Kagetsu wrote:

it's not about following an official number, but rather to make things work within the game limits.
exactly what limits are being pushed here? there shouldn't be a need to stray away from the songs original bpm to reflect more accurate timing - based off your example in your earlier post. Your timing points seem to reflect more of an alternating 5/4, 6/4 rather than what the song was truly written to according to the tabs. I'm going to have to say I agree with Zhur on this one.

Let's get another say in this from someone who's a lot more experienced in this stuff, since were obviously at a disagreement and trying to prove eachother wrong won't be as productive :P
Kagetsu

squirrelpascals wrote:

there shouldn't be a need to stray away from the songs original bpm to reflect more accurate timing - based off your example in your earlier post. Your timing points seem to reflect more of an alternating 5/4, 6/4 rather than what the song was truly written to according to the tabs. I'm going to have to say I agree with Zhur on this one.
i don't think you get the full picture of what i'm trying to explain so i made a video showing what the time signatures and bpm actually mean.


  1. from bar 1 to 6, it shows a 6/4 110 bpm pace (this is what's in the map, currently)
  2. from bar 7 to 12, it shows a 6/8 110 bpm pace (this is what the original composer wrote, whether it's 11 or 5+6 /8 is irrelevant, as these changes would only add more bars)
  3. from bar 13 to 18, it shows a 6/4 220 bpm pace (this is what i consider a more accurate adaptation of what the composer wrote)
i know you guys are attached to this "110 bpm" number and don't want to change it, but in reality the song's pace is way faster. even if you're trying to represent an 11/8 signature, 220 bpm 11/4 is proven to be more accurate.
Topic Starter
Zhuriel

Kagetsu wrote:

  1. from bar 1 to 6, it shows a 6/4 110 bpm pace (this is what's in the map, currently)
what's in the map currently is not a 6/4 but a 11/8 implemented by resetting the timing with red lines. as far as i'm concerned, (as well as the game mechanically is concerned) this is equivalent to a 11/8 with a different structure (which is not a thing that osu cares about) and thus is the best way to implement a 11/8 time signature in osu.

Kagetsu wrote:

i know you guys are attached to this "110 bpm" number and don't want to change it, but in reality the song's pace is way faster. even if you're trying to represent an 11/8 signature, 220 bpm 11/4 is proven to be more accurate.
the song's "pace", in my opinion, lies in the subdivisions of the 11/8 (3-2-3-3 for the most part), which is not something that osu is (nor in all likelyhood ever will be given the popularity of songs with the level of rhythmic complexity needed for that to matter) capable of accurately representing. while 220 may cause all metronome beats to land on subdivisons, it also misrepresents the "pace" you seem so intent on. there are no rules in the ranking criteria stating that all metronome beats have to land on subdivisions, and there are ranked maps in 6/8 implemented as 3/4, so i see no argument why 220 11/4 is a more accurate representation of the song than 110 11/8 with a different structure.

frukoyurdakul wrote:

05:19:837 - I don't think this is flat 4/4. I haven't came up with a solution yet but I think that section needs to be fixed as well.
Secondly, the part after that kiai is also wrong (because of the similiar rhythms.)
i originally timed it like your suggestion, however in the transcription it is written as 4/4 with heavy syncopation so i updated the timing to be accurate to that.
Kagetsu

Zhuriel wrote:

while 220 may cause all metronome beats to land on subdivisons, it also misrepresents the "pace" you seem so intent on.
they're not subdivisions though. if you watched the video, you would understand that you're missing half of the downbeats. the downbeats for 6/8, 11/8, whateverthing/8 are supposed to land twice the speed than it would happen for a /4 song. it doesn't misrepresent the pace of the song, actually it makes more accurate.

Zhuriel wrote:

there are no rules in the ranking criteria stating that all metronome beats have to land on subdivisions,
i insist, they're not subdivisions. and yes, there is a rule that says that the timing should represent the beats of the song which is not the case for this map.

Zhuriel wrote:

and there are ranked maps in 6/8 implemented as 3/4, so i see no argument why 220 11/4 is a more accurate representation of the song than 110 11/8 with a different structure.
i don't know how is this a valid excuse. appealing to common practice is a fallacy. i don't see any valid argument here other than you wanting to keep this 110 number for any arbitrary reason
Topic Starter
Zhuriel
Allow me one last attempt at explaining the structure of the 11/8 meter in this song:



similar to a 12/8, each of these groupings structurally works like a beat in a 4/4, whereas that would not be the case in a 220BPM 11/4. this is why i do not consider timing at 220 to be a more accurate representation of the composition.

adding to that, having to either drastically and unfittingly change tempo at some point or time the entire song at double tempo, as well as undesired slider ticks introduced by the doubling would mean investing a significant amount of time into reducing the quality of the map, which i have no intention of doing.
Kagetsu

Zhuriel wrote:

Allow me one last attempt at explaining the structure of the 11/8 meter in this song:



similar to a 12/8, each of these groupings structurally works like a beat in a 4/4, whereas that would not be the case in a 220BPM 11/4. this is why i do not consider timing at 220 to be a more accurate representation of the composition.
that's not how it works though. those groupings are meant to clarify how to count the notes in the measure (like 1 2 3, 1 2, 1 2 3, 1 2 3, also known as metre, however that's not the pace of the song. as you might know, 11/8 clarifies that there should be 11 eight notes per measure so that's what the issue is at the moment, you're missing half of the beats in the song, (because the beats are meant to be eight notes).

i find it weird that you're mentioning metre, because your current timing doesn't even land the spots that should be accentuated in the "score" you just post.

the groups you're alluding to, in the first measure are:
  1. 00:01:305 -
  2. 00:01:850 - this isn't even a beat in your current timing
  3. 00:02:395 - more of the same
  4. 00:03:214 -
  5. 00:04:032 -
metric isn't really a thing on osu, the only requirement is to have beats synchronized with the song. however you can always divide the 11 measures into 3-2-3-3 by using metronome resets if you want to do so. it would be something like this:

[TimingPoints]
1305,272.727272727273,11,1,1,70,1,0
2123,272.727272727273,11,1,1,70,1,0
2668,272.727272727273,11,1,1,70,1,0
3486,272.727272727273,11,1,1,70,1,0
4304,272.727272727273,11,1,1,70,1,0

in any case, using the first timing point would be enough
Topic Starter
Zhuriel
a recent RC update was pointed out to me that says:

Ranking Criteria wrote:

  1. Uninherited timing points must be used to accurately map the song's time signatures. If an incorrect time signature lasts for more than one bar, a uninherited timing point must be added on the next downbeat to reset the time signature. For time signatures unsupported in the editor, metronome resets or editing of the .osu file are acceptable.
therefore, my implementation is now explicitly allowed by ranking criteria.
Turquoise-
absolutely rekt
Kagetsu

Zhuriel wrote:

a recent RC update was pointed out to me that says:

Ranking Criteria wrote:

  1. Uninherited timing points must be used to accurately map the song's time signatures. If an incorrect time signature lasts for more than one bar, a uninherited timing point must be added on the next downbeat to reset the time signature. For time signatures unsupported in the editor, metronome resets or editing of the .osu file are acceptable.
therefore, my implementation is now explicitly allowed by ranking criteria.
true, but not exactly for the reasons you pointed. the new RC just doesn't state that the metronome should follow the beats in the song. in any case, it says something about accurately map the song's time signatures but that's now kinda vague in my eyes ¯\_(ツ)_/¯


Turquoise- wrote:

absolutely rekt
please avoid comments like this. it creates a wrong perception of what i was trying to achieve here. this wasn't a personal attack or anything. let's say it's just my "job" as a bn to discuss these type of stuff (because the metronome is still wrong)
Topic Starter
Zhuriel

Kagetsu wrote:

true, but not exactly for the reasons you pointed. the new RC just doesn't state that the metronome should follow the beats in the song. in any case, it says something about accurately map the song's time signatures but that's now kinda vague in my eyes ¯\_(ツ)_/¯
not sure how explicitly allowing metronome resets is vague in any way, if anything it is vague in a good way as it allows mappers to choose which of the available inaccurate workarounds works best for them. i feel like you misunderstood my point, i never argued this implementation is accurate to the song, however i consider it more accurate and resulting in a better map than the alternative.
Kagetsu

Zhuriel wrote:

not sure how explicitly allowing metronome resets is vague in any way, if anything it is vague in a good way as it allows mappers to choose which of the available inaccurate workarounds works best for them. i feel like you misunderstood my point, i never argued this implementation is accurate to the song, however i consider it more accurate and resulting in a better map than the alternative.
i never said metronome resets are vague though? i'm questioning the part of Uninherited timing points must be used to accurately map the song's time signatures. it says accurately but doesn't explain what they consider accurate as you can now use a sum of correct bpm + wrong time signature which results in the metronome being off just like in this case.
even if you're using metronome resets, that doesn't change the fact that you're missing half of the beats or that the metronome should be twice as fast as the current one.
Topic Starter
Zhuriel

Kagetsu wrote:

i never said metronome resets are vague though? i'm questioning the part of Uninherited timing points must be used to accurately map the song's time signatures. it says accurately but doesn't explain what they consider accurate as you can now use a sum of correct bpm + wrong time signature which results in the metronome being off just like in this case.
as opposed to your variant which uses both incorrect tempo and incorrect time signature? (refer to my previous posts for the difference between 11/8 and 11/4, not gonna explain this a third time)

i'm not sure how you reconcile explicitly allowing metronome resets with the rule being vague as to whether this is correctly timed - i can't think of any other way to implement unsupported time signatures using metronome resets, so explicitly allowing metronome resets refers this implementation, unless you can come up with another reasonable way of implementing unsupported time signatures using metronome resets which i very much doubt there is.
dsco
okay hopefully i can help address / mediate this on some level as it is not progressing anywhere.

using 220bpm is a bad idea for this map and would set a bad precedent for maps to come, and here's why:
if a song were to be 110bpm 4/4 and then have a measure of 7/8, you would have to add an extra red point with double the bpm at 220bpm 7/4 which would not only mess with SV but be an inaccurate BPM reading which it shouldn't read as in the song info, because the song is not in *any* way 220bpm. yes, you could fix the SV, but is an extra step that it does not make sense to require.
i've spoken with pishifat on this and he also agrees that you should not double the song's bpm.

thus, the only way to correctly time the map is with metronome resets, as zhuriel has done. i do believe, however, it makes more sense to change the time signature from 6/4 to 11/4 so that the 'correct time signature' can at least be ascertained from the timing panel, and maintain at least some level of relationship between the time signature chosen in the editor and the true time signature of the song, though this does not do anything. it should also be noted that this is done later in the map with 7/4 (instead of 4/4) starting at 06:04:331. also 06:16:091 ought to be changed to 9/4 to keep consistent with the measures / time signatures chosen before.

i can also verify that the 4/4 section int he middle is indeed 4/4, heavily syncopated groupings, though i dont agree with having truncated measures of 4/4 (starting at 05:35:510) instead of adding a red tick that says 3/4 (as would be correct in the tabulature, as i've gathered from zhuriel)

hopefully this can at the very least progress discussion on this map.
Topic Starter
Zhuriel

dsco wrote:

i do believe, however, it makes more sense to change the time signature from 6/4 to 11/4 so that the 'correct time signature' can at least be ascertained from the timing panel, and maintain at least some level of relationship between the time signature chosen in the editor and the true time signature of the song, though this does not do anything. it should also be noted that this is done later in the map with 7/4 (instead of 4/4) starting at 06:04:331. also 06:16:091 ought to be changed to 9/4 to keep consistent with the measures / time signatures chosen before.
though there is no mechanical difference i can see the point of wanting a cleaner timing, so i'll implement this.

dsco wrote:

i can also verify that the 4/4 section int he middle is indeed 4/4, heavily syncopated groupings, though i dont agree with having truncated measures of 4/4 (starting at 05:35:510) instead of adding a red tick that says 3/4 (as would be correct in the tabulature, as i've gathered from zhuriel)
technically this falls under the "one bar" rule and reduces rounding errors by eliminating a few red lines but again i can see the point of clean timing so will do.

on the same note the same thing applies for the 2/4 in the calm section so i will be implementing that too

oh i also removed one superfluous redline and fixed like 2 hitsounds because i always find mistakes in the hitsounds somehow
Bonsai
Hi, since the topic of how this sort of timing should be handled has been brought up to the the timing-UBKRC by dsco recently, we are currently working on figuring out how we can regulate this - Whatever the exact results will be, I can already relatively safely say that doubling the BPM for this is not what we want at all. This would go against the definition of "Beats per Minute" (a "Beat" generally being defined as a (occasionally dotted) quater note, and thus a white tick in osu! representing that quater note, never an eighth note), and as a result that would lead to a lot of issues of how to handle stuff overall.

tl;dr current timing is fine, move along
squirrelpascals

Bonsai wrote:

the the

:) :) :) :) :) :)
SilverCatalyst

squirrelpascals wrote:

Bonsai wrote:

the the

:) :) :) :) :) :)
[unrelated to the map but]
i checked to see who bubbled this amazing map and of course it was squirrelpascals
you're a blessing as a mapper lmao, you're almost my favorite mapper of 2017
celerih
Hello I'm here because Zhuriel doesn't know how to talk to BNs

[
The End of Everything
]
  1. 00:27:897 (3) - Have this as a circle + a 1/4 slider because a reverse is too weak imo for the drums on 00:28:034 -
  2. 00:37:170 (3) - Put this a bit lower so it doesn't touch 00:36:897 (1) -
  3. 01:22:306 (1,2,3,4) - can u make these a bit more parallel or at least be at the same angle pls
  4. 01:23:532 (6) - I don't think there's anything to justify 6 not being grouped with 4 and 5
  5. 03:53:602 (1) - For more impact overlap this note with the slider head of 03:52:352 (3) -
  6. 04:09:102 (6,7) - Looks like a 1/4 gap because of 04:08:727 (4,5) - . Try and differentiate them a bit
  7. 04:23:727 (4,5,6,7) - same as above
  8. 05:18:335 (1,2,3,4) - Decrease distance here because pitch is going down
  9. 06:39:566 (1,2,3,4,1) - Why is spacing decreasing here?
  10. 08:12:366 - What's up with the 5 greenlines here?

Call me back for a rebubble (:
Topic Starter
Zhuriel

celerih wrote:

Hello I'm here because Zhuriel doesn't know how to talk to BNs ɿ(。・ɜ・)ɾ
SPOILER
[
The End of Everything
]
  1. 00:27:897 (3) - Have this as a circle + a 1/4 slider because a reverse is too weak imo for the drums on 00:28:034 - i want to emphasize the held guitar note here and that would somewhat take away from that. i tried out a few patterns to increase emphasis on (3) with spacing and have the kick clickable but i can't really find anything that i like
  2. 00:37:170 (3) - Put this a bit lower so it doesn't touch 00:36:897 (1) - would mess with the triangle pattern in a way i really don't like, alternative would be to increase spacing on the triangle but that would mess with the decreasing spacing in the pattern as well so i think this overlap is the least of the evils there are to choose from
  3. 01:22:306 (1,2,3,4) - can u make these a bit more parallel or at least be at the same angle pls rotated to sit symmetrically on 01:22:851 (1) -
  4. 01:23:532 (6) - I don't think there's anything to justify 6 not being grouped with 4 and 5 follows the same pattern as 00:27:079 (1,2,3) - in emphasizing bass drums
  5. 03:53:602 (1) - For more impact overlap this note with the slider head of 03:52:352 (3) - i want this to follow the back-and-forth pattern of 03:51:102 (5,6,1) -
  6. 04:09:102 (6,7) - Looks like a 1/4 gap because of 04:08:727 (4,5) - . Try and differentiate them a bit
  7. 04:23:727 (4,5,6,7) - same as above that would be because the kickslider was added later on, moving the double a bit closer to the kickslider to differentiate
  8. 05:18:335 (1,2,3,4) - Decrease distance here because pitch is going down starting pitch is lower but it switches from a descending run to an ascending one with wider intervals, so lower spacing would be unfitting imo
  9. 06:39:566 (1,2,3,4,1) - Why is spacing decreasing here? rhythm guitar descending like the rest of the patterns in this section
  10. 08:12:366 - What's up with the 5 greenlines here? i covered the other cymbals in the outro with sliderticks but since there isn't a slider tick here i made my own pseudo-tick with sliderslide volume manipulation

Call me back for a rebubble (:
celerih
(: Rebubbled!

Metadata: https://plini.bandcamp.com/album/the-end-of-everything

Logs
2017-10-24 17:49 celerih: did u update it
2017-10-24 17:49 celerih: yes you did
2017-10-24 17:49 Zhuriel: just now
2017-10-24 17:52 celerih: okay time to actually recheck
2017-10-24 17:55 celerih: only thing really that I think you should change it 03:53:602 (1) -
2017-10-24 17:55 celerih: I get the back and forth you're going for but as the end of a section it feels quite lacking
2017-10-24 17:56 Zhuriel: hm
2017-10-24 17:56 Zhuriel: how about rotating the entire triangle so there's more space to go with the back and forth at higher spacing
2017-10-24 17:56 celerih: that would work
2017-10-24 17:58 Zhuriel: osu.ppy.sh/ss/9390196 like this
2017-10-24 17:58 Zhuriel: http://osu.ppy.sh/ss/9390196 like this
2017-10-24 17:58 Zhuriel: y u no copy http cmh my head software
2017-10-24 17:58 celerih: yeah that's fine
2017-10-24 17:59 Zhuriel: anything else?
2017-10-24 17:59 celerih: mot a fan of how 00:54:352 (1,2) - is stacked
2017-10-24 18:00 Zhuriel: hm
2017-10-24 18:00 Zhuriel: it's kinda a consequence of the two patterns that come together there
2017-10-24 18:00 Zhuriel: but i guess i could try inverting the first stack to make it look nicer
2017-10-24 18:00 Zhuriel: or all of them really
2017-10-24 18:01 celerih: that would work
2017-10-24 18:01 Zhuriel: not like the pattern shows up that often
2017-10-24 18:04 Zhuriel: https://osu.ppy.sh/ss/9390219
2017-10-24 18:04 celerih: better
2017-10-24 18:07 celerih: increase distance here to make it more obvious it's not 1/2 07:41:848 (1,2,3,1) -
2017-10-24 18:08 Zhuriel: huh what
2017-10-24 18:08 celerih: wait
2017-10-24 18:08 celerih: nvm I'm drunk
2017-10-24 18:08 celerih: no it's good
2017-10-24 18:09 celerih: I think that should be it then
2017-10-24 18:09 Zhuriel: wheee
2017-10-24 18:09 celerih: oh wait
2017-10-24 18:09 celerih: add prog to that
2017-10-24 18:09 celerih: *to tags
2017-10-24 18:10 celerih: a lot of people use that abbreviation so it could be useful to include it
2017-10-24 18:10 celerih: website can be weird about it
2017-10-24 18:10 Zhuriel: makes sense
2017-10-24 18:10 Zhuriel: i have to go into text editor for that cause wine
2017-10-24 18:11 celerih: ya ok I just tried prog metal in website and paper moon didn't pop up
2017-10-24 18:12 Zhuriel: ok updating then
Bergy
holy when did this all happen

its happeNING and i didnt even notice
squirrelpascals
The mappers understand this stuff; they have the intellectual capacity to truly appreciate the depths of these patterns, to realise that they’re not just good patterns- they say something deep about LIFE.
Topic Starter
Zhuriel
took me a while
Shovan
Zhu seems to be speedranking maps here smh.
gratz on qualified. Traces next? :roll:
Suissie
Placeholder for dq mod :^)
Gimme 6 six days
Saileach
grats zhu, mod traces
Ohwow
00:23:534 - why did you skip this? At first, it really seemed like you're following the guitar (since it's really prominent) and all of the sudden you skipped this guitar. Even if you argue that you are following the cymbals, it still feels awkward to have a pause there when there's no pause in the music. I would've liked at least a circle stacked onto 00:23:670 (1) -
01:11:534 - ^

00:36:897 (1,2,3) - why overlap (1) and (3)? it will easily look better if spaced. and why is (1) & (2) aligned while 00:36:625 (1,2) - and 00:36:352 (1,2) - are not? https://i.gyazo.com/09e16055084afd8cf12 ... 457f04.jpg

04:08:727 (4) - there's no snare here in the music, so should remove drum-normal. like 04:23:727 (4) -
04:08:852 - on top of that, not really liking how the actual snare (which is the loudest) is mapped to slider end.

06:21:731 (5,1) - The flow here is really bad compared to the rest of the streams you did.

07:31:288 (1) - there's no snare on the sliderend.

07:57:698 (2) - make this a slider? again with the rhythm pauses.

meh. cool stuff, but I feel like this map could be improved. Feel free to decline everything if you have reasons.
Topic Starter
Zhuriel

Ohwow wrote:

00:23:534 - why did you skip this? At first, it really seemed like you're following the guitar (since it's really prominent) and all of the sudden you skipped this guitar. Even if you argue that you are following the cymbals, it still feels awkward to have a pause there when there's no pause in the music. I would've liked at least a circle stacked onto 00:23:670 (1) -
01:11:534 - ^ i focus more on the rhythm guitar here, mapping an additional note for the lead would be somewhat awkward and take away emphasis from 00:23:670 - which i consider very important since it marks the song falling back into the earlier pattern

00:36:897 (1,2,3) - why overlap (1) and (3)? it will easily look better if spaced. and why is (1) & (2) aligned while 00:36:625 (1,2) - and 00:36:352 (1,2) - are not? https://i.gyazo.com/09e16055084afd8cf12 ... 457f04.jpg this is consistent with other triangle based patterns as explained in celerih's mod response

04:08:727 (4) - there's no snare here in the music, so should remove drum-normal. like 04:23:727 (4) - there are ghost notes on the snare here so i consider this fitting
04:08:852 - on top of that, not really liking how the actual snare (which is the loudest) is mapped to slider end. the primary emphasis in this section is put on the bass, while the snare might be the loudest it is by no means the most important here

06:21:731 (5,1) - The flow here is really bad compared to the rest of the streams you did. i use the somewhat umcomfortable movement for the difference in emphasis between lead and rhythm guitar, and while this particular instance worked out a bit differently than others i think it achieves the desired effect

07:31:288 (1) - there's no snare on the sliderend. it sounds like a double hit on the snare to me which is one of the reasons i mapped short kick sliders here

07:57:698 (2) - make this a slider? again with the rhythm pauses. same reasoning. it's not required to map everything and rests are a powerful tool for adding emphasis

meh. cool stuff, but I feel like this map could be improved. Feel free to decline everything.
Kroytz
Sorry, gonna have to DQ-mod this. Accept what you will, feel free to deny

Mod
Metadata:
Artist should be Tommy heavenly6 and not Plini
Title should be PAPERMOON and not Paper Moon

That's it. No need to KD me~

Good luck, hope this gets ranked. :)
Topic Starter
Zhuriel
can you maybe not
celerih
Congratz to our favourite software hating baby boy on his first ranked map
BrianTheDrummer
Congrats!! 🌙
jrcrash
Great map! its different. I like that. It is also difficult lol :D
rinkon
wtf! plini song in osu
love it! keep up the good work
Please sign in to reply.

New reply