Essential hooks for modding with Fabric.
Find a file
Technici4n a025543665 Model Loading API v1 (#3145)
This PR deprecates and supersedes the old `fabric-models-v0` module.

## Refactors compared to v0
### Model loading hooks
Mods now register a single `ModelLoadingPlugin` for any change they want to make to the model loading process. (Or multiple plugins if they want to). This replaces the old `ModelLoadingRegistry`.

Here is an example:

```java
ModelLoadingPlugin.register(pluginContext -> {
    // ResourceManager access is provided like in the v0 API, but in a central place, and can be used for shared processing in the plugin.
    ResourceManager manager = pluginContext.resourceManager();

    // Model resource providers still exist, but they are called model resolvers now
    pluginContext.resolveModel().register(context -> {
        // ...
    });
});
```

#### `ModelVariantProvider` -> `BlockStateResolver`
`ModelVariantProvider` was heavily reworked, and is now replaced by the `BlockStateResolver`, with a much better defined contract.

#### `ModelResourceProvider` -> `ModelResolver`
The resource provider is mostly unchanged. The biggest difference is that it is now registered as an event listener. This allows mods to use event phases for ordering between conflicting ~~providers~~ resolvers.

#### Removed custom exception
Additionally, `ModelProviderException` could be thrown by a variant or resource provider in the v0 API. This was not explained in the documentation, and would according to the code stop further processing of the providers and log an error.

In the new API, any `Exception` is caught and logged. If that happens, the other resolvers are still processed. There is no custom `Exception` subclass anymore.

### Helper method to get a `BakedModel` by `Identifier` from the manager
The v0 had such a method in a helper class: `BakedModelManagerHelper#getBakedModel`. It is now interface-injected instead. See `FabricBakedModelManager`.

## New model wrapping hooks
New hooks are added for the various needs of mods that want to override or wrap specific models. Thanks to @embeddedt for contributing an initial version of them!

Here is an example of wrapping the gold model to remove the bottom quads, for example:
```java
ModelLoadingPlugin.register(pluginContext -> {
	// remove bottom face of gold blocks
	pluginContext.modifyModelAfterBake().register(ModelModifier.WRAP_PHASE, (model, context) -> {
		if (context.identifier().getPath().equals("block/gold_block")) {
			return new DownQuadRemovingModel(model);
		} else {
			return model;
		}
	});
});
```

There are 3 events, for the following use cases:
- Wrapping `UnbakedModel`s right when they are loaded. This allows replacing them entirely in dependent models too.
- Wrapping `UnbakedModel`s right before they are baked. This allows replacing them without affecting dependent models (which might not be expecting a model class change).
- Wrapping `BakedModel`s right when they are baked.

Multiple mods have implemented their own version of them. Providing them in Fabric API will make it easier on these mods, and will additionally allow optimization mods that perform on-demand model loading to simply fire the hooks themselves instead of working around injections performed by other mods.

Co-authored-by: embeddedt <42941056+embeddedt@users.noreply.github.com>
Co-authored-by: PepperCode1 <44146161+PepperCode1@users.noreply.github.com>
Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
Signed-off-by: modmuss50 <modmuss50@gmail.com>
2023-07-18 13:16:17 +01:00
.github Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
deprecated Model Loading API v1 (#3145) 2023-07-18 13:16:17 +01:00
fabric-api-base Terminally deprecate EventFactory isProfilingEnabled and invalidate (#3050) 2023-05-14 14:56:20 +01:00
fabric-api-lookup-api-v1 Split test mods into client and common. (#3033) 2023-05-01 13:55:19 +01:00
fabric-biome-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-block-api-v1 Fix block api resources path (#2749) 2022-12-23 13:37:29 +00:00
fabric-blockrenderlayer-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-client-tags-api-v1 Add support for partially synced client tags (#3118) 2023-07-03 13:13:13 +01:00
fabric-command-api-v2 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-content-registries-v0 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-convention-tags-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-crash-report-info-v1 Rename and validate Mixin class names. (#2450) 2022-08-15 18:59:19 +01:00
fabric-data-generation-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-dimensions-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-entity-events-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-events-interaction-v0 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-game-rule-api-v1 23w04a 2023-01-24 16:59:43 +00:00
fabric-gametest-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-item-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-item-group-api-v1 Add vi_vn.json (#3167) 2023-07-03 13:12:01 +01:00
fabric-key-binding-api-v1 Split test mods into client and common. (#3033) 2023-05-01 13:55:19 +01:00
fabric-lifecycle-events-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-loot-api-v2 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-message-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-mining-level-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-model-loading-api-v1 Model Loading API v1 (#3145) 2023-07-18 13:16:17 +01:00
fabric-networking-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-object-builder-api-v1 Add builders for BlockSetType and WoodType to replace registries (#3115) 2023-07-03 13:13:08 +01:00
fabric-particles-v1 Add event for preventing particle tinting for colored blocks (#3146) 2023-07-03 13:19:38 +01:00
fabric-recipe-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-registry-sync-v0 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-renderer-api-v1 Model Loading API v1 (#3145) 2023-07-18 13:16:17 +01:00
fabric-renderer-indigo Interface inject FabricBakedModel (#3099) 2023-06-21 09:58:54 +01:00
fabric-rendering-data-attachment-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-rendering-fluids-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-rendering-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-resource-conditions-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-resource-loader-v0 Fix injected resources not overriding certain vanilla resources (1.20) (#3164) 2023-07-03 13:54:51 +01:00
fabric-screen-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-screen-handler-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-sound-api-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
fabric-transfer-api-v1 Fix default fluid names for non-placeable fluids, clarify Storage iterator lifecycle with modification (#3141) 2023-07-03 13:13:56 +01:00
fabric-transitive-access-wideners-v1 Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
gradle Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
src Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
.editorconfig Update .editorconfig (#1830) 2021-11-16 12:48:32 +00:00
.gitattributes 22w19a 2022-05-12 21:58:35 +01:00
.gitignore Convention Tags Improvements (#3051) 2023-05-14 15:00:30 +01:00
build.gradle Setup unit tests & format gradle files. (#3073) 2023-05-30 13:10:24 +01:00
checkstyle.xml Split all duplicated packages (#2617) 2022-11-20 13:58:41 +00:00
CONTRIBUTING.md Generate package-info files for all impl and mixin packages (#2615) 2022-11-22 16:35:52 +00:00
gradle.properties Model Loading API v1 (#3145) 2023-07-18 13:16:17 +01:00
gradlew Update to Loom 1.2 and Gradle 8.1 (#3016) 2023-04-23 13:02:02 +01:00
gradlew.bat Update to Loom 1.2 and Gradle 8.1 (#3016) 2023-04-23 13:02:02 +01:00
HEADER Move deprecated modules, create own maven BOM for the deprecated modules. (#2171) 2022-05-01 15:44:16 +01:00
LICENSE first commit - resource pack hook and little else 2018-11-05 15:54:18 +01:00
README.md Add development guidelines (CONTRIBUTING.md) (#2377) 2022-07-29 18:30:02 +01:00
settings.gradle Model Loading API v1 (#3145) 2023-07-18 13:16:17 +01:00

Fabric API

Essential hooks for modding with Fabric.

Fabric API is the library for essential hooks and interoperability mechanisms for Fabric mods. Examples include:

  • Exposing functionality that is useful but difficult to access for many mods such as particles, biomes and dimensions
  • Adding events, hooks and APIs to improve interopability between mods.
  • Essential features such as registry synchronization and adding information to crash reports.
  • An advanced rendering API designed for compatibility with optimization mods and graphics overhaul mods.

Also check out Fabric Loader, the (mostly) version-independent mod loader that powers Fabric. Fabric API is a mod like any other Fabric mod which requires Fabric Loader to be installed.

For support and discussion for both developers and users, visit the Fabric Discord server.

Using Fabric API to play with mods

Make sure you have install fabric loader first. More information about installing Fabric Loader can be found here.

To use Fabric API, download it from CurseForge, GitHub Releases or Modrinth.

The downloaded jar file should be placed in your mods folder.

Using Fabric API to develop mods

To setup a Fabric development environment, check out the Fabric example mod and follow the instructions there. The example mod already depends on Fabric API.

To include the full Fabric API with all modules in the development environment, add the following to your dependencies block in the gradle buildscript:

Groovy DSL

modImplementation "net.fabricmc.fabric-api:fabric-api:FABRIC_API_VERSION"

Kotlin DSL

modImplementation("net.fabricmc.fabric-api:fabric-api:FABRIC_API_VERSION")

Alternatively, modules from Fabric API can be specified individually as shown below (including module jar to your mod jar):

Groovy DSL

// Make a collection of all api modules we wish to use
Set<String> apiModules = [
    "fabric-api-base",
    "fabric-command-api-v1",
    "fabric-lifecycle-events-v1",
    "fabric-networking-api-v1"
]

// Add each module as a dependency
apiModules.forEach {
    include(modImplementation(fabricApi.module(it, FABRIC_API_VERSION)))
}

Kotlin DSL

// Make a set of all api modules we wish to use
setOf(
    "fabric-api-base",
    "fabric-command-api-v1",
    "fabric-lifecycle-events-v1",
    "fabric-networking-api-v1"
).forEach {
    // Add each module as a dependency
    modImplementation(fabricApi.module(it, FABRIC_API_VERSION))
}

Instead of hardcoding version constants all over the build script, Gradle properties may be used to replace these constants. Properties are defined in the gradle.properties file at the root of a project. More information is available here.

Contributing

See something Fabric API doesn't support, a bug or something that may be useful? We welcome contributions to improve Fabric API. Make sure to read the development guidelines.

Modules

Fabric API is designed to be modular for ease of updating. This also has the advantage of splitting up the codebase into smaller chunks.

Each module contains its own README.md* explaining the module's purpose and additional info on using the module.

* The README for each module is being worked on; not every module has a README at the moment