Rhythia Map Editor Guide: Build, Test, and Export a Playable Map

A Rhythia map can look convincing in the editor and still fail the first real playtest for one of three reasons: the first beat is offset, the BPM drifts, or the cursor movement says something different from the music. Fix those in that order. More notes will not rescue a bad timing base, and a clever pattern will not rescue a route that cannot be read at speed.

This workflow follows the in-game Map Editor added on June 1, 2026. Rhythia is still in Early Access, and the developer described that first editor release as unfinished, so treat button names and import support as a July 21 source snapshot. If the current client differs, keep the diagnostic method below and follow the controls shown in your build.

Enter the editor with one musical promise#

Open Map Editor from Rhythia’s main menu. The launch announcement confirms that route; older instructions for a separate Sound Space Quantum Editor describe a different tool and should not be used to locate the current in-game editor.

Before placing a note, write one sentence about what the map will ask the player to follow. Examples include a steady kick-and-snare exchange across the grid, a vocal melody traced through compact turns, or a high-difficulty stamina section built around repeated streams. This is not flavor text. It decides which sounds become notes and which sounds remain musical context.

The post-launch community editor reference lists common audio inputs including WAV, MP3, OGG, and FLAC, plus several map-oriented formats. Import support can change during Early Access, so use the file picker in the current build as the authority. If one encoding fails, convert from a lawful source to a normal WAV or OGG outside the game instead of renaming the extension.

Fill the metadata while the choice is fresh:

• Artist and title identify the recording, not the map concept.
• Mapper identifies the chart author.
• Description can state the musical focus, unusual timing, or intended skillset.
• Difficulty is a promise about readability and permitted pattern language, not a reward for note count.
• Custom difficulty, if still present in the current editor, changes the displayed label; it does not repair an inaccurate base rating.

Prove the offset before judging the BPM#

Offset answers one question: where does the musical grid begin? Pick the first stable sound that belongs to the chart, not necessarily the first audible noise in the file. A pickup vocal, fade-in, or loose cymbal can occur before the beat you actually want to anchor.

1. Enable the waveform if the current editor offers it, then lower playback speed.
2. Find the attack of the first dependable beat and place the first timing point there.
3. Turn on the metronome and replay only the opening phrase.
4. If every click is early or late by roughly the same amount, move the offset. Do not change BPM yet.

The in-game editor reference describes an Add point control with offset and BPM values, plus a way to push selected timing points. It also documented osu! timing import in the June build. Imported timing is a starting hypothesis, not proof: audio files can have different silence, edits, or encoders even when the song title matches.

Use drift to separate a BPM error from an offset error#

Once the first click lands, play farther into the song. A wrong offset stays wrong by a similar amount. A wrong BPM grows farther from the beat as time passes. That difference is the most useful timing test in the whole editor.

What the metronome does	Likely cause	Next action
Starts early and stays early	Offset is too small	Move the timing point later, then replay the opening.
Starts late and stays late	Offset is too large	Move the timing point earlier without touching BPM.
Begins aligned, then gets progressively early	BPM is too high	Lower BPM slightly and test a longer section.
Begins aligned, then gets progressively late	BPM is too low	Raise BPM slightly and test a longer section.
Holds, then breaks at one musical change	Tempo change, syncopated reset, or edited audio	Add a justified timing point at the change; do not scatter fixes across individual notes.

Change the song divisor only after the base beat is stable. A higher divisor creates more legal placement lines between beats; it does not make the timing more accurate. If the waveform and metronome disagree with a note you want to emphasize, first decide whether that sound is deliberately syncopated. Do not bend the whole timeline around one off-beat accent.

Map one phrase as sound, movement, and difficulty#

A useful first phrase contains enough information to expose the map’s design: one repeated sound, one transition, and one point of emphasis. Eight or sixteen bars are usually more informative than charting the entire intro before a playtest.

Evaluate that phrase in three layers:

1. Sound selection: every placed note should correspond to something the player can hear. Not every audible layer needs a note.
2. Movement: the route between notes should express the phrase without forcing blind travel. A strong accent can justify a larger jump; a quiet repeated texture usually cannot.
3. Difficulty: density, spacing, divisor, off-grid placement, and reading load must agree with the selected label.

Rhythia’s official mapping material calls these concerns song representation and execution. Representation asks whether the chart communicates the music. Execution asks what the player must physically read and perform. When they conflict, repair execution first: a musical idea that cannot be understood from the playfield is not being represented successfully.

Give Select, Brush, and Path separate jobs#

The June in-game editor reference documents three central tools. Use them deliberately instead of treating them as three ways to place more objects.

• Brush is for individual decisions: a single accent, the start of a motif, or a note whose position needs to be heard and judged on its own.
• Path is for a controlled sequence between at least two points. Set its length and beat divisor to the rhythm first, then shape the motion. More path notes are not automatically a smoother or better phrase.
• Select is for revision. Move, copy, paste, flip, rotate, or scale a group only after the source pattern already works.

The captured editor maps Q/W/E to the top row, A/S/D to the middle, and Z/X/C to the bottom; the numpad is an alternate placement grid. Use one input scheme consistently during the first pass. Switching between mouse placement and keys without checking the timeline can create visually plausible notes on the wrong subdivision.

The same reference warned that its June build did not yet provide undo and redo. That may change. Test the current client’s undo command on a disposable note before making a large transform. If it does not restore the change, save a versioned checkpoint before each bulk edit.

Transform a motif without erasing its logic#

Horizontal and vertical flips, rotation, scale, and paste transforms can make a returning phrase recognizable without making it identical. The test is not whether the result looks different in the editor. Ask whether the same sound-to-movement rule is still visible to the player.

Anchor choice changes what stays fixed while a selection transforms. A shape anchor preserves the group’s own center; a square or playfield anchor relates it to a larger frame. Preview the first and last note after every rotation or scale. A selection can remain inside the editor canvas yet create a sudden cursor crossing that the music never announced.

Use unclamped or Quantum placement only when the current difficulty and musical idea justify it. Off-grid freedom increases the number of possible routes, but also increases reading cost. The official difficulty guidance keeps Easy on the regular 3×3 grid, allows controlled Quantum use at Medium, keeps off-grid notes out of Hard, and reserves broader off-grid language for higher categories. Those are guardrails, not a formula: actual difficulty also depends on speed, spacing, pattern complexity, and readability.

Run three playtests, each with one purpose#

Do not try to judge sync, readability, and stamina in the same run. A failed run should identify one defect, not produce a vague feeling that the map is wrong.

1. Timing pass: slow the song, keep the metronome on, and watch for constant displacement versus growing drift. Ignore score.
2. Reading pass: return to normal speed and play without looking ahead in the editor. Mark the first place where the intended motion becomes ambiguous.
3. Difficulty pass: play from a cold restart. Check whether density, cursor travel, recovery time, and repeated strain fit the chosen category across the whole section.

The editor’s 3D or play view is useful because it reveals approach distance and movement from the player’s perspective. Approach Rate and Spawn Distance affect how the chart is presented, so avoid compensating for a hard-to-read pattern with a personal display setting that other players may not share.

Rate the hardest sustained demand, not one spike#

A single jump can be an accent. A repeated jump becomes a skill demand. Rate the map by what the player must sustain and read, while also checking isolated spikes that could make the label misleading.

Use the official category guidance as a rejection test:

• If an Easy map needs off-grid reading, it is not behaving like Easy.
• If a Medium map depends on dense, high-divisor Quantum movement, simplify the idea or move the rating upward.
• If a Hard map uses off-grid notes, bring the pattern back onto the grid or reassess the category.
• At LOGIC? and above, a named skillset does not excuse messy movement. High difficulty still needs a readable rule.

Official guidance gives approximate BPM bands for some higher categories but also says pattern difficulty and readability can move the practical boundary. Do not turn those bands into an automatic rating calculator. A 200 BPM stream and a 200 BPM sequence of wide jumps do not ask the same thing from the player.

Export a playable file and preserve an editable checkpoint#

When the complete map survives all three passes, use Export RHM. The captured Windows workflow places exports under C:Users<user>AppDataRoamingCapoRhythiaexports; macOS and Linux locations may differ, and a later build may expose the folder directly.

Do not treat the appearance of an exported file as the final test:

1. Close or leave the editor in the normal supported way.
2. Import or open the exported RHM as a player would.
3. Confirm audio, cover, metadata, timing points, difficulty, and the last mapped section.
4. Keep a separate editable checkpoint before upload. An exported play file should not be your only recoverable copy.

Uploading to the community and receiving a ranked state are separate events. Publication proves that the file was accepted, not that its timing, difficulty, or mapping choices satisfy current ranking criteria. Use the current Rhythia portal and current moderation guidance for submission; the supplied old portal route now renders as a JavaScript shell to a non-interactive fetch, so this guide does not invent an upload form or approval sequence.

When the result feels wrong, repair the earliest broken layer#

Failure signal	Repair first	Do not do yet
The whole opening feels late	Offset	Move every note by hand.
The ending is off but the opening is clean	BPM or a later timing point	Add random local offsets.
The chart is on beat but hard to follow	Cursor route, spacing, and pattern contrast	Lower playback speed and call the problem solved.
A copied chorus feels lifeless	Transform only the sounds that actually changed	Replace the entire section with unrelated patterns.
The label seems too low	Sustained density, off-grid use, and reading load	Rate from note count alone.
The export opens without expected content	Metadata, audio reference, final timing point, and saved checkpoint	Upload another copy of the same unverified file.

The fastest reliable route through Rhythia’s editor is not to map faster. It is to make each layer earn the next one: timing earns notes, notes earn movement, movement earns difficulty, and a clean restart earns the export.

Sources & credits#

The official Rhythia Steam listing and appdetails establish AppID 2250500, Capo Games’ developer/publisher credit, the February 20, 2026 Early Access release, level-editor support, and both original 1920×1080 JPEG assets used here. The developer’s Steam announcement feed dates the in-game editor to June 1. Timing diagnosis, the representation/execution distinction, and conservative difficulty checks were reconciled with the Rhythia mapping wiki. A readable Steam Community reference posted after the editor update supplied current control labels; the thin RP, skin, general-keybind, and old-import pages did not expand the article.