
Dreams Speedrunner Swap + Task Master
Three iconic Dream challenges in one plugin: Speedrunners vs Hunters, Multi-Runner Control Swap, and the new Task Master mode. Experience all of Dream's most popular Minecraft challenges with customizable features, team management, and seamless gameplay.
Tags
Creators
Details
4.1
Compatibility
Changes
SpeedrunnerSwap 4.1
Added full multiworld / Multiverse compatibility support.
Changes
- Runner respawns now stay tied to the active game session world instead of falling back to the serverโs default world.
- Added post-respawn enforcement to handle plugins like Multiverse setups that apply a second teleport after respawn.
- Added a new Multiworld settings section in the GUI.
- Added same-world player filtering in team selection menus.
- Added session-world assignment restrictions so players from the wrong world canโt be assigned by mistake.
- Added session-world status info to the main GUI and
/swap status. /swap setrunnersand/swap sethuntersnow respect multiworld restrictions and explain skipped players.- Added soft dependency support for
Multiverse-CoreandMultiverse-Inventories.
How to use
- Open
/swap gui - Go to
Settings - Open
Multiworld - Configure:
Multiworld CompatibilitySession-World RespawnsPost-Respawn EnforcementSame-World Team SelectorRestrict AssignmentsUpdate Session World
Recommended setup
- Leave Multiworld Compatibility enabled
- Leave Session-World Respawns enabled
- Leave Post-Respawn Enforcement enabled
- Leave Restrict Assignments enabled
- Use Same-World Team Selector if you want team setup to only show players in your current world
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:fJ45DptH:wFjp00BQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fJ45DptH:wFjp00BQ"
}
