You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
SteamMultiplayerPeer will complain that the user is still in a lobby even after calling close(). This prevents the user from joining another lobby and forces the creation of another SteamMultiplayerPeer object.
To Reproduce
Steps to reproduce the behavior:
Create a script that with two buttons: the first should create a lobby through SteamMultiplayerPeer.create_lobby() and the second should close the connection with SteamMultiplayerPeer.close().
Click the first button to create a lobby.
Click the second button to close the peer.
Click the first button again to create a different lobby. An error in the console should pop up stating that the user is already in a lobby.
Expected behavior
I expect the multiplayer peer to create a different lobby and connect the user to that one instead.
Screenshots
Initial state before joining a lobby.
After clicking on "Create" which calls SteamMultiplayerPeer.create_lobby() and updates the lobby ID.
After clicking on "Leave" which calls SteamMultiplayerPeer.close() and clears the lobby ID.
After clicking on "Create" again. Notice that the lobby ID is still "None".
The error that is displayed in the terminal.
Desktop (please complete the following information):
OS: Microsoft Windows 10 Home
Version: 10.0.19045 Build 19045
Version of Godot:
Godot Engine v4.3.dev.custom_build.d00734053
Version of GodotSteam:
GodotSteam Multiplayer Peer 4.8 (Module) (Latest Version)
Additional context
I think the fix is very simple, just add a line to reset the lobby_state in the close method back to disconnected.
The text was updated successfully, but these errors were encountered:
Describe the bug
SteamMultiplayerPeer will complain that the user is still in a lobby even after calling close(). This prevents the user from joining another lobby and forces the creation of another SteamMultiplayerPeer object.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect the multiplayer peer to create a different lobby and connect the user to that one instead.
Screenshots
Initial state before joining a lobby.
After clicking on "Create" which calls SteamMultiplayerPeer.create_lobby() and updates the lobby ID.
After clicking on "Leave" which calls SteamMultiplayerPeer.close() and clears the lobby ID.
After clicking on "Create" again. Notice that the lobby ID is still "None".
The error that is displayed in the terminal.
Desktop (please complete the following information):
Version of Godot:
Godot Engine v4.3.dev.custom_build.d00734053
Version of GodotSteam:
GodotSteam Multiplayer Peer 4.8 (Module) (Latest Version)
Additional context
I think the fix is very simple, just add a line to reset the lobby_state in the close method back to disconnected.
The text was updated successfully, but these errors were encountered: