Notice: JMWS has been discontinued
With the release of JourneyMap v6.0 for all major versions of Minecraft (Beta: 1.7.10, 1.12.2, 1.16.5, 1.20.1, Stable: 1.21.1, 1.21.11, and 26.2) JourneyMap introduces what JMWS was designed to do, which is server-sided waypoints. You should not use JMWS and should just use JourneyMap. There is no benefit to using JMWS.
If you have been using JWMS and need to migrate to JourneyMap, the migration will happen automatically when you first join a server with JM on both server and client. JMWS should be uninstalled afterwards.
Update (3 October 2026)
I have closed the Discord support server. Support will no longer be given under any circumstances including migration. Thank you for using JMWS. It was a pleasure to work on over the past year and thank you to all contributors which include any pull requests, issues, and feature suggestions.
Original description below.
JourneyMap Waypoint Syncing (JMWS)
This mod allows you to save and share waypoints on JourneyMap between multiple devices via the players account UUID on the server.
Think of this mod as a cloud where all your waypoints are stored, and if you join a server on another computer / device where this mod is installed on the server-side, it'll share all waypoint data like the cloud shares photos, videos, etc with all devices on that cloud.
This mod seamlessly integrates with JourneyMap, and if desired can be totally obscured but still work in the background via this mods configuration page which is in the addon section of JourneyMap.
This mod does not upload your saved JourneyMap settings. Only your waypoints and groups will be uploaded.
How to use?
Drop this mod into the the clients and servers mod folder. The server must have the mod CommonNetwork installed for your appropriate version. There is no extra setup. If working correctly, when you join a server you will get a green success message.
Why?
This is a personal project. I made it because I played on a server I owned on multiple devices (I played on PC, and before I went to bed I played on steam deck) but, I could never find a mod that synced JourneyMap waypoints between devices (If you know / find one, please do let me know)
This is also my first ever Java project, and publicly released programming project, so it is very likely there are bad practices. View the source code and give me feedback. There are also no guarantees I will maintain this codebase as at heart, this is still a personal project and I will do with it as I please, as long as it functions how I want it to.
You can use in modpacks.
All Versions
+ Add Version| Name | Game version | Platforms | Published | Downloads | Actions |
|---|---|---|---|---|---|
| 4mo ago | 1 | ||||
| 4mo ago | 1 | ||||
| 4mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 5mo ago | 1 | ||||
| 6mo ago | 1 | ||||
| 6mo ago | 1 | ||||
| 6mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 7mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| 11mo ago | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 |
## Bug fixes / changes
- Fixed bug where stable version of JM would not work with JMWS
> ### Server
> Server version remains 1.14
Thank you for all your support.
## Bug fixes / changes
- Fixed bug where stable version of JM would not work with JMWS
> ### Server
> Server version remains 1.14
Thank you for all your support.
## Bug fixes / changes
- Fixed bug where stable version of JM would not work with JMWS
> ### Server
> Server version remains 1.14
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version is 1.14*
## Bug fixes / changes
- Fix missing i18n key in addon config screen and generally cleaned up the config categories
- Changed wording in addon config screen
- Global objects are now migrated
- Replaced old JMWS icons with new ones backported from 2.0.0
- Very small optimisations
> ### Server
> Server version is 1.14, up from 1.13.
> - Global objects are migrated. This is a server-side change.
>
> Both client and server are fully backwards and forwards compatible with 1.13
Thank you for all your support.
- Server version 1.13*
## New
- No new features
## Bug fixes / changes
- Added logic to port synced JMWS waypoints and groups to JourneyMap. Once this is finished, JMWS should be uninstalled.
To transition synced JMWS waypoints and groups to JourneyMaps server waypoints, simply join a server with JMWS v1.2.6 and the latest version of JourneyMap.
The migration will happen automatically. JMWS will put itself in a disabled state for that server, and then you are free to uninstall it.
If you join a server with JMWS v1.2.6 on both sides but no JourneyMap on the server, JMWS will just function as normal.
- What about my shared waypoints and groups?*
You will have to share them again manually using JourneyMap, which now supports shared waypoints and groups.
- What about my global waypoints and groups?*
You will have to make them global manually using JourneyMap, which now supports global waypoints and groups.
- What if I for some reason want to keep using JMWS?*
- You can continue to use it, but consider this a warning not to as I will not update JMWS for any new versions past 26.1.2
- Sharing UI
- Global object UI
- Seamless, native integration
- More stable, less buggy
- More frequent updates and guaranteed support
- Syncing will work on any server with JourneyMap v6 beta.71 or newer installed
## 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 is
1.13 up from 1.12>
> Very small server change where a new parameter was added to the sync packet to indicate to the client if JourneyMap is installed on the server.
> Despite the small change, this makes clients on 1.13 not able to join 1.12 servers, and if a 1.12 client joins a 1.13 server, there may be unexpected results.
> Please update both client and server immediately, at the same time.
Thank you for all your support.
- Server version 1.13*
## New
- No new features
## Bug fixes / changes
- Added logic to port synced JMWS waypoints and groups to JourneyMap. Once this is finished, JMWS should be uninstalled.
To transition synced JMWS waypoints and groups to JourneyMaps server waypoints, simply join a server with JMWS v1.2.6 and the latest version of JourneyMap.
The migration will happen automatically. JMWS will put itself in a disabled state for that server, and then you are free to uninstall it.
If you join a server with JMWS v1.2.6 on both sides but no JourneyMap on the server, JMWS will just function as normal.
- What about my shared waypoints and groups?*
You will have to share them again manually using JourneyMap, which now supports shared waypoints and groups.
- What about my global waypoints and groups?*
You will have to make them global manually using JourneyMap, which now supports global waypoints and groups.
- What if I for some reason want to keep using JMWS?*
- You can continue to use it, but consider this a warning not to as I will not update JMWS for any new versions past 26.1.2
- Sharing UI
- Global object UI
- Seamless, native integration
- More stable, less buggy
- More frequent updates and guaranteed support
- Syncing will work on any server with JourneyMap v6 beta.71 or newer installed
## 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 is
1.13 up from 1.12>
> Very small server change where a new parameter was added to the sync packet to indicate to the client if JourneyMap is installed on the server.
> Despite the small change, this makes clients on 1.13 not able to join 1.12 servers, and if a 1.12 client joins a 1.13 server, there may be unexpected results.
> Please update both client and server immediately, at the same time.
Thank you for all your support.
- Server version 1.13*
## New
- No new features
## Bug fixes / changes
- Added logic to port synced JMWS waypoints and groups to JourneyMap. Once this is finished, JMWS should be uninstalled.
To transition synced JMWS waypoints and groups to JourneyMaps server waypoints, simply join a server with JMWS v1.2.6 and the latest version of JourneyMap.
The migration will happen automatically. JMWS will put itself in a disabled state for that server, and then you are free to uninstall it.
If you join a server with JMWS v1.2.6 on both sides but no JourneyMap on the server, JMWS will just function as normal.
- What about my shared waypoints and groups?*
You will have to share them again manually using JourneyMap, which now supports shared waypoints and groups.
- What about my global waypoints and groups?*
You will have to make them global manually using JourneyMap, which now supports global waypoints and groups.
- What if I for some reason want to keep using JMWS?*
- You can continue to use it, but consider this a warning not to as I will not update JMWS for any new versions past 26.1.2
- Sharing UI
- Global object UI
- Seamless, native integration
- More stable, less buggy
- More frequent updates and guaranteed support
- Syncing will work on any server with JourneyMap v6 beta.71 or newer installed
## 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 is
1.13 up from 1.12>
> Very small server change where a new parameter was added to the sync packet to indicate to the client if JourneyMap is installed on the server.
> Despite the small change, this makes clients on 1.13 not able to join 1.12 servers, and if a 1.12 client joins a 1.13 server, there may be unexpected results.
> Please update both client and server immediately, at the same time.
Thank you for all your support.
- 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.12 up from 1.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.12 up from 1.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.
- 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.12 up from 1.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.12 up from 1.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.
- 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.12 up from 1.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.12 up from 1.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.
- 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.12 up from 1.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.
- 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.12 up from 1.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.
- 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.12 up from 1.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.
- 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.12 up from 1.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.
- 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.12 up from 1.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.
- 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.12 up from 1.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.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.
- Server version 1.11*
## New
- New command
remove_global_no_op waypoint|group <object_identifier>--> Removes a global object that was made by an opped player who is no longer opped.
## Bug fixes / changes
- Added text response if a global object is already global.
- Added server-side config option for handshake packet delay, before, some clients may not have been able to sync if on a lower-end computer. This can now be fixed by extending the handshake packet delay. Default is 250.
- Internal changes
## Pre-existing bugs
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 is now
1.11 up from 1.103- Added new command stated above.
- Added new client text.
Due to the new client text and server changes, plus changes with JourneyMap, all clients connecting to a 1.11 server **MUST** also be on 1.11.
If a client isn't on the correct version, it could cause catastrophic side effects for said client.