1.2.1-1.21.1
Compatibility
Required content
Changes
1.2.1 Changelog
New
No new features.
Changes
- Can now change the sync interval to any number between 2 and 2,147,483,647 (64-bit int limit) Before was 2 - 120
- Added sync on disconnect. Thought there was before but apparently not, whoops.
Bug fixes
- Fixed a bug where, if a local object was not synced with the server, an error would be thrown if deleted.
All changes here are fully thanks to "notdysthymia" on GitHub. Partially resolves issue 5: https://github.com/NavidRohim/JMWS/issues/5
Bugs that I am aware of
- Unpredictable waystones waypoint behaviour.
- This has been reported by notdysthymia. They had their waystone waypoints wiped. Personally when testing, the waypoints stay, but they duplicate.
- There is definitely something wrong and there will be a fix in a future version.
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
New server version: 1.11
Very slight changes. Should cause no issues but still a good idea to update. All clients who use JMWS 1.2.0 can join servers with 1.2.1 or vice versa.
For Devs
1.2.1 Changes to Gradle 9.3.0, and also changes to ForgeGradle 7.
This introduces massive changes, mainly regarding the move from ForgeGradle 6 to ForgeGradle 7. FG7 is still in beta and still buggy in noticeable ways. If at all possible, check here for new ForgeGradle 7 versions which will make your life developing easier.
Also check this repo for ForgeGradle 7 examples.
Thanks!
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:2HbDMlbq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cF5KO1B5:2HbDMlbq"
}

