From aedb51766267bd6f8450d740c1c931b0c1b14af8 Mon Sep 17 00:00:00 2001 From: William Date: Sat, 19 Feb 2022 19:27:19 +0000 Subject: [PATCH 1/3] Update README.md --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 03484ac5..6d09dbd1 100644 --- a/README.md +++ b/README.md @@ -37,10 +37,15 @@ To migrate from MySQLPLayerDataBridge, you need a Proxy server with HuskSync ins #### Commands do not function Please check that the plugin is installed and enabled on both the proxy and bukkit server you are trying to execute the command from and that both plugins connected to Redis. (A connection handshake confirmation message is logged to console when communications are successfully established.) -#### SQL errors in proxy console / data not synchronising +#### Data not being synced on player join and SQL errors in proxy console This issue frequently occurs in users running Cracked (illegal) servers. I do not support piracy and so will be limited in my ability to help you. If you are running an offline server for a legitimate reason, however, make sure that in the `paper.yml` of your Bukkit servers `bungee-online-mode` is set to the correct value - and that both your Proxy (BungeeCord, Waterfall, etc.) server and Bukkit (Spigot, paper, etc.) servers are set up correctly to work with offline mode. +#### Data sometimes not syncing between servers +There are two primary reasons this may happen: +* On your proxy server, you are running FlameCord or a similar fork of Waterfall. Due to the nature of these forks changing security parameters, they can block or interfere with Redis packets being sent to and from your server. FlameCord, XCord and other forks are not compatible with HuskSync. For security-conscious users, I reccommend Velocity. +* Your backend servers/proxy and Redis server have noticably different amounts of latency between each other. This is particularly relevant for users running across multiple machines, where some backend servers / the proxy are installed with Redis and other backend servers are on a different machine. The solution to this is to have your BungeeCord and Redis _alone_ on one machine, and your backend servers across the others - or have a seperate machine with equal latency to the others that has Redis on. In the future, I may have a look at automatically correcting and accounting for differences in latency. + ## How it works ![Flow chart showing different processes of how the plugin works](images/flow-chart.png) HuskSync saves a player's data when they log out to a cache on your proxy server, and redistributes that data to players when they join another HuskSync-enabled server. Player data in the cache is then saved to a database (be it SQLite or MySQL) and this is loaded from when a player joins your network. From cfe38790102e954600a3d1124ebd84011c2e6b2c Mon Sep 17 00:00:00 2001 From: William Date: Sat, 19 Feb 2022 19:29:38 +0000 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6d09dbd1..8253a9d9 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ If you are running an offline server for a legitimate reason, however, make sure #### Data sometimes not syncing between servers There are two primary reasons this may happen: -* On your proxy server, you are running FlameCord or a similar fork of Waterfall. Due to the nature of these forks changing security parameters, they can block or interfere with Redis packets being sent to and from your server. FlameCord, XCord and other forks are not compatible with HuskSync. For security-conscious users, I reccommend Velocity. +* On your proxy server, you are running _FlameCord_ or a similar fork of Waterfall. Due to the nature of these forks changing security parameters, they can block or interfere with Redis packets being sent to and from your server. FlameCord, XCord and other forks are _not compatible_ with HuskSync. For security-conscious users, I reccommend Velocity. * Your backend servers/proxy and Redis server have noticably different amounts of latency between each other. This is particularly relevant for users running across multiple machines, where some backend servers / the proxy are installed with Redis and other backend servers are on a different machine. The solution to this is to have your BungeeCord and Redis _alone_ on one machine, and your backend servers across the others - or have a seperate machine with equal latency to the others that has Redis on. In the future, I may have a look at automatically correcting and accounting for differences in latency. ## How it works From fb3b2bd66ee790ad3d15a9ca3f591f1f7d9aa406 Mon Sep 17 00:00:00 2001 From: William Date: Sat, 19 Feb 2022 19:31:03 +0000 Subject: [PATCH 3/3] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8253a9d9..4b0400e5 100644 --- a/README.md +++ b/README.md @@ -43,8 +43,8 @@ If you are running an offline server for a legitimate reason, however, make sure #### Data sometimes not syncing between servers There are two primary reasons this may happen: -* On your proxy server, you are running _FlameCord_ or a similar fork of Waterfall. Due to the nature of these forks changing security parameters, they can block or interfere with Redis packets being sent to and from your server. FlameCord, XCord and other forks are _not compatible_ with HuskSync. For security-conscious users, I reccommend Velocity. -* Your backend servers/proxy and Redis server have noticably different amounts of latency between each other. This is particularly relevant for users running across multiple machines, where some backend servers / the proxy are installed with Redis and other backend servers are on a different machine. The solution to this is to have your BungeeCord and Redis _alone_ on one machine, and your backend servers across the others - or have a seperate machine with equal latency to the others that has Redis on. In the future, I may have a look at automatically correcting and accounting for differences in latency. +* On your proxy server, you are running _FlameCord_ or a similar fork of Waterfall. Due to the nature of these forks changing security parameters, they can block or interfere with Redis packets being sent to and from your server. FlameCord, XCord and other forks are not compatible with HuskSync. For security-conscious users, I recommend Velocity. +* Your backend servers/proxy and Redis server have noticeably different amounts of latency between each other. This is particularly relevant for users running across multiple machines, where some backend servers / the proxy are installed with Redis and other backend servers are on a different machine. The solution to this is to have your BungeeCord and Redis alone on one machine, and your backend servers across the others - or have a separate machine with equal latency to the others that has Redis on. In the future, I may have a look at automatically correcting and accounting for differences in latency. ## How it works ![Flow chart showing different processes of how the plugin works](images/flow-chart.png)