Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 months ago
Updated 3 days ago
All versions
1.0.3-beta
Beta
New Bedwars 1.0.3-beta4 months ago 30
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
Platforms
Paper
Spigot
Changes
[1.0.3-beta] — 2026-06-14
Fixed
- Potion items not working on 1.21+ —
PlayerItemConsumeEventnow applies the configured potion effect and removes the item manually; previously the event was cancelled with no effect applied, leaving the potion permanently in inventory on newer server versions - Armor can be bought multiple times — purchasing a
GIVE_ARMORitem is now blocked when the player's current armor tier is equal to or higher than the item being bought (prevents wasting currency on redundant purchases) - Sharpness and Haste lost on death — upgrade effects are now re-applied on respawn after potion effects are cleared; previously only armor protection was restored
- QuickVoid not killing armored players — void kill damage changed from
health + 1tomaxHealth × 1000; armor can absorb up to 80 % of damage, sohealth + 1left heavily-armored players alive - Broken placed wool drops vanilla item — breaking a placed wool block now suppresses the default drop and gives back one unit of the custom team-colored
Woolshop item instead of a plain named block (e.g.Red Wool) - Wool block break returned 16 items — the wool refund was accidentally using the shop stack size (16); now correctly gives back 1 wool per broken block
- GUI category icons showed item cost and description — category buttons in the shop GUI now show only the category name and an optional configurable description; the underlying item's price/amount lore is no longer inherited
Added
Descriptionfield for shop GUI categories — each category in a GUI YAML file can now define an optionalDescription:key that is shown as the lore on the category button (example values added toexampleGui.ymlandexampleGui2.yml)
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:e6sbnIml:KxYQrLS5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e6sbnIml:KxYQrLS5"
}

