Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 9 months ago
All versions
1.0.1
Release
SpyBedWars 1.0.19 months ago 33
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Spigot
Changes
SpyBedWars Changelog - v1.0.1
Bug Fixes
- Iron Golem Damage & AI: Fixed Iron Golems failing to deal damage and improve their targeting/attack reliability.
- Arena World Difficulty: Implemented a natural hostile mob spawn blocker, allowing arenas to run on Normal difficulty (enabling Golem AI) without random mobs spawning.
- Post-Game Entity Cleanup: Fixed entities like Iron Golems, TNT, Fireballs, and Silverfish persisting in the arena after a game ends.
- NPC Visibility: Resolved "ghost" NPCs by forcing a refresh of Shop and Upgrade NPCs whenever players join an active game or a world wakes from hibernation.
- Bridge Egg Naming: Fixed incorrect display names for Bridge Eggs in the shop.
- Heal Pool Persistence: Fixed an issue where Heal Pool effects would carry over into new matches.
- Tool Retention: Fixed tools being kept after death; they now correctly downgrade or are removed.
- Ender Chest Clearing: Ensured Ender Chests are fully cleared between matches.
- Combat Mechanics: Disabled sweeping attack animations and damage for a classic BedWars feel.
Improvements
- Buffed Iron Golems: Increased base attack damage and added knockback to make Golems a more strategic defense choice.
- Extended tracking: Improved the persistent entity system to track more entity types (TNT, Projectiles, etc.) for reliable cleanup.
- Quick Buy Customization: Quick Buy shop layouts are now fully configurable via
config.yml.
Compatibility
- Fully compatible with PaperMC 1.21.11.
- Requires SpyCore and SpyNPCs.
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:X6MkO1Ey:czLXmZBz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:X6MkO1Ey:czLXmZBz"
}

