Links
Tags
Creators
Details
1.3.0-test.1-1.20.1-forge
Compatibility
Changes
FindMe 1.3.0-test
Release note
FindMe 1.3 went through substantial feature expansion and repeated refactoring. This build is published as a test release so players and pack authors can validate it in real modpacks. It may be less stable or compatible than earlier releases. Back up your world before installing or upgrading.
Highlights
- Reworked mount, companion, and vehicle storage, summon, switch, and lifecycle flows.
- Added classic radial, six-wing, tactical strip, and folded-shard wheel styles; the classic radial wheel is the default.
- Added pending, deployed, switching, and dead states with teams, warehouse, and paging.
- Added fall rescue, tactical companion commands, ride-home flow, and riding camera settings.
- Added Small House residents, patrol boundaries, unloaded-area storage, and restoration.
- Reworked ApricityUI management, settings, details, diagnostics, backups, and entity editor.
- Added entity category, movement, binding, animation, effect, preview NBT, and scale overrides.
- Added automatic/manual backups, death records, and an opt-in diagnostic logging switch.
- Reduced chat commands to management, editor, reload, and administrator force-tame tools.
- Added recipes for Name Paper, Vehicle Binder, and Small House; NeoForge also has a Seat Cushion.
- Published separately identified Forge 1.20.1 and NeoForge 1.21.1 test builds.
Platform differences
- NeoForge 1.21.1 exposes optional Cobblemon, Sable/Aeronautics, MachineMax, and Waystones integrations.
- Forge 1.20.1 does not include Cobblemon or Sable-specific features; it retains integration paths appropriate to that version, including Waystones and MachineMax.
Known risks
- Modded entities with custom AI, riding controllers, multipart renderers, or unusual serialization may not be fully compatible.
- Rescue, vehicle handoff, cross-dimension ride-home, and entity previews carry higher risk.
- Do not remove a creature or vehicle mod while FindMe records still depend on it.
- Store deployed entries and create a manual backup before changing versions or configuration.
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:bBltNHbY:6wivCerf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bBltNHbY:6wivCerf"
}

