1.7.0.6
Compatibility
Changes
Swag Warps — Multi-Version Release
Swag Warps is now available for:
- Minecraft 1.6.4 Forge
- Minecraft 1.7.10 Forge
- Minecraft 1.8.9 Forge
- Minecraft 1.12.2 Forge
- Minecraft 1.16.5 Forge
- Minecraft 1.18.2 Forge
- Minecraft 1.20.1 Forge
- Minecraft 1.21.11 NeoForge
What’s New
- Added support for seven additional Minecraft versions.
- Kept the same delayed teleport system across supported versions.
- Teleports are canceled if you move or take damage during the countdown.
- Spawn and warp behavior has been updated to work correctly with each version’s native respawn and dimension systems.
- Improved
/setworldspawnhandling and spawn placement consistency. - Added proper support for underground spawn locations.
- Added support for newer respawn systems such as respawn anchors where applicable.
- Legacy configs and warp data can migrate into the current format.
- Fixed several version-specific spawn and teleport issues discovered during the ports.
- Swag Warps remains primarily server-side for its core functionality.
Java Requirements
- Java 8: Minecraft 1.6.4–1.16.5
- Java 17: Minecraft 1.18.2 and 1.20.1
- Java 21: Minecraft 1.21.11
1.6.4 Alpha Notice
The Minecraft 1.6.4 release is currently marked Alpha.
Swag Warps uses Java 8-compatible classes, but the ASM version included with a standard Minecraft 1.6.4 Forge environment is too old to read them.
As a result, the 1.6.4 build is not compatible with a completely stock 1.6.4 Forge launcher setup unless its ASM library is upgraded to a compatible version such as ASM 5.0.3.
The mod itself still targets Java 8; this limitation comes from the old class-reading library bundled with that Minecraft/Forge generation.
Use the 1.6.4 build only if you know your launcher or installation provides a compatible ASM version.
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:d0bDZhOO:2oPxvJQp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d0bDZhOO:2oPxvJQp"
}

