Lord_Meshadieme

there are 8 server SE and DE regions, SE just came online a day ago while DE was on for a long time( you rpobably need to increase the ping limit). I do agree a changelog should be a slight priority, cause you know we are testers and we can't do it when we don't know what to test, but it matters not.it is experimental alpha after all.

Heres a big update on this bug, I managed to confirm one thing, IT IS NOT inventory or save related!!!! Heres why, i asked a friend to use my account and i used his, he never had the problem before and got 6 containers and it worked fine for him. While i've always had the problem after 4 or more containers + re connecting (the initial time I play is fine, or new spawns) the only time i get this is when i have already collected enough containers or spawn NEAR enough of them.and then i Login it happens. So when i used my friends account and collect enough containers, geuss what it happened again. So to summarise what do we know so far? - The containers definitely trigger the bug on a new synchronization (or connection) to the servers. - It is something in OUR network configuration / PC that is CAUSING the RARENESS of it. - It is NOT the saved CHARACTER AND/OR ITEM that gets bugged. - It is related to the VICINITY of the player, as some spawn where you MIGHT be near some containers (on a Player OR GROUND?) - Approximately 3-6 containers are required for this to occur, it probably varies on the configuration issue. - What happens is the connection with the server, is maintained but ONE-SIDED, thep layer can communicate to the server. - BUT the server tries and fails to communicate back OR the player fails to RECEIVE it. I am willing to help the developers pinpoint this issue personally, if they contact me. I hope you all put a bit more priority towards this issue. Regards.