You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first snapshot has big internal changes but it wont effect normal functionality of redis-bungee unless there is bad bugs
before implementing velocity support
my initial testing went great and fixed some issue with payloads, Also Old plugins should work great but If by any MEANS getting JedisPool in your plugin it will fail with NoSuchMethod error due maven shade plugin weirdness that i removed.
looking forward for feedbacks
Changes in this update
API is longer depending on Bungeecord apis
deprecated RedisBungeeAPI#getJedisPool() and replaced with RedisBungeeAPI#requestJedis() which returns instance of Jedis
reason for this that we are going implement redis sentinel or clusters in future update (JedisPool != SentinelJedisPool)
RedisBungeeAPI#getServerFor(UUID player) now returns String instead of bungeecord net.md_5.bungee.api.config.ServerInfo
Relocation was disabled due causing issues with Jedis importing on plugins which throws NoSuchMethod errors
(if you plan to use redisbungee in your plugins make sure you dont have jedis shaded )
Events are now platform dependent, for example RedisBungee-BungeeEvents will be for bungeecord
reason for this because events on some platforms like bungeecord needs to be extended By Event class
which not supported to another proxies like velocity + API must be bungeecord clean
config option use-random-id-string has been removed due being useless
added warnings when ssl/tls is disabled or password is empty
23:50:57 [WARNING] [RedisBungee] INSECURE setup was detected Please set password for your redis instance.
23:50:57 [WARNING] [RedisBungee] INSECURE setup was detected Please setup ssl for your redis instance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The first snapshot has big internal changes but it wont effect normal functionality of redis-bungee unless there is bad bugs
before implementing velocity support
my initial testing went great and fixed some issue with payloads, Also Old plugins should work great but If by any MEANS getting
JedisPool
in your plugin it will fail withNoSuchMethod
error due maven shade plugin weirdness that i removed.looking forward for feedbacks
Changes in this update
API is longer depending on Bungeecord apis
deprecated
RedisBungeeAPI#getJedisPool()
and replaced withRedisBungeeAPI#requestJedis()
which returns instance ofJedis
reason for this that we are going implement redis sentinel or clusters in future update
(JedisPool != SentinelJedisPool)
RedisBungeeAPI#getServerFor(UUID player)
now returnsString
instead of bungeecordnet.md_5.bungee.api.config.ServerInfo
Relocation was disabled due causing issues with
Jedis
importing on plugins which throwsNoSuchMethod
errors(if you plan to use redisbungee in your plugins make sure you dont have jedis shaded )
Events are now platform dependent, for example
RedisBungee-BungeeEvents
will be for bungeecordreason for this because events on some platforms like bungeecord needs to be extended By Event class
which not supported to another proxies like velocity + API must be bungeecord clean
config option
use-random-id-string
has been removed due being uselessadded warnings when
ssl/tls
is disabled or password is emptyJava docs here
Importing in your projects
way of import RedisBungee has been changed
If you want to have
RedisBungeeAPI
classand if you want to use the events Import RedisBungee-BungeeEvents which for bungeecord
note: you need API imported too
Beta Was this translation helpful? Give feedback.
All reactions