Beau_Nearh
Portal
- Joined
- Jan 31, 2014
I'm not 100% what has happened so I'll try to explain it fully as this is a bulls*it bug. (Going to bullet point it)
>was combat tagged by a mob while I was having connection issues
>shortly after being tagged, my game froze for a second. I noticed that all mobs were standing still (this may be the point in which I was timed out from the server) and I could freely move around
>after about 30 seconds I was disconnected
>logged back into the server to see that I have died. However it wasn't allowing me to press re spawn.
>after going back to the title screen and re-connecting, I was then was able to re spawn at a grave yard
>after returning from the grave yard and looking within the area I died. I can not find any items or chests (this means the new death chest didn't actually work)
>I've tried relogging to see if it is just client side (there is a known minecraft bug where sometimes you can't see items that have been dropped) and I've still not been able to find the items.
I hope this covers it in enough detail for a possible fix to come out as I've lost a lot of good items. I will keep looking (I'll keep relogging every few minutes just incase the 5 minute despawn timer gets the items if they have in fact been dropped somewhere). I'll keep this up to date on if I manage to find anything.
Edit 1; it appears that the items I managed to keep after death (armor and the tool I was holding) has took a considerable amount of durability damage (a lot more than usual)
Edit 2; I've tried a series of tests to try and replicate what happened, these tests include;
>dieing from fall damage, then disconnecting rather than respawning
>let a mob kill me, then go back to title screen, relog then respawn
>hit a mob to gain a combat tag, let it hit me, then let it kill me. Then title screened it. Reconnected and respawned
>let a mob hit me, I hit the mob then disconnected
From doing these tests I have found that if you do indeed get a combat tag from a mob however you can freely disconnect without being killed after relogging (another bug maybe?). Regarding the tests I wasn't able to replicate what happened.
>was combat tagged by a mob while I was having connection issues
>shortly after being tagged, my game froze for a second. I noticed that all mobs were standing still (this may be the point in which I was timed out from the server) and I could freely move around
>after about 30 seconds I was disconnected
>logged back into the server to see that I have died. However it wasn't allowing me to press re spawn.
>after going back to the title screen and re-connecting, I was then was able to re spawn at a grave yard
>after returning from the grave yard and looking within the area I died. I can not find any items or chests (this means the new death chest didn't actually work)
>I've tried relogging to see if it is just client side (there is a known minecraft bug where sometimes you can't see items that have been dropped) and I've still not been able to find the items.
I hope this covers it in enough detail for a possible fix to come out as I've lost a lot of good items. I will keep looking (I'll keep relogging every few minutes just incase the 5 minute despawn timer gets the items if they have in fact been dropped somewhere). I'll keep this up to date on if I manage to find anything.
Edit 1; it appears that the items I managed to keep after death (armor and the tool I was holding) has took a considerable amount of durability damage (a lot more than usual)
Edit 2; I've tried a series of tests to try and replicate what happened, these tests include;
>dieing from fall damage, then disconnecting rather than respawning
>let a mob kill me, then go back to title screen, relog then respawn
>hit a mob to gain a combat tag, let it hit me, then let it kill me. Then title screened it. Reconnected and respawned
>let a mob hit me, I hit the mob then disconnected
From doing these tests I have found that if you do indeed get a combat tag from a mob however you can freely disconnect without being killed after relogging (another bug maybe?). Regarding the tests I wasn't able to replicate what happened.
Last edited: