Players do not get disconnected when already logged in #27

New Issue

Exynox · 2024-06-02T22:56:09+03:00

Exynox commented

2024-06-02 22:56:09 +03:00

A player's connection might still be alive, even though the client was disconnected. In this case, and all other cases where players are already connected, they won't be disconnected when a re-log is attempted.

A player's connection might still be alive, even though the client was disconnected. In this case, and all other cases where players are already connected, they won't be disconnected when a re-log is attempted. ![image](/attachments/81ac23c3-eeab-4f12-8a07-9cdb43c3f418)

image.png

1.8 MiB

Exynox added this to the Ready for public testing milestone 2024-06-02 22:56:09 +03:00

Exynox added the

bug

label 2024-06-02 22:56:09 +03:00

Exynox commented

2024-11-16 21:59:33 +02:00

This only seems to happen in the Docker deploy environment. Might be due to the fact that there are multiple game cores running at the same time. Might also be related to #32.

Exynox commented

2024-11-17 06:24:58 +02:00

The bug seems to happen if the account is connected with a player in map c1 (ID 41). For example, if account is in map c3 (ID 43), the logout message is received and the player is disconnected.

We can see that metin2_map_c3 (ID 43) is handled by ch1_first, whereas metin2_map_c1 (ID 41) is handled by ch1_game2, so there definitely is a communication issue between the cores.

The bug seems to happen if the account is connected with a player in map c1 (ID 41). For example, if account is in map c3 (ID 43), the logout message is received and the player is disconnected. We can see that metin2_map_c3 (ID 43) is handled by ch1_first, whereas metin2_map_c1 (ID 41) is handled by ch1_game2, so there definitely is a communication issue between the cores.

Exynox commented

2024-11-17 09:20:51 +02:00

Duplicate of #32, fixed.

Exynox closed this issue

2024-11-17 09:20:51 +02:00

Sign in to join this conversation.