Tags
Creators
Details
All versions
1.0.9
Release
DeathSwap 1.0.916 hours ago 10
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Fixes
- Fixed death screen freezing after a match ends — dead players are now auto-respawned and match cleanup is deferred to the next tick.
- Fixed a thread-safety race condition in async chat handling (no more
ConcurrentModificationException). - Fixed Nether and End teleports being treated as leaving the match when portals are used.
- Fixed player spawns at match start: players are now distributed across the spawn radius instead of all appearing at one point.
/ds leavenow properly restores inventory, health, XP and effects.- Fixed alive-player counting: eliminated players awaiting respawn are no longer counted.
- Fixed
pvp-enabledhandling for projectile damage. - Lobby start countdown is no longer reset while enough players remain.
- Guaranteed a true derangement of all alive players during swaps (no player keeps their position).
- Fixed world deletion: selective region/entity/POI cleanup, unload verification before deletion, corrected chunk pregeneration and proper pool shrinkage on reload.
- World settings (
name-prefix,generate-dimensions,generate-on-start, pool expansion) now apply immediately after/ds reload. - Teleports are now validated against the current match's dimensions instead of the global world pool.
- The world retry task is properly cancelled on stop/match creation, and
min-players-to-startis enforced.
Changes
- Swaps now affect all alive players;
PlayerSwapEventexposes the full player list. - The lobby now acts as a virtual matchmaking queue without forcing a gamemode change.
- Removed Folia from the supported platforms list in the README.
- Simplified
PlayerSwapEventand removed redundant config handling inonEnable.
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:KFeMJeDW:wPf3UVv6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KFeMJeDW:wPf3UVv6"
}

