Tags
Creators
Details
Licensed MIT
Published last year
Updated last year
All versions
2.0-BETA
Beta
AfroPets2 2.0-BETAlast year 43
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
Platforms
Paper
Spigot
Changes
- When you install version 2.0 on your server, it will automatically create a new folder called "AfroPets2" with all the default configuration files.
- The "pets.yml" file remains mostly unchanged — the only difference is that now you can assign a group to a pet.
- A new file, "groups.yml", allows you to override specific pet attributes. An example group is included inside — groups don’t need to define all values, so you can, for example, assign a group that only changes the pet’s position :)
- Another new file, "menu.yml", helps organize the config — from now on, pets will only be shown in available slots in the menu.
- In "menu.yml", when creating or editing a slot, you can now specify multiple slots using commas — instead of writing "10-11", you can use "10,11". This should come in handy when customizing corner items in your menu.
- A new command has been added: /afropets hide — this allows players to hide their pet via command, without needing to use the menu.
- Two new settings have been added to the config: "remove-pet-distance" and "visible-distance".
- You can now define a default description for each pet directly in the config.
- Player commands now require specific permissions:
- /pets – afropets.use
- /pets menu – afropets.use
- /pets about – afropets.use
- /pets hide – afropets.hide
- Pet data is now saved in NBT tags, and if the plugin detects that a pet shouldn't exist anymore — it will be removed automatically.
- Two new placeholders have been added for PlaceholderAPI:
- %afropets_pets_size%
- %afropets_colors_size%
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:hMAMgikC:xl6lHTi5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hMAMgikC:xl6lHTi5"
}

