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

error when switching in between 1.8.8 and 1.20.1 servers on a Waterfall proxy #10

Open
4 tasks done
random-tek opened this issue Jan 13, 2024 · 10 comments
Open
4 tasks done

Comments

@random-tek
Copy link

/viaversion dump Output

https://dump.viaversion.com/e463da18d1f902bc16263cc5fc191fe92e7c03dafbabb4845a393b9fef245f72

Console Error

https://paste.gg/p/anonymous/96b404149fd84a568c68dd4ab6dd8c53

Bug Description

The proxy console outputs this error every time someone switches in between servers that have different versions (Paper 1.8.8 as the lobby and Paper 1.20.1 as a survival server). When switching from the lobby to the survival, the player does get switched over, however the error still occurs. It even gives out the same error when switching back to the lobby, but the player gets stuck in a void this time, as shown in this image below:
image

Steps to Reproduce

  1. Set up a 1.20 Waterfall proxy with two Paper servers (1.8.8 and 1.20.1)
  2. Add ViaVersion to the "plugins" folder in the proxy
  3. Join the server on a 1.20.1 client or higher
  4. Switch in between servers using "/server servernamehere" and the error should appear in the Waterfall console.

Expected Behavior

The error should'nt have occured and get the player stuck in a void while switching servers.

Additional Server Info

The Waterfall proxy also has the "VersionControl-1.3.4.jar" plugin in order to prevent players playing below 1.20 to connect to the newer server.

Checklist

  • Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. BungeeCord), not on both.
  • I have included a ViaVersion dump.
  • If applicable, I have included a paste (not a screenshot) of the error.
  • I have tried the latest build(s) from https://ci.viaversion.com/ and the issue still persists.
@Barvalg
Copy link
Member

Barvalg commented Jan 13, 2024

Platform: git%3AWaterfall--Bootstrap%3A1.20--R0.2--SNAPSHOT%3A92b5149%3A562
ViaVersion (4.9.2): 37 commits behind master

Please update all Via* plugins from https://ci.viaversion.com/. In case the issue still persists send the new dump and the issue will be reopened


corrupt_jar

@Barvalg Barvalg added the invalid This doesn't seem right label Jan 13, 2024
@Barvalg Barvalg closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
@random-tek
Copy link
Author

@Barvalg
Copy link
Member

Barvalg commented Jan 13, 2024

Platform: git%3AWaterfall--Bootstrap%3A1.20--R0.2--SNAPSHOT%3A92b5149%3A562
ViaVersion (4.9.3-SNAPSHOT): Even with master

@Barvalg Barvalg reopened this Jan 13, 2024
@Barvalg Barvalg removed the invalid This doesn't seem right label Jan 13, 2024
@Kichura
Copy link
Member

Kichura commented Jan 13, 2024

Can you test with an vanilla client to see if it persists? if it does then a third-party plugin is causing chunks to not load as intended.

@random-tek
Copy link
Author

Can you test with an vanilla client to see if it persists? if it does then a third-party plugin is causing chunks to not load as intended.

The issue still persists with a vanilla client AND with all of the third-party plugins removed.

@Kichura
Copy link
Member

Kichura commented Jan 13, 2024

will try to investigate this then.

@Kichura
Copy link
Member

Kichura commented Jan 13, 2024

Cannot reproduce your problem:

mc

Is the world save bad perhaps? because something isn't adding up.

@random-tek
Copy link
Author

Is the world save bad perhaps? because something isn't adding up.

I tried regenerating the world save. This time I also set online-mode=true in the proxy's config.yml. Once I did that, the results were different. I was sent to the 1.20.1 server instead of the lobby, and got this error when switching over to the lobby:
image
Same results after setting online-mode back to false.

@Kichura
Copy link
Member

Kichura commented Jan 13, 2024

Can you test viaversion on spigot/paper servers instead of waterfall to see if it recovers at all? if yes; then something is making viaversion break on proxy side.

@random-tek
Copy link
Author

random-tek commented Jan 13, 2024

I moved the plugin from the proxy over to both servers. It does indeed work as intended - no errors at all.

However, I wouldn't be able to use the VersionControl addon since it's a proxy-sided plugin.

@FlorianMichael FlorianMichael transferred this issue from ViaVersion/ViaVersion Jul 27, 2024
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

3 participants