Invisible Lightning Strikes & "Not the Master of this World" Issue (v1.3.0.5)

Grim Dawn Bug Reporting
1

Hello Dev Team!

I am a Grim Dawn content creator from Japan. For over two years, I have been continuously creating videos and live streaming Grim Dawn, and I’ve received great support from enthusiastic Japanese fans, especially since the launch of Fangs of Asterkarn.

I’m writing to report two bugs I’ve encountered in v1.3.0.5.

Bug 1: Invisible Lightning Strike / Hit Registration Issue

Regarding the fix mentioned in the v1.3.0.4 Hotfix release notes:

Fixed an issue where moving out of monster lightning strikes could still register as a hit (thanks Titan Quest!). This issue impacted the Fangs of Asterkarn Final Boss.

It appears this issue is still present in v1.3.0.5.

During a live stream playing on v1.3.0.5, I took fatal damage from an invisible Doom Bolt (or similar lightning strike) during the Belonath fight. Here is the timestamped link to the stream showing the exact moment:

https://www.youtube.com/live/4aPtpiTeCh4?si=AqkzGhagrQozl02P&t=4639

One of my viewers spent two hours testing this bug and managed to reproduce the exact same symptom in the same location. It seems there might still be an issue with this specific area/encounter.

Bug 2: “Not the Master of this World” & Dreads Not Spawning

I have 14 Level 100 characters. In v1.3.0.5, even when playing in Single Player or hosting a Multiplayer game, one specific character displays the message “Not the Master of World”.

20260803003138_1
20260803003138_11920×1080 356 KB

Additionally, despite playing in Ascendant Mode for a long time with this character, no Dreads have spawned at all. In v1.3.0.3, Dreads were spawning normally.

  • Note1: This character is the very first one I ever created. My other 13 characters can toggle the Remnants of Dread switch ON/OFF without any issues.

  • Note 2: Some of my viewers have reported experiencing the exact same issue on their end.

If it helps with your investigation, I can send you the save data for the affected character via direct message. Please let me know if you need it!

Thank you so much for all your hard work on FoA—I am thoroughly enjoying the expansion. Keep up the amazing work!

Piromusama Ch.

1 Like
2

We believe we found an edge case causing issue 1.

Please send me the save for issue 2.

3

Thank you for the quick response!
I have sent you the save file for the character experiencing Issue 2 via DM

1 Like
4

Not sure how, but you have the token credit for starting the quest, but no credit for the quest itself, which should not be possible.

However, the Dread is not disabled on that character. It is just unable to interact with the orb.

Your character will be unblocked in v1.3.0.6 though.

1 Like
5

Konnichiwa,Zantai-san

Thank you so much for taking the time to investigate this during your busy schedule! I deeply appreciate that it will be resolved in v1.3.0.6.

Just as a quick follow-up: I tried hunting enemies until nearly 10 Nemeses spawned, but unfortunately, no Dreads appeared at all—it effectively feels the same as having them sealed.

That said, I can still hunt Dreads in multiplayer by joining someone else’s game in the meantime, so I’m more than happy to wait for the v1.3.0.6 update!

Arigatou💜

6

Hi Zantai and the dev team,

I have a quick update regarding the Issue 2 bug I reported earlier.

When I defeated a Dread on a character that had normally completed the quest “A Dreadful Encounter”, the Remnants of Dread started displaying the message “Not the Master of this World” on that same character. Furthermore, “A Dreadful Encounter” completely vanished from my completed quest log.

20260806000950_1
20260806000950_11920×1080 318 KB

20260806001544_1
20260806001544_11920×1080 367 KB

I asked my viewers to check their logs, and they confirmed that normally both “The Dread” and “A Dreadful Encounter” should remain listed under the completed quests.

Additionally, after testing, the viewers who previously had normal characters ended up experiencing the exact same issue after defeating a Dread.

It seems possible that the flag for “The Dread” might be somehow overwriting “A Dreadful Encounter”.

I understand this is scheduled to be addressed in v1.3.0.6, but since it appears to be happening to multiple players upon defeating a Dread, we would really appreciate it if a fix could be released as soon as possible!

7

We cannot reproduce this. The steps you list are not enough, so there is another factor.

8

Regarding the Remnant of the Dread issue:

I was able to reproduce the issue in my own environment, so I did some testing.

Cause #1 (confirmed): outdated text mod

The first cause I was able to confirm was a mod that replaces resources\Text_XX.arc. The version I had installed was outdated and did not include sq_09b_dreaddisable.txt.

With that mod installed, I confirmed that A Dreadful Encounter was removed from the QuestList when the character approached the Remnant of the Dread in Devil’s Crossing.

In other words, if a character entered Ascendant in v1.3.0.5 or later while this kind of outdated mod was installed, A Dreadful Encounter can end up removed. After that, the Remnant of the Dread no longer accepts interaction.

In my case, this was a local setup issue caused by using an outdated mod, rather than a problem with the base game itself. Removing the mod afterward did not restore the already removed quest.

Cause #2 (rarer): Ultimate quest data first generated in Ascendant

There is also a second reproduction pattern.

This occurs when a character reaches level 100 on Elite or lower, then starts Ascendant without ever having played Ultimate. The key factor seems to be that Ultimate\quest.gdd is generated for the first time in Ascendant rather than in Ultimate.

If the QuestList is not available yet at the moment the Remnant of the Dread is added to the world and dreadDisableQuest() is called, GrantQuest() appears to fail, so A Dreadful Encounter never starts.

In this case, AREAH_DREADORB_SPAWNED is still recorded, but A Dreadful Encounter does not exist in the QuestList. As a result, the Remnant of the Dread exists but cannot be interacted with.

That said, I think this second case is likely very rare in normal play.

1 Like
9

We are resetting the quest for everybody next patch as a precaution, but we generally cannot prevent quest corruption due to installing hard mods like that.

I wish I had known mods were involved though, cause this issue made no sense and we redid a bunch of work to try to restore the quest state. But at least now we have confirmation it wasn’t because of a game error.

That is quite the edge case, but we’ll add an additional check to prevent that. Thanks.

2 Likes
10

Hello Zantai-san and the dev team,

Thank you so much for testing and investigating my save data.

It turns out that Cause #1 identified by meiha-san was indeed the issue on my end. I am extremely grateful to meiha-san for their thorough testing.

To clarify my setup: I had previously installed the Japanese rainbow font file in the wrong location, overwriting Text_Ja.arc inside the resources folder. Although I had already corrected the installation path to gdx3\resources back in v1.3.0.4 and verified game file integrity, the quest state on this character had apparently already been corrupted prior to that fix.

When I tested defeating a Dread afterwards (during my stream: https://www.youtube.com/live/i5guVH38YsY?si=GrBAzaTTvKx1WYtb ), the symptom remained because of that existing data corruption.

I am truly sorry for causing confusion and extra work for the team by having modified files involved in the character’s history.

I am deeply grateful that you are resetting the quest state for everyone in the next patch as a precaution. Thank you so much for your time, patience, and continued support!

1 Like