How Moddria works

If you're modding a map

1. 1

   Make a mod

   Click New Mod and drop the map's .zip in the pop-up. Moddria automatically reads the title, artist, mapper, BPM, cover art, and every difficulty from this zip.

2. 2

   Write feedback on the beat

   Pick a difficulty and add feedback for beats.

3. 3

   Send one link

   Share the mod and the mapper sees everything.

4. 4

   Iterate

   Once the mapper has gone over your mod, you can create a new version to bring up new issues or previous unaddressed feedback.

Writing beats

The box on the left of the feedback bar takes the beat. There are a few ways to write one, and they all come back in the same format once submitted.

Writing several beats at once puts them in one row rather than several, with the beats listed side by side. Click it to expand and work through them one at a time. Adding the same comment at another beat later joins that row too, so a recurring issue stays in one place instead of spreading down the table.

Reusing feedback

The same problem usually turns up more than once. Rather than retyping it, copy what you already wrote.

• One issue: Pick Copy from its menu, or click the row and press Ctrl + C. It goes back into the feedback bar with its label, text and timing fix, ready for a new beat.
• Several at once: Click a row, then shift-click to take everything in between or ctrl-click to pick them out one by one. A bar appears at the bottom with Bulk copy.

Bulk copy asks two things: which difficulties to copy into, and the beat the first issue should land on. Everything after it keeps its spacing relative to that first one, so a run of feedback written once on Expert can be dropped onto Hard starting wherever the same section begins there.

The image button in the feedback bar attaches screenshots, which is usually faster than describing a pattern in words. They show as thumbnails on the row and open full size when clicked.

General feedback

Not everything belongs to a difficulty. Next to the difficulty tabs there is a General tab for feedback about the map as a whole: metadata, the audio, the cover, or something that applies to every difficulty at once.

If someone modded your map

1. 1

   Open the link

   Everything the modder wrote, grouped by difficulty and ordered by beat.

2. 2

   Reply where it happened

   Every item has its own thread. You can directly reply to feedback you do not agree with.

3. 3

   Auto-fix the timing

   For timing feedback, upload your map and Moddria snaps the notes for you, then hands back the fixed difficulty file.

Working through a mod

A full mod can build up to tens of items. Moddria's feedback table is built for iterative fixing, you can fix and check everything off one by one.

Ticking things off

Each row has a checkbox. Tick it once you have dealt with the issue and the counter in the header moves, so you can see how much is left at a glance. Both the modder and anyone they shared the mod with can resolve, and unticking is always possible if you change your mind.

Finding things

The search icon above the table, or Ctrl + Shift + F, opens a bar that searches both text and beats: type a beat and you get the feedback covering it, including ranges that contain it. The same bar filters by label, by Unresolved or Resolved, or down to items that have replies, and sorts by beat, severity, newest or replies.

Edit history

Feedback can be edited after it is posted, and nothing is thrown away when it is. A clock icon appears on any row that has been changed, and opening it lists every past revision with when it was made. The modder can put an old one back with Restore.

Auto-fixing timing

Most timing feedback ends the same way: the mapper opens the editor, finds the beat, moves the note, and repeats it a billion times. Moddria can do that part for you.

Attaching a fix (modder)

When your feedback is about timing, press the Timing button in the feedback bar before adding it. A second row appears where you say what should happen to the objects on that beat:

• Nudge moves them by an amount, written the same way as a beat: 1/8 later, 1/4 earlier.
• Move to puts them on an exact beat instead.

A nudge is relative, so you can list several beats and give them all the same fix in one go. Move to points at one exact beat, so it takes a single beat only.

Ranges work as well, in which case everything inside the range moves together. The fix shows up on the row, so a mapper reading the mod can see the exact change being asked for before applying anything.

Applying it (mapper)

Open a difficulty that has timing feedback on it and press Auto-fix timing above the list. Pick a map source: Current uses the file stored with the mod, which is usually the one you gave the modder, and Own lets you upload an updated zip if you have kept working since. You get a list of every fix with a checkbox, so you can leave out the ones you disagree with, and then download a fixed .dat to drop into your map folder.

Modders don't always indicate beats perfectly, so each fix is marked with how it was matched: exact found objects right on the beat, nearest used the closest ones within the (customizable) tolerance, and not found means there was nothing there to move. Those last ones are worth a look by hand.

Auto-fix can still get things wrong, so back up your difficulties and check the result in the editor before you start replacing stuff.

Versions

A map usually gets modded more than once. When the mapper has been through everything and the modder finds new issues, they can open the version dropdown at the top of the mod and pick Add New Version, choosing whether to carry the still-unresolved items over to it.

Each version keeps its own feedback and its own history. Older ones stay readable so you can point back at what was said the first time round, but they can no longer be edited.

Labels

Every piece of feedback carries a label saying how strongly it is meant. These are the built-in ones:

Custom labels

You are not stuck with those five. In Settings → Labels you can build your own sets, with your own names and colours, and pick which set a mod uses when you create it or from the mod menu afterwards. Useful if you're not strictly an RT member, QAT for example mods maps differently.

A mod keeps a copy of the set it was created with, so editing a set later will not go back and relabel mods that are already shared with people.

Who can see a mod

You can change this at any time from the mod by clicking on 'Share'. There you can add people by their Discord usernames or by sharing invite links with them, each as a Modder or a Mapper.

A Modder writes and edits feedback and can manage the mod itself. A Mapper resolves feedback and replies to it. Only you, as the owner, can change who has access or delete the mod. A Private mod is visible to you and the modders while you work on it. Switch to Restricted when the mappers should see it too.

Marking progress

The modder can put a status on a mod from the dropdown next to its title. It shows on the mod and on its card in the lists, and you can filter by it, which is the quickest way to see which mods are finished and which ones aren't.

People you add to a mod by Discord username are marked Mapper. They can do everything with the feedback except write it: resolve items, reply, and run auto-fix. Anyone who only has the link can read the mod but not change it.