Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 months ago
Updated 2 weeks ago
All versions
2.1.0
Release
Locate Plus 2.1.0+1.21.1last month 33
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
2.1.0
Adds 1.21 and 1.21.1. Still works on 1.20.1 through 1.20.4.
Fixed
- /lp clear only switched off glowing in the dimension you ran it in, and dropped its record of the rest, so anything lit in another world stayed lit with nothing able to turn it off. It now clears every dimension.
- Glowing on a boat, minecart, item frame or dropped item is a flag the game saves with the entity. The timer that switched it off only ran while the entity was loaded, so one that unloaded, or that was still lit when the server stopped, came back glowing for good. The flag now comes off when the entity unloads and when the server stops.
- /lp inspect could take the whole server down if a modded block misbehaved while being read. It now says it could not read that position and carries on.
- The mod loaded on 1.20.5 and 1.20.6, where it cannot work, then failed on use. It refuses to load there instead, with a message naming the versions it needs.
- Chest minecarts and other entity inventories counted as mobs, so a result read "on chest_minecart" and the split line put them under mobs. They count as containers now.
- Names printed with underscores in them. Containers, mobs, nested items, enchantments and biome type all read as words now, so "fire protection 4" rather than "fire_protection 4".
- The inspect and analyzechunks switches did nothing. Both commands were always registered, and /lp config would show them off while they still worked.
- /lp visualize had no switch at all. It has one now. /lp clear is always registered, so an outline can always be removed even with everything else switched off.
- A scan_min_y set above the ceiling flipped the height band, and every scan then read nothing without saying why.
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:jewd3Rbf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xG1rYaqo:jewd3Rbf"
}

