
Configured Defaults in FTB Skies 2: Aero
FTB Skies 2: Aero 1.13.0 ships version 21.1.3 · First seen in 1.0.3
Configured Defaults is a mod in FTB Skies 2: Aero 1.13.0, where it is version 21.1.3. Allows for providing defaults for files absent in .minecraft like configs. A quintessential modpack utility. (Summary from the mod's Modrinth page.)
Configured Defaults guide for FTB Skies 2: Aero
Last verified for FTB Skies 2: Aero v1.10.0 on Oct 7, 2026 · text last changed Oct 7, 2026
This is the newest guide. It hasn't been checked against 1.13.0 yet.
Also applies to:FTB Evolution 2 1.0.2 to 1.4.0FTB Skies 2 1.13.0 to 1.24.0FTB StoneBlock 4 1.1.1 to 1.23.0
- Sections
- 4
1 section is written for this pack; 3 are shared from another pack's guide.
Every recipe and number here was checked against FTB Skies 2: Aero 1.10.0, read from the running game on Sep 22, 2026.
What is Configured Defaults?
3 parts
Same as in the FTB Skies 2 1.22.0 guide
Configured Defaults is a small utility mod for modpack makers. It copies files and folders that are missing from the game or server directory out of a folder called configureddefaults. Nothing gets overwritten, because it only fills in what isn't there yet.[1]
Its main job is shipping default config files. When a pack update adds a new mod, you get the config the pack author intended, instead of the mod generating its own defaults on first launch.[1]
What it can handle
- Any file or folder in the game directory, so it's useful for far more than configs.[1]
- The options.txt file gets special treatment. Your existing file isn't replaced. Missing entries are merged in from the default version, so new settings arrive and your own preferences stay put.[1]
Who it is for
This one is mainly for pack authors and server admins. As a player you'll rarely touch it. It works in the background when the game starts. Installing it is optional on both client and server.[1]
If you do want to use it yourself, the mod writes a README.md into its configureddefaults folder after the first run with the mod installed. That file holds the detailed usage instructions.[1]
In this pack
The pack ships Configured Defaults 21.1.3, built for NeoForge on Minecraft 1.21.1.[2]
Unverified No quests, guidebook entries or ATM Star path steps for this mod were found. It looks like a behind-the-scenes utility, not part of the progression you play through.
How do you get started with Configured Defaults?
3 parts
Same as in the FTB Skies 2 1.22.0 guide
Good news: there's nothing to craft here. Configured Defaults is a utility mod for modpacks, so you won't be making items or following a build order with it. It works quietly in the background.[1]
What it does for you
The mod automatically copies missing files and folders into the game or server directory from a default location, the configureddefaults folder. Pack makers use it to ship default config files. When a mod is added in an update, you get the intended configuration instead of the mod generating its own defaults on first launch.[1]
It isn't limited to configs. It supports any file or folder in the game directory.[1]
Your options.txt is safe
The options.txt file gets special handling. Instead of replacing your existing file, the mod can merge in missing entries from the provided default version. New settings can show up while your own preferences are kept.[1]
If you run a server or tweak the setup
- Installation is optional on the client and optional on the server.[1]
- Further instructions are in configureddefaults/README.md, which generates after the game has run for the first time with the mod installed. Read that file first if you want to add your own defaults.[1]
Unverified The sources I have don't show which specific files this pack ships as defaults, and they don't confirm any items, recipes or quests tied to this mod. Don't expect to find any of those in-game.
How does Configured Defaults work?
3 parts
Same as in the FTB Skies 2 1.22.0 guide
Configured Defaults is a modpack utility, not a content mod. The only thing the sources describe is file handling, so there are no machines, multiblocks, power, fluids or item automation to cover here. What it does is simple, and it matters a lot for how this pack's files reach you.[1]
What the mod does
On launch, the mod copies missing files and folders into the game or server directory. It takes them from a default location, the configureddefaults folder. If a file is already in your game directory, the sources describe the mod only as filling in what is absent.[1]
The main purpose is to help modpack creators ship default configuration files. This helps most when an update adds a new mod. You get the configuration the pack author intended instead of whatever that mod would generate on its first launch.[1]
It isn't limited to configs. The mod supports any file or folder within the game directory.[1]
How options.txt is handled
The options.txt file gets special treatment. The mod doesn't replace an existing file. Missing entries can be merged in from the provided default version. New settings can be added while your existing preferences are preserved.[1]
Client and server
Installation is optional on both the client and the server.[1]
Unverified The exact rules for what counts as a missing file, how the defaults folder is laid out, and how the options.txt merge works in detail are not covered by the available sources. This pack also has no config files for the mod, so none are listed here.
What changed in Configured Defaults between versions?
FTB Skies 2: Aero 1.10.0 ships Configured Defaults 21.1.3, the NeoForge build for Minecraft 1.21.1. It was already in the pack by version 1.0.3, so it has been there from the early releases.[3]
There are no pack changelog entries for this mod, so here is what the mod's own changelog lists, from oldest to newest.[4]
- v21.1.0 (2024-09-18): the port to Minecraft 1.21.1.[4]
- v21.1.1 (2024-12-28): special handling for the options file was added. Missing entries in an existing options file are now complemented. It also fixed a dedicated server crash on Fabric.[4]
- v21.1.2 (2024-12-30): fixed a start-up crash on Fabric.[4]
- v21.1.3 (2025-01-06): fixed custom options.txt handling that could lead to an invalid file because some strings were parsed incorrectly. This is the version in the pack.[3][4]
Sources
- Configured Defaults project page (modrinth) · official mod data
- FTB Skies 2 1.22.0 mod list · pack file
- FTB Skies 2: Aero 1.10.0 mod list · pack file
- Configured Defaults 21.1.3 changelog · changelog
Where this guide comes from
Written from what FTB Skies 2: Aero itself ships: its files and recipes, the in-game guidebooks and the mods' own pages. Every statement links to the source it came from, and the numbers are checked against the pack before publishing.
Guide last verified Oct 7, 2026.
Report wrong info
Version in each release
21 releases, first in 1.0.3
| FTB Skies 2: Aero | Version | Jar | Where it came from |
|---|---|---|---|
| 1.13.0 Sep 28, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.12.1 Sep 22, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.12.0 Sep 21, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.10.0 Sep 8, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.9.1 Sep 2, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.9.0 Sep 1, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.8.0 Aug 25, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.7.3 Aug 19, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.7.2 Aug 18, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.7.1 Aug 18, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.6.1 Aug 13, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.6.0 Aug 11, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.5.1 Aug 8, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.4.1 Aug 4, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.4.0 Aug 3, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.3.0 Jul 30, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.2.1 Jul 28, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.2.0 Jul 28, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.1.1 Jul 25, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.1.0 Jul 24, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
| 1.0.3 Jul 17, 2026 | 21.1.3 | ConfiguredDefaults-v21.1.3-1.21.1-NeoForge.jar | From the published release |
"From pack files" means the list came from the pack's own files; "from the published release" means ForgeBase read the jars of the release itself.
Items and blocks
We can't match this mod to the pack's item list: it registers as configureddefaults, and the pack's recipe dump has nothing under that name. That means we found nothing, not that the mod adds nothing. Search the item browser
Comments and tips
Loading comments...