DevKit API

🧰 DevKit API 0.2.0-alpha.4

A maintenance and tooling release: registry lookup, targeted config synchronization, runtime diagnostics, and cross-version tag generation.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation, without adding gameplay content of its own.

✨ Highlights

Registry Lookup

Declared entries can be resolved again by path, which helps when registration and use live in different classes:

• KRegister.get(path) returns `Optional<RegistrySupplier>`, empty for unknown paths;
• KRegister.contains(path) reports whether a path was declared;
• KRegister.size() reports how many entries a container holds;
• all three work before bootstrap() runs, and the supplier stays unbound until it completes.

Targeted Config Synchronization

Configuration synchronization is no longer limited to a full broadcast:

• ConfigSyncManager.sendTo(player, configId) pushes one configuration to a single player;
• non-authoritative configurations are refused, matching the client-side check that already rejected them on arrival;
• ConfigManager.delete(modId, name) removes a configuration file and reports whether one was removed;
• applying a synced config on the client is logged at info level with the number of fields written, so synchronization is observable without a debugger.

Runtime Diagnostics

The all-in-one artifact registers one read-only status command, /devkit info. It reports the installed DevKit version, networking capabilities, the number of registered packets, how many declared registry entries are bound, and the number of synchronized configs.

DevkitCore.getApiVersion() and DevkitCore.getModVersion() expose the same information programmatically, which is useful for crash reports and support requests.

Tag Generation Across Versions

The vanilla tag provider API changed twice between 1.21.1 and 1.21.11. TagHelper now hides both renames behind a single hook:

• override buildTags() instead of the version-specific provider hook;
• add(key, entries...) and addOptional(key, entries...) write identifiers directly, with no need to resolve a registry key first;
• tag(path) and cTag(path) build namespaced and convention tag keys;
• overriding the provider hook directly still works, so existing code keeps compiling.

One provider source file now compiles unchanged on 1.21.1, 1.21.8 and 1.21.11.

🔧 Fixes

• Config sync initialization: the synchronization payload and the player join listener are initialized on demand. Server-authoritative configs reach clients even when the sync manager is never initialized explicitly. Previously a config could be registered and then silently never sent.
• Config path validation: segments that start with a dot are rejected instead of resolving outside `config/`.
• Client initialization failures: reported as errors, so a missing client packet receiver is no longer hidden behind a debug message.
• devkit-core dependencies: the module declares its Fabric API dependency. Installing a module without Fabric API now fails with a dependency error instead of a class loading failure during startup.
• ModelGen.simpleItem: logs a warning instead of silently skipping identifiers that are not registered.
• Config sync logging: the manager no longer logs a misleading zero config count on startup.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.4+1.21.1"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.4

A maintenance and tooling release: registry lookup, targeted config synchronization, runtime diagnostics, and cross-version tag generation.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation, without adding gameplay content of its own.

✨ Highlights

Registry Lookup

Declared entries can be resolved again by path, which helps when registration and use live in different classes:

• KRegister.get(path) returns `Optional<RegistrySupplier>`, empty for unknown paths;
• KRegister.contains(path) reports whether a path was declared;
• KRegister.size() reports how many entries a container holds;
• all three work before bootstrap() runs, and the supplier stays unbound until it completes.

Targeted Config Synchronization

Configuration synchronization is no longer limited to a full broadcast:

• ConfigSyncManager.sendTo(player, configId) pushes one configuration to a single player;
• non-authoritative configurations are refused, matching the client-side check that already rejected them on arrival;
• ConfigManager.delete(modId, name) removes a configuration file and reports whether one was removed;
• applying a synced config on the client is logged at info level with the number of fields written, so synchronization is observable without a debugger.

Runtime Diagnostics

The all-in-one artifact registers one read-only status command, /devkit info. It reports the installed DevKit version, networking capabilities, the number of registered packets, how many declared registry entries are bound, and the number of synchronized configs.

DevkitCore.getApiVersion() and DevkitCore.getModVersion() expose the same information programmatically, which is useful for crash reports and support requests.

Tag Generation Across Versions

The vanilla tag provider API changed twice between 1.21.1 and 1.21.11. TagHelper now hides both renames behind a single hook:

• override buildTags() instead of the version-specific provider hook;
• add(key, entries...) and addOptional(key, entries...) write identifiers directly, with no need to resolve a registry key first;
• tag(path) and cTag(path) build namespaced and convention tag keys;
• overriding the provider hook directly still works, so existing code keeps compiling.

One provider source file now compiles unchanged on 1.21.1, 1.21.8 and 1.21.11.

🔧 Fixes

• Config sync initialization: the synchronization payload and the player join listener are initialized on demand. Server-authoritative configs reach clients even when the sync manager is never initialized explicitly. Previously a config could be registered and then silently never sent.
• Config path validation: segments that start with a dot are rejected instead of resolving outside `config/`.
• Client initialization failures: reported as errors, so a missing client packet receiver is no longer hidden behind a debug message.
• devkit-core dependencies: the module declares its Fabric API dependency. Installing a module without Fabric API now fails with a dependency error instead of a class loading failure during startup.
• ModelGen.simpleItem: logs a warning instead of silently skipping identifiers that are not registered.
• Config sync logging: the manager no longer logs a misleading zero config count on startup.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.4+1.21.1"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.4

A maintenance and tooling release: registry lookup, targeted config synchronization, runtime diagnostics, and cross-version tag generation.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation, without adding gameplay content of its own.

✨ Highlights

Registry Lookup

Declared entries can be resolved again by path, which helps when registration and use live in different classes:

• KRegister.get(path) returns `Optional<RegistrySupplier>`, empty for unknown paths;
• KRegister.contains(path) reports whether a path was declared;
• KRegister.size() reports how many entries a container holds;
• all three work before bootstrap() runs, and the supplier stays unbound until it completes.

Targeted Config Synchronization

Configuration synchronization is no longer limited to a full broadcast:

• ConfigSyncManager.sendTo(player, configId) pushes one configuration to a single player;
• non-authoritative configurations are refused, matching the client-side check that already rejected them on arrival;
• ConfigManager.delete(modId, name) removes a configuration file and reports whether one was removed;
• applying a synced config on the client is logged at info level with the number of fields written, so synchronization is observable without a debugger.

Runtime Diagnostics

The all-in-one artifact registers one read-only status command, /devkit info. It reports the installed DevKit version, networking capabilities, the number of registered packets, how many declared registry entries are bound, and the number of synchronized configs.

DevkitCore.getApiVersion() and DevkitCore.getModVersion() expose the same information programmatically, which is useful for crash reports and support requests.

Tag Generation Across Versions

The vanilla tag provider API changed twice between 1.21.1 and 1.21.11. TagHelper now hides both renames behind a single hook:

• override buildTags() instead of the version-specific provider hook;
• add(key, entries...) and addOptional(key, entries...) write identifiers directly, with no need to resolve a registry key first;
• tag(path) and cTag(path) build namespaced and convention tag keys;
• overriding the provider hook directly still works, so existing code keeps compiling.

One provider source file now compiles unchanged on 1.21.1, 1.21.8 and 1.21.11.

🔧 Fixes

• Config sync initialization: the synchronization payload and the player join listener are initialized on demand. Server-authoritative configs reach clients even when the sync manager is never initialized explicitly. Previously a config could be registered and then silently never sent.
• Config path validation: segments that start with a dot are rejected instead of resolving outside `config/`.
• Client initialization failures: reported as errors, so a missing client packet receiver is no longer hidden behind a debug message.
• devkit-core dependencies: the module declares its Fabric API dependency. Installing a module without Fabric API now fails with a dependency error instead of a class loading failure during startup.
• ModelGen.simpleItem: logs a warning instead of silently skipping identifiers that are not registered.
• Config sync logging: the manager no longer logs a misleading zero config count on startup.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.4+1.21.1"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.2

A focused update delivering version-resilient registry builders, command helpers, config reload, and several reliability fixes.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Version-Resilient Registry Builders

Item and block registration no longer requires version-specific code. The new ItemSettings and BlockSettings builders produce the same registration call on Minecraft 1.21.1, 1.21.8, and 1.21.11:

• a single buildKeyed() call works everywhere;
• on 1.21.1 the registry key is safely ignored;
• on 1.21.8 and newer it is applied automatically through internal version overrides;
• buildSimple() remains available for cases where a plain supplier is preferred;
• the existing KRegister.register() overloads are unchanged — no breaking changes.

As a result, the per-version TestMod overrides for 1.21.8 and 1.21.11 have been removed. One source file now compiles on all three targets.

Command Helpers

DevkitCommands provides thin wrappers over Brigadier to reduce boilerplate when registering player commands:

• auto-registration through CommandRegistrationCallback;
• player(ctx) unwraps ServerPlayerEntity from context;
• ok(ctx, message) and okBroadcast(ctx, message) return ready-to-use feedback;
• compatible with the full Brigadier API — literal(), argument(), and custom command trees work as usual.

Config Reload

ConfigManager.reload() rereads a JSON configuration file from disk and returns a fresh instance. The caller decides when to swap the live reference. A malformed file is never overwritten — the method falls back to in-memory defaults, matching the existing loadOrCreate() safety guarantees.

🔧 Fixes

• ModMenu library badge: replaced the non-functional flat key format with the correct nested "modmenu": { "badges": ["library"] } structure. DevKit API now appears as a Library in Mod Menu.
• Components.intComponent(String): the deprecated overload no longer passes a null identifier. It now defaults to the DevKit namespace, making buildAndRegister() safe to call.
• NetworkCompat: reconfigureIfAvailable() is now called after server-authoritative configs are sent on player join. Previously the method existed but was never wired in.
• TestMod: the example integration mod now exercises networking, config save, and config reload at runtime through live /devkit_test commands.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.2+1.21.8"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.2

A focused update delivering version-resilient registry builders, command helpers, config reload, and several reliability fixes.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Version-Resilient Registry Builders

Item and block registration no longer requires version-specific code. The new ItemSettings and BlockSettings builders produce the same registration call on Minecraft 1.21.1, 1.21.8, and 1.21.11:

• a single buildKeyed() call works everywhere;
• on 1.21.1 the registry key is safely ignored;
• on 1.21.8 and newer it is applied automatically through internal version overrides;
• buildSimple() remains available for cases where a plain supplier is preferred;
• the existing KRegister.register() overloads are unchanged — no breaking changes.

As a result, the per-version TestMod overrides for 1.21.8 and 1.21.11 have been removed. One source file now compiles on all three targets.

Command Helpers

DevkitCommands provides thin wrappers over Brigadier to reduce boilerplate when registering player commands:

• auto-registration through CommandRegistrationCallback;
• player(ctx) unwraps ServerPlayerEntity from context;
• ok(ctx, message) and okBroadcast(ctx, message) return ready-to-use feedback;
• compatible with the full Brigadier API — literal(), argument(), and custom command trees work as usual.

Config Reload

ConfigManager.reload() rereads a JSON configuration file from disk and returns a fresh instance. The caller decides when to swap the live reference. A malformed file is never overwritten — the method falls back to in-memory defaults, matching the existing loadOrCreate() safety guarantees.

🔧 Fixes

• ModMenu library badge: replaced the non-functional flat key format with the correct nested "modmenu": { "badges": ["library"] } structure. DevKit API now appears as a Library in Mod Menu.
• Components.intComponent(String): the deprecated overload no longer passes a null identifier. It now defaults to the DevKit namespace, making buildAndRegister() safe to call.
• NetworkCompat: reconfigureIfAvailable() is now called after server-authoritative configs are sent on player join. Previously the method existed but was never wired in.
• TestMod: the example integration mod now exercises networking, config save, and config reload at runtime through live /devkit_test commands.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.2+1.21.8"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.2

A focused update delivering version-resilient registry builders, command helpers, config reload, and several reliability fixes.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Version-Resilient Registry Builders

Item and block registration no longer requires version-specific code. The new ItemSettings and BlockSettings builders produce the same registration call on Minecraft 1.21.1, 1.21.8, and 1.21.11:

• a single buildKeyed() call works everywhere;
• on 1.21.1 the registry key is safely ignored;
• on 1.21.8 and newer it is applied automatically through internal version overrides;
• buildSimple() remains available for cases where a plain supplier is preferred;
• the existing KRegister.register() overloads are unchanged — no breaking changes.

As a result, the per-version TestMod overrides for 1.21.8 and 1.21.11 have been removed. One source file now compiles on all three targets.

Command Helpers

DevkitCommands provides thin wrappers over Brigadier to reduce boilerplate when registering player commands:

• auto-registration through CommandRegistrationCallback;
• player(ctx) unwraps ServerPlayerEntity from context;
• ok(ctx, message) and okBroadcast(ctx, message) return ready-to-use feedback;
• compatible with the full Brigadier API — literal(), argument(), and custom command trees work as usual.

Config Reload

ConfigManager.reload() rereads a JSON configuration file from disk and returns a fresh instance. The caller decides when to swap the live reference. A malformed file is never overwritten — the method falls back to in-memory defaults, matching the existing loadOrCreate() safety guarantees.

🔧 Fixes

• ModMenu library badge: replaced the non-functional flat key format with the correct nested "modmenu": { "badges": ["library"] } structure. DevKit API now appears as a Library in Mod Menu.
• Components.intComponent(String): the deprecated overload no longer passes a null identifier. It now defaults to the DevKit namespace, making buildAndRegister() safe to call.
• NetworkCompat: reconfigureIfAvailable() is now called after server-authoritative configs are sent on player join. Previously the method existed but was never wired in.
• TestMod: the example integration mod now exercises networking, config save, and config reload at runtime through live /devkit_test commands.

📦 For Developers

Dependent mods can consume DevKit API through Modrinth Maven:

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

dependencies {
    modImplementation "maven.modrinth:devkitapi:0.2.0-alpha.2+1.21.8"
}

Maven Local publishing remains available as a fallback. See the README for full setup instructions.

Alpha software. Public API signatures may still change before 1.0.

🧰 DevKit API 0.2.0-alpha.1

A major maintenance and compatibility update focused on reliability, safer networking, and a more complete developer experience.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Expanded 1.21.x Compatibility

DevKit API now provides dedicated builds for the actively used Minecraft 1.21.x releases.

The shared API remains consistent while version-specific implementations handle changes introduced by newer Minecraft versions, including registry-key-aware item construction and the updated client model system.

Improved Registry Kit

Registry declarations are now safer and more flexible:

• added key-aware factories for blocks and items on newer Minecraft versions;
• preserved ordered, type-safe registration;
• improved duplicate identifier detection;
• added clearer errors when entries are accessed before registration;
• made partial bootstrap failures safely retryable;
• prevented already successful entries from being registered twice.

More Reliable Networking

The networking module received a substantial reliability pass:

• improved separation between common and client-only code;
• added automatic client receiver setup;
• added support for packets registered after client initialization;
• added validation for packet identifiers and directions;
• added protection against duplicate packet registration;
• corrected main-thread task scheduling;
• improved dedicated-server safety;
• retained S2C, C2S, and bidirectional payload support through Fabric's Payload API.

Restored and Expanded Config Sync

The synchronized configuration system is now fully functional and more resilient:

• loads existing JSON configs or creates defaults automatically;
• synchronizes server-authoritative values when a player joins;
• supports manual broadcasts after config reloads;
• supports multiple named configs from the same mod;
• updates live config objects without breaking existing references;
• uses safer file replacement where supported;
• validates synchronized payload size;
• handles malformed config files without silently overwriting user data.

Updated Data Components and Datagen

Data Component helpers remain available throughout the supported 1.21.x line.

Datagen support has been updated for the newer client model system and includes reusable foundations for:

• item and block models;
• block and item tags;
• common convention tags;
• block loot tables.

The previous placeholder loot helper has been replaced with a functional implementation.

🐛 Fixes

• Fixed client networking classes being absent from the final all-in-one JAR.
• Fixed potential client-class loading failures on dedicated servers.
• Fixed client packet receivers not being initialized correctly.
• Fixed late packet registrations being ignored on the client.
• Fixed synchronized configs failing to update live config instances.
• Fixed multiple configs from one mod replacing each other's registrations.
• Fixed unsafe direct replacement of config files.
• Fixed duplicate packet identifiers being silently accepted.
• Fixed mismatches between declared packet IDs and actual payload IDs.
• Fixed registry containers becoming unusable after a partial bootstrap failure.
• Fixed item registration requirements introduced in newer Minecraft 1.21.x releases.
• Fixed outdated model datagen integration on later 1.21.x versions.
• Fixed the incomplete loot-table helper from the previous alpha.

⚠️ Alpha Notice

DevKit API is still in active development.

The core systems are operational, but public API signatures may continue to evolve before the stable release. Mod developers should pin the exact DevKit version used by their projects.

DevKit API does not add gameplay content on its own. Install it only when another mod requires it.

🧰 DevKit API 0.2.0-alpha.1

A major maintenance and compatibility update focused on reliability, safer networking, and a more complete developer experience.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Expanded 1.21.x Compatibility

DevKit API now provides dedicated builds for the actively used Minecraft 1.21.x releases.

The shared API remains consistent while version-specific implementations handle changes introduced by newer Minecraft versions, including registry-key-aware item construction and the updated client model system.

Improved Registry Kit

Registry declarations are now safer and more flexible:

• added key-aware factories for blocks and items on newer Minecraft versions;
• preserved ordered, type-safe registration;
• improved duplicate identifier detection;
• added clearer errors when entries are accessed before registration;
• made partial bootstrap failures safely retryable;
• prevented already successful entries from being registered twice.

More Reliable Networking

The networking module received a substantial reliability pass:

• improved separation between common and client-only code;
• added automatic client receiver setup;
• added support for packets registered after client initialization;
• added validation for packet identifiers and directions;
• added protection against duplicate packet registration;
• corrected main-thread task scheduling;
• improved dedicated-server safety;
• retained S2C, C2S, and bidirectional payload support through Fabric's Payload API.

Restored and Expanded Config Sync

The synchronized configuration system is now fully functional and more resilient:

• loads existing JSON configs or creates defaults automatically;
• synchronizes server-authoritative values when a player joins;
• supports manual broadcasts after config reloads;
• supports multiple named configs from the same mod;
• updates live config objects without breaking existing references;
• uses safer file replacement where supported;
• validates synchronized payload size;
• handles malformed config files without silently overwriting user data.

Updated Data Components and Datagen

Data Component helpers remain available throughout the supported 1.21.x line.

Datagen support has been updated for the newer client model system and includes reusable foundations for:

• item and block models;
• block and item tags;
• common convention tags;
• block loot tables.

The previous placeholder loot helper has been replaced with a functional implementation.

🐛 Fixes

• Fixed client networking classes being absent from the final all-in-one JAR.
• Fixed potential client-class loading failures on dedicated servers.
• Fixed client packet receivers not being initialized correctly.
• Fixed late packet registrations being ignored on the client.
• Fixed synchronized configs failing to update live config instances.
• Fixed multiple configs from one mod replacing each other's registrations.
• Fixed unsafe direct replacement of config files.
• Fixed duplicate packet identifiers being silently accepted.
• Fixed mismatches between declared packet IDs and actual payload IDs.
• Fixed registry containers becoming unusable after a partial bootstrap failure.
• Fixed item registration requirements introduced in newer Minecraft 1.21.x releases.
• Fixed outdated model datagen integration on later 1.21.x versions.
• Fixed the incomplete loot-table helper from the previous alpha.

⚠️ Alpha Notice

DevKit API is still in active development.

The core systems are operational, but public API signatures may continue to evolve before the stable release. Mod developers should pin the exact DevKit version used by their projects.

DevKit API does not add gameplay content on its own. Install it only when another mod requires it.

🧰 DevKit API 0.2.0-alpha.1

A major maintenance and compatibility update focused on reliability, safer networking, and a more complete developer experience.

DevKit API is a lightweight library for Fabric mod developers. It provides reusable tools for registries, networking, Data Components, synchronized configuration, and data generation—without adding gameplay content of its own.

✨ Highlights

Expanded 1.21.x Compatibility

DevKit API now provides dedicated builds for the actively used Minecraft 1.21.x releases.

The shared API remains consistent while version-specific implementations handle changes introduced by newer Minecraft versions, including registry-key-aware item construction and the updated client model system.

Improved Registry Kit

Registry declarations are now safer and more flexible:

• added key-aware factories for blocks and items on newer Minecraft versions;
• preserved ordered, type-safe registration;
• improved duplicate identifier detection;
• added clearer errors when entries are accessed before registration;
• made partial bootstrap failures safely retryable;
• prevented already successful entries from being registered twice.

More Reliable Networking

The networking module received a substantial reliability pass:

• improved separation between common and client-only code;
• added automatic client receiver setup;
• added support for packets registered after client initialization;
• added validation for packet identifiers and directions;
• added protection against duplicate packet registration;
• corrected main-thread task scheduling;
• improved dedicated-server safety;
• retained S2C, C2S, and bidirectional payload support through Fabric's Payload API.

Restored and Expanded Config Sync

The synchronized configuration system is now fully functional and more resilient:

• loads existing JSON configs or creates defaults automatically;
• synchronizes server-authoritative values when a player joins;
• supports manual broadcasts after config reloads;
• supports multiple named configs from the same mod;
• updates live config objects without breaking existing references;
• uses safer file replacement where supported;
• validates synchronized payload size;
• handles malformed config files without silently overwriting user data.

Updated Data Components and Datagen

Data Component helpers remain available throughout the supported 1.21.x line.

Datagen support has been updated for the newer client model system and includes reusable foundations for:

• item and block models;
• block and item tags;
• common convention tags;
• block loot tables.

The previous placeholder loot helper has been replaced with a functional implementation.

🐛 Fixes

• Fixed client networking classes being absent from the final all-in-one JAR.
• Fixed potential client-class loading failures on dedicated servers.
• Fixed client packet receivers not being initialized correctly.
• Fixed late packet registrations being ignored on the client.
• Fixed synchronized configs failing to update live config instances.
• Fixed multiple configs from one mod replacing each other's registrations.
• Fixed unsafe direct replacement of config files.
• Fixed duplicate packet identifiers being silently accepted.
• Fixed mismatches between declared packet IDs and actual payload IDs.
• Fixed registry containers becoming unusable after a partial bootstrap failure.
• Fixed item registration requirements introduced in newer Minecraft 1.21.x releases.
• Fixed outdated model datagen integration on later 1.21.x versions.
• Fixed the incomplete loot-table helper from the previous alpha.

⚠️ Alpha Notice

DevKit API is still in active development.

The core systems are operational, but public API signatures may continue to evolve before the stable release. Mod developers should pin the exact DevKit version used by their projects.

DevKit API does not add gameplay content on its own. Install it only when another mod requires it.

First public release.

Modules: core, registry, networking, components, config, client, datagen, fabric (aggregator).

Highlights:

• Fluent KRegister registry container
• @AutoPacket annotation for automatic S2C/C2S registration
• Data Components 1.21+ builder with network sync
• @SyncedConfig server-authoritative config sync
• Datagen helpers (tags, loot, models)
• Multi-version support: 1.21.1, 1.21.8, 1.21.11

Notes:

• This is an alpha. API may change before 0.1.0 stable.
• No gameplay content — pure library, install only if another mod requires it.