V11.4

Small fix release: dropping a whole edition and choosing Delete the files no longer deletes songs of your own, and every deletion is now written to a log.

Fixes

• "Delete the files" no longer wipes custom songs. When you untick a whole edition in Select maps / songs and choose Delete the files, V11.3 and older removed the entire maps\<edition> folder - including a custom song you had added there yourself. Now only songs the song server (or the community sheet) knows are deleted. Anything else in that folder - a custom map, other files, sub-folders - is left in place, and so is the folder itself. The prompt says how many songs will really be deleted (instead of "all songs") and tells you that your own songs are never touched. If nothing in the folder is known, nothing is offered for deletion.
• Every deletion is recorded. Each file the prompt deletes - and each file it leaves alone - is added to bin\logs\deleted-files.txt with a timestamp, so if something is ever missing there is a record of what happened. (It is kept separate from the run logs, which are trimmed automatically.)

Both front-ends (GUI and console) behave the same, the new note is translated into all 13 languages, and the README and tutorials describe it.

One thing to know

A modified copy of an official song (for example a custom map you made by replacing adeyyo_pc.ipk) still counts as that official song: updates replace it with the server's file, and "Delete the files" can remove it. Mark it with Keep my version in the song picker to protect it from both. Songs that are not on the server at all (your own custom codenames) are never touched by updates, and no longer by "Delete the files".

Everything else is unchanged from V11.3

Keep my version, the single Delete / Keep / Cancel prompt, the song picker listing editions that are only on the share (3111), the self-update progress window and the update check that no longer hits GitHub's rate limit are all still there. (The tutorial screenshots still say "V11" in the title bar; that is the only difference.)

Upgrading

• From V10 / V11 / V11.1 / V11.2 / V11.3: click the Update Available button. If your network is one that hit the 403 on V10/V11, it may not appear until the hourly limit resets - in that case download LegacyDownloaderV11.4.zip below and extract it over your old folder (keep your config.txt).
• From V9.x or earlier: delete everything in your old install folder except config.txt, then extract this zip into that same folder.

Getting started

1. Download LegacyDownloaderV11.4.zip below and extract it anywhere.
2. Double-click LegacyDownloader-GUI.bat.
3. Follow the on-screen setup - or open the tutorial for a full walkthrough.

Requirements

Windows with PowerShell 5.1 (built into every modern Windows install). Nothing else to install - rclone.exe ships inside the zip (its license notice is in THIRD-PARTY-NOTICES.txt).

Antivirus note

Some people's Windows Defender has flagged a release zip as a trojan shortly after it was published (a cloud "reputation" detection on a brand-new file). It is a false positive: the zip contains only the PowerShell scripts in this repository, language files, an icon, two .bat launchers, and the official rclone.exe. You can verify the download against the SHA-256 shown next to the asset on this page, or read the source in this repository first.