Blueprint

Core Framework Overview

Blueprint functions as the central architecture supporting mods created by TeamAbnormals. Rather than introducing standalone gameplay elements on its own, it unifies underlying logic across multiple releases while welcoming general community development. Third-party modders and enthusiasts are free to integrate its components directly into their independent projects.

Developer APIs and Built-in Utilities

Inside the library, creators gain access to several specialized programming interfaces and gameplay modification systems:

• Registry Helper: Streamlines object and game content registration routines.
• Data Syncing: Facilitates communication and synchronization of data across game boundaries.
• Data-Driven Systems: Enables configurable modification mechanics driven by data.
• Biome API: Supplies tools tailored for manipulating and configuring biome parameters.
• Trim Material API: Provides hooks specifically designed for armor trim customization.
• Endimator Animation API: Powers custom animation logic and visual routines across entities.

TeamAbnormals Ecosystem Integration

The library serves as an essential framework for a diverse catalog of TeamAbnormals releases, categorized into major and minor projects.

Major Dependent Mods

• Atmospheric
• Autumnity
• Buzzier Bees
• Caverns and Chasms
• Endergetic Expansion
• Environmental
• Neapolitan
• Savage and Ravage
• Upgrade Aquatic

Minor Dependent Mods

• Abnormals Delight
• Allurement
• Berry Good
• Boatload
• Clayworks
• Gallery
• Incubation
• Personality
• Pet Cemetery
• Woodworks

Environment Compatibility and Installation

Blueprint operates across the Forge and NeoForge mod loaders, specifically supporting Minecraft versions 1.20.1 and 1.21.1. Look, operating the mod in any environment demands dual installation, requiring the archive to be present on both the client side and the server side.

Workspace Integration Guide

Integrating Blueprint into an external development project involves configuring standard build scripts and loader metadata files.

Gradle Repository and Dependency

Add the official TeamAbnormals repository and library dependency into the build.gradle configuration:

repositories {
    maven {
        url = "https://maven.teamabnormals.com"
    }
}

dependencies {
    implementation("com.teamabnormals:blueprint:<version>")
}

Replace <version> with the corresponding version string combined with the desired Minecraft release.

NeoForge Metadata Configuration

For NeoForge environments, specify the dependency declaration inside the neoforge.mods.toml descriptor to ensure Blueprint loads before your mod on both sides:

[[dependencies.<modId>]]
    modId = "blueprint"
    type = "required"
    versionRange = "[<version>,)"
    ordering = "AFTER"
    side = "BOTH"