Tags
Creators
Details
0.4.0+1.21.8-neoforge
Compatibility
Changes
Changelog - Find My Villager v0.4.0
This major update introduces the Online Sharing System, allowing you to securely share your trading hall data directly with other players on your server without using manual codes.
New Features
-
Direct Player-to-Player Sharing
Send and receive villager databases directly through a secure, privacy-focused online relay. -
Background Lifecycle Management
The sharing process is now fully automated. Once you send an invite or click accept, the mod handles the data transfer in the background, allowing you to return to your game immediately. -
Rebindable Controls
The Open Find My Villager key is now a standard Minecraft keybind. You can rebind it to any key in:Options > Controls > Key Binds
-
Privacy-First Hashing Implemented SHA-256 scoped identity hashing. Your raw Minecraft UUID is never sent to the relay, helping keep your persistent identity and server history private.
-
Dynamic UI Feedback Added system toasts and overlay messages that track background uploads, downloads, and incoming invites.
Improvements & Fixes
-
Network Reliability Increased payload transfer timeouts to 30 seconds to support large trading halls, up to 512 KB, on slower connections.
-
Server Identity Normalization Fixed an issue where slight variations in server addresses, such as case differences, could prevent players from finding each other on the relay.
-
Protocol Synchronization Overhauled the Cloudflare Worker routing to support both legacy and modern sharing protocols at the same time.
-
Validation Hardening Every incoming share is now strictly validated for structural integrity before being presented for import.
Privacy & Disclosure
- Added a comprehensive Privacy Warning Screen and Privacy Notice that clearly disclose when data is uploaded and what specific information is shared.
- Online sharing is strictly opt-in and disabled by default.
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:VlxHvtNW:XkdLyA82"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VlxHvtNW:XkdLyA82"
}

