All versions
New: Config System (
Improved: Train Boarding Pathfinding (
1.1.0
Release
Villager Tourism (NeoForge Port) 1.0.02 weeks ago 67
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
Villager Tourism v1.1.0 Changelog
New: Config System (VillagerTourismConfig)
- Configurable reward item — change the payout from emeralds to any item (coins, custom currency, etc.) via the common config.
Default:minecraft:emerald - Per-structure point values — override how many points each structure awards (e.g.
minecraft:village/plains = 3) - Structure blacklist/whitelist — ignore specific structures from counting, or enable whitelist mode
- Business tourist multiplier — configurable multiplier instead of the previously hardcoded
2x
Improved: Train Boarding Pathfinding (BoardTrainGoal)
- Path-distance-aware target selection — tourists now evaluate candidate boarding positions using actual A* path node count instead of Euclidean distance, preferring reachable locations over geographically closer but obstructed ones.
- Best seat selection — selects the closest available seat (Manhattan distance) instead of a random empty seat.
- Train movement tracking — boarding path automatically recalculates whenever the train moves to a new block.
- Periodic path recalculation — refreshes the path every 15 ticks to prevent stale navigation.
- Wider walkable search — boarding search radius increased from 7×7×4 to 9×9×6.
- Slightly faster movement — tourist walking speed increased from 0.80 to 0.85.
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:mACqfpPL:kB7AhQBW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mACqfpPL:kB7AhQBW"
}

