Skip to main content
← All Guides
Modpack Hosting · 4 min read

How to Use BluePrint Configs for Modpacks

Guide to using BluePrint configs for modpacks, covering the BluePrint library, common configuration options, data pack integration, and per-mod overrides.

What Is BluePrint?

BluePrint (formerly Abnormals Core) is a shared library mod used by Team Abnormals and other mod developers as a foundation for their Forge and NeoForge mods. If your modpack includes mods like Autumnity, Atmospheric, Buzzier Bees, Upgrade Aquatic, or Endergetic Expansion, you are running BluePrint. Understanding blueprint configs modpacks use lets you fine-tune these mods without digging through individual mod settings blindly.

BluePrint provides common configuration hooks that apply across all mods built on it. This means changing one BluePrint setting can affect multiple mods simultaneously, which is powerful but also means you need to understand what each option does.

Where to Find BluePrint Configs

BluePrint configs live in config/blueprint-common.toml (or .cfg on older versions). The file is generated on first server boot. Additional per-mod configs are created in config/ under each mod's own filename. When working with blueprint configs modpacks include, check both the BluePrint common config and the individual mod configs.

Key Configuration Options

The BluePrint common config controls several cross-cutting features:

  • Quark compatibility flags. BluePrint has built-in hooks for Quark. If Quark is in your modpack, these flags control how BluePrint mods interact with Quark's features like variant chests, signs, and boats.
  • Data pack overrides. BluePrint mods often register their content through Minecraft's data pack system. You can override recipes, loot tables, and world generation by creating a data pack that targets the mod's namespace.
  • Spawn weight adjustments. Many Team Abnormals mods add new animals and creatures. The blueprint configs modpacks rely on include spawn weight settings that control how often these creatures appear. Reducing spawn weights is one of the easiest performance wins on entity-heavy servers.

Customizing Individual Mods

Each mod built on BluePrint has its own config file. For example, Atmospheric has settings for its biome generation, tree types, and crop growth rates. Upgrade Aquatic lets you toggle individual sea creatures and adjust their spawn rates. The pattern is consistent: find the mod's config file in config/, open it, and look for clearly labeled sections.

When adjusting blueprint configs modpacks ship with, always restart the server after making changes. Most BluePrint config values are read at startup and are not hot-reloadable. If you change a spawn weight and do not see the effect, check that you restarted rather than just reloading.

Data Pack Integration

BluePrint mods register recipes and loot tables through Minecraft's data pack layer. This means you can override any recipe by creating a data pack with the same namespace and path. Place custom data packs in world/datapacks/. This approach is cleaner than editing config files because it uses Minecraft's native override system and is easy to share or version-control.

For example, to disable a specific BluePrint mod recipe, create a data pack that replaces the recipe JSON with an empty recipe. This keeps your config files untouched and makes updates easier because you do not need to re-merge configs when the modpack updates.

For broader modpack customization topics, see our guide on adding mods to existing servers and disabling mods without removing them.

Host your modpack on Astroworld Hosting, NVMe SSDs, full panel access, 24/7 support.

Related Tools & Resources

🔧

Minecraft Tools

Calculators, generators & server tools

🧱

Item Database

Browse all Minecraft items, stats & recipes

⚒️

Crafting Recipes

Visual crafting guides for every recipe