BloodyGir

I have the same problem on a 317 RWG map updated to 324. The key exception in the logs is: 2023-06-29T20:08:43 1126.235 EXC Object reference not set to an instance of an object at QuestEventManager.QuestUnlockPOI (System.Int32 entityID, UnityEngine.Vector3 prefabPos) [0x0001e] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at Quest.HandleUnlockPOI (EntityPlayer player) [0x00038] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at QuestEventManager.HandlePlayerDisconnect (EntityPlayer player) [0x0001f] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ConnectionManager.DisconnectClient (ClientInfo _cInfo, System.Boolean _bShutdown, System.Boolean _clientDisconnect) [0x0010e] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ConnectionManager.Net_PlayerDisconnected (ClientInfo _cInfo) [0x00013] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at NetworkServerLiteNetLib.OnPlayerDisconnected (System.Int64 _peerConnectId) [0x00014] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at NetworkServerLiteNetLib+<>c__DisplayClass14_0.<StartServer>b__3 (System.Object _taskInfo) [0x00036] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ThreadManager.UpdateMainThreadTasks () [0x0006c] in <faea3a5b1cd24d60977fa28c6573de8f>:0 My hunch was the latest patch POI updates broke this call back. Maybe ID changes? Removing all existing quests will throw this exception again, but then the DisconnectClient method completes successfully on log out. I reset the trader's daily quests to be safe and was able to accept a new quest and log out without issue. Catch your exceptions in network resource code TFP!

I have the same problem on a 317 RWG map updated to 324. The key exception in the logs is: 2023-06-29T20:08:43 1126.235 EXC Object reference not set to an instance of an object at QuestEventManager.QuestUnlockPOI (System.Int32 entityID, UnityEngine.Vector3 prefabPos) [0x0001e] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at Quest.HandleUnlockPOI (EntityPlayer player) [0x00038] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at QuestEventManager.HandlePlayerDisconnect (EntityPlayer player) [0x0001f] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ConnectionManager.DisconnectClient (ClientInfo _cInfo, System.Boolean _bShutdown, System.Boolean _clientDisconnect) [0x0010e] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ConnectionManager.Net_PlayerDisconnected (ClientInfo _cInfo) [0x00013] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at NetworkServerLiteNetLib.OnPlayerDisconnected (System.Int64 _peerConnectId) [0x00014] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at NetworkServerLiteNetLib+<>c__DisplayClass14_0.<StartServer>b__3 (System.Object _taskInfo) [0x00036] in <faea3a5b1cd24d60977fa28c6573de8f>:0 at ThreadManager.UpdateMainThreadTasks () [0x0006c] in <faea3a5b1cd24d60977fa28c6573de8f>:0 My hunch was the latest patch POI updates broke this call back. Maybe ID changes? Removing all existing quests will throw this exception again, but then the DisconnectClient method completes successfully on log out. I reset the trader's daily quests to be safe and was able to accept a new quest and log out without issue. Catch your exceptions in network resource code TFP!