generated from PrismarineJS/prismarine-template
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Can't connect to flying squid server with prismarine-web-client #301
Labels
bug
Something isn't working
Comments
I have managed to get it working by wrapping a couple of things in hud.js in a bot.on('spawn' ...) but as I've only looked at the code for about an hour, I'm guessing I shouldn't be the one to make the change. Here are the changes: line 215 of ./lib/menus/hud.js: lines 254-263 of ./lib/menus/hud.js:
|
rom1504
added a commit
that referenced
this issue
May 21, 2022
Co-authored-by: Keir Finlow-Bates <[email protected]> Co-authored-by: Romain Beaumont <[email protected]>
extremeheat
referenced
this issue
in extremeheat/prismarine-web-client
Apr 13, 2023
Co-authored-by: Keir Finlow-Bates <[email protected]> Co-authored-by: Romain Beaumont <[email protected]>
Moondarker
referenced
this issue
in Moondarker/prismarine-web-client
Apr 13, 2023
Co-authored-by: Keir Finlow-Bates <[email protected]> Co-authored-by: Romain Beaumont <[email protected]>
Moondarker
referenced
this issue
in Moondarker/prismarine-web-client
Apr 13, 2023
Co-authored-by: Keir Finlow-Bates <[email protected]> Co-authored-by: Romain Beaumont <[email protected]>
Having the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please see PrismarineJS/flying-squid#591
There seems to be an issue with the playerlist_overlay.js file in prismarine-web-client when connecting to a flying squid server, in that https://github.com/PrismarineJS/prismarine-web-client/blob/master/lib/menus/components/playerlist_overlay.js#L106 is called too early.
The text was updated successfully, but these errors were encountered: