All versions
2.0-alpha-2+mod
Alpha
Riyuki's Pet Teleport Fix 2.04 months ago 675
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Singleplayer
Changes
The public test version of the next major 2.0 release. This version is still WIP and may have issues and is only published for testing purposes, not for general use.
New changes from alpha-1:
- Completely rewritten how the pack works (again): Switched back to
/forceloadcommand, but without the use of/forceload remove allto ensure compatibility with other packs while still having good performance (the ender pearl method was quite resource-intensive). - Added way to add support for modded pets. A proper documentation on this will be published later. (Experimental)
- Added the teleport command + GUI! (Experimental)
- You can now teleport either all of your selected pet type, one of the nearest pet type, or the furthest, by either using the /trigger command, or via the custom GUI.
- The GUI can be accessed only by OP by running the command
/dialog show @s ray_allay:teleport. This will be able to be accessed in survival on the later release. - Please note that this feature is still experimental, therefore some features are not properly polished yet.

Todo for the next alpha-2.1 update:
- Make the custom GUI to be accessible in survival mode without OP permission
- Add a config to enable/disable each features added by this pack, preferably a template for for vanilla-like settings as well.
Planned for a later update:
/whistlecommand that doesnt use/triggerfor the mod version.- A way to disable allay's hitbox when holding a block, that way allays will not be annoying when we're building something, and a way to make them invincible when inside a block we placed.
Credit:
- VanillaTweaks, for providing the mob head texture used in the teleport GUI <3
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:QZ5S10DM:LUM2e81C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QZ5S10DM:LUM2e81C"
}

