Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's Talk About Bungeecord... #295

Open
darbyjack opened this issue Feb 25, 2020 · 8 comments
Open

Let's Talk About Bungeecord... #295

darbyjack opened this issue Feb 25, 2020 · 8 comments

Comments

@darbyjack
Copy link
Member

Hi all,

Over the past few months, people have been specifically suggesting Bungeecord support in the plugin and I just want to talk to you about what Bungeecord means to me and I would like your input on it too.

People are talking about syncing server data across multiple servers, but the issue here is, at least with most servers, you can't treat the data in this plugin on one server as a clone for another server.

The data inside the plugin relies on multiple things such as locations of the world, player data, and so much more.

For example: If you have a guild home set on one server, and a player on another server tries to go there, how is that going to work? It's going to take you to a random location, because the worlds wouldn't be the same.

Another thing would be Guild Vaults. Do you guys understand how much duping would be allowed if you tried to allow players on 1 server put items in and let players on another server take it out in real time?. I don't think that's even possible to try and mitigate.

When it comes to Bungee, what exactly are you wanting to sync across servers.

I hope that you can understand where I'm coming from when it comes to Bungee. I'm not officially saying no to supporting it, but I need to understand why I should and what the benefits are because right now, if I implemented it, I'd be disabling homes, vaults, claims, arenas, etc.

All of them aren't designed to work across servers.

Thanks for taking the time to read this and I look forward to your input.

@Danrique
Copy link

Very cool, you make this.

Ok how I though I would use with multiple servers.

I would configurate the plugin to be one home server, the server would be the home of all guilds. all the others servers, I would only allow to use the chat and receive the buffs (buff like potions, or better attack and xp rate for exemple)

I dont need vaults in every server, or bank. All this would be done in the main server only.

Of course, the commands to add, promote and remove ppl from your guild would be cool to be able to use in the network...

I think with a main jar for the home server and another jar for the support on the others servers would be easy to start and will attend the majority of users.

Another option is each guild choose witch server they want as home. Of course, you as owner of the server should list servers/worlds allowed to do this.

With the option of a secondary jar we would be able to make arenas in others servers, use buffs in servers made for gather resourses and atc. If we have a server of "minigames" and we dont want to apply the buffs there, we simply dont instal the secondary jar.

Thanks for hear us!

@Dapill
Copy link

Dapill commented Mar 23, 2020

We need teleportation between servers
A guild vault can be made in such a way that only one player can open at a time

@Dapill
Copy link

Dapill commented Mar 23, 2020

BungeeSuite is a cool teleport plug-in between servers, you can somehow make support🤔

@Danrique
Copy link

Danrique commented Aug 5, 2020

ok then...

@Cesaario
Copy link

I started to implement this feature. It's working almost ok in my bungee server. I'd really appreciate some help doing that if anyone wants to join me.

@x9nico
Copy link

x9nico commented Jun 7, 2021

It could be cool to add for Velocity proxy to !

@goflishMC
Copy link

You would make a addon that catches events and sends to each server in a defined list with your bungeecord addon.

So, if I'm in server A, and set a guild home, it would be added to each server when the bungeecord addon catches it. I'm assuming right now when a player creates the guild home some code writes the location. Using that same logic, you would also record the server where it was created. Then when you do the guild home command you you could check for the correct server, send them there and then to the location.

Bungeecord will queue the events that need to be run on each server if one of the server goes offline, when that server comes back up then the events will run for that server. (this will keep the data synced properly, bungee does this already)

This would work the same for commands, so if you run a command to add a player to your guild, the event catcher with the bungeecord addon will run that command on all servers, same thing with any of the other commands.

An idea bout guild vaults: Would you be able to make it so that the items are not saved until the GUI is closed?

Other possible options for the guild vaults, stop players from opening if it's already opened.

Add an option to remove guild vaults, and an option to only be able to open guild vaults in a certain server/world.

@darbyjack
Copy link
Member Author

Hey @goflishMC,

Thanks for your input on this.

I would agree with you that if this were to ever be done, there would most likely need to be a Bungee addon to handle some of this stuff.

For the homes, logically that would make sense but we would need to design a way to work on single servers because that was the original intention when the design was implemented.

The data syncing on Bungee isn't necessarily the easiest. I know there's multiple ways, one being PluginMessaging which from my knowledge only works if there are actually players on the receiving server else it will just ignore it.

The commands seem logical the way you put it, so, I like that.

When it comes to the vaults, it wouldn't really matter if the items aren't saved until the GUI is closed because they would constantly write over each other and could easily be exploitable. The best thing I could think of for that would just be to just disable the vaults as you said for cross server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants