Also, adding to that, if beatmaps only "reflected" the song, then maps like Can Do, Nandemo nai ya, Transform, would not have existed. Mapping isn't limited to just reflecting music. It is also about interpreting music, creating variance, and most importantly, introducing gameplay elements to the music. You map a song because you want to create a fun gameplay experience for the player. If your objective is to construct a map that embodies the song perfectly, good for you, but you've lost the game element of mapping. In any case, my decisions for flow changes, spacings, patterns, are not created because I think using a triangular pattern will emphasize the music better. They are born from my decision that using this specific movement will play well, or that switching movement will allow specific patterns to be more interesting to play. Your argument is that I am not following consistency fully. My argument is that there is no need to follow consistency fully. If you look at my map, I already do so for a good 80-90% of it.
You told me before, that you wished you could map something that people will remember you by. Perhaps you should take from my perspective instead and not just produce maps that reflect the song, but rather maps that make an otherwise boring song interesting or fun. If you reflect a boring and unmemorable song, your map will be equally boring and unmemorable because that's what you've reflected.
You told me before, that you wished you could map something that people will remember you by. Perhaps you should take from my perspective instead and not just produce maps that reflect the song, but rather maps that make an otherwise boring song interesting or fun. If you reflect a boring and unmemorable song, your map will be equally boring and unmemorable because that's what you've reflected.