Cascade
Find the problems before a modder does
Most of the notes you get on a first mod are not about taste. They are unsnapped objects, a difficulty with no red line, two notes stacked in one column, a long note one millisecond long. Cascade's AiMod sweeps the whole mapset for exactly that class of problem, so the feedback you do get is about the mapping.
Open the editor and run AiModWhat it checks
- Metadata: missing romanised title, artist or creator, and an empty tags field.
- Mapset: no audio loaded, no difficulties, difficulties that share a name, and a set that mixes key counts.
- Timing: a difficulty with no uninherited red line, objects that start before the first timing point, invalid BPM values, duplicate points, and inherited green lines sitting before the first red one.
- Snapping: objects and long note ends that do not sit on the beat grid.
- Notes: concurrent objects in the same column, long notes that end before they start, long notes too short to be playable, and objects in a column outside the key count.
Errors and warnings are not the same
Anything marked as an error will either break the file or get the set rejected: a missing creator, a chart with no timing, a note in column five of a 4K difficulty. A warning is something to look at and possibly keep, like a set that deliberately mixes key counts, or an unsnapped object in a section that is intentionally free.
Jump straight to the issue
Every finding names the difficulty it came from, so a set with eight charts still gives you a list you can work through instead of a wall of text. Fix, re-run, and watch the list shrink.
AiMod checks structure, not taste. It will never tell you a pattern is boring, and it is not a substitute for a real mod.