Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 months ago
Updated 2 weeks ago
All versions
2.0.0
Release
Locate Plus 2.0.0last month 23
Compatibility
Minecraft: Java Edition
1.20.1–1.20.4
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
2.0.0
Works on 1.20.1 through 1.20.4.
Heads up
- /analyzechunks is now /lp analyze, /inspect is now /lp inspect
- Radius needs a unit: 64 blocks or 4 chunks, not just 64
- 4 chunks now means 4 in every direction (49 chunks), not the 4 nearest
- No radius at all scans everything loaded around you
New
- /locate item finds items in chests, shulker boxes, on the floor, on mobs, in player inventories
- /lp visualize shows the scan area before you scan it
- /lp stop cancels a running scan
- /lp clear removes glowing and markers
- Config file with 43 settings, /lp reload to apply
- Export results to a text file
- Set a height range so scans skip depths you do not care about
- Every command can be switched off completely, including the ones under /lp
- Teleport buttons have their own switches, separate for block results and biome results
- Turn off the outline on /locate block, or change how many results chat lists
Better
- Found blocks glow through walls
- Only you see your results
- Shorter chat, 60 results instead of 15
- Big scans no longer freeze the server
- /safetp lands you on chests, in composters, at the foot of pillars, and avoids lava, magma, powder snow, campfires and cactus
- Faster scans, and /safetp is much quicker when it has to search
Fixed
Tons, mostly /safetp being dumb.
1.0.0
First release. /locate block, /locate entity, /inspect, /safetp, /glow, /analyzechunks and /purgeentities.
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:xG1rYaqo:63RnpZ2g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xG1rYaqo:63RnpZ2g"
}

