no the player.h is only refered to when player actually disconnects the Disconnect (e.g when player connects with second client as it has to "disconnect" him then "reconnect" him) function from protocol and connection is the one that refers to actual socket disconnection when players IP is 0.0.0.0 that you refer to.
you could technically make a function inside of player to detect the ip loss aswell but it would be a better option to sort it when the socket is disconnected.
C++:
if (isConnectionExpired()) {
// ProtocolGame::release() has been called at this point and the Connection object
// no longer exists, so we return to prevent leakage of the Player.
return;
}
ProtocolGame::release()
so probably in here somewhere you would need to reference player object last time before its released
try this:
C++:
void ProtocolGame::release()
{
//dispatcher thread
if (player && player->client == shared_from_this()) {
player->addStorageValue(45971, -1, false);
player->client.reset();
player->decrementReferenceCounter();
player = nullptr;
}
OutputMessagePool::getInstance().removeProtocolFromAutosend(shared_from_this());
Protocol::release();
}
then onLogin add check to check the storage value and see if it properly set to -1 before you set it to 1 aka logged in if thats what you have in login.lua
this should effectively set the storage before releasing the player pointer from the game.
just to point out even
if player logs out the storage
will set to -1 but it shouldnt be an issue since its a logout and not death right? you're implementing some form of death protection or something?
just make sure that line is before client reset, the decrease of referencecounter and removing the pointer to player object. if you put it after the engine will either crash or the storage wont set because of wrong player object being referenced after being removed.
just imagine you have a Paper that has all player information you want to add to that paper your storage before you put it back in file cabinet. if it does not work try changin the boolean to true I have not checked how the boolean operates but its something with player being inside of the game and not inside of game I just assumed false since player is technically not in the game but character might still be there if its non logout tile etc.
also in that case you have conflict if player does it on non logout zone he will be in game permanently with full death loss its something to think about you can add additional logic checks for that since player is referenced in protocol.
just had look at isLogin seems like its executed when player logs in? I see multiple references to that when sending magic effect so i assume thats the case here.
