Standard and Dawn of the Hunt - Atlas broken (SOLVED)

GGG see this situation from the totally wrong point.

This is NOT about THE FOG ON THE COMPLETED MAP.

First, it's COLLISION among multiple atlas map layouts.
Second, map completion event is not triggered after map completion. (thus, completion is not registered on database)


Users suffering from this issue have multiple atlas map layout data.

Old atlas map layout should have been wiped with 0.2.0 update, but it has not. This happens.
แก้ไขล่าสุดโดย JohnBour#5311 เมื่อ 22 เม.ย. 2025 01:14:55
+ 1 wait GGG fix
I just quit the game cuz of this dam bug. GOOD JOB GGG!!!
..............
Fix it as soon as possible!
..........
dont even bother to post or report the bug,,

i asked them by email,, kieran said "we are not able to provide technical support via email at this time"

this automatic replay email since patch 0.2 until now still not fix the problem..

they refered to post at forum .. same thing no answer,,,

ggg better stop throwing stupid patch or 90% bug patch ... we are not in hurry to play a new patch as long as not bug everywhere...

ive post this problem like 5-6 title ,, all of em no respons.. no wonder every youtuber leaving this game ,, sad...
请快点解决,玩不下去了,这怎么玩?
I have been hit by the same bug since the day of 0.2 "VISION" patch.

I myself also knew a bit of coding, the "bug" looks to me is a untested flawed design from scratch.

Well, obviously every player has their atlas progression stored on the server side in some sort of data format, and the data size grows along with the player atlas progression.

So the first group of people hit by the bugs are the players massively openned their atlas nodes/territories just like me.

what i could guess is, these players data exceeded some sort of server side resource limits which has been set for a single user, so when the user tries to open his/her altas, server side would render/parse the user data and create/restore the user's atlas map on the client side.

But if the data is too much to parse during the restoration/or exceeded the parsing time limits then the server will give player a completely un-played atlas as default to prevent the entire game client crash. (i.e all territories are covered by fog except the refugee base and few nodes around it).

And i noticed the resource assigned to parsing player's altas data was set dynamically? since once in a while we could somehow still load back our proper atlas progression. So i would guess the "bug" was caused by lacking server side computing hardware resource? (i.e CPU/Memory/IO)

I am guessing this happens on the standard first is becuz there are huge numbers of people has their atlas wildly openned, it might be ok when there is only 1 league happening, but with 0.2 "VISION" league, i would assume at least 50% of the hardware resource was allocated to "VISION" league? so the poorly left over 50% hardware resource if not less was not capable of dealing with these massive data from standard league?

But don't worry, if this is how the atlas was designed, this WILL hit the new league sooner or later, we prpbably will hear some new league player screams when enough league players have their atlas wildly openned

The new atlas is a disaster design IF what i have guessed was true. each player's data could grow to a huge data truck along with their atlas progression

Anyway, been guessed too much, just FIX THE DAM ATLAS, at least let us play
PLS FIX!

รายงานโพสต์

รายงานบัญชี:

ประเภทรายงาน

ข้อมูลเพิ่มเติม