Add Bungee/Velocity support by integrating RedisBungee #8

New Issue

Govindas · 2020-12-04T15:19:58Z

GovindasOM commented

2020-12-04 15:19:58 +00:00

(Migrated from github.com)

for maximum functionality in a proxy environment, we should add "on proxy join" and "on proxy leave" events. for this we will need to integrate RedisBungee support.

we will also need a way to send message to all players/specific players at a proxy level, so you don't have to always keep track of player's current server.

another useful feature could be kicking the player at a proxy level

(all data should be managed by player names instead of uuids for maximum compatibility, as it won't matter if player name changes in this temporary data environment)

for maximum functionality in a proxy environment, we should add "on proxy join" and "on proxy leave" events. for this we will need to integrate RedisBungee support. we will also need a way to send message to all players/specific players at a proxy level, so you don't have to always keep track of player's current server. another useful feature could be kicking the player at a proxy level (all data should be managed by player names instead of uuids for maximum compatibility, as it won't matter if player name changes in this temporary data environment)

👍 2

GovindasOM commented

2020-12-04 15:23:52 +00:00

(Migrated from github.com)

LimeworkProxy (private repository) already supports all of this, however its way of doing it is not ideal as it requires more work for the user. we could send differently formatted JSON instead that'd be processed on Java side instead of Skript side.

ham1255 commented

2020-12-14 11:19:38 +00:00

(Migrated from github.com)

well we can do it on the same repo

ham1255 commented

2021-05-16 17:44:43 +00:00

(Migrated from github.com)

we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it

GovindasOM commented

2021-05-16 18:16:40 +00:00

(Migrated from github.com)

we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it

I very much agree with this

> we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it > I very much agree with this

ham1255 commented

2021-05-16 18:19:27 +00:00

(Migrated from github.com)

we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it

I very much agree with this

What if proxy version of the plugin uses redis bungee too? So no config needed since redis bungee can provide the jedis pool for us

> > we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it > > > > I very much agree with this What if proxy version of the plugin uses redis bungee too? So no config needed since redis bungee can provide the jedis pool for us

GovindasOM commented

2021-05-16 18:23:43 +00:00

(Migrated from github.com)

we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it

I very much agree with this

What if proxy version of the plugin uses redis bungee too? So no config needed since redis bungee can provide the jedis pool for us

issue is AES encryption would not be applied

> > > we could strip Limework proxy redis stuff and use it at redisskript instead and make limework proxy hook into it > > > > > > > I very much agree with this > > What if proxy version of the plugin uses redis bungee too? So no config needed since redis bungee can provide the jedis pool for us issue is AES encryption would not be applied

GovindasOM commented

2021-05-16 18:24:08 +00:00

(Migrated from github.com)

unless you can make it support that, i think you can

ham1255 commented

2021-05-16 18:25:50 +00:00

(Migrated from github.com)

I can put config for that thing just redis connection is just already provided by redis bungee

Govindas added

help wanted

and removed

work in progress