1.2.5-1.21.11
Compatibility
Required content
Changes
JMWS 1.2.5 for 1.21.11
Server version 1.12
New# JMWS 1.2.5 for 1.21.11
Server version 1.12
New
- Added new server-side command: /jmws_handshake
- Tries to resend handshake to client.
Bug fixes / changes
- Fixed issue where joining server with different mod-loader than the client or vice versa would not properly process JMWS handshake packet on the client and said client couldn't sync.
Pre-existing bugs
Technically not a bug with JMWS, but I realise the config screen inside JourneyMap is very messy. JourneyMap is supposed to have categories so it looks much cleaner, but currently they are broken. When they are fixed in JourneyMap, so will the config screen in my mod (E.g. I won't have to release a bug fix)
Server
Server version remains
1.12up from1.11
- Added new command stated above.
- Changed how packets are sent from server to client.
1.12 is fully backwards compatible with 1.11, but it is recommended to update both client and server for QOL reasons.
- Added new server-side command: /jmws_handshake
- Tries to resend handshake to client.
Bug fixes / changes
- Fixed issue where joining server with different mod-loader than the client or vice versa would not properly process JMWS handshake packet on the client and said client couldn't sync.
Pre-existing bugs
Technically not a bug with JMWS, but I realise the config screen inside JourneyMap is very messy. JourneyMap is supposed to have categories so it looks much cleaner, but currently they are broken. When they are fixed in JourneyMap, so will the config screen in my mod (E.g. I won't have to release a bug fix)
Server
Server version remains
1.12up from1.11
- Added new command stated above.
- Changed how packets are sent from server to client.
1.12 is fully backwards compatible with 1.11, but it is recommended to update both client and server for QOL reasons.
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:cF5KO1B5:Jt3i46jK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cF5KO1B5:Jt3i46jK"
}

