ВЕРСИИ (112)

# JMWS 1.2.8 for 1.21.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.

# JMWS 1.2.8 for 1.21.11 ## 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.

# JMWS 1.2.8 for 26.1.2 ## 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.

# JMWS 1.2.7 for 1.21.1 *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.

# JMWS 1.2.7 for 1.21.1 *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.

# JMWS 1.2.7 for 1.21.1 *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.

# JMWS 1.2.7 for 1.21.11 *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.

# JMWS 1.2.7 for 1.21.11 *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.

# JMWS 1.2.7 for 1.21.11 *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.

# JMWS 1.2.7 for 26.1.2 *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.

# JMWS 1.2.7 for 26.1.2 *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.

# JMWS 1.2.7 for 26.1.2 *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.

# JMWS 1.2.6 for 26.1.2 *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 and JourneyMaps syncing system is far superior to JMWS. Including** - 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.

# JMWS 1.2.6 for 26.1.2 *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 and JourneyMaps syncing system is far superior to JMWS. Including** - 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.

# JMWS 1.2.6 for 26.1.2 *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 and JourneyMaps syncing system is far superior to JMWS. Including** - 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.

# 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.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.

# 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.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.

# 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.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.

# JMWS 1.2.5 for 1.21.1 *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.

# JMWS 1.2.5 for 1.21.1 *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.

# JMWS 1.2.5 for 1.21.1 *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.

# JMWS 1.2.5 for 26.1.x *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.

# JMWS 1.2.5 for 26.1.x *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.

# JMWS 1.2.5 for 26.1.x *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.

# 1.2.4 for 26.1.x *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.

# 1.2.4 for 26.1.x *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.

# 1.2.4 for 26.1.x *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.

# 1.2.4 for 1.21.1 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 1.21.1 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 1.21.1 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 1.21.11 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 1.21.11 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 1.21.11 changelog (Direct port from 26.1.1, no changes) *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.

# 1.2.4 for 26.1.1 changelog (Direct port from 26.1, no changes) *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.

# 1.2.4 for 26.1.1 changelog (Direct port from 26.1, no changes) *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.

# 1.2.4 for 26.1.1 changelog (Direct port from 26.1, no changes) *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.

# 1.2.4 Changelog *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.

# 1.2.4 Changelog *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.

# 1.2.4 Changelog *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.

This is a beta. Full changelog will be shown on release.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.3 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed an issue where Waystones waypoints would duplicate / not show at all. - Resolves https://github.com/NavidRohim/JMWS/issues/5 - Fixed an issue where, if using the Flashback mod, the client would crash when playing back a recording. - Resolves https://github.com/NavidRohim/JMWS/issues/7 - JMWS no longer syncs objects belonging to other plugins. Only player-made objects. - To any normal user, this change does nothing. ## Bugs that I am aware of - When using fullscreen map, you cannot delete synced objects with the dropdown menu. - This is a JourneyMap problem and will be fixed in the future. I realize 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.102 (Up from 1.101, minor changes) updating is recommended.

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 1.2.2 Changelog ## New No new features. Very minor bug fix. ## Bug fixes - Fixed a bug where if you tried to update a local-only waypoint, game would crash. - Issue discovered by Kaac on discord. I owe them this as it caused trouble for them. ## 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 Server version is still 1.101 (No change)

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 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](https://files.minecraftforge.net/project_index.html) for new ForgeGradle 7 versions which will make your life developing easier. Also check [this repo](https://github.com/MinecraftForge/MDKExamples) for ForgeGradle 7 examples. Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.2.0 Changelog ## New - New feature: Shared objects - New feature: Global objects Read below for what they are and do. ### What are objects? "Objects" is simply a generalised term I use for waypoints or groups. ## Bug fixes / Changes - Fixed possible bug where waypoints / groups added by 3rd party plugins of JM would be persistent when created (would reappear after being deleted and joining back) ### What are shared objects? Shared objects are just waypoints or groups that have been shared by one player to others. These objects update live (changing name, location, etc) which includes deletion. #### How do they work? Create a waypoint or group like normal. Then do `/share_waypoint <share_to> <waypoint>` where `share_to` is the user you want to share with, and `waypoint` is the name of the waypoint you want to share. This is the same for groups but using `/share_group` The user who receives the object will have to accept the share request, there is a 20-second timeout. If this time passes, the request will automatically be declined. #### How do I stop sharing an object? Simply do `/stop_sharing_waypoint <waypoint>` where `waypoint` is the name of the waypoint you want to stop sharing. This is the same with groups but you do `/stop_sharing_group` ### What are global objects? Global objects are like shared objects, but they are shared with everyone at the same time! These can only be made by administrators. #### How do they work? Create a waypoint or group like normal. Then do `/jmws_admin create_global_waypoint <waypoint>` where `<waypoint>` is the name of waypoint that will become global. This is the same for groups but using `/jmws_admin create_global_group` #### How do I stop sharing a global object? Do `/jmws_admin remove_global_waypoint <waypoint>` where `<waypoint>` is the name of the global waypoint you want to remove. This is the same for groups but using `/jmws_admin remove_global_group`. Also, "remove" means to just stop sharing it with everyone. The player who originally made it will regain it as normal waypoint / group #### I want to know more. When a shared / global object is created, users will gain access to it, but they will not be able to modify it. Only the original creator can. And, if in a LAN world, the host cannot share nor create global objects. Also, if an object is global, you'll see a little `(G)` at the end of the name. You can turn this off in the config (Uncheck "Global Label?") This is the same with shared objects, but instead you'll see the name of the user who owns the object. And if they are offline, it'll just be `(S)` like global objects. ## Bugs that I am aware of None (with my mod) 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) ### Other New server version = 1.1 (Up from 1.01) *Server version is 1.1, massive server changes from 1.01. Update server and client immediately. Clients who join a 1.1 server when on 1.01 WILL face errors and possibly lose saved objects. I do not take responsibility if this occurs. You have been warned.* Thanks!

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.8 Changelog ## New No new features. ## Bug fixes / Changes - Fixed bug where users with large amount of waypoints / groups would disconnect due to default size limit of 32k bytes. - Now fixed by increasing the limit to 2MB (2,097,000) - This is technically possible to reach but, I just refuse to believe anyone has that amount. This fix is courtesy of isHaack on GitHub (resolves https://github.com/NavidRohim/JMWS/issues/4) ## Bugs that I am aware of None! ### Other *Server version is 1.01, fully backwards compatible with 1.00 granting you don't have a lot of waypoints / groups (100+)*

# 1.1.7 for 1.12.2 Changelog This is mostly a direct port with one exception that is: you cannot view the servers config in forge's config screen. May rectify with another update in the future. ## New - JMWS will now work on LAN servers. - Auto-Syncing can be disabled in the config. - JMWS syncs immediately instead of a 3-second delay. ## Bug fixes / Changes - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Server now sends handshake instead of the client - Fixed bug where getSyncInterval and nextSync commands wouldn't work. - Fixed bug where coloured action bar text would glitch - Fixed bug where server config just did not work. ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7-001 Changelog ## New (001) No new features, but 001 is a hotfix to fix a fabric fatal dependency issue. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7-001 Changelog ## New (001) No new features, but 001 is a hotfix to fix a fabric fatal dependency issue. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7-001 Changelog ## New (001) No new features, but 001 is a hotfix to fix a fabric fatal dependency issue. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7 Changelog ## New No new features. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7 Changelog ## New No new features. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.7 Changelog ## New No new features. ## Bug fixes / Changes - The servers JMWS configuration is now visible to the client in the Addon Options screen - This may be helpful if you find you cannot create waypoints or groups. - When JourneyMap is not installed on the client side, a screen is now shown instead of an overly-verbose crash report. - Added server version checking. This is to make debugging easier. - Added JavaDocs to GitHub - Couldn't delete waypoints in nether when in dimension other than nether (and vice versa) ## Bugs that I am aware of None! ### Other *Server version is 1.00*

# 1.1.6 Changelog ## Installation Changes (JMWS 1.21.8) There have been changes regarding dependencies. The server-side must have [CommonNetworking 1.0.21-1.21.7](https://www.curseforge.com/minecraft/mc-mods/common-network/files/all?page=1&pageSize=20) installed. As usual, the client-side must have JourneyMap 1.21.8-6.0.0-beta.52 or newer. ## New This is mostly bug fixing and tweaks. - Waypoint drag-and-drop now finally works (You MUST have JourneyMap Version 6 Beta 52 or newer for this to fix) - JMWS will now sync as soon as JourneyMap is ready (There was a 3-second delay before, due to initialisation) ## Bug fixes / Changes - Server will once again send handshake packet as soon as possible (There was a 3-second delay before because the clients map needed to initialise) - Game can load without JourneyMap installed (JMWS will be disabled, before the game would send an error) - CommonNetworking or JourneyMap is now sadly required on the server side. It has always been required, but I only realised now. I have no clue why it took me so long. - Added unique text when death waypoint is made ## Persistent bugs that I am aware of None. If there are any please do make a GitHub issue or join my discord. I will be happy to help

# 1.1.6 Changelog ## Installation Changes (JMWS 1.21.8) There have been changes regarding dependencies. The server-side must have [CommonNetworking 1.0.21-1.21.7](https://www.curseforge.com/minecraft/mc-mods/common-network/files/all?page=1&pageSize=20) installed. As usual, the client-side must have JourneyMap 1.21.8-6.0.0-beta.52 or newer. ## New This is mostly bug fixing and tweaks. - Waypoint drag-and-drop now finally works (You MUST have JourneyMap Version 6 Beta 52 or newer for this to fix) - JMWS will now sync as soon as JourneyMap is ready (There was a 3-second delay before, due to initialisation) ## Bug fixes / Changes - Server will once again send handshake packet as soon as possible (There was a 3-second delay before because the clients map needed to initialise) - Game can load without JourneyMap installed (JMWS will be disabled, before the game would send an error) - CommonNetworking or JourneyMap is now sadly required on the server side. It has always been required, but I only realised now. I have no clue why it took me so long. - Added unique text when death waypoint is made ## Persistent bugs that I am aware of None. If there are any please do make a GitHub issue or join my discord. I will be happy to help

# 1.1.6 Changelog ## Installation Changes (JMWS 1.21.8) There have been changes regarding dependencies. The server-side must have [CommonNetworking 1.0.21-1.21.7](https://www.curseforge.com/minecraft/mc-mods/common-network/files/all?page=1&pageSize=20) installed. As usual, the client-side must have JourneyMap 1.21.8-6.0.0-beta.52 or newer. ## New This is mostly bug fixing and tweaks. - Waypoint drag-and-drop now finally works (You MUST have JourneyMap Version 6 Beta 52 or newer for this to fix) - JMWS will now sync as soon as JourneyMap is ready (There was a 3-second delay before, due to initialisation) ## Bug fixes / Changes - Server will once again send handshake packet as soon as possible (There was a 3-second delay before because the clients map needed to initialise) - Game can load without JourneyMap installed (JMWS will be disabled, before the game would send an error) - CommonNetworking or JourneyMap is now sadly required on the server side. It has always been required, but I only realised now. I have no clue why it took me so long. - Added unique text when death waypoint is made ## Persistent bugs that I am aware of None. If there are any please do make a GitHub issue or join my discord. I will be happy to help

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

Refer to 1.1.5 for changes. This port has no code changes. Thanks to stark on discord.

# 1.1.5 Changelog ## New - JMWS now works in LAN servers! - Can now turn off auto-syncing - Many bug fixes ## Bug fixes - Fixed bug where /jmws clearAll and any subcommands did not work - Fixed bug where if the player was dead and JMWS tried to auto-sync, an error would occur - Death waypoints can now be synced without the need for auto-sync - Fixed bug where players local objects would be wiped if the server disallowed syncing, but the client synced anyway - Fixed major bug where if a user used an illegal character for a waypoint, there would be a recursion error on the server (from trying to create the filename too many times) - Fixed bug where JMWS would not obligate config value for waypoint events - Internal changes due to LAN support (mainly to the handshake packet sequence, **Please report any bugs**) ## Persistent bugs that I am aware of - Dragging and dropping waypoints does not work, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if available) ## Future beyond v1.1.5 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.5 Changelog ## New - JMWS now works in LAN servers! - Can now turn off auto-syncing - Many bug fixes ## Bug fixes - Fixed bug where /jmws clearAll and any subcommands did not work - Fixed bug where if the player was dead and JMWS tried to auto-sync, an error would occur - Death waypoints can now be synced without the need for auto-sync - Fixed bug where players local objects would be wiped if the server disallowed syncing, but the client synced anyway - Fixed major bug where if a user used an illegal character for a waypoint, there would be a recursion error on the server (from trying to create the filename too many times) - Fixed bug where JMWS would not obligate config value for waypoint events - Internal changes due to LAN support (mainly to the handshake packet sequence, **Please report any bugs**) ## Persistent bugs that I am aware of - Dragging and dropping waypoints does not work, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if available) ## Future beyond v1.1.5 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.5 Changelog ## New - JMWS now works in LAN servers! - Can now turn off auto-syncing - Many bug fixes ## Bug fixes - Fixed bug where /jmws clearAll and any subcommands did not work - Fixed bug where if the player was dead and JMWS tried to auto-sync, an error would occur - Death waypoints can now be synced without the need for auto-sync - Fixed bug where players local objects would be wiped if the server disallowed syncing, but the client synced anyway - Fixed major bug where if a user used an illegal character for a waypoint, there would be a recursion error on the server (from trying to create the filename too many times) - Fixed bug where JMWS would not obligate config value for waypoint events - Internal changes due to LAN support (mainly to the handshake packet sequence, **Please report any bugs**) ## Persistent bugs that I am aware of - Dragging and dropping waypoints does not work, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if available) ## Future beyond v1.1.5 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# IMPORTANT When installing JMWS for Forge 1.12.2, sadly you will need an additional dependency **only** on the client side called "mixinbooter" which you can find here (you can add this to the server side but it will do nothing): https://www.curseforge.com/minecraft/mc-mods/mixin-booter Download the latest version of mixinbooter and drop it into your mods folder. Thank you and sorry for the inconvenience. Credits to NuRoZ on discord for giving me inspiration to make this port, plus Mysticbrew for technical support. ## 1.1.4 Changelog (1.12.2 only) - Switched to using Forge configuration screen - Added support for auto death waypoint deletion ## Bugs - Action bar text will flicker (only on 1.12.2) looking for a fix ## Differences between 1.1.4 for 1.21.x and backport for 1.12.2 - Waypoint group support is gone (because JourneyMap doesn't have it in this version) - Using forge's configuration system instead of JourneyMap's or owo-lib's - Internal differences to how waypoints are stored on the server. They are stored with the primary dimensionID, then the Y level, then the name of the waypoint followed by the users UUID Aside from that, 1.1.4 for 1.12.2 and 1.1.4 for 1.21.x are identical in how they work. It is a direct backport and even uses the same code for most of it. If there are any bugs at all, please feel free to join my discord server or file a GitHub issue about it. If you have any other sort of request like a pull request or feature request please also mention it to me in the methods I mentioned. I will be happy to listen.

# 1.1.4 Changelog ## New - Switched over to JourneyMap configuration. To access new config, press `J`, click the options icon next to the waypoint button second from the far left, then click "Addon Options" - Added support for Forge and Neoforge ## Bug fixes - Due to new MultiLoader setup, there are probably infact *more* bugs. Please report any with a GitHub issue or tell me in the discord server (just @ me) ## Persistent bugs (only with newer versions of journeymap) - Dragging and dropping waypoints does not work yet again, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if avalible) ## Future beyond v1.1.4 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.4 Changelog ## New - Switched over to JourneyMap configuration. To access new config, press `J`, click the options icon next to the waypoint button second from the far left, then click "Addon Options" - Added support for Forge and Neoforge ## Bug fixes - Due to new MultiLoader setup, there are probably infact *more* bugs. Please report any with a GitHub issue or tell me in the discord server (just @ me) ## Persistent bugs (only with newer versions of journeymap) - Dragging and dropping waypoints does not work yet again, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if avalible) ## Future beyond v1.1.4 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.4 Changelog ## New - Switched over to JourneyMap configuration. To access new config, press `J`, click the options icon next to the waypoint button second from the far left, then click "Addon Options" - Added support for Forge and Neoforge ## Bug fixes - Due to new MultiLoader setup, there are probably infact *more* bugs. Please report any with a GitHub issue or tell me in the discord server (just @ me) ## Persistent bugs (only with newer versions of journeymap) - Dragging and dropping waypoints does not work yet again, not my fault will be fixed with new JourneyMap version (use JM beta.54 or newer if avalible) ## Future beyond v1.1.4 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# Added official support for Minecraft 1.21.8 There are no code changes in this version. The JourneyMap version minimum requirementis still 1.21.7-6.0.0-beta.53 due to the fact 1.21.8 is a hotfix update and has no code changes.

# 1.1.3 Changelog ## New - Drag and drop support for waypoints to groups now supported. (Read persistent bugs paragraph for more info) - Server-side configuration for administration (can disable waypoints / groups for users server-wide) - Change; added failsafe if "jmws" folder is deleted while server is running. ## Bug fixes - Groups deleted with waypoints inside would not be moved to the Default group until next sync. - Fixed version checking (would allow any JourneyMap jar) ## Persistent bugs (1.1.3-1.21.7 only) - Dragging and dropping waypoints does not work in latest version of JM. This is not my fault and will be fixed with new JourneyMap version (use JM beta.54 or newer if avalible) ## Future beyond v1.1.3 Ports for new minecraft versions and nothing more. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.3 Changelog ## New - Drag and drop support for waypoints to groups now supported. - Server-side configuration for administration (can disable waypoints / groups for users server-wide) - Change; added failsafe if "jmws" folder is deleted while server is running. ## Bug fixes - Groups deleted with waypoints inside would not be moved to the Default group until next sync. - Fixed version checking (would allow any JourneyMap jar) ## Persistent bugs *None that I know of, either make issue or let me know on discord.* ## Future beyond v1.1.3 There is none. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.3 Changelog ## New - Drag and drop support for waypoints to groups now supported. - Server-side configuration for administration (can disable waypoints / groups for users server-wide) - Change; added failsafe if "jmws" folder is deleted while server is running. ## Bug fixes - Groups deleted with waypoints inside would not be moved to the Default group until next sync. - Fixed version checking (would allow any JourneyMap jar) ## Persistent bugs *None that I know of, either make issue or let me know on discord.* ## Future beyond v1.1.3 There is none. This mod is finished in my eyes and I have no further ideas. If there are any bugs that are found, let me know via issue or discord and I will fix them. If you have some sort of feature request I will do my best to fulfill it but as for me, I have no further ideas. Thank you for anyone who has showed an interest, joined the discord or just has used the mod.

# 1.1.2 Changelog ## New - Important continuity change to match with v1.1.2-1.21.1 ## Bug fixes *None* ## Persistent bugs - Same bugs as in v1.0.7 changelog.

# 1.1.2-1.21.1 Changelog ## Changes - Initial release for 1.21.1 - Hotfix; fixing internal mechanisms for continuity across all versions. ## Bug fixes *None* ## Persistent bugs *Same bugs as in v1.0.7 changelog.*

# 1.1.1 Changelog ## Changes - JourneyMap now not needed server-side. - JMWS returns new text if playing on single player, and JMWS map buttons do not render. - Commands are now client-side only. - `/jmws clearAll groups` now deletes all groups on the client - Text colour changes - Wording changes ## Bug fixes - When editing local object; game would crash. Object is now just uploaded. - When making group in waypoint creation dialogue box; Error would be shown (like a group could not be created, though that wasn't the case) group is now made with no false-positive. ## Persistent bugs - Same bugs as in v1.0.7 changelog.

# 1.1.0 ### New - Added sound effects (disabled by default, enable in config) - Added coloured text code (will be used in the future) ### Changes - Fixed language strings ### Bug fixes - fixed crash if malformed group / waypoint data was passed to client ### Persistent bugs *Same bugs stated in 1.0.7 changelog*

# 1.0.9 - Added buttons to JourneyMap for JMWS settings. * On and off button (same as config) * Sync button (same as doing `/jmws update`) ### Fixed bugs - caught potential crash regarding packet sizes for huge amounts of waypoints and groups. ### Persistent bugs *Same bugs as stated in 1.0.7 changelog*

# 1.0.8 ### Small change only - Client now syncs after 2 seconds when switching dimensions. Thank you to YifePlayte once again for pointing this out. ### Other This mod is basically finished in my eyes. I will continue to fix bugs as people come across them, fix the bugs mentioned in the changelogs of v1.0.7, and I am open to translation requests if translations are provided. I will look into doing a backport for 1.12.2.

# 1.0.7 ### Bug fixes only. - Resolved bug when joining a server with JMWS installed for the first time, waypoints would not be put in their respective groups. - When editing a group, the waypoints in that group would be deleted temporarily until next sync. ### Known bugs (unrelated to JMWS, JourneyMap API is to fault) - You cannot drag and drop waypoints to groups. - When you delete a waypoint thats in a custom group, it will not be moved to the Default group until next sync. *Thanks to YifePlayte for finding the first bug.*

# 1.0.6 (important; JourneyMap Version 6.0.0-beta 47 or higher required) - Groups now supported - New configuration options where you can turn off waypoint and group syncing individually - Fixed bugs - Mod detection (mod will turn off if server doesnt have JMWS installed) - Optimisations thanks to JourneyMap 1.21.5 Beta 47 *Very big thank you to Mysticbrew on discord-- the creator of JourneyMap who helped guide me through some things and introducing API changes for me*

# 1.0.5 - Death waypoints have been fixed (before they would not upload and would be deleted, but still not added to the death waypoint group. This will change in the near future) - Waypoints are now added to their respective groups (they all go to the default group before, except death waypoints) - Internal changes (waypoints are now non-persistent and will stay that way) - Added new command (\`/jmws nextUpdate\`) which shows how long until next automatic waypoint update - Local waypoint bug fixes (before they would be added but you would either have to wait until the next waypoint update, 40 seconds by default or update with \`/jmws update\` - Other smaller bug fixes and language changes. - Internal changes regarding packets HUGE Thank you to the JourneyMap mod developer "Mysticdrew" on discord for technical support.

Removed old debug item Internal renaming because I said so (the old jm_server name was confusing me) waypoints are now fully reconstructed (except from groups, that will be sorted) fixed bug where the primary dimension for a waypoint was always the overworld

# 1.0.2 - Can now disable the mod - Fixed issue where when updating a waypoint, the creation / deletion text would show. A new message is now shown - When joining a server for the first time with JMWS, if you had waypoints prior to installing on the server, those waypoints would be wipped as they werent registed on the server. They will now be registered.

initial release