All versions
2.0.0
Release
Effect Shop 2.0.02 weeks ago 34
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Folia
Paper
Purpur
Spigot
Changes
EffectShop 2.0.0 — Full Rewrite
The plugin has been completely rewritten. One jar now supports Minecraft 1.16.5 through 26.3 on Spigot, Paper, Purpur, Folia (and other Bukkit-based forks). Java 17+ required.
Breaking changes
- The command is now
/effectshop(the old/eshophas been removed) - New
config.ymlformat (v2) — your old config is automatically backed up toconfig-v1-backup.ymland ported prices must be moved over
New
- Fully config-driven menus: slots, sizes, materials, icons, lore, prices, durations, fill/accent panes, header and back items — everything editable, unlimited categories
- Stack modes for buying an already-active effect:
REPLACE(restart),ADD(extend duration),MAX(refund-free refusal while the remaining time is longer) - Sound feedback (open / navigate / purchase / denied), configurable resource keys
- MiniMessage support (
<gold>,<bold>, ...) alongside legacy&codes - Real potion items: the Invisibility icon looks like an actual potion
- Close button in the main menu; staying in the menu after a purchase with live balance update
/effectshop reload— hot-reload the configuration (no restart)/effectshop test— builds all menus headlessly (handy for setup and CI checks)- Attributes / "No Effects" lines are hidden from item tooltips on every version (data components on 1.21.5+, item flags on older servers)
Fixes and hardening
- Fixed the balance line rendering a literal
%player_level%placeholder in the main menu - Items can no longer be moved into/out of the shop via drag or shift-click
- Purchases are race-safe and verified against the live XP level
Compatibility
- Runtime capability detection instead of hardcoded versions: Adventure components, registries, data components and potion APIs all have legacy fallbacks
- Folia support via the entity scheduler (
folia-supported: true) - Verified on: Paper 1.16.5 / 1.21.11 / 26.1.2 / 26.2 / 26.3, Spigot 1.21.1, Folia 1.21.11
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:OBgoY03S:osfwyz8Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OBgoY03S:osfwyz8Q"
}

