Closed UnknownNull closed 7 months ago
I don't think this is the right way to fix this, the player should be always connected
I don't think this is the right way to fix this, the player should be always connected
Thread: Main Error: Player is not connected File: pmsrc/src/player/Player Line: 607 Type: LogicException Backtrace:
I don't think this is the right way to fix this, the player should be always connected
With these changes, crashes sometimes occur to me due to the player not being connected and the execution of a part of the code related to the player.
error: https://github.com/Sergittos/BedWars/pull/32#issuecomment-1921318933
I don't think this is the right way to fix this, the player should be always connected
With these changes, crashes sometimes occur to me due to the player not being connected and the execution of a part of the code related to the player.
error: #32 (comment)
This happends when you use NetherGames fork of Pocketmine-MP.
I don't think this is the right way to fix this, the player should be always connected
With these changes, crashes sometimes occur to me due to the player not being connected and the execution of a part of the code related to the player. error: #32 (comment)
This happends when you use NetherGames fork of Pocketmine-MP.
Why? I really do not understand the reason.
I was also using pocketmine and faced the same error, but less...
I tested again with the original version of Pocketmine and this crash occurred again
This is not way to change/fix this, there's no need to cache the player class. We just need to replace Session->getPlayer() function returning value to Server->getPlayerExact(
Closed as I'm not able to reproduce this problem
This bug is created in special cases, for example, disconnection of the player if the code is continuing.