All versions
2.0.5+neoforge-26.1.2
Release
Arcadia Pets 2.0.5 (NeoForge 26.1.2)last week 13
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Arcadia Pets 2.0.5
Downloads
arcadia-pets-forge-1.20.1-2.0.5.jar(forge-1.20.1)arcadia-pets-neoforge-1.21.1-2.0.5.jar(neoforge-1.21.1)arcadia-pets-neoforge-26.1.2-2.0.5.jar(neoforge-26.1.2)
Fixed
- Pets of hostile species no longer attack players or their owner - A pet left in a chunk that went inactive (its owner teleported or walked far away) was forgotten by a periodic check, because the game hides such a mob without removing it. When the chunk woke up, the pet was no longer treated as one and ran the AI of its species, still invulnerable and with its name: a zoglin pet attacked its owner in the test that reproduces this. The check now asks which pets their owners hold. A pet also never deals damage by itself any more, which stops the magma cube burning whoever touches it, and any mob from another mod that would hit a player without using its AI.
Correctifs
- Les familiers d'espèces hostiles n'attaquent plus les joueurs ni leur propriétaire - Un familier resté dans un chunk devenu inactif (propriétaire téléporté ou parti loin) était oublié par une vérification périodique, car le jeu masque un tel mob sans le retirer. Quand le chunk se réactivait, le familier n'était plus traité comme tel et reprenait l'IA de son espèce, toujours invulnérable et avec son nom : un familier zoglin attaquait son propriétaire dans le test qui reproduit le problème. La vérification regarde maintenant quels familiers leurs propriétaires ont sortis. Un familier n'inflige plus aucun dégât par lui-même, ce qui empêche aussi le magma cube de brûler qui le touche, ainsi que tout mob d'un autre mod qui frapperait un joueur sans passer par son IA.
Optional dependencies
Any compatible version
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:lyWTFPn4:oabppusg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lyWTFPn4:oabppusg"
}

