Guide how to create a good catch chart (Beta ver.)

Catch mode in malody is optimized for mobile gameplay, so we don’t consider what happen to users who play catch on malody at pc. We don’t have any similiarities toward osu!catch in terms of mapping techniques as osu! is pc oriented while malody is mobile oriented gameplay.

--------------------------------------

Mapping on catch malody most of time aimed toward one finger player. Make everything is jumping because sounds difference isnt good idea.

--------------------------------------

Also try to enable key sound on setting, and set the custom key sound. This stuff help you make map catch chart better.

--------------------------------------

For further info, join discord server "Malody Catch". Almost all of our stable process visible there, we are doing very transparent check before stable a map. The link for join you can find here.

--------------------------------------

Catch chart stable list link can be found here.

Important stuff

1. Usage of drop speed

2. Salad and cup cannot have dash notes. Platter could have dash note but only in extreme cases.

3.Don’t use the copy paste feature in the catch editor

4.Note color changes when you use different snap timing on catch

5. Add + on your chart version name if you use double notes

6. When mapping high difficulty such as rain or harder, you may not skipping the difficulties below it unless theres specific reason

Tips on mapping catch. (Guidelines)

1. Try to be consistent when mapping.

2. Usage of Dash Notes

3. Guidelines regarding specific difficulties on catch

4. Try to spread note placement when mapping catch

5. Try to start and finish "rain" on white/blue line when using it

Adressing the jump issue and offset

Offset Issue

Personally (Yes its personal), the offset should be checked thoroughly from now. Any uncertainty indicated multi bpm or low quality audio need to be proved whether its right or not. This is actually general stable rules. Just because it sounds *right* doesnt mean its right. Some song such as *black rover*, the song actually sounds right but it has multiple small bpm change should be follow correctly.

Any blatantly disregard of those would be mean disrespect toward the music itself.

Jump Issue

This issue are related to playability of the chart. Personally, i wouldnt care about it because every mapper has different mapstyle and such representation of music with multitude jump are ok as long we understand the reasoning.

As checker stance here, we also sometimes overlook the playability of chart (just check with editor and watch with auto not playing directly). Mapper need to check their own "playability". You can do it by playing it directly and feel how it is or ask people to testplaying and see their opinion.

A chart with high playability (comfortable to play) would be loved by people, and has a lot smaller chance being disliked.

I would prefer simple chart any day than playing hard map that i had no idea what it is doing.

Overmap Issue

This issue is very easy to trigger. Personally, you need to truly assess the music, don't aim for the max amount of combo. That is a very bad approach. If the music itself sounds like for example, LN for Key, you need to truly access if what you're expressing for that sound is accepted.

Comparing it to o!ctb and creating "stream" for a long sound without any other sound to guide you isn't correct. o!ctb has droplets. We don't have that, so it doesn't make sense to express it as if you were just putting note mindlessly. Common overmapping is using ghost notes, if you need more guidance, join the Catch group.

Editors

Sign inX

Sign in

Forgot Password? Register

Wait...