Tags
Creators
Details
All versions
4.2.3-beta.2
Beta
Petting 4.2.3-beta.24 months ago 388
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Petting 4.2.3-beta.2 (Forge 1.20.1)
This version is a backport of the latest features from NeoForge 1.21.1 to Forge 1.20.1!
Major Changes and Backported Features:
- Registry System Overhaul: Migrated from NeoForge's \DeferredHolder\ and \DeferredItem\ back to Forge's \RegistryObject.
- Networking Modernization: Migrated the \Payload\ based networking to Forge's \SimpleChannel\ and \PacketDistributor.
- Capability System Reset: Downgraded the NeoForge Attachment system back to the classic Forge \Capability\ system for pet inventories.
- Attributes System: Adjusted UUID-based \AttributeModifier\ system to match the legacy 1.20.1 signature. Reverted \Attribute\ registry logic to use Supplier-based definitions.
- Config & GUI Enhancements: Ported the \ConfigScreenFactory\ implementation to use the older \ConfigScreenHandler. Also resolved numerous screen rendering changes, falling back to 1.20.1 compatible enderBackground\ and GUI drawing methods.
- Event Bus Adjustments: Re-mapped \LivingEvent, \LivingDamageEvent, and Menu Screen Registration events to their appropriate 1.20.1 equivalents.
- Controls & Keybindings Overhaul: Replaced brittle manual thread polling with native Forge \RegisterKeyMappingsEvent\ and \InputEvent.Key\ for responsive and reliable Pet Settings (P) activation.
- Settings UI & Network Synchronization: Resolved missing Network Packet registrations that caused the Settings UI to silently fail, fully restoring bidirectional UI-to-Server syncing.
- Translation Keys & Localization: Performed a massive extraction and injection of missing localization strings, tooltips, and dynamic action mapping states into
en_us.jsonfor proper English formatting.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:vf91JXwf:bXjipQzb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vf91JXwf:bXjipQzb"
}

