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

Bungee teleport setting break AuthmeBridge #1061

Closed
Twonox opened this issue Jan 9, 2017 · 12 comments
Closed

Bungee teleport setting break AuthmeBridge #1061

Twonox opened this issue Jan 9, 2017 · 12 comments

Comments

@Twonox
Copy link
Contributor

Twonox commented Jan 9, 2017

When bungeecord setting is true, a new registered player must type his login after the teleportation in other server by authme.

@sgdc3
Copy link
Member

sgdc3 commented Jan 9, 2017

That's because we deleted all the plugin message listeners

@sgdc3
Copy link
Member

sgdc3 commented Jan 9, 2017

We need to implement them again

@sgdc3
Copy link
Member

sgdc3 commented Jan 9, 2017

I just closed #197 as we should implement a new bukkit <-> bukkit and bukkit <-> bungee protocol

@Twonox
Copy link
Contributor Author

Twonox commented Jan 10, 2017

Any solution? It's urgent :/

@Xephi Xephi added this to the 5.2 Release milestone Jan 11, 2017
@ljacqu ljacqu modified the milestones: 5.3 Snapshot, 5.2 Release Jan 14, 2017
@sgdc3
Copy link
Member

sgdc3 commented Jan 20, 2017

@Twonox AuthMeBridge should work fine, could you test it? https://www.spigotmc.org/resources/authmebridge-for-bungeecord.574

@Twonox
Copy link
Contributor Author

Twonox commented Jan 21, 2017

OK, I will redo my test.

@Twonox
Copy link
Contributor Author

Twonox commented Jan 21, 2017

There is still this problem.
I remind that there is this issue only for players who have just been registered. If they join after his registration, they are successful login with AuthmeBridge.

@sgdc3
Copy link
Member

sgdc3 commented Jan 21, 2017

@ljacqu this is the last issue we need to fix to release, what do you think about it? Maybe caching issue?

@ljacqu
Copy link
Member

ljacqu commented Jan 21, 2017

@sgdc3 Nothing comes to mind currently, if I look at the registration code I see in three clicks where we update the DB to set logged = TRUE... Hmm. But please keep in mind I know very little about the Bungee part

@Twonox
Copy link
Contributor Author

Twonox commented Feb 13, 2017

Any solution ?
Maybe AuthmeBridge fault ?

@ljacqu ljacqu modified the milestones: 5.4 (Future), 5.3 Apr 29, 2017
@sgdc3
Copy link
Member

sgdc3 commented Nov 2, 2017

We completely changes how this work, this issue is now invalid

@sgdc3 sgdc3 closed this as completed Nov 2, 2017
@ljacqu
Copy link
Member

ljacqu commented Nov 3, 2017

I'm conflicted about keeping this in the milestone because we didn't do any work for this issue, but is this bug fixed (players don't have to use /login anymore after registering)? If so, fine for me to keep it in 5.4 milestone, since the bug was fixed somehow.

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

No branches or pull requests

4 participants