Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Exit to main menu, came back, re-did the quest and it worked. Not sure why it bugged to begin with.
Before the recent patch 0:20 (maybe even 25)--100% success rate [of *not* having the bug]. After the recent patch 3:3--0% success rate.
seems like a spawn issue, where either basilisk doesn't spawn in the world "proper" or the counter doesn't register it's time
either way, it can definitely happen without, seems like "waiting it out" by either spam aoeing until you hit something (in case it spawned underground i guess) or until the trigger finally registers (portal out and back or something, run around like a headless chicken) to pass time
-but since i've had the bug, without using GD internals, can definitely say GD Internals is not the sole cause of the issue at least
It happened to me a few times all w/o any mods. I can always resolve it though by just doing other stuff and coming back later and it'll be spawned.