Random disconnects

Same here.

Server issues being reported by people in the Chats as well.

Same here lost two T13 maps and all loot that I picked up in the maps as well.

Also having this issue. Losing everything I have picked up in the map as well upon reconnect. Should I even keep playing if I'm not able to complete a map?

Same here, lost 2 maps and my loots disappeared

Same here! tried 5 maps so far and every one DC;s at some point and rolls back all my progress and drops.

Purely anecdotal, but I wasn't being disconnected at all until I speccecd Unstable Energies in my Atlas Tree. Lost two maps 2/4 maps directly after turning it on.

Will update if it happens again with it off, but I ran at least 6+ maps without it, and never experienced a disconnect. Weird.

Shitty as hell that it eats the map + all the mods.

(nope, has nothing to do with it, disconnected the same way on next map)

server is fucked, please fix.

Same issue here, started mapping for first time today just ~30 minutes ago (played hours yesterday no issues), and 3 maps in a row I get full crash, then 2x disconnects in a row ~1 minute into the map. I'm doing all the standard verifying files, rolling back any driver/win updates in 12 hours, etc etc. But if the standard stuff doesn't fix it, it is absolutely unplayable it seems.

"

S0rada#0980 wrote:

Random disconnects during the mapping in last three maps. It looses map it self as well and rollbacks any progress which is not fun or cool, since we have only single attempt.

Only this entry is visible in client logs: 221560890 923444e [INFO Client 8156] Abnormal disconnect: An unexpected disconnection occurred. Internet connection is fine on my end.

I've had like 9 DCs in the last hour. Mostly in Breaches. Lost a JUICED 1100 Waypoint Citadel.

Somethings fucked.

It will be server side issue. It looks like any progress in map is "persisted" when you change instance. Until that it is in "transaction" state. When instance crashes (either docker container or the server it self) it rollbacks the entire transaction.

My assumption it works like this.

Open the map.
Enter the map - persist that user used map (take a snapshot of everything)
you are mapping, collecting loot.
Portal back to town - persist if map is completed and all the loot.

On each portal back (zone change) it persist changes or you can image it takes a snapshot of your inventory and stash tabs, exp etc.

in our cases.
Enter the map - persist that user used map
server or docker container crashes
we re login
it sees that map was opened but it missing "completed" state. And since we are in different seed, it treats like "failed" map. - Persist this state. Because map can't be in "started" state for ever, and cant open new map in that state as well.

I think from technical point of view this design / architecture is bound to fail, as it does.

Unplayable, plz fix ggg