Links
Tags
Creators
Details
All versions
1.0.0+fabric-26.3
Release
TileFinder 1.0.0 (Fabric 26.3)3 weeks ago 22
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
A rewrite, for Minecraft 26.3, 26.2 and 1.21.1, on NeoForge and Fabric.
- New finder screen, built with Vellum: search by name, by mod (
@mekanism) or by a chest's custom name (in singleplayer; vanilla servers don't send those names); filter to blocks that hold items, fluids or energy, or to your starred spots; sort by distance, name, mod or count; change the radius with a slider. - Finds what you'd call one thing as one thing: a double chest is one chest, a bed is one bed (1.21.1; 26.x beds have no block entity), a run of cable or pipe is one network (expand it to see each block), and wall signs, wall heads and banners list with their items.
- Decoration (signs, banners, heads, beds, pots) is kept out of the way under its own filter. Packs can hide or
reclassify block entities with the
tilefinder:hiddenandtilefinder:decorativeblock entity type tags. - Track one block or every block of a kind: boxes around each, a beam to the nearest, and a HUD line with the distance and direction. Targets drop off as you reach them. Everything shows through walls.
- Hover an item in JEI, REI, EMI (1.21.1) or any inventory and press the TileFinder key to find that block nearby. The finder's R and U buttons open recipes and uses in your recipe viewer.
- Stars are saved per world. Coordinates copy to the clipboard with one click.
- Settings in the finder's Settings tab, also from NeoForge's mod list and Mod Menu.
- Servers:
/tilefinder [radius] [filter]works for players without the mod, in a chest menu, and points the way with particles. No library needed (GooeyLibs is gone). - Scanning reads each loaded chunk's block entities instead of probing every block, so large radii are cheap.
Optional dependencies
Any compatible version
Any compatible version
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:HPYRSZMx:4GM8MKvr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HPYRSZMx:4GM8MKvr"
}

