Tags
Creators
Details
2.27.0-260811
Compatibility
Required content
Changes
๐ช Packetevents, new shop browser and more!
โจ New
๐บ๏ธ Shop Browser โ /shopbrowser
Browse every player shop on the server. A grid of player heads, one per
shop owner; click a head to see all of that player's shopkeepers with
their type, world and coordinates; click a shop to teleport straight to
it. Paged, so it handles hundreds of shops fine.
Aliases: /shopowners, /browseshops
๐ฏ Teleports actually land somewhere sensible No more arriving inside a slab or halfway through a wall. You now land in front of the shop, facing it, on ground you can actually stand on. Lava, fire, cactus, magma, powder snow, cobwebs and portals are all avoided, and if there is genuinely nowhere safe it tells you before the countdown instead of after.
New config: playerShops.teleport.distance and
adminShops.teleport.distance (default 2, range 1 to 8) set how
many blocks away you arrive.
๐ PacketEvents support ProtocolLib still works and is still the default, so nothing changes if you already run it. If you would rather use PacketEvents, the plugin now detects it automatically. It also runs with neither installed now, instead of refusing to load.
๐ ๏ธ Fixed
๐ฆ Items could be put into the plugin's menus, and were lost forever Shift-clicking, dragging or clicking outside a menu could drop your items into it, where nothing ever gave them back. All of those routes are closed. Every empty-slot click was also throwing an error into console; that is gone too.
โ๏ธ Two settings that did nothing
playerShops.teleport.enabled and adminShops.teleport.enabled were
never actually read. Turning them off did not disable teleports. They
work now.
๐ Notes
- Your config updates itself on first start. Existing settings are kept.
- New messages are configurable as usual.
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:pznDR0gz:kE1h0l5B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pznDR0gz:kE1h0l5B"
}

