Limework/RedisBungee
2
0
Fork 0
mirror of https://github.com/proxiodev/RedisBungee.git synced 2026-05-15 09:26:50 +00:00
Code Releases Activity
680 Commits 2 Branches 32 Tags
stable
Commit Graph

26 Commits

Author SHA1 Message Date
ham1255 1d2c11c538 maintenance: velocity require java 21 now for 3.5.0 2026-03-17 00:31:36 +04:00
ham1255 e495b11587 maintenance: fix javadocs of bungeecord and update to 5 instead of 4 2026-03-17 00:28:08 +04:00
ham1255 92c965bfc6 readd leagacy methods to bungeecord only 2025-02-24 23:20:02 +04:00
ham1255 1fb429ea77 finishup bungeecord, move to mini message as serialzier 2025-02-22 19:04:06 +04:00
ham1255 338297192c reimpl kick api using serialized messages instead, Move language to own module, depenedcies fixes 2025-02-22 17:57:06 +04:00
ham1255 1d3bd7e101 remove depercated apis | begin removing adventure api from the main api 2025-02-22 15:43:49 +04:00
ham1255 8177260991 make platforms can't see each other when using same redis server and network id 2025-02-21 19:44:52 +04:00
ham1255 287f037774 Remove generics used for events in PlayerData 2025-01-28 20:14:45 +04:00
ham1255 c633f1a106 properly cache last online and its invalidation 2025-01-28 20:14:45 +04:00
ham1255 9fd1da5f92 fix depenedcies being copied 2025-01-28 20:14:45 +04:00
ham1255 0050575aff update okhttp 2025-01-28 20:14:45 +04:00
ham1255 6eab4ef602 move gradle plugins to libs file 2025-01-28 20:14:44 +04:00
ham1255 8b9af8838d Fix methods of Bungeecord listener being private 
seems like i forgot to check the bungeecord impl correctly.
 2025-01-28 20:14:44 +04:00
Dawid Sawicki 81bf06e2df Allow to customize ping events priority via handle-motd-order (#108) 
Currently, the bungee implementation is using NORMAL priority for the
ping event handler, while the velocity implementation is using LAST.
Regardless of which choice may be the better one, this is an
inconsistency that this patch addresses by using NORMAL as the default
for both platforms.

Additionally to addressing the inconsistency, this patch adds a new
config option `handle-motd-order` which uses velocity's event priority
nomenclature to allow configuring the behavior of the MOTD handling on
both platforms.

In cases where there is a MOTD plugin that incorrectly overrides a
player count using the local player count, one may choose to use order
LAST to override the value back to the global player count.

In cases where there is a MOTD plugin that relies on a player count
value from the ping response, one may choose to use order FIRST to make
sure the response will have the correct global player count.

Fixes https://github.com/ProxioDev/ValioBungee/issues/107
 2025-01-28 20:14:44 +04:00
ham1255 41b1dab8cc update velocity runner 2025-01-28 20:14:44 +04:00
ham1255 a437db32b8 update gradle, update depends 2025-01-28 20:14:44 +04:00
ham1255 2bd79f628e runWaterfall & Waterfall proxy EOL 2025-01-28 20:14:44 +04:00
ham1255 91ea0b08dc relocate adventure api in bungeecord due collison with other plugins 2025-01-28 12:08:10 +04:00
ham1255 dab5f26e2c fix event double firing in velocity 2024-09-26 19:24:38 +04:00
ham1255 69e91c3e42 check if player is really on the proxy when connecting 
this prevents logged in error if somehow proxy shutdowns at weird time
 2024-09-26 13:43:33 +04:00
ham1255 e8715e5399 ignore IllegalStateException thrown by ServerConnection class in velocity 2024-05-14 19:23:09 +04:00
ham1255 71287055b4 fix javadocs x2 2024-05-13 02:43:47 +04:00
ham1255 8b48736bc1 fix javadocs 2024-05-13 02:38:58 +04:00
ham1255 a2e6aff4c2 remove java docs from proxy impl 2024-05-13 02:33:56 +04:00
ham1255 7f35b64d93 stupid git 2024-05-13 02:00:31 +04:00
ham1255 765e6fe122 redo module system 2024-05-13 01:54:50 +04:00