• Time & Patience
  
• A text editing software (e.g.Notepad++)

Before you start make sure to set "Cache track data" to "Yes" in Melody's Escape and load up your song at least once, so that a .track file is generated

Windows
The files you will need to locate are in the "%AppData%\MelodyEscape\TracksCache" folder (without the quotes).

Linux
The files you will need to locate are in the "$HOME/.config/MelodyEscape/TracksCache/" folder (without the quotes).

Mac
Coming Soon™

(I don't play on Mac, so anyone who knows where the files are, please tell me so I can add it to the guide)

This is generally what a .track file looks like


The name of the file is represented in the folowing way:

[Synchronization method]_[Difficulty]_[Song Filename].track

Synchronization method used to generate the file.
EP - Energy Peaks
TEMPO - Tempo (who would've thought)

Difficulty used to generate the file. Depends on the Synchronization method.
For Tempo:
1 - Relaxing
2 - Medium
3 - Intense
4 - Overload

For Energy Peaks:
1 - Relaxing & Medium
2 - Intense
3 - Overload

Your song's filename.

The file contains 4 lines each with specific values.
Values are separated with a semicolon(;)
The last value doesn't need a semicolon after it.

Version of the algorithm used to make the file.
When it's lower than the current version tells the game to generate a new one.

Current Version:1.02

Song data

General data regarding the song you are playing

1. Total gametime in game ticks.
   That is from the begging of the song to its end.
   The game runs at 44100/1024 ticks per second.
   The reason for this number is that the audio uses 44,1 kHz sample rate and every 1024 samples is a gametick.
   
   
2. Song lenght in seconds
   From the begging of the song to its end in seconds.
   
   
3. BPM/Unknown
   This depends on the syncronization method the game used.
   
   In "Tempo" mode this value shows the BPM of the song.
   In "Energy Peaks" mode I do not know.
   (If anyone does please tell me, so I can add it.)
   
   
4. Tempo analysis confidence
   How well the game detected the tempo of the song.
   
   1 - No stable 4/4 tempo detected
   Causes the game to use "Energy Peaks" as Synchronization Method.
   
   
   2 - Acceptable
   Uses "Tempo" as a Synchronization Method but don't expect it to be perfect.
   
   
   3 - Good
   Uses "Tempo" as a Synchronization Method.
   Gives good results.
   
   
   4 - Excellent
   Uses "Tempo" as a Synchronization Method.
   Most of the obstacles will be perfectly synchronized to the music.
   
   

Intensity Changes

Each value in this line shows when an intensity change is happening. They are represented in the following way:

[Ending Intensity]:[Gametick]-[Beggining Intensity]:[Gametick]

Example - Changing from Walking to Jogging one second into the song looks like this:
L:43-N:85

NOTE: A track always starts and ends in Walking Intensity and must have at least 1 gametick duration.

Intensity Table

Keep in mind that when changing intensities there's a difference between the ending gametick and the beggining one. This is done so that there's no obstacle detection between the changes.

Intensity Change Table

Obstacle Data

Each value in this line shows when there's an obstacle and what is it. They are represented in the folowing ways:

[Gametick]:[Obstacle]
[Gametick]:[Obstacle]-[Duration]

The first way is for an obstacle where only a press is needed.
The second one is for an obstacle where a press+hold is needed.

Obstacle Table

It doesn't work and it will cause Melody's Escape to generate a new file.

In Walking intensity they are perfectly fine. In all other intensities they work as expected, however they are not showing trails so you have no way of knowing when they have to be held down.

Jogging
Adds a little slope similar to Press+Hold Right Arrow

Running

Flying

The hold detection stops when the Intensity change begins.

They appear as normal Up Arrow Obstacles without slow-motion.
On the loading screen they appear with the blue dashed line.

It doesn't work as you would expect.
The hold detection stops when you reach the first Orb.
This causes graphical glitches.

The appear as normal orbs with the same direction (e.g. Up Arrow becomes Up Orb).

The built-in manual sync song tracks are hardcoded into the game. There is currently no known way to get your track files to say that they are built-in manual sync.

Thanks to Quadropillar for this one.
When obstacles begin within 4 gameticks of each other the game does not render the first one, but still requires input for it.

To anyone who's gotten this far: I hope this guide has helped you in your endeavours and thank you for reading.

If you know something that needs to be added to this guide feel free to tell me.

2016-12-19

• Added Linux Folder
  
• Changed gametick counter to real one confirmed by developer
  
• Added Built-in Manual Sync explanation under Non-standard Behaviours
  
• Changed TODO Section to Change Notes

2018-02-10

• Fixed spelling mistakes

2018-11-18

• Fixed grammar mistakes
  
• Added info about obstacles less than 5 gameticks away from each other. (Thanks to Quadropillar)