Skip to content

Configuration

Jump to bottom
Ghost edited this page Apr 10, 2026 · 1 revision

Config File Location

The config file is created automatically on the first launch at:

<your minecraft directory>/config/autodownload/downloads.json

Top-level Fields

Field Type Description
showPromptOnFirstLaunch boolean Reserved for future use. Leave as true.
promptShown boolean Managed automatically by the mod. Do not edit.
files array List of file entries to check on every launch.

The type field is case-insensitive — "Mod", "mods", and "MOD" all work the same way. Unrecognised values fall back to mod.

How fileName Works

When checking for an existing file and when saving a download, the mod resolves the file name using this priority order:

  1. fileName is set — uses that value. If it has no extension, the default extension for the type is appended automatically.
  2. fileName is blank, URL has a filename — the name is taken from the end of the download URL (e.g. https://example.com/files/coolmod-1.2.jar → coolmod-1.2.jar).
  3. URL has no usable filename — falls back to a sanitised version of name plus the default extension.

If a file with the resolved name already exists in the target folder, the mod considers that entry satisfied and will not prompt for it.

If two downloads would produce the same file name, the newer one is saved as filename (1).jar, filename (2).jar, and so on.

Automatic fileName Saving

When fileName is left blank and a download completes successfully, the mod writes the saved file name back into downloads.json automatically. On future launches it uses that stored name to check for the file, making the lookup faster and more reliable.

You will notice your config updating itself after a first-time download — this is expected behaviour.

Comments in the Config

Lines starting with // or # are stripped before the file is parsed, so you can freely annotate your config:

// Core mod required for the pack
{
  "name": "Transit Mod",
  "link": "https://example.com/transit.jar",
  "type": "mod",
  "fileName": ""
}

Full Example

{
  "showPromptOnFirstLaunch": true,
  "promptShown": false,
  "files": [

// --- Mods ---
{
  "name": "Sodium",
  "link": "https://example.com/mods/sodium-fabric-0.5.3.jar",
  "type": "mod",
  "fileName": "sodium-fabric-0.5.3.jar"
},

// --- Resource Packs ---
{
  "name": "My Texture Pack",
  "link": "https://example.com/packs/mytexturepack.zip",
  "type": "resource_pack",
  "fileName": ""
},

// --- Shader Packs ---
{
  "name": "Complementary Shaders",
  "link": "https://example.com/shaders/complementary.zip",
  "type": "shader_pack",
  "fileName": ""
},

// --- World Saves ---
{
  "name": "Starter World",
  "link": "https://example.com/worlds/starter.zip",
  "type": "saves",
  "fileName": "starter.zip"
}



]
}

Common Mistakes

File keeps showing as missing even though I downloaded it manually. Set fileName to the exact name of the file on disk, including the extension. Without it, the mod may look for a different name than what you have saved.

The mod downloaded the file but used the wrong name. Your URL probably doesn't end with a readable filename. Set fileName explicitly to control what it saves as.

I added an entry but nothing happens. Make sure link is not blank. Also confirm type is one of the four supported values — an unrecognised value silently falls back to mod and saves to the wrong folder.

Clone this wiki locally